WhatsApp for Indian restaurants — the 2026 operator playbook.

Triggered on every booking confirmed by phone, walk-in waitlist, web widget, or aggregator. The flow sends a T-24h utility template with one-tap confirm/reschedule/cancel buttons, and a T-2h reminder with the table number, cover count, and a Razorpay UPI deep-link if an advance is configured (typical ₹250–₹500 per cover for prime-time weekend slots in Mumbai BKC, Bangalore Indiranagar, Delhi Khan Market).

Measured on a 14-outlet casual-dining cohort across Mumbai, Pune and Bangalore (Jan–Mar 2026): weekend no-shows compressed from 18% to 6%, freed roughly 4 prime-time tables per Friday and Saturday per outlet, and the advance-payment funnel converted 41% of high-risk first-time bookings.

Cost on RichAutomate: ₹0.115 utility conversation. A single saved no-show on a ₹3,200 average prime-time cover yields ~₹28,000× ROI on the message cost.

Triggered Day-7 and Day-21 after a customer's last order, scoped by cuisine cluster and average order value. The flow opens with a question-first headline ("Last time you loved the dum biryani — want it again tonight?"), renders the previous cart inside a Meta Native Flow, and closes with a Razorpay UPI link. Delivery is routed via the restaurant's own rider pool or Dunzo/Porter at flat rates, never via Zomato/Swiggy where 20–30% commission is bled per order.

A 6-outlet North Indian QSR chain in Pune ran this flow Feb–Apr 2026 against a control branch on aggregators only: direct re-order share moved 0% → 38% within 90 days, contribution margin per direct order improved ₹68 (saved aggregator commission net of WhatsApp + Razorpay + rider cost), and the chain renegotiated its Zomato slab one tier down because its aggregator dependency had visibly fallen.

Cost on RichAutomate: ₹0.78 marketing conversation. Break-even at one direct order saved every ~60 messages — typical hit-rate is 4-7% on cohort-segmented sends, well above break-even.

Triggered T+45 minutes after the bill is settled (POS-side webhook from Petpooja, Posist or urbanpiper). The flow asks one tap question ("How was tonight, 1–5?"), branches: 4–5 stars get a one-tap deep-link to Google Maps + Zomato review; 1–3 stars get an empathic apology, a free starter on the next visit (loaded as a coupon on the loyalty record), and a private escalation to the outlet manager's WhatsApp.

A 9-outlet premium-casual chain in Delhi NCR + Gurugram ran this flow Q1 2026: WhatsApp NPS response rate 38% (vs 9% on email control), 41% of would-be negative public reviews were intercepted into private channels, and Google rating climbed 4.1 → 4.4 across the cohort over 11 weeks.

Cost on RichAutomate: ₹0.115 utility conversation. The flow is utility-categorised because it is a post-transaction service notification.

Every bill closure pushes the loyalty card balance, the points earned on that visit, and the next-tier threshold into the customer's WhatsApp thread. Tier upgrades fire a marketing template with a redeemable voucher and a Razorpay-backed renewal-fee prompt if the program is paid. The loyalty record lives inside RichAutomate's tenant database with DPDP-compliant consent, retention and erasure handling.

Measured on a 22-outlet North Indian + South Indian multi-format chain (Hyderabad, Bangalore, Chennai) over Oct 2025 – Mar 2026: enrolled-customer visit frequency 1.6× the control cohort, average ticket size at tier-2 and tier-3 customers +18%, lapsed-customer reactivation (90+ days dormant) 23% on the "we miss you" template at a typical ₹0.78 cost.

Integration surface: Petpooja CRM webhook, Posist Loyalty API, urbanpiper Atlas customer object. No POS? RichAutomate ships a thin loyalty engine that runs purely off the WhatsApp + Razorpay record.