Someone wanted to give you money on Tuesday evening. They filled in your form, or emailed, or messaged the page, or rang and left a voicemail.
Nobody answered until Thursday. By Thursday they had already spoken to someone else.
You will never know that happened. There is no report anywhere in your business that lists the customers you lost by being slow, which is exactly why this problem survives in businesses that are otherwise run tightly.
Inquiries arrive in more places than anyone thinks
Write down every route by which a stranger can reach you. Be thorough and slightly uncomfortable about it.
- The contact form on the site
- The general email address
- Someone’s individual work email, because that is who they met once
- The phone, in hours
- The phone, out of hours, into a voicemail box someone checks eventually
- Messages on whichever social pages you keep
- A message to a staff member’s personal phone, because they gave a customer their number to be helpful
- Walk-ins and people asking at a counter
- Whichever directory or marketplace you are listed on, with its own inbox nobody has logged into since setup
Most businesses find seven or eight routes. Then ask which of those has a person definitely responsible for it, by name, today. The gap between those two lists is your leak.
Why nobody notices
Every other problem in a business announces itself. A late job gets a phone call. A wrong invoice gets a complaint. A broken system gets shouted about.
A missed inquiry does nothing. The person quietly goes elsewhere and does not tell you why, and your inbox looks exactly the same as it would on a good week.
This is the same failure that makes silent problems so expensive everywhere else: absence produces no signal. Nothing arrives to tell you that nothing arrived. Which means the only way to see it is to go looking on purpose.
The other half: the ones that were answered badly
The inquiries you did answer have their own losses, and they are more measurable.
Someone replies to say they have received it and will get back. Someone else has to work out what the customer actually wants. A third person turns out to be the one who handles jobs like that. By the time a real answer goes out, three people have touched it and a day has gone.
None of that is bad service. It is a routing problem being solved by hand, every single time, from scratch. Routing is the most automatable thing in your entire business and it is almost always done by a human reading and forwarding.
What five years on a service desk taught me about this
I started on service desks in 2006 and spent years there before moving on, then ran a support team at Pantheon later. The queue was the job, so here is what I would want to know if I were you.
The thing that made a queue healthy was never how fast people typed. It was whether every arriving thing landed in one place with a name attached to it within minutes. Where that was true, a busy day was tiring and fine. Where it was not, work fell through gaps that nobody could later reconstruct — and the reconstruction attempt was always worse than the original loss, because now you have also lost the trust.
The uncomfortable part: on the desks where things went missing, everybody was working hard. Effort was never the variable. The variable was whether the arrival had an owner before a human decided it did.
Find your own leak this week
- List every route in, including the awkward ones — personal phones, old marketplace inboxes, the address on a business card printed in 2019.
- For each, name the person responsible. If you cannot name one, that route has no owner and is where things go.
- Send yourself a test inquiry down every route. All of them, on a normal working day, and see what happens and how long it takes. This takes an hour and it is the most informative hour you will spend this month.
- Do it again at 7pm on a Friday. The difference between the two results is your out-of-hours exposure.
- Count last month’s inquiries against last month’s quotes. If you cannot produce the first number at all, that is the finding.
If every route has an owner, every test came back within the hour, and you can produce both counts — genuinely, you are fine. Go and count a different flow, and do not let anyone sell you a fix for this one.
What to do next
Send yourself a test inquiry down every route this week, once in hours and once on a Friday evening. The results are frequently uncomfortable and always specific.
If routing is where yours falls over, the comparison with a chatbot covers what happens after an inquiry is qualified — which is where most of the loss actually is.
If you want the whole picture instead of one workflow: tell us what’s still manual. You get a map of every point where your business stops and waits for a person, what that costs you in hours, and which of those an engine would take over first. Free, yours to keep, and useful even if you never hire us — including on the days the honest answer is that you should not build anything yet.
Common questions
Would an auto-reply solve most of this?
It solves the customer’s anxiety and none of your loss, which is worth being clear-eyed about. An automatic acknowledgement buys goodwill and time, and it is cheap, so send one. What it does not do is get the inquiry to the right person or make sure anyone acts on it. If the auto-reply is the whole system, you have automated the reassurance and left the work where it was.
How fast do we actually need to respond?
Ask your own lost customers rather than a benchmark. Call five people who enquired and did not buy, and ask when they decided and who they went with. Their answers give you the real window, and it varies hugely — an emergency trade call is a different race from a considered purchase. Measuring your own is worth more than any published average.
We’re a small team. Isn’t a shared inbox enough?
It can be, if two things are true: every route feeds into it, and every arriving item gets an owner rather than sitting in a pile everyone can see and nobody holds. Shared inboxes fail in a specific way — the diffusion of responsibility means a message read by four people can be actioned by none. If yours has assignment and you use it, that is a real system.
What about the inquiries we never see because we’re not found at all?
That is a genuinely different problem and it is not one we work on — how customers find you is marketing, and Anito builds engines for how the work gets done once it arrives. Worth separating the two before you spend money, because they have completely different fixes and it is easy to buy one while suffering from the other.