In brief Email triage automation reads every message that arrives, sorts it into the categories your firm works in, routes it to the named owner and sends an honest holding reply within minutes. Where the answer already sits in your systems, it drafts a reply for the owner to approve. Urgent items come straight to the top, and anything it isn't confident about goes to a person instead of being guessed.
-
Define the categories and owners Eight to twelve categories that match how work really moves through the firm: new enquiry, existing client service, documents in, billing, urgent regulatory, junk. Each one has an owner and a target response time.
-
Classify and route continuously Every email is read and put in a category with a confidence level. Anything it isn't sure about goes to a person rather than being guessed. Routing updates the CRM and tells the owner.
-
Acknowledge fast, honestly A holding reply suited to the category goes out within minutes, promising only what your response times really deliver. It doesn't pretend to be a person, and no person has to write it.
-
Draft the response where the answer is knowable Standard requests get a drafted reply with the relevant details filled in, waiting for the owner's approval. New or sensitive items are routed with a short summary of the context.
-
Watch the misses Every week, look at misrouted emails, missed urgent items and complaints about tone. Each miss adjusts a rule or a prompt, and the error rate is managed like a new starter's probation.
A shared inbox is where response-time promises fall apart. Everything arrives mixed
together, urgent emails hide among routine ones, and whoever is busiest does the worst
job of sorting. That’s why triage is the usual first agent, and why it’s the worked
example on the Kick-starter page: the actions are limited,
it’s easy to measure, and the relief is immediate.
| The build at a glance | |
|---|
| Best first candidate when | A shared inbox sets your response times |
| Human gate | All substantive replies; low-confidence to a person |
| Surfaces immediately | Urgent-regulatory and distressed-client buckets |
| Measured by | Time-to-acknowledge; misroute rate |
| Typical shape | The Kick-starter worked example |
Building categories from real email
The categories have to match the email you really get, not the email you’d like to
get. Build them from a fortnight of real traffic, and let the low-confidence queue take
the unclear cases instead of forcing a wrong guess.
The honest acknowledgement
A holding reply that arrives in two minutes and states your real response time does
more for a client than a fake “personal” reply or a real one three days later. It’s
the cheapest part of the build and the part clients notice first.
Drafted replies
Drafting is the second win. For requests whose answers already sit in your systems,
the owner opens a prepared reply with the details filled in and approves it in
seconds. The triage pattern and the
first-agent playbook cover the
governance around it.
