WhatsApp for restaurants: bookings, regulars and quiet-night offers

WhatsApp for restaurants means using the official WhatsApp Business Platform to stay in touch with guests who asked to hear from you: booking confirmations and reminders, answers to questions, specials and quiet-night offers for regulars, and a quick follow-up after the visit. Booking messages are usually utility templates; offers are marketing.

This playbook is for restaurants, cafés, bakeries, bars, hotels and other hospitality businesses. It sets out seven plays with the trigger, the Meta template category, sample copy, how to run each one in Buddy today and the metric to watch, plus consent, cost and what needs a booking-system integration.

Why use WhatsApp for a restaurant?

Because your guests are already on it. WhatsApp has more than 3 billion monthly users, according to Meta, and in many cities, from Madrid and Mexico City to Dubai, Lagos and Mumbai, it is how people book a table or ask whether you have a vegan option. Even where it is less dominant, a message on the phone gets seen faster than an email newsletter.

Hospitality also suits short, timely messages. "Two tables free tonight" is worthless tomorrow. SendPulse's 2026 broadcast benchmarks put the median WhatsApp broadcast read rate at 63% across 355 accounts (November 2025 to April 2026), with a median click rate of 0.6%. Read that as one vendor's sample. The lesson for restaurants: put the offer, the time and the way to book in the message itself, because most people will read it and few will click.

What WhatsApp does not tolerate is a phone number collected from a booking and then used for promotions nobody agreed to. That is the fastest way to get blocked, reported and rate-limited.

What are the WhatsApp rules for restaurants?

You need opt-in. Meta's Business Messaging Policy requires that people give you their number and agree to receive messages from you, and its opt-in guidance says the wording must make clear they are agreeing to WhatsApp messages from your business. A number taken to confirm a booking is not permission to send offers. In the UK and EU, consent must be specific and unambiguous; the ICO says pre-ticked boxes and silence do not count. The simplest approach: ask separately, "Can we send you our specials on WhatsApp?"

When a guest messages you, you can reply freely for 24 hours. Outside that window, every message must be an approved template (Meta). Templates are categorised, and the category sets the price. Meta's utility templates documentation uses a restaurant reservation confirmation as its worked example, with "Change reservation" and "Call us" buttons. Its categorisation guidance adds that feedback requests must relate to a specific order or interaction to be utility, and that mixed content (a booking reminder with a dessert offer) is classified as marketing.

Meta makes the final call at review. For wording that gets approved, see our guide to WhatsApp message templates.

The restaurant WhatsApp playbook: seven plays

1. Menu and table QR opt-in

• Trigger: a guest scans a QR code on the menu, a table card, the bill folder or the receipt.
• Category: the welcome is a template, because the guest has not messaged you. If it includes an offer, it is marketing.
• Sample copy: table card: Get our weekly specials and last-minute tables on WhatsApp. Scan to join, leave any time. Welcome: Thanks for joining Table House on WhatsApp, {{1}}. Expect one message a week, usually on Thursday. Reply STOP to leave.
• In Buddy: your hosted opt-in page (usebuddy.app/yourname) and its QR code, ready to print, plus a "When someone subscribes" automation that sends your approved welcome template. Each opt-in is recorded with date and source. On your website, the Buddy Embed form (beta) does the same.
• Metric: opt-ins by day on your Dashboard's Audience growth chart. Every QR code points to the same opt-in page, so to compare placements, try one at a time (table cards one week, receipts the next) and compare the weeks.

2. Booking confirmations and reminders

• Trigger: a guest books, then the day before or the morning of the booking.
• Category: utility.
• Sample copy: Hi {{1}}, your table for {{2}} is booked for {{3}} at {{4}}. Reply here if your plans change. Add a Call button for the restaurant.
• In Buddy today: if guests book by messaging you on WhatsApp, your team confirms in the Inbox as a normal reply inside the 24-hour window. A day-before reminder is outside that window, so it needs your utility template; a small restaurant can send it each afternoon as a WhatsNew to a "tomorrow" tag. WhatsNews only go to subscribed contacts, so add guests to your Audience (with their agreement to WhatsApp messages) and move the tag each day. Sending automatically from a reservation system needs the Buddy API (sending approved templates arrives with the public beta from 12 October 2026) or Buddy Connect, which is planned, with Zapier and Make among its first connectors. No booking-system integration is live today.
• Metric: replies asking to change or cancel (a cancellation you hear about is a table you can resell), and your no-show count from the booking book.

3. Handle changes and questions in one inbox

