Restaurant No-Shows: Where OpenTable Stops and WhatsApp Actually Wins

What we actually know about restaurant no-show rates in 2026

Restaurant no-show rates vary meaningfully by segment, and headline figures should be read with segment context in mind.

Casual dining without deposit or pre-authorisation. No-show rates commonly reported in industry press in the 10-20% range for typical urban casual-dining venues, with higher rates during high-demand periods (weekend evenings, holiday seasons) and lower rates for lunch service or lower-demand slots. Restaurant trade associations in the UK and US have consistently identified no-shows as a top operational challenge — see the UK Hospitality trade body for UK-specific commentary and the US National Restaurant Association for US-side context.

Fine dining with deposit or pre-authorisation. Low single-digit no-show rates. The deposit itself is the primary deterrent; the reminder workflow is secondary. Tock in particular pioneered ticket-based dining (pay in advance, non-refundable within cancellation window) for high-end venues, with a corresponding drop in no-show behaviour.

Casual dining with active reminder workflow but no deposit. Reservation platforms report meaningful reductions from automated reminder cadence versus no reminders at all. The exact percentage varies by platform, restaurant type, and reservation lead time. Individual restaurant reports of 30-50% reductions after implementing platform-native reminders are common in the industry press, but restaurant operators should treat these as directional rather than as a specific figure to plan against.

High-demand-slot no-show behaviour. Restaurants that take reservations for peak Saturday-evening slots without any deposit or friction see the worst no-show rates. Anecdotal industry reporting includes London high-demand venues facing 20%+ no-show rates on weekend prime-time seatings before deposits were introduced.

The honest framing: your restaurant's own historical no-show rate — from the reservation platform's dashboard, if you use one, or from your own reservation-book audit — is a better planning number than an industry average. What you can expect from adding a supplementary WhatsApp reminder layer on top of an already-existing reminder workflow is meaningful but incremental; what you can expect from adding a deposit or pre-authorisation policy is a much larger step-change.

The reservation-platform landscape — what already covers the reminder use case

For most restaurants above a certain size, the reservation platform is the operational hub and it already handles reminder workflows as part of the product.

OpenTable (restaurant.opentable.com) — the largest reservation platform in the US and one of the largest globally. Owned by Booking Holdings. Sends automated email and SMS confirmations and reminders with the restaurant's brand; supports pre-authorisation and no-show fee workflows on higher-tier plans. WhatsApp integration is limited natively.

Resy (resy.com/business) — American Express-owned. Strong in US markets particularly among independent full-service restaurants. Automated confirmation and reminder emails, deposit workflows, cancellation policy management.

SevenRooms (sevenrooms.com) — restaurant-CRM-focused reservation platform used by hotel groups and high-end restaurant chains. Deep guest-profile data (dietary preferences, previous visits, spend history), automated confirmations and reminders, marketing broadcast to guest lists.

Tock (exploretock.com) — Squarespace-owned. Pioneer of ticket-based reservations (pay in advance). Strong in high-end and destination dining venues. Automated confirmation and reminder cadence built into the ticket-purchase flow.

TheFork (thefork.com/business) — European reservation platform, Michelin / Tripadvisor-owned. Dominant in France, Spain, Italy, and other EU markets. Guest confirmation and reminder cadence, no-show tracking on the guest side.

Yelp for Restaurants (restaurants.yelp.com) — Yelp's reservation product; part of the broader Yelp business ecosystem.

Quandoo (quandoo.com/business) — European reservation platform.

All of these ship native reminder workflows. If a restaurant is already on one of them, the incremental value of adding a WhatsApp layer for reminders is limited to: reaching guests who prefer WhatsApp over the platform's email / SMS defaults; providing a personal-touch high-value-reservation confirmation flow; and handling any post-reservation communication (order-ahead for a private-dining event, dietary-preference collection, wedding-anniversary personalisation) that the platform's standard flow doesn't cover elegantly.

For restaurants not on a reservation platform — often smaller neighbourhood restaurants that take bookings by phone, walk-in, or Instagram DM — a WhatsApp Business Platform layer provides the reminder infrastructure the restaurant currently lacks. That is where the incremental value is highest.

The deposit / cancellation-fee strategy — bigger no-show reduction than any reminder

The single most effective no-show-reduction lever is not a better reminder; it is a deposit or pre-authorisation policy that gives the guest financial skin-in-the-game.

How it works. At the point of booking, the restaurant captures either a per-person deposit (commonly £10-£50 for casual, up to £200+ for high-end tasting menus) or a pre-authorised card hold that will be charged if the guest fails to arrive without cancelling within the notice period. Tock's ticketing model takes this further — the full booking value is paid at time of reservation, non-refundable within cancellation window.

