How Much Revenue Is Your Restaurant Losing from Missed Calls?
The number exists. It is sitting in your call logs, your average booking value and your peak hour data. This article shows you exactly how to calculate it, and what to do once you have it.
Every missed call to your restaurant has a value. Not an approximate value. Not a ballpark figure. A specific number, calculable in under five minutes from data you already have access to.
Most operators know, in the way you know something without ever having counted it, that missed calls are costing them money. This article moves that knowledge from instinct to arithmetic. By the time you finish reading, you will have a weekly figure, a monthly figure and an annual figure, specific to your restaurant.
Once you have the number, the business case for solving the problem becomes straightforward. The question is no longer "should we do something about this?" It is "how quickly can we start?"
Step 1 · Run your calculation
The calculator uses four variables, all available from your existing data. Fill in your own numbers, or use the defaults if you don't have the data to hand.
| Variable | Default | How to find it |
|---|---|---|
| A · Weekly inbound call volume | your log | Check your phone system's call log for the last 30 days and divide by 4. No log? Count manually for one full week including evenings. |
| B · Missed call rate (peak hours) | 25-35% | The proportion of calls unanswered during service. Default to 30% if unknown, the industry average for full-service restaurants. |
| C · Booking conversion rate | 70% | Of callers who want to book, what percentage actually books? Industry standard is 65-75%. Use 70% if unknown. |
| D · Average booking value | from POS | Average covers per table × average spend per cover. Example: 2.4 covers × £42 = £101. Use your trailing 90-day average. |
× missed call rate (25-40%)
× booking conversion (70%)
× average booking value
= weekly revenue lost to unanswered calls
These are conservative estimates. Actual peak-hour miss rates are typically 30-40%, and the weekly figure × 52 gives a number most operators find uncomfortable to look at the first time. Prefer to skip the maths? Use our interactive ROI calculator.
Step 2 · See the numbers across restaurant types
If you don't yet have your own data, this benchmark table shows pre-calculated estimates for five common profiles. Find the row closest to your operation and use it as a baseline.
| Restaurant type | Calls/wk | Miss % | Conv % | Avg booking | Est. annual loss |
|---|---|---|---|---|---|
| Small café / wine bar | 40 | 28% | 65% | £38 | £14,350 |
| Independent (40-60 covers) | 80 | 24% | 70% | £90 | £62,900 |
| City-centre, full service | 120 | 30% | 72% | £130 | £175,200 |
| Fine dining / destination | 60 | 20% | 78% | £250 | £121,700 |
| Restaurant group (3 sites) | 300 | 28% | 70% | £90 | £294,800 |
Based on UK market figures. Multiply by roughly 1.1 for euro equivalents. All figures assume a 25-30% miss rate and 65-72% booking conversion.
Step 3 · Understand what your number represents
The figures above measure only the direct revenue lost, the bookings that would have converted if the caller had reached you. They do not include:
Lifetime customer value. A new customer who can't reach you and books a competitor doesn't just cost you one booking, they cost you every future visit, typically 5-8 per year over 3-5 years. Our full analysis of missed call costs shows this multiplier can be 15-20× the value of the original booking.
Reputational impact. Callers who reach voicemail or a ring-out don't always move on quietly. The words "called twice, nobody answered" appear in one-star reviews across every market, visible to every future customer who searches your name.
Competitive displacement. Your missed call is a competitor's answered call. The restaurant three streets away is benefiting from your unanswered phone right now.
Step 4 · Project forward three years
The annual figure is large. The three-year figure makes the urgency undeniable. If your operation continues as-is, here is what the direct revenue loss compounds to over 36 months.
| Restaurant type | Year 1 | Year 2 | 3-year total |
|---|---|---|---|
| Independent restaurant | £62,900 | £125,800 | £188,700 |
| City-centre restaurant | £175,200 | £350,400 | £525,600 |
| Restaurant group (3 sites) | £294,800 | £589,600 | £884,400 |
Step 5 · Calculate your recovery potential
The table above shows what you are losing. This shows what you could recover, based on VoiceHelden's average call resolution rate of 73-90% across restaurant clients.
| Restaurant type | Annual at risk | Recoverable (90%) | Conservative (75%) |
|---|---|---|---|
| Independent restaurant | £62,900 | £56,610 | £47,175 - £56,610 |
| City-centre restaurant | £175,200 | £157,680 | £131,400 - £157,680 |
| Restaurant group (3 sites) | £294,800 | £265,320 | £221,100 - £265,320 |
"These recovery figures are not projections. They reflect the actual call resolution rates of VoiceHelden restaurant clients across the UK, Netherlands, Belgium and the US. The investment required to achieve them is a fraction of the revenue recovered."
What to do with your number
Put it in front of the right person. If you are the owner, that person is you. If you are a manager, this number is your business case for investment. A weekly revenue loss figure is more persuasive than any general argument about "improving the phone experience."
Compare it to the cost of solving it. Divide your annual revenue loss by 12 and compare it to the monthly cost of AI call handling. In virtually every restaurant scenario, the comparison is not close.
Set a decision deadline. Every week without a solution is another line on the loss column. The calculation you ran is not a one-time number, it recurs, every service, until the underlying cause is addressed.
The number you calculated is not a worst-case estimate. It is a conservative baseline, derived from industry-standard miss rates and typical booking values. Your actual figure may be higher. The restaurants that have already addressed this did so because someone sat down, ran the calculation, and decided the number was too large to leave on the table for another service.
VoiceHelden is built to recover it.
By answering every call your restaurant receives, automatically, 24/7. See how much of that annual figure you could recover in a free 15-minute demo.
.png)