• Trigger: a guest replies "Can we make it 7:30?" or "Do you have vegan options?"
• Category: service messages inside the 24-hour window.
• Sample copy: No problem, we've moved you to 7:30. See you tomorrow.
• In Buddy: the Inbox keeps every conversation on your number so front-of-house and managers can share it. Responses sorts replies into Interested, Question, Purchased, Follow up and Not now, and an automation on "When a reply is categorized" as Question can notify the team. A keyword automation on "menu" can send your menu link instantly. Invite floor staff as Members and keep settings with Admins.
• Metric: time to first reply, especially on the day of a booking.

4. Fill quiet nights and last-minute tables

• Trigger: Tuesday looks empty at 3pm, or a party of six cancels.
• Category: marketing.
• Sample copy: Two tables just opened for tonight at 8pm. Reply BOOK and we'll hold one for you.
• In Buddy: "Send now" to a "regulars" or "nearby" tag, starting from the Limited-time offer starter. A keyword automation on "book" can tag the reply and notify the team so someone confirms quickly. Keywords match any message containing the word and stay on until you pause them, so this one will also catch "can I book for Friday?"; pause it once the tables are gone.
• Metric: replies and covers booked from the message. Buddy counts replies; covers come from your booking book, because revenue attribution is not in Buddy yet.

5. New menus, seasonal dishes and event nights

• Trigger: the autumn menu launches, or you host a wine night or live music.
• Category: marketing.
• Sample copy: Our autumn menu starts Friday: slow-roast lamb, pumpkin gnocchi and a new vegan tasting plate. Book here: {{1}}
• In Buddy: a scheduled WhatsNew with a photo header, sent to an interest tag. Build those tags by asking people to reply VEGAN, WINE or MUSIC and using keyword automations that add each tag, so vegans do not get the steak night.
• Metric: read rate and replies per send, and opt-outs on the Consent page.

6. Regulars, birthdays and rewards

• Trigger: a guest's birthday month, or their tenth visit.
• Category: marketing.
• Sample copy: Happy birthday month, {{1}}. Dessert is on us any time before the end of the month. Just show this message.
• In Buddy today: there is no birthday or visit-count trigger. The manual version works well: ask for birth month on your opt-in follow-up, tag guests (for example "bday-mar"), give regulars a "regulars" tag in Audience (WhatsNews target tags, so use a tag rather than the VIP status), and schedule a monthly WhatsNew to each tag. Automatic visit-based rewards need data from your POS or booking system, which is what the API is for.
• Metric: redemptions counted at the till, against the number sent.

7. Follow up after the visit

• Trigger: the morning after a booking.
• Category: utility if it asks about that specific visit and sells nothing; marketing if it adds a return offer.
• Sample copy: Thanks for dining with us on {{1}}, {{2}}. How was everything? Reply with anything we could have done better.
• In Buddy: send a WhatsNew to the previous night's tag. Replies land in Responses and the Inbox, where a manager can pick up problems quickly and privately, before they become a public review.
• Metric: reply rate and the share of replies that need action.

What works today, and what needs a booking-system integration?

The API can already add subscribers today, so a booking widget that collects WhatsApp consent can push guests into Buddy with tags. Template sends through the API arrive with the public beta on 12 October 2026, and transactional messages are planned for release 1.1 shortly after.

How much does WhatsApp cost for a restaurant?

Meta charges per delivered template message, at a rate that depends on the category and the guest's country (Meta pricing). Marketing templates are always charged, and utility templates are charged outside the 24-hour window. From 1 October 2026, service replies and utility messages inside the window are charged too, with service replies at the utility rate (Meta). Our October 2026 pricing explainer has the detail.

In practice: keep booking messages strictly utility so they stay at the lower rate, and send offers to the tag that wants them instead of everyone. Meta bills your WhatsApp Business account directly and Buddy adds no markup; Buddy's plans are on the pricing page. Blocks and reports lower your number's quality rating (Meta), which Buddy shows on the WhatsApp health page along with your messaging limit.

How do you set up WhatsApp for your restaurant?

1. 1Sign up and connect your restaurant's WhatsApp number from Settings, WhatsApp, through Meta's Embedded Signup. It stays in your own Meta business portfolio.
2. 2Create four templates in Message templates: booking confirmation and reminder (utility), a post-visit check-in (utility), and a weekly specials message (marketing). Review can take up to 24 hours.
3. 3Print the opt-in QR code for table cards, menus and receipts, and brief staff on a one-line ask.
4. 4Build three automations: a welcome on subscribe, a "menu" keyword reply, and a team notification for questions.
5. 5Schedule your first specials WhatsNew for a quiet night and check replies and opt-outs the next morning.
6. 6Read the hospitality solution page for more ideas, and the WhatsApp marketing platform guide for how templates, health and insights fit together. For consent wording, see the WhatsApp opt-in guide.

Frequently asked questions