Online restaurant booking: never miss a request, day or night
47% of French restaurants still have no online booking, and 52% of requests come outside service hours. Here's how to capture every single one — without hiring.
Two things get sold as online booking. One is an engine on your site: the guest picks a slot, the booking is written. The other is a DM, a WhatsApp message, a form, a call nobody took, where the request becomes a booking only if something replies to it.
Almost all the leakage below sits in the second category. Not a demand problem: a question of who answers.
1 in 2 booking requests arrive outside your service hours. Source: TheFork.
Why one in two requests never reaches you
Count the entry points before counting the losses. Phone, website, Instagram DMs, WhatsApp, Google, TheFork, form: seven channels, seven queues, seven owners.
None is broken on its own. What breaks is that none of them talks to the others: a request landing on the wrong channel at the wrong hour has no path forward. The guest does not wait.
The result: 52% of requests arrive outside service hours, and no one captures them. The architecture decides what gets lost, not the guest. See our analysis of booking leakage.
The real cost of every missed request
- 47% of French restaurants (have no online booking system at all)
- 52% of requests (arrive outside service hours (TheFork))
- 75% of guests (treat online booking as the norm (Lightspeed))
On an average ticket of £40, ten missed requests a week add up to £20,800 a year. Lifetime value not included.
An order of magnitude, not your number. Estimate your recoverable volume
From overloaded line to one unified channel
Not an eighth channel: a layer above them, holding one queue and one history per guest.
A call nobody took is followed up by WhatsApp, then by SMS if WhatsApp is unavailable on that number, and the exchange carries on in writing, where it can be qualified at 11 pm. DMs, email and the form join the same queue. The booking software stays the system of record.
Case study: Noto Paris, 2,500 missed calls recovered
Moma Group's Italian table recovers 2,500 missed calls a month by message, without hiring
- Before Heep: about a quarter of all calls missed during service. No follow-up.
- After deployment: each missed call gets a WhatsApp follow-up, then SMS; written channels answered around the clock, booking written into Zenchef.
- 2,500 missed calls recovered / month · 1,600 confirmed bookings / month · 0 extra hires
One precision: those bookings are counted inside Zenchef, so they are measured. The revenue behind them is an estimate.
The four-step method
Audit your real leakage
Count missed calls over seven days. Note unanswered DMs. Measure the delay before a reply.
Pick your booking software
Zenchef, TheFork Manager or SevenRooms. The foundation, not the orchestrator.
Connect the secondary channels
Missed calls, DMs, WhatsApp, forms: one queue. Separate tools, and you have an eighth silo.
Measure what changes
Capture rate, time to first reply, conversion. If you do not measure, you do not know.
How to choose your solution: 5 criteria
- 24/7 availability. It replies at night, on Sunday, during service, on the written channels.
- Native multi-channel. Missed-call follow-up by message, web, DMs, WhatsApp, forms. One memory behind all of them.
- Booking sync. A direct write into Zenchef or equivalent, not a link sent back to the guest. Both are sold with the same words.
- Full conversation history. Every exchange readable word for word. You keep the guest memory.
- No long lock-in. a few days to start, no penalty.
Two conditions decide the rest, and neither is on a feature list: whether your booking software's API is open on your contract tier and in your country, and which setting must be switched off so nothing is written twice.
Frequently asked questions
Should we drop the phone altogether?
No. The phone is still preferred by 37% of guests. The point is to add an AI layer that follows up by message (WhatsApp, then SMS) when the team cannot pick up.
What does a missed request actually cost?
On an average ticket of £40, one lost request a day adds up to roughly £14,500 a year in missed revenue. Lifetime value over twelve months not included.
Can we keep Zenchef and add an AI agent?
Yes. Heep integrates natively with Zenchef, TheFork Manager and SevenRooms. The booking lands directly in your software, with no double entry.
How long does it take to go live?
A few days. The agent learns your menu, opening hours and rules. You stay in control of what it says or does not say.
What about no-shows?
Handled too. The agent sends reminders, prompts re-confirmation and frees the table if the guest cancels. Details in our no-show guide.
