One thread
per client.

A client can put up to five photos on one message, ten megabytes each. They arrive at full size in the thread, not as a link to somewhere you have to go and find.

Open one full screen, or file it against one of that client's open requests without leaving the conversation. Photos are stored privately and served through signed links, so a thread cannot be read by anyone who guesses the address.

A message that is only photos shows as "Photo" in your inbox rather than as an empty row, so the list stays readable when someone sends photos without a caption.

Schedule a message from the conversation menu. It is queued as a job and goes out on the minute you chose, in the timezone you chose, whether or not you have the app open. Scheduled messages are text only for now. The scheduled message guide covers timing, editing and cancelling a message before it sends.

Anything you send also emails the client a nudge, unless you turn that off for the send with the switch in the composer. The nudge is capped at one per client per request every three minutes, so a run of short messages does not become a run of emails.

You get two green ticks when they have read it. Read receipts run one way on purpose: your clients are never told when you read theirs. See how client conversations work for the full messaging guide.