WhatsApp Business API for restaurants: setup, rules and real costs

The app is fine until these start happening to a restaurant:

• No-shows burn your revenue daily. Empty tables on Friday evening — booked, never showed, no call. 4-5 tables a week = pure lost revenue.
• Guests come once and are never heard from again. A great evening ends at the door. Nobody has their number, nobody follows up, and the table sits empty next Friday.
• Instagram DMs sit unanswered for hours. "Table for 2 tonight?" asked at 6 PM. You reply at 9 PM. They've already eaten elsewhere.

The app cannot send on a trigger, share one number across staff, or read your records. The API can. And customers keep asking the same things: guests ask whether there is a table tonight, whether the kitchen can do a dish without nuts or dairy, how late you serve, whether there is parking, and whether a large group can have a set menu.

• A verified Meta Business account in the restaurant's legal name, backed by a registration, GST or utility document.
• A number not active on the WhatsApp app — your current one works once it is removed from the app.
• A display name matching the business, and a website or public page Meta can check.
• Opt-in from every customer you message first. The reservation itself is the natural moment: a line on the booking form, or a table-tent QR code that opens a chat with the menu already sent.

1. Connect the number through Meta's embedded signup inside Reputoo, and submit business verification — you can start sending within Meta's starting limit while it is reviewed.
2. Get your first templates approved for the 1 routine message listed below; anything outside a customer's 24-hour reply window must be a template.
3. Wire the triggers to your records. What to connect: most restaurants already run a POS and often a table-booking system; the useful connection is the guest record, so a returning diner is recognised.
4. Put staff on one shared inbox, with conversations assigned so two people never answer the same customer.

A restaurant with 60 reservations a day sending a confirmation and a reminder for each sends about 3,600 utility messages a month — roughly ₹414 in Meta fees on the July 1, 2026 India rate card, before GST. A monthly menu message to 2,000 opted-in guests costs ₹1,726 at ₹0.8631 each. Keep offers out of the reminder template, or Meta will treat it as marketing too.

A confirmation that says only "table booked" invites a phone call. One that carries the details prevents it: the date and time, the number of guests, the name on the booking, the seating preference, any occasion ("birthday — we'll bring a candle"), and how long the table is held if they are late. Put the address and a map link in it too; late guests are usually lost guests.

For large groups, add the rules that matter — a set menu, a deposit, the final-numbers deadline — to the confirmation itself, so the organiser can forward it to the group.

Meta charges per delivered template message, and the price depends on the category. For restaurants, the day-to-day messages sort like this:

• Customer books via WhatsApp — service reply
• 24hr & 2hr reminders sent — utility
• Post-meal win-back timer — marketing
• 30-day win-back for lapsed guests — marketing

Timing matters as much as category. Confirmations belong the moment a table is booked and reminders a few hours before service. Offers do best mid-afternoon, when people are deciding where to eat — never during the rush you are trying to fill.

A service reply answers a customer who wrote first; from 1 October 2026 Meta charges those at the utility rate. Utility messages (confirmations, reminders, status updates) cost a fraction of marketing messages, so keep them strictly transactional — a discount line inside a reminder makes Meta classify the whole template as marketing.

Meta list rates, July 1, 2026. India in INR, plus 18% GST.

Most no-shows are not rude; people forget or plans change and cancelling feels awkward. A reminder on the day with three buttons — [See you then] [Change time] [Cancel] — makes cancelling as easy as confirming, and a cancelled table at 2 pm can be offered to the waitlist or a walk-in. A booking that is neither confirmed nor cancelled by the afternoon is worth one short follow-up; after that, hold it for your usual grace period and release it.

A no-show party of twelve on a Saturday, or a table for two on New Year's Eve, costs far more than a normal booking. Many restaurants take a deposit for these, and WhatsApp is the simplest place to collect it: a payment link in the confirmation, the amount and the refund rule in one sentence, and the booking held as provisional until it is paid. Leave exceptions to the manager.

Meta rates every number on how customers react. For restaurants, the risk is usually messaging the whole contact list about something only some of them asked for. Send reminders only to people with a booking or order, promotions only to people who opted in to them, and never use a bulk-sender tool on the ordinary app — that is the route to a banned number. The full list of what Meta checks is in our WhatsApp Business API guide.

Orders through delivery apps come with commission and without the customer's contact. A direct WhatsApp order — from the menu you send, a WhatsApp catalogue, or a link to your ordering page — keeps both. The API lets the kitchen see orders in a shared inbox instead of on the manager's phone, confirm them with a utility template, and send "ready for pickup" or "out for delivery" without anyone typing. Start with regulars who already call to order; they are the ones who will switch first.

An allergy mentioned in a chat is only safe if it reaches the kitchen. Make it a field on the booking or order, not a line buried in a conversation: the confirmation should repeat it back ("noted: severe peanut allergy for one guest"), and the kitchen ticket should show it. Anything medical or severe should be confirmed by a person, never only by an automated reply.

Restaurant groups usually run one number per outlet, each with its own display name, under one business account — guests book the outlet they know. Head office sees every conversation and can run group-wide campaigns to guests who opted in. If you use one number for several outlets, the first question in every booking must be which outlet, and the confirmation must name it.

1. Week 1: move the number to the API and get the confirmation, reminder, waitlist and order templates approved.
2. Week 2: every booking — phone, walk-in, online — gets the same confirmation and a day-of reminder.
3. Week 3: switch on the waitlist message and direct takeaway orders.
4. Week 4: the first menu message, only to guests who opted in, on a quiet afternoon rather than during service.

A short message the next morning — "Thank you for dining with us last night. How was everything?" with [Loved it] [Could be better] — tells you which evenings went wrong while there is still time to fix the guest's impression. "Could be better" goes straight to the manager with the booking attached. Keep it to one question, send it once, and never tie it to an offer; a guest who had a bad evening wants to be heard, not sold to.

Restaurants trip on the same template issues: offers slipped into reminders, vague placeholder text, and all-capital "IMPORTANT" lines. Keep variables for the parts that change — name, date, time, party size, outlet — and write everything else in plain, specific words. Submit the confirmation, reminder, waitlist and order templates separately; each purpose approved on its own stays in the cheaper utility category and is easier to fix if one is rejected.

• The reservation book and the WhatsApp number are connected, so every booking triggers a confirmation.
• Reminder buttons release cancelled tables automatically.
• Allergy notes appear on the booking and on the kitchen ticket.
• Marketing goes only to guests who opted in to it.
• Someone owns the inbox during service, and the manager gets allergy and complaint handovers.