WhatsApp for Restaurants: The Complete Order-to-Review Playbook

It is 8:40 pm on a Friday. The counter phone is ringing, a rider is asking about order 217, a table of six wants to book for tomorrow, and someone just sent a photo of your menu with the message "2 of this?" Most restaurants do not have a demand problem on weekend nights — they have a message-traffic problem, spread across phone calls, three apps and a notepad. WhatsApp for restaurants works because it pulls order-taking, confirmations, delivery updates and feedback into one channel that customers already open several times a day.

TL;DR

• Split traffic into two lanes: order-taking in free-form chat inside the 24-hour customer service window, and order-status via approved utility templates.
• Build three flows first: order confirmation through delivery updates, table and booking confirmations, and the post-meal feedback loop.
• Broadcast the menu weekly at a fixed hour; run festival and weekend promos as short, segmented bursts.
• Track first reply time, template delivery rate, feedback reply rate and repeat-order rate — not vanity counts.
• A shared team inbox such as Whaterakt's multi-number inbox lets counter, kitchen and delivery coordinate on one number without passing phones around.

Why restaurants keep landing on WhatsApp

In much of India, Southeast Asia, the Middle East and Latin America, customers already try to order food over WhatsApp before they open a delivery app — which is why Meta positions the WhatsApp Business Platform heavily for food and beverage businesses. Message open rates on WhatsApp are commonly reported above 90 percent, an order of magnitude above typical email campaigns, and the message lands on the same screen where the customer is already deciding what to eat. For a restaurant, that means faster order capture, fewer missed calls, and a direct line to regulars that no aggregator marketplace gives you.

The two lanes: order-taking vs order-status

Live chat is for taking the order; templates are for telling the customer what happened to it.

Lane 1 — Order-taking lives inside the 24-hour window

When a customer messages you first, a 24-hour customer service window opens. Inside that window your team can chat freely: clarify the dish, confirm the total, share a payment link, take the delivery address. This is where a shared inbox earns its keep — the counter claims the chat, the kitchen sees the thread, and the customer never has to repeat "no onions" twice. The mechanics of the window and the conversation categories are covered in detail in WhatsApp conversation categories and the 24-hour rule.

Lane 2 — Order-status messages are utility templates

Anything you send outside the open window needs an approved template. Order confirmations, "your food is being prepared", "rider has picked up order 217" and table confirmations are utility templates: factual status the customer effectively asked for, not marketing. Get them approved before the weekend, not during it — template review usually takes minutes to hours, but festival queues run longer. Meta bills per delivered template conversation at category-specific rates, so check current numbers on Meta's WhatsApp pricing documentation and budget accordingly.

The ops table: who sends what, and when

Print this and pin it next to the counter terminal. Every recurring restaurant message has a category, a timing rule and an owner; once those three are fixed, new shift staff stop improvising.

Three flows to set up first

Flow 1 — Order confirmation to delivery updates

1. A customer messages your number (or taps a click-to-WhatsApp ad). A keyword auto-reply instantly sends today's menu link or catalog so nobody waits for a human to free up.
2. Counter staff confirm items and total in the live chat. A catalog or storefront link lets customers tap dishes instead of typing them — the pattern is covered in catalog and storefront selling on WhatsApp.
3. The moment the order is locked, the confirmation template fires with order number, items, total and ETA.
4. Status templates go out on cooking and dispatch automatically. Nobody has to remember to update anyone at 9 pm.

Flow 2 — Table and booking confirmations

1. The booking request arrives in chat; the host checks availability, with a Sheets or Calendar integration keeping the booking sheet honest.
2. A confirmation template goes out with date, time, party size and a reply keyword for changes or cancellation.
3. A reminder fires two hours before the slot. Reminders will not eliminate no-shows, but they give the waverers a chance to cancel politely instead of simply not appearing.

Flow 3 — The post-meal feedback loop

1. One to two hours after delivery, a short utility template asks: "How was order 217? Reply 1 to 5."
2. A 1, 2 or 3 routes the chat to the manager with a gentle recovery prompt; a 4 or 5 gets a thank-you and, where consented, an invitation to the weekly menu list.
3. Low ratings open an assigned task in the team inbox so somebody owns the apology before it becomes a public review.

