WhatsApp for Restaurants: Reservations, Menu Questions, and Friday-Night

Manchester, Friday 7pm — 19 WhatsApp messages and one person on the floor

A 45-cover restaurant in the Northern Quarter, Manchester operates Friday and Saturday with a team of four: one chef, one sous, one server, one front-of-house. On a typical Friday evening between 6pm and 9pm, the restaurant's WhatsApp Business number receives 15-20 messages. Reservation requests (can you fit 6 at 8pm?). Dietary questions (is the risotto gluten-free?). Directions (which entrance is it, the car park side?). Table queries from people already inside (can we order dessert via WhatsApp?). All of this while the single front-of-house person is seating, taking orders, and managing the till.

In February 2025, the owner configured auto-replies for the five message categories that accounted for 85% of inbound. Hours and location → instant reply with address, parking note, and Friday/Saturday walk-in policy. Allergen queries → 'our allergen menu is at [link] — for complex requirements please call us before arrival at [number].' Reservation requests → 'we're fully booked tonight, click here to see Saturday availability' or 'your preferred time is available, tap to confirm for [number] guests.' Directions → pinned location message.

The result: the front-of-house person now handles WhatsApp messages roughly once per hour rather than continuously. The restaurant captured three Saturday bookings in one Friday evening from people who had received the instant 'tonight is full, here's Saturday' reply — previously those would have gone unanswered until closing time.

The four message shapes a restaurant gets — and what to do with each

Restaurant WhatsApp traffic breaks into four shapes. Each needs a different approach.

Shape 1: Transactional / operational. 'Are you open today?' 'What's your last order time on Sunday?' 'Do you take walk-ins?' These are pure FAQ — the answer is always the same, the information is public, and a human should never be spending time on these. Auto-reply with a single accurate message, include the correct opening hours (updated for bank holidays and seasonal changes), and include a link to the booking page if you have one.

Shape 2: Reservation request. 'Can you fit 4 tonight at 7:30?' This is where the flow splits. If your booking system has a WhatsApp integration (OpenTable, Resy, SevenRooms, ResDiary all have API or Zapier connections), the auto-reply can check availability in real time and confirm or offer alternatives. If it doesn't, the auto-reply should tell the guest your current status and give a direct booking link or callback number. The worst outcome is a reservation request that sits unanswered for 3 hours — the guest has booked elsewhere by the time you reply.

