What handling customer enquiries is actually costing your business

Every enquiry that lands in your inbox — email, a web form, a message through the site — needs the same three things before it's dealt with: someone has to read it, work out what it's actually asking, and decide whether it needs a reply now, a reply later, or a person. That sorting happens before any reply gets written, and it's the part that quietly eats a working day without ever showing up as its own task.

The inbox nobody owns full-time

Most small businesses don't have someone whose job is "read the inbox." It's whoever gets to it first, between the other things they're meant to be doing — the owner between calls, the office manager between invoices, whoever's desk is nearest the screen when the notification pings. That works fine when three enquiries come in a day. It works a lot less well on a Monday morning after a weekend, when twelve have piled up and half of them are asking the same two or three questions.

The problem isn't any single enquiry. A question about pricing, stock, or whether you cover a particular job takes thirty seconds to answer once you know the answer. The problem is that every enquiry gets read, mentally triaged, and actioned from scratch, by whoever happens to pick it up — and the business doesn't get faster at this over time, because every inbox session starts cold.

Where the time actually goes

Reading and sorting an enquiry takes longer than answering it. Before a reply gets typed, someone has already decided: is this routine, does it need a quote, does it need someone who knows the job, is it a complaint that needs careful handling. That judgement call, repeated across every message, is the real cost — and it's invisible on a timesheet because nobody logs "read the inbox and worked out what's urgent" as a line item.

The knock-on cost is the enquiries that don't get a judgement call at all. The straightforward ones — stock, hours, lead times — sit in the same queue as the complicated ones, and the simple questions that should take seconds to answer end up waiting until someone has a quiet half hour, which on a busy week might be Thursday. A prospect who asked a simple question on Monday and hears nothing until Thursday has often already asked somebody else.

What automating the sorting looks like

The dooco enquiry-triage Pattern reads every enquiry as it arrives, works out what kind of question it is, and has a reply drafted and waiting — in your business's own register, using your actual prices, stock, and service details — before anyone opens the inbox. The routine, repeating questions get an answer ready to send immediately. Anything that doesn't fit a recognised pattern — a complaint, a bespoke request, anything that needs judgement — gets flagged for a person, with nothing sent on your behalf.

The Proof for this one is dooco's own operations: this is the same system that has been sorting and drafting replies to dooco's own inbound enquiries since July 2026. It isn't a pitch for something untested — it's running on the inbox this business actually uses.

What it doesn't do

It doesn't decide pricing exceptions, read a tense email and know to pick up the phone instead, or handle anything where getting it slightly wrong costs more than getting it slow. Those stay with a person, and the system is built to recognise when an enquiry is one of them rather than guess.

What it clears is the larger, duller category: the enquiries that are genuinely routine and were only ever waiting on someone having a spare ten minutes. That's most of what arrives on an average day.

Is this worth building

Look at the enquiries your business answered last week. If most of them were variations on the same handful of questions, the sorting step is pure overhead — work that has to happen but adds nothing of its own. If every enquiry needs real judgement and background context, the case is weaker.

If your inbox looks like the first case, the enquiry-triage Pattern is built for exactly this. Read how it works at /services/enquiry-triage.