Menu broadcasting without becoming spam

The weekly menu broadcast — new specials, weekend-only dishes — is the highest-revenue recurring message most restaurants send. Three rules keep it healthy. One: fixed day and hour, so customers learn the rhythm instead of feeling ambushed. Two: short copy plus one image or a catalog link, not a photo album. Three: marketing templates go only to opted-in contacts, because opt-in for marketing messages is a platform requirement, not a suggestion — our WhatsApp opt-in guide covers formats that hold up. And if you are currently blasting promos from the personal WhatsApp app, stop: app broadcast lists cap at a few hundred recipients, fail silently for people who have not saved your number, and put the number itself at risk.

Festival and weekend promo bursts

Diwali, Ramadan, Christmas week, Valentine's Day, big match days — treat these as three-to-five-day bursts, not one-off blasts. A rhythm that works: a teaser two days out, the main offer on the day, and a last-call message the final evening. Segment the audience — past customers inside the delivery radius get the delivery offer, dine-in regulars get the table offer — and use a separate template per beat so you can see which one pulled. In Whaterakt you can schedule the entire burst in one sitting, with day-level waits between messages, so during the festival the team is cooking rather than clicking Send. For the wider mechanics of lists, scheduling and frequency caps, see the complete WhatsApp broadcast campaign guide.

Staffing the inbox: shifts, roles, handoffs

Restaurants run in shifts, and an inbox that only works when one person's phone is switched on is not an inbox. Set it up so each shift has a named owner, chats are assigned rather than answered from a shared login, and closing notes are written into the thread before handover. Saved replies for the twenty most common questions — delivery radius, timing, today's special, payment options — turn a new hire into a competent responder within a day. The fuller model is in the WhatsApp team inbox guide.

Metrics that matter for a restaurant

• First reply time — the biggest lever on order capture during rush hour; aim for minutes, not hours.
• Template delivery rate — a falling rate means stale numbers, missed opt-outs or blocks.
• Feedback reply rate — how many customers actually answer the 1-to-5 question.
• Repeat-order rate — the share of broadcast recipients who order again within 30 days.
• Block and report rate — the early-warning light for frequency creep.

Log these weekly and compare them across weeks, not against other restaurants — your cuisine, catchment and price point set your baseline. When you are ready for the fuller metric set with definitions, the WhatsApp analytics guide on this blog covers it.

FAQ

Is the free WhatsApp Business app enough for a restaurant?

For a single-location café with light traffic, the free app is a fair start. It cannot send approved templates outside the 24-hour window, share one number across counter and kitchen, or automate status updates — all of which matter once you take delivery orders at volume. That is the point where teams move to the official API through a platform like Whaterakt.

Can customers place full food orders inside WhatsApp?

Effectively yes: a catalog or storefront link lets them browse and tap items, then confirm the order in chat. You will not get marketplace-style rider tracking, but you keep the customer relationship, the order data and the commission you would otherwise pay an aggregator.

How many promotional messages per week is safe?

One weekly menu broadcast plus occasional festival bursts is a rhythm most customers tolerate well. Watch blocks and reports: if they climb after a send, your frequency or your targeting is wrong, and Meta's quality systems will eventually act on it.

Do I pay for order-status templates?

Yes. Meta charges per delivered template conversation, including utility templates, at rates that vary by category and country. Per-message costs are small, but multiply them by order volume — most restaurants still find it cheaper and better-delivered than order-status SMS.

Can I send food photos in templates?

Approved templates support images, headers and buttons, so one strong photo plus a "View menu" button is standard practice. Keep media light: heavy headers load slowly on budget phones and occasionally slow down template approval.

How do we handle Friday-night volume without dropping orders?

Keyword auto-replies for instant menu delivery, assignment rules so every new chat lands on a named person, and saved replies for standard confirmations. Add a short handover note at shift change so the next shift inherits context, not just an open thread.

Wrap-up

Restaurants win on WhatsApp by separating the two lanes — live order-taking inside the window, status by utility template — and automating everything customers should never have to wait for: confirmation, dispatch, booking reminders, feedback. The flows above are deliberately boring; boring is what survives a Friday rush. Start them on the free plan and scale up from Whaterakt pricing when order volume demands it.