The WhatsApp API for restaurants is the official Meta WhatsApp Business API, used to run table bookings, direct orders, delivery and COD confirmations, offers to regulars and review requests from one approved business number. On RichAutomate a single outlet sending 3,000 order updates and 500 promos a month pays about ₹1,127 before GST: Meta's own message charges plus a flat ₹0.10 per message, with ₹0 setup.
Updated 7 November 2026. This refresh adds a single-outlet cost example, a WhatsApp ordering section and a list of the restaurant automations worth building first.
Disclosure: this guide is published by RichAutomate, one of the WhatsApp Business API platforms it discusses. Prices for Meta and other vendors were checked on their public pricing pages on 29–30 October 2026; vendors change rates, so confirm on their pricing page before you buy. All figures exclude 18% GST unless stated.
A restaurant does not need a generic chat tool. It needs WhatsApp wired into the parts of the business that leak money: empty tables, missed call-in orders, unconfirmed cash-on-delivery and customers who never come back. This guide covers what Indian restaurants, cafes, cloud kitchens, bakeries, bars and caterers actually need, the criteria that matter, which provider shape fits which kind of restaurant, two worked monthly bills and a one-week rollout plan. Treat every competitor figure as something to verify on their site, and every rupee number as illustrative until you run your own covers and order counts.
WhatsApp API for restaurants: what it actually does
In most Indian cities the customer already has WhatsApp open. They message to ask if a table is free on Saturday, to place a Sunday biryani order, to confirm a cake pickup, or to ask whether the kitchen is still serving. The phone rings during the dinner rush and nobody can pick up; the message sits unanswered and the order goes to the place that replied. That gap between when a guest reaches out and when the restaurant responds is the biggest, cheapest revenue leak in food service, and it is exactly what the WhatsApp Business API closes.
The official API is what lets a restaurant move past the limits of the consumer WhatsApp Business app: automated replies at any hour, reservation and order flows with buttons and lists, broadcasts of the day's specials to opted-in regulars, delivery and pickup confirmations, and review collection after the meal, all on an approved business number with a path to the green tick. Four food-service moments pay for themselves:
- Reservations and waitlist. A booking flow captures party size, date and time without a phone call, sends a confirmation, and nudges a reminder so the table is not held empty for a no-show.
- Takeaway, delivery and COD confirmation. Direct orders skip aggregator commission, and a confirmation step before dispatch cuts the cash-on-delivery returns that quietly eat margin.
- Loyalty and re-ordering. A "reorder your usual" nudge and a festival or weekend special to opted-in regulars brings repeat covers at very low cost.
- Reviews and recovery. A polite post-meal message asking for a Google review, or quietly catching an unhappy guest before they post, protects the rating that decides your next walk-in.
WhatsApp ordering for restaurants in India
WhatsApp ordering means the guest browses your menu, builds a cart and confirms an order inside the chat, without an app download or an aggregator in the middle. For a neighbourhood restaurant or cloud kitchen this is the most direct way to win back orders that would otherwise go through a delivery platform and its commission.
A working WhatsApp ordering setup on the official API has five parts:
- Menu as a WhatsApp catalogue. Dishes, prices and photos load into a catalogue the guest can scroll and add to a cart.
- Order capture. The cart order lands in your inbox with items, quantity and the guest's number, so the kitchen sees a clean ticket, not a typed paragraph.
- Payment or COD choice. Send a Razorpay payment link (when you connect your own Razorpay account) or mark it cash-on-delivery.
- COD confirmation before dispatch. A one-tap "confirm your order" message before the rider leaves cuts fake and forgotten COD orders.
- Order updates. "Order received", "out for delivery" and "ready for pickup" go out as utility templates, which are the cheap category on Meta's rate card.
Most outlets start with a short menu of best-sellers rather than the full card, then grow the catalogue once orders start coming in. For delivery-heavy kitchens, our QSR and food-delivery WhatsApp playbook covers rider updates and peak-hour handling in more depth.
What restaurants actually need from a WhatsApp Business API
Running WhatsApp for a kitchen is not the same as running it for a software company. Staff are on the floor, not at a desk; volumes spike at lunch and dinner; and the people answering messages change shift. The needs that matter most for food and beverage:
- Low platform fee. Restaurant margins are thin. A per-seat or monthly platform fee on top of message cost is the first thing that makes WhatsApp feel expensive.
- A no-code flow builder. You should be able to build a reservation flow, an order menu and a review nudge yourself, not file a ticket with a developer. Buttons, lists and simple branching cover most restaurant journeys.
- A shared inbox the floor can use. Several staff need to see and reply to the same number across a shift, with a clean handoff so a guest is not answered twice or not at all.
- Multi-outlet management. If you run two cafes or a small group, you want each outlet number manageable from one place rather than juggling logins per branch.
- Predictable per-message cost. Meta has billed per delivered message, not per conversation, since July 2025. A flat, knowable platform rate on top lets you budget the channel against covers.
- Consent built in. Opt-in capture, easy opt-out and clean approved templates keep your number healthy and keep you on the right side of India data-protection expectations.
Restaurant WhatsApp automation: the flows to build first
Restaurant WhatsApp automation works best when it handles the repetitive questions and confirmations, and hands anything unusual to a person. These are the flows that earn their keep, roughly in the order most outlets build them:
| Automation | Trigger | What it saves |
|---|---|---|
| Instant welcome + menu | Guest sends "hi" or taps a click-to-WhatsApp link | Replies at 11 pm without staff; shows menu, timings, location |
| Table booking | "Book a table" button | Phone calls during service; double bookings |
| Booking reminder | Delay step a few hours before the slot | No-shows on Friday and Saturday nights |
| Order confirmation + updates | New cart order | "Where is my order?" calls |
| COD confirmation | COD order before dispatch | Wasted rider trips and food on fake orders |
| Review request | A set time after the visit or delivery | Forgotten reviews; catches complaints privately first |
| Weekend / festival special | Scheduled broadcast to opted-in regulars | Empty Tuesday tables; slow monsoon weeks |
| Keyword auto-replies | "timings", "address", "veg", "parking" | The same five questions answered fifty times a day |
Before you submit templates for the confirmation and promo messages, check the category: order and booking updates should be written as utility, offers as marketing. A promo worded as a "confirmation" is likely to be re-categorised or rejected.
Built-in WhatsApp table booking on RichAutomate
RichAutomate ships a dedicated restaurant table-booking step for its flow builder, so a reservation flow does not have to be assembled from scratch:
- Booking form inside WhatsApp. The guest picks date, time and party size in a native WhatsApp Flows form instead of typing back and forth.
- Slots from your own hours. You set opening and closing time, slot length and a buffer between seatings, and only valid slots are offered.
- Table allocation. An allocator seats the party at a suitable table and can combine tables you have grouped for larger parties.
- Optional advance payment. Ask for a Razorpay advance to cut no-shows, and choose whether it is adjusted against the final bill.
- Confirmation and manager alert. The guest gets a WhatsApp confirmation and the manager gets an alert on their own WhatsApp number. A Google Sheets step in the same flow can log each booking.
See the WhatsApp restaurant table booking feature for screenshots of the flow.
Criteria to compare WhatsApp Business API providers for restaurants
Score any provider against the things that move a restaurant P&L, not the long enterprise feature list:
Get the India 2026 WhatsApp BSP price comparison
Wati vs AiSensy vs Interakt vs RichAutomate: Meta rates, platform fees and hidden costs, side by side. We send it to your WhatsApp in a minute.
| Criteria | Why it matters to a restaurant | RichAutomate |
|---|---|---|
| Platform fee | On thin food margins, any fixed fee on top of messages makes the channel feel costly | ₹0 setup; ₹0.10/msg platform fee; plans ₹499 / ₹899 / ₹1,199 a month add seats and features |
| No-code flow builder | Floor managers build reservation and order flows without a developer | Visual builder with buttons, lists, delays and branching, plus a table-booking step |
| Shared inbox | Several staff answer one number across a shift with clean handoff | Shared team inbox with assignment and handoff |
| Multi-outlet management | Run several branch numbers from one place as you grow | Several outlet numbers under one account; extra numbers ₹399/mo |
| Per-message transparency | Budget against covers and orders, not a mystery wallet | Client Pay: Meta bills you direct, plus a flat ₹0.10/msg |
| Order and payment flows | Take direct orders and confirm COD without aggregator commission | WhatsApp catalogue with cart orders; Razorpay links via your own Razorpay account |
| Consent and templates | Opt-in, opt-out and approved templates keep the number healthy | Opt-in capture, opt-out handling, template management built in |
The platform fee is the lever restaurants underweight most, because the per-message rate looks small in isolation. The cost examples below show why.
Want to see a booking and order flow on your own number? Start the 14-day free trial, with ₹0 setup, and build the first flow in an afternoon.
WhatsApp API cost for one restaurant outlet (monthly)
Meta charges per delivered template message by category; RichAutomate adds a flat ₹0.10 per message on Client Pay, and Meta bills its share directly to your own account. Here is a typical single outlet: 3,000 order updates (utility) and 500 promos (marketing) a month.
| Line | Calculation | Monthly, before GST |
|---|---|---|
| Meta: utility (order and booking updates) | 3,000 × ₹0.115 | ₹345.00 |
| Meta: marketing (specials, offers) | 500 × ₹0.8631 | ₹431.55 |
| RichAutomate Client Pay fee | 3,500 × ₹0.10 | ₹350.00 |
| Total | ₹1,126.55 (≈ ₹1,329 with 18% GST) |
That works out to roughly ₹0.32 per message on average, or about ₹0.215 per order update and ₹0.96 per promo before GST. Promos are where the money goes: 500 marketing messages cost more at Meta than 3,000 order updates. If budget is tight, send fewer, better-targeted offers rather than cutting confirmations.
Second worked bill, with competitor rates (checked October 2026)
A slightly more promo-heavy outlet: 2,200 utility and 800 marketing messages a month. Competitor lines use their listed rates as checked on 29–30 October 2026; verify on their sites before deciding.
| Line | Calculation | Monthly, before GST |
|---|---|---|
| Meta: utility (confirmations, order updates) | 2,200 × ₹0.115 | ₹253 |
| Meta: marketing (specials, offers) | 800 × ₹0.8631 | ₹690.48 |
| RichAutomate Client Pay fee | 3,000 × ₹0.10 | ₹300 |
| RichAutomate Client Pay total | ₹1,243.48 (≈ ₹1,467 with 18% GST) | |
| AiSensy listed rates | 2,200 × ₹0.145 + 800 × ₹1.09, plus plan (see their pricing page) | ₹1,191 + plan |
| Interakt Growth | ₹2,799 + 800 × ₹0.949–₹0.970, plus utility at their rate | ₹3,558–₹3,575 + utility |
| WATI Growth | ₹2,699 a month (3 users, billed quarterly) + template charges | ₹2,699 + messages |
Guest questions answered by staff inside an open 24-hour window are service messages: each number gets 1,000 free a month, then ₹0.115 each. If you need more logins, Starter (₹499 a month, 2 seats) or Pro (₹899, 5 seats) sits on top of the RichAutomate line. Being fair: AiSensy's listed per-message rates land close to Client Pay before its plan fee; the gap to weigh is the fixed monthly plan, which a quiet month still pays.
The point is the shape, not one magic number: a flat per-message line means a quiet monsoon month costs less and a Diwali rush costs more, in proportion to what you send. Run your own outlet numbers through the WhatsApp API cost calculator before you commit, and confirm Meta's current rates on Meta's pricing page.
Which provider fits which restaurant
RichAutomate fits an independent restaurant, cafe, bakery, bar, cloud kitchen or small multi-outlet group that wants WhatsApp doing real work (reservations, direct orders, COD confirmation, loyalty broadcasts and reviews) with cost that tracks volume. The no-code builder lets a manager set up the flows, and the multi-outlet inbox grows with you.
A single-purpose aggregator inbox tool may be enough if all you want is a shared inbox for delivery-aggregator chats and a couple of canned replies, with no reservations, direct ordering or broadcasts. Check whether it runs on the official WhatsApp Business API and what it charges per seat (as of 2026, verify on their site), because seat fees add up across a busy floor.
An enterprise CPaaS may fit better if you are a large national chain that needs a deep two-way integration with a specific POS or aggregator, SMS, voice and email behind one API, and a named account manager. Enterprise platforms such as Gupshup (as of 2026, verify on their site) are built for that managed relationship.
How a restaurant goes live in one week
You do not need to build everything at once. Ship the two or three flows that move money first, then add the rest:
- Day 1: start the trial and connect your number. Use the 14-day free trial with 100 free credits, then connect or migrate your restaurant number onto the official Meta WhatsApp Cloud API. Going live depends on Meta verification, usually a day or two, but treat that as an estimate.
- Day 2: reservations and order menu. Set up a booking flow (party size, date, time, confirmation, reminder) and a takeaway order flow from your menu. These two carry most of the value.
- Day 3: confirmations and reminders. Create utility templates for booking confirmation, order-ready and COD confirmation, and submit them for Meta approval.
- Day 4: the floor inbox. Put shift staff into the shared inbox, assign each conversation to one person so messages are not double-answered, and write quick replies for common questions (timings, address, veg options).
- Day 5: loyalty and reviews. Add an opted-in specials broadcast and a polite post-visit review nudge. Capture opt-in at booking and honour opt-out from the first message.
- Days 6–7: watch and tune. Read the first few days of real conversations, fix the points where guests drop off, and only then add festival campaigns or a second outlet.
For the complete picture across reservations, FSSAI-aware messaging and loyalty, see the WhatsApp for restaurants India guide.
Connecting your POS: Petpooja and others
Whichever provider you use, the official WhatsApp Business API sits underneath, so message types, template rules and Meta policies are the same across tools. What changes is the commercial model and how the platform connects to the systems you already run. Many Indian restaurants bill on a POS such as Petpooja; if that is you, see how to connect Petpooja with WhatsApp for bills and feedback, using an order push, Make or a report export.
The bottom line
For an Indian restaurant, cafe, cloud kitchen or small F&B group, the right WhatsApp API provider is the one that turns the channel into reservations, direct orders, repeat covers and protected reviews, at a cost you can predict. RichAutomate offers ₹0 setup, a flat ₹0.10 per message on Client Pay with Meta billing you direct, plans from ₹499 a month, a 14-day free trial, a no-code flow builder, a shared multi-outlet inbox, and consent and template handling built in. Pick by the shape of your restaurant, not by hype. One caveat: no vendor can guarantee against a WhatsApp restriction. What keeps a restaurant number healthy is relevant, consented, well-spaced messaging on the official API with an easy opt-out.
Ready to put WhatsApp on the menu?
Tell us how many outlets you run and your rough monthly covers, and we will model the real cost with you and show a reservation, order and review flow live. WhatsApp us at +91 81603 11319, or book a 30-minute demo.