MSG91 vs Wati: Which is Better in 2026?

The short answer

Pick MSG91 if your burn shows up as OTP SMS lines and DLT templates before WhatsApp ever gets a meeting invite. Pick Wati if WhatsApp is already where revenue happens — support queues, catalog replies, agents bumping into each other on one number — and you’d rather not hire an engineer to make chat usable.

For most Indian SaaS teams we’ve watched (including ours for stretches): heavy transactional SMS + API-led stacks skew MSG91. Customer-heavy WhatsApp ops with non-dev owners skew Wati. One wins on rupees per million pings; the other wins on sanity per agent shift.

Where MSG91 actually wins

Indore isn’t a flex on LinkedIn. It shows up when your CFO asks why ₹62L GMV produced ₹1,23,400 in payment-gateway MDR and someone quietly adds another lakh for messaging — and you still need DLT headers that don’t get scrubbed at 2am.

MSG91 is built like plumbing: SMS API first, WhatsApp as another pipe, voice and email bolted where enterprises still ask for them. Wallet recharge annoys marketing; finance teams oddly prefer it.

• OTP flows at scale (think 8–15 lakh verifications a quarter): per-SMS economics beat subscription SaaS that bills [USD] before you’ve sent a broadcast.
• One vendor for SMS + WhatsApp + voice when logistics or BFSI compliance wants audit trails and Indian-hours escalation — IST window Mon–Sat 10am–7pm, GST visible on wallet loads (messy? Yes. Predictable? Often).
• RCS and promotional lanes matter when Meta conversation billing feels arbitrary next to RBI’s push on tokenisation hygiene — you still need receipts and reminders that aren’t all inside WhatsApp’s pricing circus.

Counter-example: if your “engineering resource” is a founder copy-pasting JSON into Postman once a quarter, you’ll hate the inbox. MSG91 won’t mother your agents through a shared queue the way a WhatsApp-first product will.

Where Wati actually wins

Hong Kong on the letterhead, India in the Zoom noise — Wati sells polish: shared inbox, KnowBot (their builder), drip-ish campaigns without sounding like a lecture from a vendor deck.

We asked four founders who’d switched off the consumer WhatsApp Business app; three cited agent collisions before they cited price.

• Multi-agent support with tagging beats spreadsheet reconciliation when Diwali sale tickets spike.
• Shopify/WooCommerce-shaped teams get commerce-shaped defaults — catalog, broadcasts, click-to-WhatsApp — without drafting an RFC.
• Non-dev ops can ship a usable bot; documentation reads like someone wanted readers to finish the page.

Five beats four on purpose here: USD sticker shock is real (Growth [USD] ~₹4,200/mo before Meta), but “hours saved arguing in internal Slack” isn’t on the invoice — until it is.

Counter-example: pure SMS OTP at crore-scale monthly volume? You’ll bleed versus Indian CPaaS unit rates. Wati isn’t pretending to be MSG91’s SMS backbone.

Pricing, in INR, no spin

MSG91 (mostly INR-native): SMS roughly ₹0.15–₹0.30 per message depending on route/tier; WhatsApp = Meta’s charges + about ₹0.10 platform fee per message (their stack sits on Meta rails — you’re not escaping Meta’s arithmetic). Wallet is prepaid; GST hits recharges and usage. UPI for top-ups helps.

Wati [USD]: Growth $49/mo — ballpark ₹4,080–₹4,300 at typical cards/settlement rates (carry FX spread mentally). Pro $99, Business $299. Users scale by plan; Meta bills conversations separately — that line item bites harder than founders model on day one.

Worked scenario (rounded, blunt):
Suppose you’re doing ₹50L GMV/month, average ticket ₹1,200 → ~417 orders. Assume 2 transactional WhatsApp touches per order (confirmation + dispatch) → 834 Meta-priced conversations/month if Meta buckets them as charged sessions (your actual bill varies by windowing — treat this as order-of-magnitude).

• Wati-side fixed: ~₹4.2L/year subscription alone (Growth) before Meta — ₹35k/month band — plus conversation charges (depends on category + country pricing Meta publishes; India rates move — budget ₹15k–₹45k/month for this volume unless you’re mostly utility windows).
• MSG91-side variable: if those touches map closer to messages on their meter (still Meta underneath for WhatsApp), think platform fee 834 × ₹0.10 ≈ ₹83/day-ish on platform fees alone — ~₹2.5k/month platform-only math — plus Meta’s portion, plus SMS if you’re still blasting OTP on SMS separately.

Hidden costs to pencil:

• FX + GST friction: Wati’s [USD] billing sometimes invites reverse charge / GST headaches for Indian purchasers — check with your CA (especially vs MSG91’s straightforward INR GST trail).
• Wallet recharge ops: MSG91 — finance approvals for recurring wallet loads; failed recharge mid-campaign is a real outage class.
• Integration rework: Shopify deep workflows vs CPaaS-style APIs — time-to-ship isn’t free either way.
• Settlement cycles: gateway settlement vs prepaid messaging wallets — working capital shows up in different rows.

