Restaurant phone time: 45 hours a month up in smoke (and the €956 hidden bill no-one tracks)

Thursday, 12:40. The phone rings for the sixth time since service started. Whoever picks up has a plate in the other hand. Three minutes later they have taken a table of four for Saturday. They have also lost the thread on table 7.

I see that in almost every room I work with. Nobody counts it. It still costs 1h 45 a day, 45 hours a month, €956 of payroll.

Why your team spends 1h 45 a day on the phone

An industry study by Vigilantia shows that a restaurant serving 120 covers uses 2 hours of phone time per day. At 80 covers, expect 1h 45.

The breakdown is brutal:

• Inbound bookings3 to 5 minutes per call. 25 to 35 calls per day depending on capacity.
• Repeat questionsHours, menu, allergens, parking. 30% of total volume.
• Changes and cancellations2 to 3 minutes per call, often mid-service.
• Groups and private hireVerbal quotes, follow-ups. One call equals 7 to 10 minutes.

Worst moment? Noon-2pm and 7-9pm. More than 40% of volume lands during service.

“We share the calls out here.” True, and it changes nothing about the total. It just slices it up, at the moment it costs the most.

€956 of payroll burned every month

The French HCR collective agreement sets minimum hospitality pay at €9.40 net/hour. With employer charges, the loaded cost climbs to €17/hour on average.

The monthly bill looks like this:

• 45 h Phone time/month (Based on 80 covers × 26 days)
• €956 Payroll cost (At €17/h fully loaded)
• 18% Bookings lost (Unanswered calls at peak)

That's only the direct cost. 80% of customers never call back after a first unanswered call (Customer Service Observatory 2023). Indirect losses easily double the bill.

Your numbers are not mine. Take the number of calls in one service, the average length, the loaded hourly cost of whoever picks up, and multiply by your opening days. Estimate the cost for my restaurant

Before / after: a missed call is no longer a lost customer

Today, twelve calls in a hundred hit voicemail, and the customer rings the place next door.

What changes isn't the number of calls: it's what happens to the ones nobody could take. The customer gets a WhatsApp or SMS message a few seconds later. They book, ask their question or move their visit in writing, and the booking is written into your software. The team only steps back in on the cases you listed: groups, allergies, press.

The win isn't just financial: it gives the floor back to service. You can let it ring in the middle of the rush without losing the customer.

How to take back control in a few days

1. Measure

   Count one week of missed calls from your phone's call log, service by service. Note the recurring reasons: booking, hours, allergens, group.

2. Setup

   Heep brief: house tone, booking rules, allergies, cancellation policy. Connection to your booking system (Zenchef, TheFork, SevenRooms).

3. Missed-call redirection

   Every unanswered call triggers a WhatsApp message, then SMS as a fallback. You define your escalation cases: groups > 8, severe allergy, complaint, press.

4. Follow-up

   The inbox for escalations. The counter for recovered calls and bookings written.

3 mistakes to avoid before automating

• Assuming voicemail is enough80% of customers don't leave a message. Voicemail turns a call into a lost customer.
• Picking a generic AIA non-hospitality assistant stumbles on kids' menu, accessibility, vegetarian. Check for sector specialisation. See how Heep handles these cases.
• Skipping escalation rulesWithout clear rules, AI hesitates on sensitive cases. Define your 5-6 critical cases before go-live.

One thing to do tonight, at close: open the call log on the floor phone and count the unanswered calls from that service. Two minutes. That's the number that will open the conversation at tomorrow's mise en place.