Open your inbox. Somewhere in there, right now, is an order, a complaint and an invoice, all dressed as ordinary emails, all waiting for a human to notice them and type their contents into the right system.
Reading, sorting, extracting and summarising: this is exactly the drudgery AI now handles well, and it's where we point clients who ask "what should we actually do with AI?" Not a moonshot. The inbox. But the difference between useful and dangerous is entirely in the controls, so here's the practical version.
"Use AI for our email" is a mess waiting to be automated. "Classify incoming messages as order, invoice, complaint or other, and extract the reference number" is a task you can test, measure and trust. Narrow is not timid. Narrow is how confidence gets built. And if part of the job follows fixed rules (an email from the courier always goes to dispatch), keep that deterministic and boring; save the AI for the genuinely fuzzy reading. We've written about drawing that line.
An AI drafting replies should work from your approved wording, your prices, your policies, not whatever the internet taught it. Grounding outputs in controlled information is the single biggest difference between an assistant and a liability. The same goes for what flows in: personal and confidential information deserves to be minimised, protected and processed under terms you've actually read.
Let the clear cases move quickly and the uncertain ones queue for a person. But confidence is the machine's opinion of itself, so treat it as routing, never as approval. Anything a customer sees, anything money depends on, gets human eyes first. And design that review experience properly: original document alongside the AI's reading, one glance, one decision. A reviewer who has to open three systems to check one invoice will stop checking by Thursday.
Always preserve the source document and the decision history: what the AI extracted, who approved it, what changed. When a number looks odd in month three, that trail turns an argument into a two-minute lookup. It's the same discipline as any good system, applied to a new kind of worker.
The question isn't "how clever is the model?" It's: are invoices processed faster, are fewer things mis-filed, did the team get hours back, including the review time? Wire the whole thing into the actual workflow (the extracted order lands in the order system, not in a demo dashboard) and judge it in business terms. That's the standard our AI integration work is built to, and it's why the wins stick.
AI as a controlled assistant, doing the reading while your people do the deciding, is available to ordinary businesses today, at sensible cost. If your inbox is the bottleneck, that's a very fixable problem.