The real cost of a missed customer request

What does one missed request actually cost?

When a prospective customer asks a question and hears nothing back, the visible loss is that one job, one booking, one appointment. The invisible losses are larger and they compound.

Think through what a single answered enquiry normally turns into:

Add the softer costs: the staff hour spent apologising when the person chases you a week later, the discount you offer to smooth it over, and the quiet erosion of a reputation you spent years building. None of it appears on a spreadsheet, and all of it is real.

• The lifetime value of a customer who would have returned for years, not once.
• The five-star review you never got — and perhaps the frustrated one you did.
• The referral that went to a competitor who simply replied faster.
• The staff time spent apologising, chasing context and rebuilding goodwill.

Misses are structural, not a staff failure

The instinct is to blame busyness or a careless employee. But watch how requests actually arrive: an email to a shared inbox, a WhatsApp to someone’s personal phone, a voicemail, a message through the website, a comment made in passing at the front desk.

Each channel is someone’s part-time responsibility and no channel is anyone’s whole job. Nothing confirms receipt, nothing assigns an owner, and nothing flags a request that has gone quiet. In that structure, misses are not an accident — they are the expected output.

The problem gets worse outside office hours, when even your most conscientious people are asleep. Hiring more diligent staff does not fix a system with no memory.

What changes when every request has an owner and a deadline?

The fix is structural too. In ReQuest DESK, every channel — email, web portal, chat widget, WhatsApp, even transcribed voice — feeds one classifier, so a request is a request regardless of where it arrived.

Each one is logged with a named owner and timestamps, classified against your service catalog with a confidence score, and given a committed resolution time. Because every request needs an owner, “I thought you had it” stops being possible; a stalled case surfaces before the customer has to chase.

Routine requests can resolve automatically from your published knowledge, while anything unusual queues for a person with full context attached. You can see how the whole flow fits together in how it works.

Start by counting what you can see

Before changing anything, run a one-week audit. Count every enquiry across every channel, note who answered it and when, and mark the ones that were never answered at all. Most owners who do this find the last column is not empty.

Then ask what each of those unanswered rows would have been worth over a few years of repeat business and referrals. The number does not need to be precise to be persuasive — it only needs to be honest.