How Much Does a Missed Call Actually Cost Your Restaurant?

Every restaurant owner has a gut feeling that missed calls cost them money. Fewer have actually run the numbers. The exercise is worth doing, because the answer usually surprises people — not because it's dramatic, but because it's a bigger, steadier drain than it feels like night to night.

This isn't going to cite a study. There isn't a reliable industry-wide number for "how many calls does the average restaurant miss," because it depends entirely on your hours, your staffing, and how busy your dining room gets during service. Instead, here's a conservative way to estimate it for your restaurant, using your own numbers.

Why phone calls get missed in the first place

During service, the person closest to the phone is usually a host, server, or manager who is also seating guests, running food, or handling a line at the door. The phone competes with everything happening in the room, and the room usually wins — reasonably, since the guests in front of you matter more in the moment than the one on hold.

• Peak dinner rush, when the phone rings most and staff are busiest
• Understaffed shifts, especially early or late in the week
• Off-hours: after close, before open, on your closed day
• Kitchen-adjacent stations where no one is near a handset
• Multiple lines ringing at once with only one person free to answer

None of this is a staffing failure — it's just what happens when a phone call and a walk-in guest need the same person at the same time.

A conservative math model, step by step

Rather than assume a number, plug in your own. The formula is simple:

Missed calls per week × conversion rate × average check value × party size = estimated weekly revenue at risk

Step 1 — Estimate missed calls per week

Look at your phone system or POS if it logs call volume. If you don't have that, ask whoever answers the phone for a rough estimate of how many rings go unanswered during a typical dinner rush, then multiply by the number of service periods in a week. A single mid-size restaurant open for lunch and dinner, six days a week, missing even 3-4 calls per service isn't unusual — that's roughly 20-25 missed calls a week. Use your own estimate; the point of this exercise is to be honest, not alarming.

Step 2 — Estimate what fraction of those calls were reservation attempts

Not every missed call is a lost booking — some are suppliers, delivery drivers, or wrong numbers. A conservative assumption is that half of missed calls during service hours are guests trying to book or ask if you have room. If you genuinely don't know, start at 50% and adjust once you start tracking it.

Step 3 — Estimate how many of those callers try somewhere else instead

This is the step people skip, and it matters. A caller who doesn't get an answer doesn't necessarily wait and call back — many will simply call the next restaurant on their list, especially on a Friday night. Assume conservatively that only half of unanswered reservation calls convert to a lost booking (the other half call back, walk in anyway, or weren't serious in the first place).

Step 4 — Multiply by average check value and party size

Take your average check per person and multiply by your average party size for a phone reservation (often larger than a walk-in — think birthday dinners and group bookings).

A worked example

Here's an illustrative calculation — not a claim about any specific restaurant, just an example of how the math comes together:

Over a year, that's a little over $42,000 in an illustrative example — using deliberately conservative assumptions at every step. Change any input and the number moves; that's the point of doing the math with your own numbers instead of trusting a generic statistic.

What this number does and doesn't tell you

This estimate ignores repeat-visit value entirely — a first-time guest who couldn't get through and booked elsewhere is also a guest who never becomes a regular. It also doesn't account for word of mouth, negative or positive. On the other hand, it also doesn't account for calls that would have been declined anyway due to being fully booked, so it can cut both ways. Treat it as a directional estimate, not a precise figure.

What actually closes the gap

The fix isn't necessarily hiring a dedicated phone person — for most restaurants that doesn't pencil out against the revenue at risk. The practical options are:

• Add staff whose job is answering the phone during peak hours — expensive, and still leaves gaps outside those hours.
• Route to voicemail — free, but most callers hang up rather than leave a message and wait for a callback.
• Use a human answering service — covers the gap but adds a per-call or monthly cost and the answering staff usually can't see your live table availability.
• Use an AI phone host — answers every call immediately, checks real availability, and books the table without pulling a staff member off the floor. This is the approach Reserva takes: 24/7 coverage, real-time table checks, and SMS confirmations via Twilio, without adding headcount.

Whichever direction you go, running your own version of the math above is the useful part — it turns "we probably miss some calls" into a number you can actually weigh against the cost of fixing it.