The Saturday night call log: 287 calls, 91 unanswered (and €2,730 lost)
Inside one Saturday-night service at a Paris bistro. 287 calls, 91 missed, €2,730 in revenue gone in five hours. The real cost of the restaurant phone — and how to plug it.
6 pm. First service. The phone rings, and nobody can take it.
That Saturday, I have the log in front of me. Between 6 pm and 11 pm, this Paris bistro took 287 calls. It left 91 unanswered. This is not a badly run floor. It is a full one.
I spend my evenings on the phone with teams living exactly that. Here is their Saturday, hour by hour, and what it costs.
Why one call in three goes unanswered
The dining room is packed. The host runs between kitchen, bar and the front door. The phone rings four times, then trips to voicemail.
It's not negligence. Two hands, three tables, one call.
Between 5 pm and 8 pm, the average restaurant misses 32% of inbound calls. That's peak hour: mise en place, first walk-ins, the whole crew on the floor. The phone rings at the exact moment it is worth the most.
Worse: 85% of callers who don't get through never call back. They don't wait. They open Google Maps and ring the next venue.
A missed call is never just an ignored ring. It's an empty table. A takeaway order gone elsewhere. An allergy question left hanging.
The real cost: €2,730 in one evening
We did the sums together on the Sunday morning, on the corner of the pass. Paris bistro, Saturday 19 April, five hours of service.
- 91 missed calls (of 287 inbound)
- €30.72 average ticket FR (source: Fiducial 2025)
- €2,730 potential revenue lost (in one evening)
The maths: 91 missed calls × 30% booking conversion × 3.2 average covers × €30.72 = €2,685.
Scale that to a full month: 22 evening services × €2,730 = €60,060 that never came in. At an 8% net margin, that's €4,800 of profit evaporating every month.
And we haven't counted takeaway orders, allergy questions, or any call landing when the floor is closed.
How many calls is your venue losing each night? See how many calls you're missing
Before / after 24/7 coverage
Before, the phone rang during the rush. The team chose the dining room, and they were right to. The next caller tried once, then phoned the place next door. No trace, no follow-up, no way of knowing how many had been lost.
Since then, every unanswered call goes back out as a message: WhatsApp, SMS if the number isn't on it, in the guest's language, at any hour. The guest replies when they have two minutes. The booking is written into your system, and the team takes the thread back when a human has to decide.
Case study: 4 Fridays, 1,217 calls recovered
80-cover bistro, République, Paris — April 2026
Before Heep: a generic voicemail at night, a stretched team between 7 pm and 10 pm. The owner knew calls were slipping — but had no idea of the volume.
After four Fridays with Heep on overflow coverage, the dashboard speaks for itself.
- 1,217 calls handled off-team
- 408 confirmed bookings
- +11% covers served per Friday
Monthly recovery: €9,800 in additional revenue — from overflow coverage alone, no menu change, no extra headcount.
Estimate your recoverable volume
Measure your leak in five minutes
The field method — no audit needed, just your telecom provider.
Pull your call logs
Every major UK and EU carrier exports inbound call CSVs with duration. Use the last 30 days as your baseline.
Filter calls under 8 seconds
Under 8 seconds, the call is either unanswered or hung up before pickup. That's your leak baseline.
Apply 30% conversion
Conservative assumption: 30% of those calls would have converted to bookings. Multiply by average ticket and party size.
Subtract gross margin
For net revenue lost, apply your gross-margin rate (typically 65 to 70%). That's the figure to take to the accountant.
For an automated version, the no-show cost calculator also covers the phone leak.
What changes with Heep
Heep picks the conversation up where the ringing stopped. In writing, in the guest's language, at the hour they tried to reach you.
- A message within seconds. The call goes unanswered, the guest gets a WhatsApp, or an SMS if they're not on it. The conversation starts before they ring the place next door.
- The booking written into your system. Zenchef, SevenRooms, TheFork: the table lands in the right service, the right slot, no re-keying.
- You set the hours. Nights, rush hours or round the clock: you decide when Heep takes over and what it may confirm on its own.
- Handover when a human is needed. Private hire, a complaint, anything outside the frame: the thread goes to the team with its context.
- The count, at last. Calls recovered, conversion, inbound languages, risk windows. You stop estimating.
One thing to do tonight, before you leave: pick up the floor phone and count the red calls from the day. You don't need the carrier's log to know whether this concerns you. If the number surprises you, go back to the method above.
Full flow detail on the Heep platform.
Frequently asked questions
How many calls is my restaurant actually missing?
Between 5 pm and 8 pm the sector average sits at 32% unanswered. Across 24 hours, factoring closed-hour calls, that climbs to 60-70%. Your telecom log gives you the exact figure.
Will Heep replace my front-of-house team?
No. Heep absorbs peak load and the night. The team stays on the floor for in-venue experience, complex requests and VIPs. Heep only takes what would have been lost.
How fast do I see impact?
Setup takes a few days. First numbers land on the very first evening — typically 30 to 50 bookings recovered on the first weekend.
Does Heep plug into my existing booking system?
Yes. Zenchef, SevenRooms, TheFork Manager, Resy: native two-way integration. No double entry, no migration.
What if I miss fewer calls than the average?
A handful of recovered calls a month is enough to cover the subscription. Below that, Heep isn't a fit, and the demo team will say so plainly.