Effectiveness. Restaurants report meaningfully lower no-show rates after implementing a deposit or pre-authorisation policy. The financial deterrent focuses guests' attention on their commitment. The exact reduction varies by segment and by how the policy is communicated, but industry reports of no-show rates dropping from 15-20% to under 5% after introducing a deposit are common in press coverage of high-profile venues.

Legal position — UK. Under the Consumer Rights Act 2015, terms in a consumer contract must be transparent and prominent. A cancellation-fee or deposit policy must be clearly communicated at the point of booking, not buried in small print. Terms that are unfair (as defined by the Act's fairness test) are not enforceable. The Competition and Markets Authority (CMA) has guidance on unfair terms including in the hospitality context. A restaurant charging a genuine pre-estimate of loss for a no-show — one that reflects the actual cost impact — is on solid ground; a punitive charge that exceeds any credible loss estimate risks being struck down.

Legal position — US. State consumer-protection law applies and varies. Most states permit reasonable cancellation fees on restaurant reservations provided they are clearly disclosed at the point of booking. TCPA applies to any SMS or WhatsApp communication about the deposit or charge. Card-network rules (Visa, Mastercard) on pre-authorisation and no-show charges apply — the pre-auth-and-capture pattern needs to comply with card-scheme merchant rules, and unauthorised charges after the fact can result in chargebacks.

Legal position — EU. Consumer-protection rules across the EU generally permit reasonable deposits and cancellation fees where disclosed. TheFork and other EU-focused platforms build the no-show-fee workflow into their platform terms.

Practical implementation. Restaurants can implement deposits or pre-authorisation through the reservation platform (OpenTable, Resy, SevenRooms, Tock, TheFork all support this on appropriate tiers) or through a standalone Stripe / Square-based deposit-collection workflow linked to a WhatsApp confirmation flow for direct-booking restaurants. The deposit / policy is separate from the WhatsApp reminder; combining both — deposit at booking + reminder before the reservation — is the strongest pattern.

Where WhatsApp Business Platform actually adds incremental value

For restaurants already on a reservation platform, adding a WhatsApp Business Platform layer makes sense in three scenarios.

Direct bookings and platform-adjacent bookings. A restaurant that takes bookings by phone, WhatsApp, Instagram DM, or its own website form (bypassing OpenTable / Resy / etc) needs an infrastructure to send confirmations and reminders for those bookings. A WhatsApp Business Platform tool with template-driven confirmations fills that gap. Even restaurants on a reservation platform typically have a stream of direct bookings that the platform doesn't handle.

High-value reservation personalisation. Wedding anniversaries, birthday celebrations, business-dinner large parties, tasting-menu private events — these bookings benefit from a personal-touch confirmation and pre-visit communication that goes beyond the reservation platform's standard template. A WhatsApp thread with the restaurant's maître d' asking about dietary requirements, cake arrangements, corkage, or celebration details produces a better guest experience than a generic OpenTable reminder email.

Post-visit engagement and marketing. Review-request messages after the visit (linked to the restaurant's Google Business Profile listing under Google's rules on non-gated review solicitation), broadcast messages to a PECR-consented guest list about new menu launches or seasonal events. This is separate from the reminder use case and is where marketing-category templates come in under Meta's July 2025 pricing.

What WhatsApp Business Platform tools do not replace: the reservation platform itself (which handles the actual booking capacity, table management, floor plan, and guest history in a way a WhatsApp inbox cannot); the payment / deposit processor (Stripe, Adyen, Square, or the reservation platform's own payment engine); the restaurant's PoS integration for the guest's actual visit spend history.

The integration pattern that works: reservation platform is the operational hub, WhatsApp Business Platform is a supplementary messaging layer, deposit / pre-auth policy sits on top of both. For direct-booking restaurants without a reservation platform, WhatsApp is a more central part of the booking workflow but usually still sits alongside a simple booking capture tool (Google Calendar with public booking link, Calendly, a booking form on the restaurant's website) rather than substituting for one entirely.

GDPR / PECR and reservation data — the compliance surface

A restaurant handling reservation data — guest name, contact number, party size, dietary information, and increasingly card-on-file details for pre-authorisation — is processing personal data subject to GDPR and PECR.

Reservation data as personal data. Guest name and contact are personal data under UK GDPR / EU GDPR. Dietary preferences may include health information (celiac, allergies) that is special-category data under Article 9. Card details are subject to PCI-DSS in addition to GDPR.

Lawful basis for reservation communications. Booking confirmations and reminders are transactional communication sitting on contract with the guest (Article 6(1)(b)) — the guest is a party to the reservation contract, and the messages serve the contract. No separate consent is needed for these.

Marketing communications. Broadcasts about new menus, seasonal events, promotional offers to past guests require PECR consent under Regulation 22 (UK) or the equivalent framework in the guest's country. The soft-opt-in exception under PECR Regulation 22(3) applies to existing customers of similar services with a working opt-out on every message.

Data-processor relationships. Both the reservation platform and any WhatsApp Business Platform vendor are personal-information processors under GDPR. The restaurant (as controller) needs a data-processing agreement with each vendor covering GDPR requirements — instruction-only processing, security, breach notification, sub-processor management, international-transfer safeguards.

Retention. Guest data should be retained only as long as necessary for the purpose. Reservation records may need to be retained for tax and accounting purposes (typically 6 years in the UK, similar in most jurisdictions), but the individual guest's contact information used for marketing should be reviewed regularly for continued relevance and consent status.

Special-category dietary data. If the restaurant captures allergy or health-related dietary information (celiac disease, severe nut allergies, diabetes-related dietary restrictions), this may be special-category personal data under Article 9. The lawful condition is usually 9(2)(a) explicit consent captured at the point of booking, or 9(2)(h) if the restaurant is providing a medical-nutrition service — which most restaurants are not. Explicit consent captured in the booking flow is the standard pattern.

Meta's 1 July 2025 pricing shift — restaurant cost model

Meta's WhatsApp Business Platform pricing shift that took effect on 1 July 2025 changed the outbound-message cost model for restaurants.

Utility templates — booking confirmations, reminder messages, cancellation acknowledgments, deposit-received confirmations, post-visit thank-you messages. Priced per template at the country's utility rate.

Marketing templates — new-menu announcements, seasonal-event invitations, chef's-table promotional broadcasts, birthday-offer messages to past guests on a consented list. Priced per template at the higher marketing rate.

Authentication templates — two-factor codes for a guest-loyalty portal, if the restaurant has one. Small line.

Guest replies inside a guest-initiated 24-hour service window remain free — which for a restaurant's inbound-heavy service pattern (guests reaching out to modify reservations, ask about menus, request dietary accommodation) keeps most of the reply cost inside the free window.

Cost picture for a mid-size independent restaurant (50-100 covers, 4-6 shifts per week, mix of platform and direct bookings): reservation-platform subscription (varies by platform tier), WhatsApp Business Platform vendor subscription (typically USD 30-100/month at small-restaurant tier), Meta template cost dominated by utility reminders for the direct-booking segment. Marketing broadcasts are optional and scale with cadence and list size.

For restaurants primarily on OpenTable / Resy / SevenRooms / Tock, the WhatsApp Business Platform cost is incremental to the reservation platform cost. For direct-booking restaurants, WhatsApp Business Platform + a simple booking capture tool may be more cost-effective than a full reservation platform if the restaurant's booking volume is modest.

The honest 2026 recommendation for restaurants tackling no-shows

For a small independent restaurant (30-60 covers, mix of walk-ins and phone reservations, minimal online booking infrastructure), the honest 2026 recommendation is: put in place a simple online booking system (either OpenTable / Resy at the basic tier, or a simple direct-booking form linked to Stripe for optional deposit collection); use the WhatsApp Business app (free consumer-tier) for informal reservation confirmations and communication with regulars; consider introducing a deposit policy for high-demand slots (weekend evenings, tasting menus) — this is the single largest lever on no-shows. A WhatsApp Business Platform paid subscription is usually not economic at this scale.

For a mid-size restaurant or small chain (60-150 covers per location, 2-3 shifts daily, direct-booking mix with online reservations), the WhatsApp Business Platform starts to earn its subscription: shared inbox for reservation questions handled by multiple front-of-house team members; utility-template automation for direct-booking confirmations and reminders; marketing broadcast to a consented past-guest list. The reservation platform remains the operational hub; the WhatsApp Business Platform is the supplementary messaging layer.

For a high-end restaurant, tasting-menu venue, or destination restaurant that already runs a deposit / ticket policy through Tock or SevenRooms, the incremental value of a WhatsApp Business Platform is mainly in the high-value-reservation personalisation use case — the maître d's-hand WhatsApp thread that produces a better guest experience for celebration bookings, private-dining events, and returning-VIP guests. Vendor selection is driven by CRM integration and by handling of high-touch personalisation, not by raw automation features.

For a restaurant group or franchise operation, WhatsApp sits inside a broader guest-experience stack that includes SevenRooms-style CRM, multi-channel marketing, and location-level analytics. Vendor selection is driven by integration and enterprise support.

What is not the right answer at any scale: presenting a WhatsApp reminder as a substitute for a deposit or pre-authorisation policy (the deposit is the bigger lever, by an order of magnitude); sending marketing broadcasts to past guests without PECR / equivalent consent; treating the reservation platform as replaceable by WhatsApp (it isn't — the platform handles floor plan, table management, capacity, and guest history in ways the messaging channel cannot); trusting vendor-marketing claims of specific no-show-reduction percentages that don't have documented methodology behind them. Measure your own no-show rate before and after any intervention, and let your own numbers drive the decision.