Notes

AI Email Triage for a Shared Business Inbox

What is AI email triage?

AI email triage reads every message that arrives in a shared inbox, works out what it is and how urgent it is, sends it to the right person, and drafts a reply where a reply is routine. A person reads the draft and presses send. Nothing leaves the business without someone approving it.

The shared inbox is the front door of most small businesses. info@, admin@, accounts@. A new enquiry sits under a supplier invoice, which sits under a complaint, which sits under three newsletters and a job application. Everyone can see it, so everyone assumes someone else has it. The enquiry that should have been answered in an hour gets answered on Thursday.

Triage fixes the sorting. Approval gates keep the judgement where it belongs.

How does it decide what each email is?

It reads the whole message the way a sharp receptionist would, sender, subject, body, attachments and thread history, and assigns it a category, an intent and a priority, with a confidence attached to each.

The categories are yours, not a vendor's. For a trades business they might be new enquiry, existing job, quote acceptance, supplier invoice, complaint, and everything else. For a professional firm they might be new matter, client document, billing query, and so on. Natural language processing means it does not need keywords; "the tap you fixed is dripping again" is an existing job and a mild complaint, even though neither word appears.

Sentiment matters too. An angry customer and a curious one can ask the same question, and only one of them should wait until tomorrow.

Where should emails be routed?

To the person or queue that will act on them, using the same rules your best staff member already follows in their head, written down.

Misrouted email is the main failure mode. When the build is not confident, it should say so and drop the message into a "needs a human" queue rather than guess. A misroute caught on day one is a fix to the rules. A misroute nobody notices is a lost customer.

Can AI draft replies safely?

Yes, if every draft waits for a person, and if the drafts are built from your real answers rather than from the open internet.

Most of what lands in a shared inbox has been answered before. Opening hours, service areas, how to book, what to send for a quote, where an invoice is. The build drafts a reply using your knowledge base and past replies, in your tone, and leaves it sitting ready. The approver reads it, edits if needed, and sends. One click, most of the work done.

Draft only, never auto-send, is our default for anything customer facing. Where that gate sits, and how you earn the right to move it, is the subject of human in the loop AI.

What about privacy and the data in your inbox?

Treat inbox data as the personal information it is: know where it is processed and stored, who can see it, and how long it is kept.

A shared inbox holds names, phone numbers, addresses, and sometimes health, financial or employment details. Any tool that reads it is handling personal information, and the Australian Privacy Principles published by the OAIC are the right starting reference. Whether they apply to your business, and what they require of you, is a question for your adviser, not a blog post. Our builds keep access scoped to the inboxes you nominate, and the keys stay with you.

Triage also has a security upside. A build that reads every email can flag the invoice with changed bank details or the link that does not match the sender, which the Australian Cyber Security Centre lists among the most common attacks on small business. Flag, never act.

How do you know triage is working?

Measure response time, misroutes and hours spent sorting, before and after, and judge it on those numbers.

First response time on new enquiries is the headline. The number of emails that landed with the wrong person is the quality check. The hours a week someone spends reading and forwarding is the cost. Write all three down before the build starts. After thirty days the verdict is one page, numbers against target, and a clear answer on whether to keep it.

Watch the drafts too. Track how often approvers edit them and what they change. Rising edits mean the knowledge base needs work. Falling edits mean the drafts are earning trust.

Does this replace a help desk?

No. If you already run a help desk with tickets and service level agreements, triage sits in front of it and feeds it cleaner work.

Plenty of small businesses never needed a help desk; they need the shared inbox to stop being a pile. For businesses with a real support function, AI for customer support covers the wider picture.

Start with one inbox

Pick the busiest shared address, list the six or so kinds of email it gets, and name who should handle each. That is the brief. If missed enquiries are the real pain, never miss a lead is the shape of that work. When you want to watch your own inbox sorted on your own data, get in touch.

Keep reading