Verdict on maths alone? High-automation, API-heavy, SMS-heavy → MSG91 tends to win unit economics at serious throughput. Agent-heavy WhatsApp org → Wati’s subscription can still net out if you measure rework avoided.

What we’d actually use each for

Case A: Twelve-person D2C on Shopify, ₹40L MRR, peak agents 6, catalog queries eating afternoons — Wati. You’ll pay [USD] subscription breathing tax. You’ll also stop losing refunds because three humans replied different things.

Case B: BFSI-ish app — OTP SMS non-negotiable, DLT templates audited — occasional WhatsApp for collections reminders — MSG91. Not glamorous. Works when regulators sneeze.

Case C: Logistics — SMS POD pings + WhatsApp customer ETA bot — split brain honestly: MSG91 for SMS throughput economics; Wati only if ops insists on inbox KPIs you can’t hack together cheaply.

Indian fit (GST, UPI, IST, support)

MSG91: INR-first psychology, UPI on wallet (per their positioning — verify at signup), GST on recharge feels domestic-scented even when annoying. Support IST window — not 24×7 romance.

Wati: no UPI emphasis (feature matrices suggest cards/international rails mindset — double-check billing portal). GST may ride reverse charge — foreign-supplier classic India headache since e-invoicing thresholds tightened discipline across vendors. Support billed 24×5 chat with IST overlap — better than US-Pacific pretending India doesn’t exist; worse than “walk into Indore office” vibes.

One blunt read: Wati sometimes presents like a polished outsider who learned Indian SMB motions well; MSG91 presents like the vendor your ISP guy already knows.

Migration: what’ll bite you

MSG91 → Wati:
Conversation windows reset semantics differ — don’t assume webhook payloads drop-in identical. Broadcast consent lists — your opt-in proof format might need re-mapping for how Wati segments contacts. Shopify plugin depth: rebuilding flows loses subtle triggers until QA burns a weekend. SMS-capable workflows vanish — reroute OTP SMS via MSG91 parallel spend if you still need both (dual vendor tax).

Wati → MSG91:
You lose “pretty inbox” unless you rebuild atop WA Cloud API yourself — team UX downgrade risk. Chatbot trees don’t teleport neatly — expect rebuild + regression testing on quick replies. GST bookkeeping shifts from reverse-charge headaches toward INR invoice familiarity — still painful mid-quarter.

Exports: neither migration is “download CSV and nirvana” when delivery receipts tie into refunds/chargebacks — history fidelity becomes political internally.

What we’d pick

If forced blindfold off? MSG91 where messaging volume is infrastructure — OTP + transactional backbone — and WhatsApp is accessory layers wired by developers.

Wati where WhatsApp is storefront + service desk — humans stepping on each other without tooling debt kills gross margin faster than Meta conversation unpredictability.

Still chewing on one awkward truth from last quarter’s RBI noise around tokenisation narratives — reminders everywhere; messaging budgets balloon quietly — who owns WhatsApp spend when finance moves OTP SMS first — still your inbox PM or still infra?

Things people actually ask

“MSG91 really cheaper if we push ₹2 cr annual messaging?”
Usually yes on SMS lanes vs subscription-led stacks — pricing ladders reward lakhs of sends; WhatsApp still inherits Meta’s bill whatever romantic notion your BD slide had.

“Wati ~₹4.2k/month — can’t we just expense it?”
You can — until Meta adds five-digit conversation variance during festival spam weeks; model Meta separately or your spreadsheet lies politely.

“Do we redo GST templates switching vendors?”
Often yes-ish — classification shifts between INR domestic invoices → reverse charge ambiguity — ask CA before migration cutover; don’t discover at reconciliation.

“Shared inbox worth losing unified SMS?”
If agents duplicate replies thrice weekly — yes; if SMS OTP is your crown jewel — no — hybrid routing exists but governance gets ugly.

“Indore support actually picks up?”
Within published IST window — enterprise escalations exist — midnight miracles aren’t contractually promised either side.

“We’re on Meta BSP via MSG91 — migrate Wati breaks BSP contracts?”
Expect number migration friction, template resubmission churn, webhook endpoint rotations — budget calendar days, not Jira hours.

“UPI wallet vs card USD — cashflow feels?”
Prepaid INR wallet feels poorer digitally — USD subscriptions hit forex silently — pick poison aligned with treasury temperament.

“DLT drama worse where?”
MSG91 lives SMS regulatory narrative daily — Wati helps WhatsApp template discipline — different nightmares.

“RCS matters for us?”
MSG91 mentions RCS explicitly — if Android-heavy promo matters — factor separately from WhatsApp inbox ROI math.

“Which dies first — ops patience or CFO spreadsheet?”
Whichever metric your standups ignore until Diwali week — measure both — still unresolved here honestly.