Shape 3: Allergen and dietary query. 'Is the [dish] suitable for coeliacs?' 'Do you do vegan options?' This is the most legally sensitive category. The auto-reply should direct to your published allergen menu (required under UK Natasha's Law / EU Regulation 1169/2011 for allergen disclosure). For anything complex — cross-contamination, severe anaphylaxis risk, multiple allergens — the auto-reply should route to a human or a callback before the guest arrives, not attempt to certify allergen-safety via a bot.

Shape 4: Complaint or issue. 'Our food took 45 minutes last time.' 'The reservation wasn't on your system when we arrived.' Automation should acknowledge and route immediately to a human — never attempt to resolve a complaint via auto-reply. The automated message is: 'I've flagged this to our manager — [name] will be in touch within [timeframe]. Can I confirm the best number to reach you on?'

UK allergen law (Natasha’s Law 2021) and WhatsApp: what restaurants can and cannot communicate

UK allergen communication for restaurants sits under two overlapping frameworks:

Natasha’s Law (Food Information (Amendment) (England) Regulations 2021): This requires pre-packed-for-direct-sale (PPDS) food to carry full ingredient and allergen labelling on the packaging. For restaurants serving food made and sold on-premises (not PPDS), the Food Information Regulations 2014 require that allergen information is available and communicable to customers on request — via a written menu, verbal communication from staff, or a combination.

What this means for WhatsApp allergen queries: A WhatsApp auto-reply that links to the restaurant’s published allergen menu (required to include the 14 major allergens under EU Reg 1169/2011) is a legitimate disclosure method. A WhatsApp auto-reply that attempts to certify a dish is safe for a severe allergy is not — it creates a false impression of certainty that a bot cannot provide (cross-contamination during preparation is a kitchen variable that cannot be templated).

The correct auto-reply approach for allergen queries:
- General enquiry (‘do you have gluten-free options?’) → auto-reply linking to allergen menu PDF and noting ‘please call us to discuss your specific requirements’
- Severe allergy or anaphylaxis risk enquiry → auto-reply immediately routes to human or requests a callback: ‘For severe allergy requirements, please call us on [number] before your reservation so we can discuss with the kitchen’
- In-service allergen queries (‘is the sauce nut-free?’) → these must always go to a human — staff, not a bot, confirm allergen status for prepared food

Food Standards Agency guidance recommends that restaurants have a clear written procedure for allergen communication. A WhatsApp auto-reply policy that routes complex allergen queries to a human is consistent with FSA’s guidance and reduces liability risk from automated mis-statements.

Restaurant booking system integration: OpenTable, ResDiary, SevenRooms, and WhatsApp

The main UK restaurant reservation platforms in 2026 have varying levels of WhatsApp integration:

OpenTable: Widely used by UK casual dining and mid-range restaurants. OpenTable has its own messaging system (SMS confirmation, email) but no native WhatsApp Business API integration. Connecting OpenTable to WhatsApp for real-time availability queries requires Zapier (OpenTable has a Zapier connector). A common setup: new OpenTable reservation → Zapier → WhatsApp template confirmation sent via BSP. Reverse flow (WhatsApp reservation request → check OpenTable availability) requires the OpenTable API and is more complex.

ResDiary: Used by independent and premium UK restaurants. ResDiary offers a booking widget and customer emails/SMS. No native WhatsApp. Zapier connection via ResDiary’s API is possible for outbound notifications.

SevenRooms: Used by upscale restaurants and hotel restaurant operations. SevenRooms has more sophisticated guest CRM features. Some WhatsApp integration capabilities exist at enterprise tier; smaller operators use Zapier bridges.

The practical reality for UK independent restaurants: Most independent restaurants under 100 covers do not use a sophisticated reservation system — they take bookings via phone, email, or a simple calendar. For these operators, WhatsApp can serve as the primary booking interface via a simple flow (Party size + Date + Time + Name + Confirmation). The restaurant owner or front-of-house confirms manually via WhatsApp within the same conversation. No Zapier required; no booking system integration needed.

The capacity problem: A WhatsApp booking flow without a real-time inventory check cannot prevent double-bookings. The auto-reply should say ‘I’ve noted your preferred time — our team will confirm within 2 hours’ rather than issuing a confirmed booking the bot cannot verify against current availability.

No-show reduction for UK restaurants: what actually works

No-shows at UK restaurants are persistent and expensive. A covered table that sits empty for a service costs the restaurant the food margin it would have earned — typically £15-40 per head on a set menu, more at premium establishments.

The confirmation flow that works:
- 48 hours before: WhatsApp template asking the guest to confirm their reservation (one-tap ‘Confirm’ / ‘Need to cancel’ button)
- 2 hours before: Short reminder if not yet confirmed, with a direct line if changes are needed
- Same-day (for evening bookings): Optional ‘Looking forward to seeing you tonight’ — creates social commitment, modestly improves show rate

The deposit option: UK restaurants taking deposits via WhatsApp (Stripe Payment Link, Square payment request) report the steepest no-show reductions. A £10-20 per-head deposit for tables of 4+ during peak times creates a financial commitment. Under UK Consumer Contracts Regulations 2013, the deposit terms must be stated clearly at booking time. A WhatsApp booking confirmation stating ‘A £15 deposit per head is required to secure this table — link: [Stripe link]. Refundable with 48h notice’ satisfies this requirement.

What doesn’t consistently work: Sending a WhatsApp reminder without a response mechanism (customers see it but don’t act). Relying on the customer having the restaurant’s number saved in their phone (not universal — Meta’s API approach sends to opted-in contacts regardless of saved status).

WhatsApp API vs Business App for confirmations: The free WhatsApp Business App requires manual sending of reminders. The API (via BSP) automates the 48h reminder without staff input. For restaurants with 30+ covers per service, the API tier pays for itself in the staff time saved on manual reminder management.