There is an email sitting in your shared inbox right now that two people are replying to and a third has already forgotten about. Nobody is sure who picked it up. Nobody wants to ask in case it looks like they dropped it. The customer, meanwhile, is waiting. This is not a technology problem. It is a process problem. And it is fixable without buying a single new platform.
The “Is Someone on This?” Problem
Every business with more than a handful of staff hits this wall eventually. You set up a shared mailbox (info@, sales@, support@) so the team can handle enquiries together. It works brilliantly for about a month. Then it quietly falls apart.
The symptoms are always the same. Someone opens an email, starts working on a reply, gets pulled into a meeting, and forgets to finish it. Meanwhile, a colleague sees the same email sitting there unanswered and starts drafting their own response. The customer either gets two different answers or none at all.
The deeper problem is uncertainty. When you open a shared inbox and see 15 unread messages, you have no way of knowing which ones a colleague is already handling. So you either duplicate effort or assume someone else has it covered. Both options cost you.
This is not about lazy staff or poor communication. It is a structural problem. Shared inboxes were designed for reading, not for workflow. They have no concept of ownership, status, or progress. You are using a reading tool to run a process, and the process is suffering for it.
What This Actually Costs You
The obvious cost is the occasional embarrassing double reply or the customer who chases because nobody got back to them. Those are visible. They sting, but you deal with them.
The hidden cost is bigger. It is the ten minutes every person spends scanning the inbox each morning trying to work out what needs attention. It is the Slack messages asking “are you on this one?” It is the mental overhead of wondering whether something has been handled.
Think about how much time your team spends in email each day. Not writing thoughtful replies to customers, but scanning, sorting, and checking whether someone else is already handling something. In a team of ten, even 15 minutes of wasted triage time per person adds up to more than 12 hours a week. That is a day and a half of productive work, gone to a problem that has a straightforward fix.
This is not a fringe problem. A sales automation startup hit a £1 billion valuation this month because investors know how much revenue businesses lose to disorganised enquiry handling. The market for fixing this is enormous precisely because the problem is everywhere.
Then there is the customer experience. A prospect who emails your sales address and waits two days for a reply is not going to tell you they are frustrated. They are going to email your competitor instead. You will never see the enquiry you lost because you will never know it was there to lose.
You Do Not Need Another Platform
The instinct when this problem surfaces is to buy software. Helpdesk tools like Zendesk, Freshdesk, and HubSpot Service Hub all promise to fix shared inbox chaos. And they can, if you have the budget, the time to configure them, and the patience to get your team to actually use them.
But for a business with 15 to 30 people, a full helpdesk platform is often overkill. You are paying for ticket management, knowledge bases, customer portals, and reporting dashboards when all you actually need is for every enquiry to be logged, assigned, and tracked.
The bigger issue is flexibility. Off-the-shelf tools give you their workflow, not yours. You adapt your process to fit the software. With automation built around your existing setup, you get exactly what you need and nothing you do not. You can add capabilities as your requirements change instead of paying for features you will never touch.
This is not an argument against helpdesk software in every situation. If you are running a 200-person support operation, you need a dedicated platform. But if you are a 20-person business where enquiries come in through one or two email addresses and you need them handled reliably, automation gives you a faster, cheaper, more tailored solution.
What Automated Enquiry Triage Actually Looks Like
The concept is simpler than it sounds. When an email arrives at your shared address, an automated workflow picks it up and does the thinking that your team currently does manually.
Step one: log it. Every inbound enquiry gets recorded automatically. Who sent it, when it arrived, what it is about. No more relying on someone remembering to update a spreadsheet or forward it to the right person.
Step two: categorise it. The workflow reads the email content and determines what type of enquiry it is. Sales question, support request, partnership proposal, job application. This can be rule-based (keywords and patterns) or use a language model for more nuanced understanding. Either way, the categorisation happens in seconds without human involvement.
Step three: assign it. Based on the category, the enquiry gets routed to the right person or team. Sales enquiries go to your sales lead. Support requests go to whoever is on the rota that day. No more guessing, no more “is someone on this?”
Step four: draft a response. This is where it gets genuinely useful. The workflow can generate a draft reply based on the enquiry type and your previous responses, then place it in the assignee’s drafts folder ready for review. The person responsible opens their drafts, reads the suggested response, makes any adjustments, and hits send. If the enquiry needs clarification before a proper response, the draft can flag specific questions to ask the customer.
Step five: track it. Every enquiry has a status. Received, assigned, draft ready, sent, resolved. If something sits unactioned for more than a set period, a reminder fires. Nothing falls through the cracks because the system does not forget.
The whole process takes an email from “sitting in a shared inbox that six people can see but nobody owns” to “assigned to a specific person with a draft response ready for review” in under a minute.
Start With Drafts, Not Sends
If the idea of automation drafting customer replies makes you nervous, good. That is the right instinct. You should not be sending automated responses to customers without a human reviewing them first, at least not until you have built confidence in the system.
The minimum viable version of this workflow is deliberately conservative. It logs the enquiry, categorises it, assigns it, and puts a draft response in someone’s outbox. That is it. A human reviews every outgoing message before it reaches the customer.
This approach has two advantages. First, it removes all the wasted time on triage (working out what the email is about, who should handle it, what the response should say) while keeping a human in the loop for quality control. Second, it gives you data. After a few weeks, you can see how often the draft responses needed editing. If 90% go out unchanged, you know the system is reliable enough to consider sending certain categories automatically. If the drafts need heavy editing, you refine the workflow.
You can also build in specific logic for tricky situations. If the workflow detects an angry customer, it can flag the email for senior attention rather than drafting a standard response. If it spots a high-value sales enquiry, it can alert the business owner directly. The rules are yours to set because the automation is yours to shape.
Your Next Step
If your team is spending time every morning working out who is handling what in a shared inbox, the process is costing you more than you think. Not just in wasted time, but in missed opportunities and inconsistent customer experience.
Automated enquiry triage is one of the fastest process improvements a growing business can make. It does not require replacing your email provider, retraining your team, or signing up to an enterprise platform. It works with what you already have.
If you want to explore what this would look like for your business, email [email protected]. No pitch, just a conversation about where your enquiries are getting stuck.