On this page
In short
- Menu and ordering with a Flow form and a payment link, commission-free for direct customers
- Reservations with reminders, order status updates and review requests as utility messages
- Weekend offers to opted-in diners only; a QR on the table tent, bill and packaging brings customers in
Restaurants and cloud kitchens use WhatsApp for five jobs: the menu and orders, table reservations, order status, review requests and the weekend offer. VGraple CRM runs the first four as utility messages from a QR on the table tent, the bill and the packaging, and keeps the offer to diners who opted in; the outcome is commission-free direct orders, fewer no-shows on reservations and reviews that reach a manager before they reach Google.
The problem in numbers
A restaurant's phone rings with orders and reservations at the busiest moments, aggregator commissions take a large slice of every delivery, and reviews arrive on Google before the manager hears the complaint. Customers already use WhatsApp to ask "are you open?" and "can I book a table?"; the change is answering automatically, taking the order with a payment link, reminding the reservation, and asking for the review two hours after the meal. Every one of those is a utility message at Rs 0.115 or free inside the window the customer opened by scanning the QR.
Six things restaurant teams automate on WhatsApp
1. Menu and ordering
Any first message or the keywords menu and order send the menu as a list, a catalog message or a PDF; a Flow form collects items, quantities, delivery or pickup and the address; a payment link confirms the order and a utility template gives the expected time.
rest_order_confirmed (utility)
Hi {{1}}, order {{2}} at {{3}} is confirmed: {{4}}. Expected {{5}}. Reply if anything changes.
Flow builder with WA Flows, the catalog and payments.
2. Order status
Stage changes send utility updates: preparing, out for delivery, ready for pickup; the kitchen sees the order in the inbox with the contact's history.
rest_out_for_delivery (utility)
Order {{1}} is on its way and should reach you by {{2}}.
Stage automation under automation rules.
3. Reservations with reminders
A table keyword opens a flow: date, time, guests, name; the appointment is created; a utility confirmation and a reminder before the slot; a no-show sends a rebook message.
rest_table_confirmed (utility)
Hi {{1}}, your table for {{2}} at {{3}} is confirmed for {{4}}. Reply to change it.
4. Review requests that reach a manager first
Two hours after delivery or the reservation slot, a utility request with buttons; Great sends the Google link, Okay asks what could be better, Not good assigns a manager.
rest_review_request (utility)
Thanks for dining with us today, {{1}}. How was it? Tap a button below.
Timers and quick reply routing in the flow builder.
5. Consent from the QR
The QR on table tents, bills and packaging opens a chat with a prefilled message; the first message is consent for service messages; a YES step collects marketing consent, recorded on the contact.
rest_optin (session, free)
Thanks for visiting {{1}}. Reply YES to get our weekend specials on WhatsApp, or tap Menu to order.
QR code generator and consent capture.
6. Weekend offers to opted-in diners
A marketing template to consenting diners, once a week at most, with an opt-out, sent mid-morning; quiet hours on.
rest_weekend_special (marketing)
Hi {{1}}, this weekend at {{2}}: {{3}}. Reply MENU to see it or STOP to opt out.
Broadcasts with consent and delivery protection.
Feature map
| Job | Feature | Plan |
|---|---|---|
| Menu, ordering and payment | Flow builder, WA Flows, catalog, payments | Free |
| Order status | Automation rules | Free |
| Reservations with reminders | Appointments | Free |
| Review requests | Flow builder, automation rules | Free |
| Consent from QR codes | QR generator, contacts | Free |
| Weekend offers | Broadcasts, delivery protection | Free within Meta limits |
| Desk and kitchen seats | Seats | Starter Rs 1,499 |
| AI for menu questions | AI chatbot | Growth Rs 3,499 |
What it costs
A 60-cover restaurant: 900 direct orders with confirmations and status updates (2,700 utility, Rs 311); 400 reservations with confirmation and reminder (800 utility, Rs 92); 1,300 review requests (Rs 150); two weekend offers to 2,000 opted-in diners (Rs 3,452). Meta's total is about Rs 4,000 a month; VGraple CRM is Free or Rs 1,499 on Starter. Aggregator commission avoided on 900 direct orders at Rs 400 average is Rs 72,000 to Rs 90,000.
A 30-day rollout plan
Week 1. Connect the number (coexistence if the owner's phone must stay); print QR codes for tables and bills; submit the templates; build the menu flow and test it with staff.
Week 2. Ordering for direct customers; reservations flow; review request on delivered orders.
Week 3. Marketing consent through the YES step; first weekend offer to consenting diners; quiet hours set.
Week 4. Review orders by channel, review reply rate, offer read and reply rates and blocks; add the AI for menu questions.
Getting the number ready
Most restaurant businesses already run WhatsApp on the owner's phone, so the first decision is how to connect: coexistence keeps the WhatsApp Business app working on that phone while the team uses the inbox, with up to six months of history imported; an API-only connection suits a new number for the team. Either way, Embedded Signup takes a few minutes, the display name is reviewed by Meta, and business verification in Meta Business Manager lifts the marketing limit from 250 unique recipients a day to 1,000 and beyond. Submit the templates on day one; most are approved within the hour, and the template library has an industry collection ready to submit.
Consent, privacy and the rules that apply
A customer who messages first has consented to service replies and to utility messages about that transaction; marketing needs an explicit yes, recorded with source and date, and an opt-out on every marketing template. VGraple CRM records consent automatically from inbound messages, YES replies, forms, ads and imports, suppresses opted-out and blocked contacts before every send, honours STOP and Meta's app-level opt-out at once, and keeps marketing to United States numbers paused as Meta requires. Personal fields are encrypted at rest, access is by role and team, and the audit log records exports and deletions, which covers India's DPDP Act and GDPR for restaurant data in practice. The opt-in rules guide has the detail.
Numbers to watch each week
First-response time on new conversations (minutes, not hours); the share of enquiries that reach the step that matters for restaurant (a booking, a visit, an order, an enrolment); utility messages sent and how many were free inside open windows; replies to the last marketing send; and blocks on it, which should stay under 0.2 percent. The Analytics page shows them per agent and per campaign on Starter and above; the channel page shows the quality rating and tier, which the blocks feed. A yellow rating is the signal to tighten the segment before the next send, not after.
Common mistakes
- Sending the weekend offer as utility.
- Messaging the aggregator's customers; they did not opt in with you.
- No human path in the ordering flow for allergies and special requests.
- Late-night broadcasts; set quiet hours.
- Forgetting the review step, which is the cheapest marketing a restaurant has.
Why VGraple CRM for restaurant
Flow builder with WA Flows and catalog messages, payment links, appointments with reminders, automation rules on order and appointment events, broadcasts with consent, quiet hours and delivery protection, and the shared inbox for the desk and kitchen are on every plan. The restaurant playbook has the flows and templates in detail.