Reads
connects to the mailboxes you already run. Google Workspace, Microsoft 365, SES relay. No migration.
AI Triage Bot
Every email in your shared inbox, understood and sent to the right place.
AI Triage Bot reads incoming mail, works out what each message is and what it concerns, then does whatever you've told it to do — route it, reply to it, or hold it for a person.
2. Demo
See it working
A live configuration for a property management group — 38 buildings, two languages, one inbox. The same engine is configured differently for every client.
3. The problem
Shared inboxes arrive in the wrong order
info@, orders@, support@, claims@, ap@ — everything lands in one place, sorted by arrival time. Customer requests, supplier invoices, regulatory notices, quote requests, automated noise.
Someone opens each message and makes the same three decisions hundreds of times a week: what is this, what does it concern, who handles it.
That decision is the work. It's also where things slip.
info@what is this
orders@what does it concern
support@who handles it
claims@what is this
ap@who handles it
4. What it does
Four steps, on every message
Understands
intent, sender type, language, urgency, and the account, site, order or project it concerns. Each with a confidence score.
Decides
applies your rules to work out what should happen next.
Acts
routes, replies, requests missing information, or holds for a person. You choose which, and when.
5. You set how much it does on its own
From read-only to fully automated, per rule
The system can run anywhere on that range, and different message types can sit at different points:
Watch only
classify and label, change nothing else. Useful for the first two weeks.
Stage for approval
compose the forward, address it, and hold it in a queue until a person clicks approve. Full record of what was approved, sent and rejected.
Route automatically
send straight to the right desk when confidence is above a threshold you set, and stage the rest.
Reply to the sender
acknowledge receipt, or answer directly from an approved template, in the language they wrote in.
Chase what's missing
when a request arrives without the unit number, PO, policy number or whatever your process requires, ask the sender for it before anything gets dispatched.
Start conservative, watch it work, and open it up where it earns trust.
6. Configured to your operation, not ours
Your categories, your desks, your exceptions
Intents, sender types, destinations and thresholds are all configuration. So are the exceptions — the ones your team currently keeps in its head.
An identical request about three different sites can route three different ways: to the regional service desk, to that desk plus ops because there's no on-site coordinator, or straight to one manager who owns their division outright.
Two ways to change any of it, neither requiring a developer:
- Rules — deterministic keyword and sender conditions. Same result every time.
- Plain-English instructions — written into the system to correct or guide how it classifies. One sentence, no ticket, no release.
And a simulator that shows where any message would land before a real one arrives.
7. Under the hood
What's already built
Multilingual
Language detected per message, templates maintained per language
Confidence scoring
Every classification and routing decision carries one
Priority scoring
0–100 on content, not arrival time
Approval queue
Full audit trail of approved, sent and rejected
Reply templates
Variable substitution, usage tracking
Ask your inbox
Natural-language questions across your mail
Multi-tenant
Every record carries its organization; every query filters on it
8. Where it fits
If your inbox has more than three possible destinations, this is worth automating
Distribution and manufacturingLogisticsField serviceInsurance and claimsHealthcare administrationProfessional servicesProperty management
Different mail, same problem: high volume, several possible owners, and a real cost when a message reaches the wrong one.
9. Close
Start with two weeks on your own inbox
We connect a copy of your shared mailbox, configure your categories and desks, and run it in watch-only mode. Nothing sends. You review what it decided and tell us where it's wrong.
At the end you'll know your own numbers — how often it's right, and how much time the routing was costing you.