Write a request like an email, track it like a folder
Write a request
Your message becomes a point-by-point list
You write as usual. Except your client doesn't get a long message: they get a clear list, point by point, with a due date. And you see what's done and what's missing.
- As simple as writing an email
- Each point tracked until it is answered
- Your usual messages ready as templates
Replaces: Long emails · “Did you see my email?”
Your client knows what to do, and you see where they stand
A long email follows none of its questions
A long email asks for three things at once and tracks none of them. Your client skims it, answers the last question, forgets the other two, and you are the one re-reading the thread to work out what is missing.
Here you write the same message, but each thing you need from your client becomes a request in its own right, with its recipient, its status and, if you want, its deadline. Your client gets what is expected of them, point by point.
Write as usual, ask point by point
You write plain text, and links become clickable. To ask for something, you add a request from the "Add" button or by typing / in the message. The types are grouped by intent:
- Ask: an answer, documents, a choice, steps to tick off, an approval, information to fill in
- Plan: an appointment, a dated milestone, a place
One post can hold up to ten of them, of different types. Each lives its own life: its status changes when it is completed, and its reminders stop at that moment.
Each request is set as you write:
- The recipient: you name a person, or leave the request to the other side. One person is enough to complete it, except for a sign-off, which each person gives for themselves.
- The deadline: optional, it triggers the automatic reminders (two days before the due date, on the day, the day after, then seven days later).
- Who reads it: everyone, or only the people you choose. An internal note stays invisible to clients, and a confidential post is read only by the team and the participants it names.
If you have already typed your list into the message, "Turn the message into…" converts it into a request: the first line becomes the title, the dashed lines become the documents or the options. The draft saves itself, per folder and per device. Recurring messages are kept as templates.
What your client sees
They open their link, enter the code sent by email on a new device, and land on what is expected of them, with no account to create and no app to install. They work through each request in its own card: filing documents, picking a slot, approving, replying. They can also send you requests of their own.
In practice
Building and renovation. One message about the revised quote: the PDF attached, a sign-off addressed to both homeowners, a document request with a deadline, an appointment proposed on site. The client sees four distinct things waiting, and you see which one is missing.
Law and accounting firms. The document request names each document expected, and an internal note tells a colleague that the client has already ruled out an option, without the client reading it. For a decision to make, the choice replaces the question lost in the middle of a paragraph.
What it does not do
The text stays plain, with no rich formatting. A post holds at most ten requests. After ten minutes, or as soon as someone has answered, a request can no longer be edited: you cancel it (the trace stays) or replace it with a new one. A sign-off is a simple, dated, named approval, with no value as a qualified electronic signature.
Related reading
- The folder thread, where these requests appear and get answered
- Document requests, for collecting documents
- Folder templates, so you do not rewrite the usual requests
Your next folder, with nothing lost along the way
Not the right time?
Get the link to this page by email and come back whenever you like.
By sending, you will receive one e-mail with this link — your address is not kept.