What happens between a client emailing you and you pressing send

Clients do not agree on a channel. One emails, one sends a WhatsApp at eleven at night, one fills in the form on your site. All three land in the same place, converted into one common shape before anything reads them.

Not everything is a message. A weekly schedule, a matter changing to retained, or one workflow finishing can all start work the same way. See which channels are live today.

A real inbox is not a queue of tidy client enquiries. It is client enquiries mixed with spam, PR pitches, recruiters, invoices, a question about parking, and someone who emailed the wrong firm. No list of rules survives that, which is why the first thing to read a message is a model rather than a filter.

Triage is given the message and its thread, whether the sender matches a case you already act on, what is attached, your firm's practice profile, and the catalogue of agents you have switched on — each with a description of what it is for. It picks from that catalogue and nothing else.

It gives a reason for every choice, in a sentence a lawyer can disagree with. Those reasons are kept.

Triage does not start anything. It hands back a decision, and Yura checks every named agent against the ones you have actually enabled before dispatching a single run.

That separation is deliberate. An agent that could start other agents on its own say-so would be a hole in the audit trail — the chain would exist only inside a model's output, and nothing afterwards could be attributed to anything. Order is fixed too: document checks always run before the intake reply, because the reply needs to mention what the checks found.

Each agent reads what it needs — the matter, the checklist, the documents themselves — and produces a list of intended actions. Draft this reply, with this text. File this passport into this client's folder under this name. Update this row to this value.

This is where the work is done and where it stops. Nothing has been sent, filed, or written to your systems yet.

The plan arrives in one place with everything it intends to do. You read it, change the wording, approve the parts you want and reject the rest. Only approved actions execute, and each one is recorded — what ran, on whose authority, against which system, with what result.

Approval is per action type and it is yours to set. Filing a document into a folder is low-stakes and most firms let it run on its own within a few weeks. Sending an email to a client is not, and most never do. Corrections you make to a draft are kept and fed back, so the next one starts closer to your voice.