Most businesses have at least one mailbox that belongs to everybody and therefore to nobody. It might be info@, sales@ or accounts@. Mail arrives, three people glance at it, each assumes another will reply, and a customer waits four days for an answer that would have taken four minutes. A shared inbox agent is one of the simplest agents to put to work, because the job is clear: read each message, decide what it is, prepare what can be prepared, and put it in front of the right person.
What the agent actually does with each message
A good shared inbox agent does three jobs, in this order.
- Sorting. It reads the message and gives it a label from a short, fixed list: new enquiry, existing order, complaint, supplier, invoice, job application, spam, other. It also pulls out the useful facts: the sender’s name, an order number if there is one, the product mentioned, and whether the sender sounds upset.
- Drafting. For common message types it writes a reply draft, using your own past replies and your price list or policy documents as its source. The draft sits in the drafts folder. It does not go out.
- Routing. It assigns the message to a person or a folder based on rules you write: complaints to the customer service lead, invoices to accounts, applications to whoever handles hiring.
The result is that when a staff member opens the mailbox in the morning, the pile has already been split into their work and everyone else’s, and half of their replies are waiting to be checked rather than written.
Start with the labels, not the model
The quality of the whole system depends on the list of labels. Before any software is involved, sit down and look at the last two hundred messages in the shared inbox. Sort them by hand into piles. You will probably find that six or seven types cover nearly everything, and that one or two of them take most of the time.
Write each label down with a one-line definition and two real examples. “Complaint: the sender says something went wrong with an order or service and wants it fixed.” This short document becomes the agent’s instructions, and it is also useful for training new staff.
Keep an “other” label and make it respectable. When the agent is unsure, “other” is the correct answer. An agent that forces every message into a confident category will send a legal letter to the sales team sooner or later.
Drafting replies without putting words in your mouth
Drafts save the most time, and they carry the most risk. A few rules keep them safe:
- Drafts only, never sent. In the first version, every reply is written into the drafts folder and a person presses send. This is the rule that lets you sleep.
- Answer only from written sources. The agent should quote prices, delivery times and policies from documents you give it, not from what sounds reasonable. If the answer is not in the documents, the draft should say so to the staff member, not guess to the customer.
- Match your tone. Give it ten of your best past replies as examples. Many Sri Lankan businesses write a little more formally than the default style of AI tools, and customers notice the difference.
- Flag, do not soothe. For complaints, the draft should acknowledge the problem and say who will follow up. It should never offer a refund, a discount or an admission of fault. Those are decisions.
A useful habit is to have staff mark each draft as “sent as is”, “edited” or “rewritten”. After a month you will know exactly which message types the agent handles well and which it does not.
Routing rules and the cost of getting them wrong
Routing is where a shared inbox agent quietly pays for itself. Say a mailbox receives sixty messages a day and three people each spend twenty minutes every morning reading through the whole pile to find their own. That is an hour a day of reading, before anyone replies to anything. If the agent routes well, each person reads only their share.
Write routing rules as plain sentences a new employee could follow. “Anything mentioning an invoice, payment or statement goes to accounts.” “Anything from a courier company goes to dispatch.” Then add a safety net: any message the agent marks as urgent or angry is copied to a named manager as well as routed normally. A misrouted enquiry is a nuisance. A misrouted complaint that sits for a week is a lost customer.
Every routing decision should be logged with the label, the reason and the person it went to. When someone says “I never got that mail”, you can check in seconds.
Where it slips, and when not to bother
Be clear about the limits before you start.
- It struggles with long threads where the real question is buried in the fifth reply. Ask it to focus on the newest message and to summarise the thread separately.
- It can be fooled by tone. Polite anger, common in formal business mail, sometimes reads as a routine enquiry. The urgent-copy rule helps here.
- Attachments are a separate problem. Reading an invoice PDF properly is its own job and should be treated as one.
- Mixed-language messages, such as English with romanised Sinhala phrases, are handled unevenly. Test with your own real mail before trusting it.
If your shared mailbox receives ten messages a day and one person handles all of them, you do not need an agent. A few mail filters and saved reply templates will do the job for nothing. The agent earns its place when volume is high enough that sorting itself has become a task, or when several people share the box and messages fall between them.
If you want to see whether your own inbox is worth it, the automation payback calculator can turn your message counts and reading time into a rough monthly figure. Then take a week of real mail, sort it by hand into labels, and you will have both the business case and the agent’s first instructions.