Lunch rush: 7 in 10 calls ring out unanswered (and what it costs)

Thursday, 1:12 pm. Lunch rush.

Your floor manager crosses the room with plates on his arm. The host stand is empty, the pass is sending, the phone rings. Nobody takes it.

For the next 90 minutes, 7 in 10 calls will ring out. Nobody will notice. That is the problem: this loss makes no noise.

Why your phone goes silent during the rush

The lunch rush runs 90 to 120 minutes. Your team is on the floor. The phone rings at the one moment nobody is free.

It is not about how seriously they take it. It is about how many hands are left.

Result: 70% of a restaurant's missed calls fall during service. And 18% of phone bookings are lost for want of an immediate reply. The caller doesn't ring back. They book next door.

• 30% of calls left unanswered at peak hours (Orange study)
• 18% of bookings lost with no immediate reply
• 56% of operators lose more than 20 bookings a month

The hidden cost of your lunch service

No sliders needed. Three numbers: your average spend, your 22 lunch services in the month, the share of calls nobody takes during the rush.

On a basis of 70% unanswered, the estimated loss lands around £5,929 a month. That is an estimate, not your number: yours, your phone provider hands over.

Does the figure land? Let's see what Heep recovers at your venue in 30 days. Estimate your recoverable volume

What a message-based recovery changes during service

1:15 pm, nothing changed. The phone rings four times. Your floor manager looks up: table 7 wants its bottle, table 12 wants the bill. He lets it ring. The caller dials the place next door.

1:15 pm, with forwarding in place. Nobody takes the call, and the caller gets a message within seconds. He answers in writing. He's offered 1:45 pm or 2:00 pm, the table goes in, the confirmation goes out.

Your team never looked up. That is all anyone is asking of them.

One hour of service, minute by minute

Case study · 90-cover brasserie, Lyon

21 calls in 60 minutes, 19 recovered by message, 9 bookings made

A Thursday, 12:30 to 1:30 pm. Before: 4 calls taken out of 21. After: 19 conversations picked back up in writing. Nobody on the floor touched a phone.

• +15 calls handled
• 9 bookings confirmed
• £268 revenue recovered, 60 min

Across the month, the same brasserie recovered ~£5,300 on the lunch slot alone. See also the no-show cost calculator.

How Heep catches the calls you miss

1. Call forwarding, set up in the first days.

   You keep your number. We set up forwarding on busy or no answer. No new handset.

2. A message, in the guest's language.

   Heep knows your menu, your hours, your cancellation policy, your table constraints. It replies in whatever language the guest writes in.

3. The booking written into your software.

   Zenchef, SevenRooms, TheFork: the table goes to the right service, with no double entry on the floor.

4. The thread and its summary.

   Every conversation lands in your inbox with the exchange, the detected intent, the action taken. You see what was asked without chasing anyone.

Going further: how Heep handles email enquiries in under a minute, 24/7.

Why not just use voicemail

Voicemail doesn't convert: fewer than 5% of callers leave a message, and half of those have booked elsewhere before you listen.

It doesn't make the booking. You call back at 4 pm, the table is gone next door. Pure loss.

And it can't tell a group-of-12 enquiry worth £350 from an allergen question that takes thirty seconds. Those two don't deserve the same treatment.

Tomorrow, at the end of lunch, ask your floor manager how many times the phone rang with nobody free to go. Do it for five days. You won't need an estimate after that.