How much is your business losing to missed calls and no-shows?

The model is only as good as the numbers you put into it. Here is how to get a measured figure rather than an impression.

1. Open your phone’s call log and filter to the last 30 days. On most Android handsets, missed and rejected calls are already a separate tab. On a business landline, check whether the provider portal or itemised bill includes call records.
2. Count missed calls, not total calls. A missed call is one that rang out, hit a busy tone, or reached voicemail. Exclude your own outgoing calls and anyone in your contacts, because those are usually staff and suppliers rather than customers.
3. Split them by hour. Mark which ones arrived while you were open and which arrived outside your staffed hours. This split matters more than the total, because after-hours calls are the ones nobody is ever going to call back.
4. Remove the obvious repeats. The same number ringing four times in six minutes is one frustrated person, not four enquiries. Count it once.
5. Ring a sample of them back. Ask what they wanted, whether they still needed it, and whether they booked elsewhere. The share that would have bought is the purchase percentage to enter above.

That last step changes the estimate more than any generic benchmark. If most callers booked elsewhere, enter that measured share. If most were price-shopping and never intended to book, use a much lower percentage.

The pre-filled values are examples, not research findings or industry benchmarks. The calculator exposes each one so you can replace it with a number from your own records.

Missed-enquiry purchase percentage. This is the share of missed callers who would actually have purchased. A callback sample is stronger evidence than a generic online conversion statistic because it reflects your offer, location, price, and caller mix.

No-show percentage. Divide missed appointments by all booked appointments over the same period. Keep this separate from missed calls: answering more calls does not by itself reduce no-shows.

Staff cost per hour. Divide the relevant monthly employment cost by paid working hours. This line represents the cost of time spent on repetitive phone queries; it is not automatically cash you can recover.

The calculator stops before recovery. To evaluate a fix, measure a new 30-day period, calculate the real change in each component, and then subtract every cost of that fix. Do not treat the scenario total as money a product will save.

The business-type rows are arithmetic examples, not measurements or benchmarks. Every row assumes that 20% of missed callers would have purchased; replace that percentage and every other input with your own data.

Each row is calls/day × 30 × miss rate × ticket × 20%. The table shows how strongly ticket size and purchase likelihood change the result; it does not say that any business actually loses these amounts.

A single monthly rupee figure hides the fact that missed calls have four quite different causes, and a fix that solves one does nothing for the others. Before you buy anything, work out which of these is actually yours — the hour-by-hour split from the counting exercise above usually makes it obvious.

1. Nobody was there. The call arrived outside your staffed hours — evenings, Sundays, festivals, the two hours the desk is unmanned at lunch. This is usually the largest bucket and the most under-counted, because these callers rarely try twice and never leave voicemail. Forwarding to a second handset does nothing here, since the second handset is also off. What fixes it is something that answers when nobody is there at all: an after-hours answering setup, or accepting the loss and pricing it in.

2. Everyone was busy. The call arrived during your peak, when the one person at the desk was already on another line or with a customer in front of them. This bucket clusters tightly — you will see it in the log as three or four missed calls inside twenty minutes, usually at the same time each day. The cheap fix is a second handset or a rota change at that specific hour. The structural fix is something that can hold more than one conversation at a time, since a queue only drains as fast as a human frees up.

3. The caller gave up on the menu. If you run a phone menu, some share of callers hang up during it rather than after it. These are invisible in a missed-call count because the call was technically answered — by the menu. If your log shows very few missed calls but your enquiry volume feels low, this is the likely explanation, and the honest comparison of menu versus conversation is in AI voice agent vs IVR.

4. The caller could not be understood, or could not understand you. A caller comfortable in Telugu, Tamil, Marathi or Bengali who reaches a desk operating in English will often end the call quickly and politely, and it will look in your log like a short answered call rather than a lost one. This bucket is invisible to every metric on this page. The only way to find it is to listen to a few short calls or ask staff how often it happens.

Buckets one and two are what an always-on answering setup is genuinely good at. Bucket three is a configuration decision you can make today. Bucket four is a language question rather than a phone question. Spending money on the wrong bucket is the most common way this calculator leads people astray.

Work down this list in order. The first three cost nothing and fix a surprising share of the leak, and we would rather you tried them before paying anyone — us included.

1. Put your actual hours on your Google Business Profile. A large share of “are you open?” calls disappear when the answer is already on the listing that brought them to you.
2. Put your prices, or a price range, on your website. Price-shopping calls are the easiest to eliminate and the least valuable to answer.
3. Turn on call forwarding to a second handset. If two people can pick up instead of one, the busy-tone share drops immediately at zero cost.
4. Send a WhatsApp reminder the day before every appointment. This addresses the no-show line of the calculator rather than the missed-call line, and it is often the larger number.
5. Take a small deposit on high-value bookings. Even ₹100 changes no-show behaviour more than any reminder.
6. Only then consider an AI receptionist. It earns its keep on the calls the steps above cannot reach: simultaneous callers, after-hours enquiries, and callers speaking a language your staff does not.

If steps one to five close the gap, you have your answer and it cost you nothing. We would rather tell you that than sell you an agent you did not need — the detail on where an AI agent genuinely does and does not pay for itself is in is an AI receptionist worth it.

Any positive inputs can produce a positive scenario total. That does not prove there is a problem worth paying to solve, so compare each component with actual records.

If you miss fewer than about three or four calls a week and someone is nearly always at the desk, you do not have a phone problem — you have a normal business, and the money is leaking somewhere else. If your average ticket is small, recovering a handful of calls a month will not cover the cost of any paid fix. And if your calls are overwhelmingly existing customers rather than new enquiries, the “they booked with a competitor” assumption does not apply to most of them, so the real loss is a fraction of what the model shows.

A good test is to run a low, middle, and high scenario, then compare the low scenario with the complete annual cost of a proposed fix. If it does not clear that bar, close the tab. Nothing on this page is worth buying on the strength of a slider.

Whatever you change, measure the same four things you measured before you changed it, over the same length of window. Most people never do this and end up arguing from impressions.

• Missed calls per week — from the same call log, filtered the same way. This should fall first and fastest.
• Answered-within-30-seconds share — speed matters more than total answer rate, because a caller who waits does not stay. The reasoning is in speed to lead.
• Bookings made outside staffed hours — if this is still zero after a month, whatever you bought is not covering evenings and Sundays.
• No-show rate — track it separately from missed calls. Reminders and deposits move it; answering the phone does not.

Give any change a full month before judging it, and compare like-for-like weeks — a festival week or an exam week will distort a fortnight’s data badly. If you want the definition and the wider context of the metric itself, see missed call alert.