WhatsApp is the cheapest channel an Indian restaurant has access to. The catch: ordering, marketing, and loyalty all sit on three different stacks. Here's the 2026 build; what to use for each, realistic costs, ROI math, and the operational mistakes that kill performance.
The three WhatsApp use cases
- Ordering; customers browse menu, place order, pay in WhatsApp. Powered by Catalog + Click to WhatsApp ads or via dotpe / Petpooja / UrbanPiper WhatsApp ordering.
- Marketing; broadcasts for new dishes, festival menus, offers. Needs the WhatsApp Business Platform API + a BSP.
- Loyalty + CRM; 1:1 communication, birthday wishes, post visit feedback, win back campaigns. Same API stack.
Pick your stack
| Use case | Stack option 1 | Stack option 2 |
|---|---|---|
| Ordering only | WhatsApp Business app + Catalog (free) | dotpe (₹0-2,500/mo + transaction fee) |
| Ordering + marketing | Wati (₹2,500-5,000/mo) | AiSensy (₹1,500-4,500/mo) |
| Full CRM + automation | Wati Pro (₹5k-12k/mo) | Interakt (₹4k-10k/mo) |
| Restaurant specific | Petpooja Connect (paired with POS) | UrbanPiper WhatsApp module |
The economics
Meta charges per ‘conversation’; a 24 hour window with a customer. India 2026 rates:
- Marketing conversations; ₹0.88-1.32 per conversation
- Utility conversations (order confirmations, OTPs); ₹0.13-0.18
- Authentication conversations; ₹0.18-0.22
- Service conversations (customer initiated within 24h); Free
BSP subscription on top; ₹1,500-5,000/month for the platform. Total monthly cost for a casual dining with 2,000 contacts running weekly marketing broadcasts: ₹4,500-8,500. Compare to Zomato/Swiggy ads at ₹15,000-40,000/month for similar incremental order volume.
Build sequence for a single outlet restaurant
- Set up WhatsApp Business app (Day 1); collect catalog, set greeting, set away message.
- Migrate to Business Platform API + BSP (Month 1, when contact base > 300); Wati or AiSensy.
- Build customer database; collect WhatsApp number at billing for dine in; via order forms for delivery.
- Segment the list; first timers, regulars (3+ visits in 90 days), churned (no visit 60+ days), VIPs (spend top 10%).
- Start broadcasts (Month 2); weekly. New menu launches, festival specials, offers.
- Layer in automations; birthday wishes, post visit thank you, abandoned order recovery, win back at day 45.
- Add WhatsApp ordering (Month 3-4); catalog + UPI payment. Shift 8-15% of orders here.
Broadcast playbook
- Frequency; 1 broadcast per week max. 2+ kills open rates and drives unsubscribes.
- Time; Friday 6-7pm and Sunday 11am-12pm have highest engagement for India F&B.
- Format; image + 2 line caption + clear CTA (‘Reply ORDER to place’). Don't use long messages.
- Personalisation; first name in the message lifts response 20-35%.
- Compliance; opt in is mandatory; non opted contacts will get your BSP banned within 30 days.
ROI math
Casual dining, 2,000 WhatsApp contacts, weekly broadcast:
- Cost: ₹1,800 × 4 broadcasts = ₹7,200/month conversation fees + ₹3,500/month BSP = ₹10,700
- Open rate: 70-85% (vs 18-25% email)
- Click + order: 2-5% of opens → 35-90 incremental orders/month at ₹620 average ticket = ₹21,700-55,800 incremental revenue
- Net contribution at 30% food cost: ₹15,200-39,000
- ROI: 1.4× to 3.6× monthly
Operational mistakes
- Broadcasting without opt in; fastest way to a permanent ban
- Sending every special, every day; open rate decays to 20% in 4 weeks
- No segmentation; generic blasts to first timers + regulars + churned customers feel impersonal
- No measurement; most owners can't say which broadcast drove which incremental orders. Tag broadcasts with unique discount codes or order numbers