Your missed calls are a bigger leak than your website

You know your form conversion rate to two decimal places. You have opinions about the button colour. You have probably A/B tested the headline.

Now: how many people rang you last month and hung up before anyone answered?

Most businesses cannot answer that. The ones that can are usually unpleasantly surprised.

Why it stays invisible

A form abandonment leaves a trace — a page view with no submit. A missed call leaves almost nothing you look at. It is a row in a carrier log, in a different system, that nobody has a reason to open. Meanwhile the caller has moved on to whoever answered.

The asymmetry is the point: someone who rings has higher intent than someone who fills in a form. They wanted to talk to a person, now. And that is the channel you are measuring least.

Find the number this week

You do not need a project. Your telephony provider already has this:

1. Pull inbound calls for the last 30 days.
2. Split into answered and not answered.
3. Of the unanswered, split by whether the same number tried again within 24 hours.

The ones who did not try again are the leak. Multiply by whatever you think a conversation is worth and you have the size of the problem in the only unit anyone acts on.

Then split by hour. Almost everyone finds the same two clusters: lunchtime, and the hour after close. Both are fixable and neither needs more staff.

The four buckets, and what each needs

After hours

Nobody was ever going to answer. The current experience is a ring-out, so anything coherent is an improvement. The obvious first place for an AI agent — with a narrow scope.

Everyone was busy

Overflow. The call was worth answering and there was nobody free. An agent that takes the details and books a callback converts a lost call into a scheduled one.

It rang and nobody picked up

Usually a routing problem, not a capacity one — it rang a desk that is not staffed, or one person's phone rather than a group. Fix the flow before you buy anything.

They hung up in the menu

Your IVR is asking people to categorise a problem they have not finished describing. Why a menu cannot resolve anything.

Ring back fast, and mean it

If you do nothing else: call back missed numbers the same day, from the same number they rang.

Most teams do this ad hoc, which means they do it when it is quiet — the opposite of when it is needed. Make it automatic: a missed call creates a callback task with an owner and a due time, and it shows up in someone's list rather than in a log.

The recovery rate on a same-day callback is far higher than most people expect, and it costs nothing but the discipline of a queue that exists.

A missed call you ring back within the hour is not a missed call. It is a slightly delayed one, and customers barely notice the difference.

What to measure afterwards

• Unanswered calls, weekly, split by hour. The headline number.
• Never-called-back. The number that should be zero and rarely is.
• Time to callback. Median, not average — one bad Friday will hide behind a mean.
• Repeat attempts. Someone ringing three times is telling you something the first two attempts did not.

The order to fix it in

1. Measure it. A week, honestly. Nothing else until this is done.
2. Fix routing. Free, and often removes a third of the problem.
3. Make callbacks a queue with owners, not a good intention.
4. Put an agent on the two buckets nobody was ever going to answer.

Steps one to three cost nothing and usually recover more than step four. Do them first — a platform you buy before you have measured is a platform you cannot evaluate. When you get to step four, bring the numbers.