crank.
Client requests

Ask once. Keep the answer in context.

Send a clear request for the document or information your team needs, then follow the reply without losing the client and project context.

Try Crank
A client request and reply with a file Two interlocking message bubbles, one containing a paperclip and the other a document and a received check mark.
A real request

“Can you send the August bank statement?”

Choose the client and contact. Say exactly what you need, add a due date, and assign someone on your team to follow it through.

What happens next
  1. The request goes to the client They receive a link to the request page.
  2. They reply and attach the file The response stays in the request conversation.
  3. Your team sees the reply The shared inbox shows what needs an answer.
  4. Reminders keep the request visible Choose when to follow up on an open request.
One thread

Goodbye to the mystery attachment.

When a file arrives as part of a request reply, your team can see who sent it, which client it belongs to and why they sent it.

Crank requests are conversations with attachments and follow-up. You can also schedule repeat requests for information you need from a client each month or quarter.

See how requests fit the monthly work →

Try one client request.

Pick a real item your firm needs and follow the response where the work happens.

Try Crank