What missed phone calls really cost your restaurant

Ask any restaurant owner whether they’re missing phone calls and you’ll usually get a shrug. “Probably a few.” The honest answer, once you look at the call logs, is almost always more than you think — and the cost is bigger than it feels in the moment.

A ringing phone during service doesn’t feel like a problem. It feels like background noise while you’re plating mains and seating a walk-in. But each of those rings is a person trying to give you money, and in a city with as much choice as Sydney, they rarely ring twice.

Let’s put a number on it.

The simple maths of a missed call

You don’t need fancy analytics. You need four figures you already roughly know:

• Missed calls per week. Pull your phone records for a normal week. Count the inbound calls that went unanswered or to voicemail during open hours.
• How many were trying to book. Not every missed call is a reservation — some are suppliers, wrong numbers, “are you open?”. A conservative rule of thumb is that half of missed inbound calls during service are would-be bookings.
• Average covers per booking. Two? Four?
• Average spend per cover. Your own number, after the obvious deductions.

Now multiply:

Missed calls × 50% × covers per booking × spend per cover × 52 weeks

Even a modest venue tends to be startled by the result. Miss ten callable bookings a week, at four covers and $55 a head, and you’re looking at well over $100,000 a year walking out the door — not because the food was wrong or the reviews were bad, but because nobody could get to the phone.

The point isn’t the exact figure. It’s that the number is never small, and it’s invisible on every report you currently look at.

Why missed calls hide so well

Missed bookings don’t show up in your POS. There’s no line item for “table we never got.” The revenue simply never arrives, so it never gets counted — which is exactly why the problem persists for years in otherwise well-run venues.

Three patterns make it worse:

1. The peaks are the worst time to answer. Calls spike at exactly the moments your staff are flat out — the lunch rush, the 7pm seating, Friday night. The busier you are, the more you miss.
2. Voicemail doesn’t convert. Diners deciding where to eat tonight want an answer now. A callback two hours later, after the kitchen’s closed, lands too late.
3. They don’t complain — they just leave. A caller who can’t reach you doesn’t leave a one-star review. They quietly book the place down the road, and you never know it happened.

What actually fixes it

There are only a few honest options, and most have a catch:

• Hire someone to manage the phone. Effective, but expensive and impractical for the dinner rush — and you still don’t cover the hours you’re closed.
• Push everyone to online booking. Helps, but a large share of diners — especially older guests, large groups, and anyone with a special request — still pick up the phone. Online-only leaves money on the table.
• Let an AI host answer every call. This is the option that’s become genuinely good in the last couple of years. A voice agent picks up on the first ring, every time, 24/7, checks your real availability, and writes the booking straight to your diary.

That last option is what we built VoxTable to do. Bella answers in a warm Australian voice, handles the back-and-forth of finding a table, and never sleeps — so the 9pm Sunday call and the Tuesday-lunch rush both get the same fast, friendly answer.

Do the audit this week

Before you change anything, just measure. Pull one week of call records, run the maths above, and you’ll have a real number instead of a shrug. Once you can see the cost, the decision tends to make itself.

If you’d rather skip the spreadsheet, we’re happy to walk through it with you — and if you want to hear what answering every call actually sounds like, give us a ring. The irony of a phone company that always picks up is not lost on us.

Next read: AI phone answering for Sydney restaurants — a plain-English guide.