Two things make a shared inbox faster: not retyping the same answer, and being able to talk to your team without talking to the customer.
Canned responses
Save any reply you send often as a canned response in Settings → Inbox. In the composer, insert one instead of retyping it, then edit before sending — a saved reply is a starting point, not a script.
Canned responses are shared across the workspace, so a good answer written once is available to everyone.
Shown with our demo workspace.
Internal notes
Every conversation has an Internal note tab beside the reply box. Notes are visible only to your team: they are never delivered to the customer and never returned by the public widget endpoints.
Use notes for the context that should not be in the reply — what you have already tried, what you suspect, what a colleague needs to know before they pick this up.
Notes versus replies
The distinction is enforced server-side, not just in the interface. A note cannot become a message by accident.
Attachments
In chat, both sides can attach files. A customer's attachments appear on their message in the inbox, and files you attach appear in their chat window. Attachments are uploaded directly to storage and shown as chips on the message rather than clogging the thread. Email conversations are text only for now: attachments aren't imported from or sent with emails.
The copilot
If you would rather start from a draft than a blank box, the copilot writes one grounded in your published articles, with the sources it used. It is a draft — you send it, edit it, or ignore it.
