Online Restaurant Booking: OTA vs Direct vs WhatsApp (2026 Guide)

An OTA and a direct channel do not sell you the same thing. The OTA brings you a guest you would not have had, and charges you for that guest per cover. A direct channel brings you nobody: it receives the demand your name, your menu or your Google listing already created.

Both are useful. But paying a commission on a guest who was already looking for you, and losing the one who messaged you at 11 pm, are two different mistakes. This guide sorts the channels by what they actually bring, and by what they let slip.

Why OTAs only cover one channel

TheFork, Zenchef, Resy: these platforms capture guests who are actively searching for a table. They do not capture the guest who sends an Instagram DM at 11 pm, calls back after missing your line, or writes on WhatsApp.

Demand is multi-channel. OTAs cover one channel, and charge you €1.50-€3 per confirmed cover for the privilege. For every other channel, you are on your own.

• 73% of restaurant bookings are now made online (NPD Group, France Food Service 2025)
• €1.50-€3 OTA commission per confirmed cover (Zenchef, TheFork pricing 2025)
• 52% of booking requests arrive outside service hours (TheFork, France Hospitality 2025)
• 30 sec response threshold, beyond which the guest books elsewhere (Heep behavioural estimate)

Comparing the options: OTA, direct site, WhatsApp

Every channel has a coverage and a blind spot. Taken alone, here is what each one lets through:

• OTA only: commission on every cover, even guests who would have found you directly.
• Phone during service: calls that ring mid-rush are not picked up. The guest does not call back.
• WhatsApp, DMs: read the next morning. The guest has already booked elsewhere.
• Contact form: average response 24 hours, when the conversion threshold is 30 seconds.

Stacking works better than replacing: the OTA stays for visibility, direct channels are handled in real time including at 11 pm and on Sundays, every unanswered call gets a WhatsApp (or SMS) within seconds, and the form becomes a conversation instead of a message waiting in a mailbox.

Case study: Noto Paris, 2,500 calls captured per month

Moma Group's Italian table runs three pieces together: its own site, Zenchef as the book, and Heep on the inbound channels. Volume handled: 2,500 missed calls and 1,300 messages a month, in more than 10 languages. Every missed call gets a WhatsApp or SMS follow-up, the agent qualifies the request and syncs the booking into Zenchef. Result: 1,600 confirmed bookings a month, no extra hires.

Further reading: why your restaurant is losing bookings, missed call revenue calculator, Heep + Zenchef integration and no-show reduction guide.

The four-step method: live in a few days

1. Keep your OTA for visibility

   TheFork or Zenchef remain useful for guests in active search mode. Do not remove them, redefine their role.

2. Activate WhatsApp Business

   Add the WhatsApp link to your Google listing, website and Instagram profile. With Heep, every message gets a reply in under a minute.

3. Catch missed calls outside service hours

   Forward unanswered calls to Heep. The guest receives a WhatsApp (or SMS) within seconds; Heep handles the request by message, checks availability in Zenchef and confirms the booking.

4. Connect DMs and contact forms

   Every inbound channel lands in the same inbox, one thread per guest whatever the channel it came from.

One condition sets the real timeline: the WhatsApp Business account goes through Meta verification, with an up-to-date Business Manager and a dedicated or ported number. Until that step is done, the other three cannot run. Book a demo