Messages & communication history
LiveInternal threads for the team, client threads the client reads in the portal, and one history of every channel.
- ✓Internal threads visible to their members only
- ✓Client threads readable by the whole firm and by the client's contact through the portal
- ✓Portal access follows the live client share — a revoked share closes the thread
- ✓Text only; never written or sent by AI
What it is.
Messages has two kinds of thread. An internal thread belongs to its members and nobody else can open it. A client thread is the firm's correspondence with a client: every user in the organisation can read it, and the client's contact reaches it through the client portal while a live share covers that client and matter. Revoke the share and the thread closes on the contact's next request.
Messages are text, written by people — nothing is sent by the AI. Communication History is a single newest-first view across messages, in-app notifications, meetings, portal activity, WhatsApp and agent email, filterable by matter or client, and it says which channels a filter could not reach. A notification shows as delivered or read, never as "sent" when only scheduled.
Three steps.
End to end.
Internal with named colleagues, or a client thread tied to a client and, optionally, a matter.
New messages notify the other members in-app. A client contact sees the thread at their next portal sign-in — they are not emailed.
Communication History merges every channel for a matter or a client, newest first.
What you get.
- ✓Internal threads visible to their members only
- ✓Client threads readable by the whole firm and by the client's contact through the portal
- ✓Portal access follows the live client share — a revoked share closes the thread
- ✓Text only; never written or sent by AI
- ✓Audit rows name ids and counts, never a subject or a body, and land on the matter timeline
- ✓Communication History across messages, notifications, meetings, portal events, WhatsApp and agent email
Quick answers.
No. The client sees the thread when they next sign in to the portal.
No — messages are text. A client sends a document through the portal's evidence request instead.
More in Clients & Matters.
A client is a record with contacts, not a name typed on a matter — and duplicates merge without losing anything.
Share a matter, a workflow, a document or a draft with the client; they sign in with a one-time link, upload evidence, answer questions and approve drafts.
Build an intake form, publish it on a public link, and every submission becomes a triaged intake request.