On 1 January 2026, Meta quietly rewrote the economics of WhatsApp Business in India. Most SMB owners noticed because their February invoice arrived 20–40% higher than December's, and nobody at their BSP (Business Solutions Provider) sent a clean explainer. Some only noticed in March, when their CFO asked why the WhatsApp line item had doubled.
If you run a 5–500 employee business in India and you use WhatsApp Business API — through AiSensy, Interakt, WATI, Gallabox, DoubleTick, or any other BSP — this post is for you. The pricing model changed in three structural ways, every Indian rupee figure is different from 2025, and there are very specific things you need to do this week to stop bleeding money.
We'll cover:
- What actually changed on 1 January 2026
- The new India per-message rates (verified against Meta's own pricing docs)
- How AiSensy, Interakt, and WATI repriced
- Three real revenue impact scenarios
- The migration checklist you can run today
What changed: from per-conversation to per-message
Until 31 December 2025, Meta charged Indian businesses by conversation. A "conversation" was a rolling 24-hour window that started the first time you sent a marketing or utility template to a user — and within that window, you could send as many follow-up messages as you wanted at no extra cost.
This was generous. It rewarded businesses that ran longer back-and-forth conversations and punished spammy one-shot blasters.
Meta killed it. Effective 1 January 2026, the platform moved to per-template-message billing. Every single template you send is metered. Conversations are no longer a billing unit at all.
The structural implications are sharp:
- Cost per active user goes up if you run multi-step nurture campaigns. The old model gave you free additional messages inside the 24-hour window; the new one bills each one.
- Cost per active user goes down if you only ever send one transactional notification per event (OTP, order shipped, payment receipt). You were paying for a "conversation" anyway under the old model.
- The free 24-hour customer service window still exists for service messages (your free-text replies to a customer who messaged you first). This is the single most important thing most SMB owners don't realise.
The new India rates (May 2026)
Verified against Meta's developer pricing page and three major Indian BSPs:
| Message category | Rate per message (INR, Meta base) | What it covers | |---|---|---| | Marketing | ₹0.8631 | Promotions, offers, abandoned cart, win-back | | Utility | ₹0.115 | Order confirmations, shipping updates, appointment reminders | | Authentication | ₹0.115 | OTPs, login codes | | Service (24-hr window reply) | ₹0 (free) | Your reply to a user-initiated conversation, within 24 hours |
Two facts that change the math:
- Marketing rates rose ~10% from ₹0.7846 (late-2025 base) to ₹0.8631 (Jan 2026), citing "sustained high demand" in India.
- All rates attract 18% GST. Both on Meta's charges and on your BSP's platform fee. Your effective marketing cost per message is closer to ₹1.02 landed.
If your BSP is showing you a marketing rate above ~₹1.10 per message, they are taking a healthy markup. That is not automatically wrong, but you should know.
How the major BSPs repriced
This is the part you won't find in any one place, so we did the comparison. Pricing as of mid-May 2026:
AiSensy
Re-launched their pricing in February 2026 with a "Meta cost passthrough + flat platform fee" model. Platform plans start at ~₹999/month and go up by feature tier. Meta charges are billed at near-cost, with the marketing rate appearing at ~₹0.88 per message. Better for higher-volume senders.
Interakt
Held their old per-conversation pricing internally for grandfathered customers until end of February, then forced everyone onto the new per-message model. Their marketing markup runs closer to ~₹1.09 per message, but their CRM and shared-inbox features are tighter than most.
WATI
Moved cleanly on 1 January with full passthrough plus tiered platform fees (~₹2,499/month for the standard plan). Their MCP integrations rolled out in Q1 2026, which matters if you want AI agents talking to your WhatsApp inbox.
The headline: all three are now in a tight pricing band for the Meta component. The differentiation is the platform fee, the inbox UX, the campaign builder, and the agent/MCP integrations.
Three real revenue impact scenarios
We've worked through these with real SMB clients in Bangalore. Numbers are illustrative; the pattern is real.
Scenario 1: A Koramangala SaaS startup running a 5-step onboarding nurture
- Old model (per-conversation): 1,000 trial signups × 1 conversation each × ~₹0.78 = ₹780/month for the entire 5-touch sequence.
- New model (per-template): 1,000 trial signups × 5 templates × ~₹0.86 = ₹4,300/month.
- Impact: 5.5× cost increase. This is the worst-case profile under the new pricing.
Their fix: collapse three of the five touches into a single, richer template, then push later touches into the service window (free) by triggering them from user replies. Net cost dropped back to ~₹1,400/month.
Scenario 2: A Whitefield-based D2C brand running cart-abandonment
- Old model: 2,000 cart-abandon events × 1 conversation each × ~₹0.78 = ₹1,560/month.
- New model: 2,000 events × 1 marketing template × ~₹0.86 = ₹1,720/month.
- Impact: ~10% increase. Negligible. Single-message-per-event campaigns are barely affected.
Scenario 3: An Indiranagar clinic chain running appointment reminders + post-visit feedback
- Mostly utility messages at ₹0.115 each — virtually unchanged in unit economics.
- Their cost moved from ~₹3,200/month to ~₹3,250/month. Effectively flat.
The pattern is clear: the new pricing punishes long template-based nurture sequences and is neutral or favourable for single-shot transactional messaging.
The 24-hour service window is where the money is
Here is the single most under-exploited fact about WhatsApp Business pricing in India: whenever a customer messages you first, you have 24 hours of completely free messaging back to them. Not cheaper. Free.
This is gold. It means the cheapest possible WhatsApp Business architecture for an Indian SMB is:
- Use a single marketing template to start a conversation (₹0.86 + GST).
- Engineer the template so users naturally reply (a question, a quiz, a "reply YES to confirm").
- Once they reply, run your entire 24-hour follow-up sequence as service messages — ₹0.
- If you need to re-engage them after 24 hours, send one more marketing template (₹0.86) to restart the window.
We've installed this pattern for half a dozen Bangalore SMBs and it typically cuts WhatsApp spend by 40–70% without reducing message volume. The flip side: it requires copywriting discipline and a CRM that knows which window each contact is in. This is exactly the kind of work our WhatsApp automation team handles for clients.
The migration checklist (run this week)
If you do nothing else after reading this post, do these eight things this week.
1. Pull your last three invoices
Pull December 2025, February 2026, and April 2026. Look at the WhatsApp line item. If April is more than 20% higher than December and your message volume hasn't grown, you are bleeding money. Continue.
2. Categorise your templates
Open your BSP dashboard. List every approved template. Mark each one as Marketing, Utility, or Authentication. Most SMBs discover at least one template mis-categorised as Marketing when it could legally be Utility — saving you ~85% per send on that one template.
3. Audit your sequences
For every multi-step sequence, ask: "Can this be one richer message?" Sequences designed for the old per-conversation model are silently expensive now. Collapse where you can.
4. Move discretionary follow-ups inside the 24-hour service window
Anything that isn't time-critical and could be triggered off a user reply should be. This is the single biggest lever.
5. Check your BSP markup
Take your last invoice. Divide marketing messages spend by marketing messages count. If you are over ~₹1.20 per message, ask your BSP to justify the markup or quote you the passthrough rate.
6. Renegotiate your platform fee
The BSP market is competitive in 2026. If your platform fee is over ₹3,000/month and you don't use 80% of the features, you have leverage. Two real Bangalore clients moved from ₹5,000/month plans to ₹999/month plans this quarter with zero feature loss.
7. Confirm GST handling
Many BSPs invoice Meta charges and platform fees separately. Confirm GST is being applied correctly and that you can claim ITC. A surprising number of finance teams are leaving 18% on the table here.
8. Set a monthly cap
Most BSPs let you set a hard message-spend ceiling. Set one. A misconfigured automation can blow out your monthly budget in two hours without it.
The five most expensive mistakes we see Indian SMBs making
After auditing dozens of WhatsApp Business setups across Bangalore this quarter, the same expensive mistakes recur. If you do nothing else after reading this, audit your setup against these five.
Mistake 1: Sending marketing templates when service messages would do
The classic example: a customer messages your business at 3:42pm. At 5:15pm, your team replies — but they send a marketing template (₹0.86) when a free-form service reply (₹0) would have worked. Most BSP UIs make it too easy to send templates by default. Train your team. The savings are immediate and large.
Mistake 2: Re-sending the same template inside one campaign
If you send a marketing template, and 24 hours later the customer hasn't responded, the natural instinct is to "remind" them with the same template again. Each re-send is another ₹0.86. Most SMBs we audit have at least one campaign doing this on autopilot. The fix is a campaign rule: maximum one marketing template per user per 7 days unless explicit re-engagement intent.
Mistake 3: Treating WhatsApp Flows as a Marketing message
WhatsApp Flows — in-message multi-step forms — are usually classifiable as Utility messages (₹0.115) when triggered by a customer action. Many SMBs are running Flows under Marketing classification and overpaying by ~7×. Re-categorise.
Mistake 4: Not tracking template-level cost-per-conversion
You almost certainly track Google Ads at the ad-level. You probably don't track WhatsApp templates at the template level. A 30-day audit of cost-per-conversion per template usually reveals 1–2 templates that produce 60% of your conversions and 1–2 templates that produce zero conversions but eat 20% of your spend. Kill the latter.
Mistake 5: Ignoring template re-approval cycles
Meta tightened template approval in 2025 and again in early 2026. Templates that worked fine two years ago may now be flagged or downgraded. Re-audit your active templates quarterly. A downgraded template can silently become more expensive without notice.
What we're seeing for SMBs in Bangalore right now
Across the verticals we work with — clinics, real estate, D2C, restaurants, professional services — the SMBs that adapted in January are now paying roughly 20% less for the same volume than they did under the old per-conversation model. The SMBs that did nothing are paying roughly 30–50% more.
The gap will only widen. Meta's next pricing review is rumoured for July 2026 and the direction of travel is up, not down. The compounding cost of a slightly-too-many-touch sequence in 2026 is much higher than it was in 2025.
The WhatsApp Business Calling API — a quick note
Meta officially launched the WhatsApp Business Calling API in mid-2025 and it went into wider availability for Indian businesses through Q1 2026. This lets you place and receive native voice calls directly inside the WhatsApp app, with AI voice agents able to handle the call.
Pricing is separate from the messaging rates above and is still in flux. Early access is mostly via enterprise BSPs and a handful of Indian providers. If you are planning a voice-AI deployment, read our companion piece on Indian-language voice AI in 2026 — combining the Calling API with a Sarvam-based voice stack is the lowest-friction way to run AI calls in 2026.
Common questions we hear on SMB owner calls
A few sharp questions worth answering directly:
"My BSP says they still charge per conversation — is that legal?" Yes, but it's a BSP-level abstraction on top of Meta's per-template billing. Your BSP is paying Meta per template and bundling it back to you as a conversation. You may be paying a premium for that simplicity. Ask them for the underlying per-message economics.
"Can I just stop using marketing templates and only use utility?" Meta's category enforcement is strict and tightening in 2026. If a template's content reads as promotional, Meta will reclassify it as Marketing and bill you accordingly — sometimes retroactively. Don't try to game the categories; design your message intent honestly.
"What about WhatsApp Flows? Are those billed differently?" Flows are typically billed as the underlying message type (usually utility). They are one of the most underused features for Indian SMBs and a great way to reduce cost-per-outcome because they collapse multiple back-and-forth exchanges into a single in-message experience.
"Should we move to RCS or stay on WhatsApp?" For India in 2026, the answer is overwhelmingly: stay on WhatsApp. Penetration, trust, and the BSP ecosystem are all on WhatsApp's side. RCS is interesting in the US; not a serious channel for Indian SMBs yet.
The strategic shift you should make this year
Stop thinking of WhatsApp as "the cheap channel where I broadcast." That model was for 2022. In 2026, WhatsApp is a conversation channel where:
- The first message is a paid invitation.
- The reply is the real product.
- The 24-hour service window is your free playground.
- AI agents (via Razorpay MCP, Zoho MCP, and others) increasingly close the conversation without a human touching it.
This is a more expensive per-message world but a cheaper per-customer world for any business willing to think in conversation design rather than blast volume.
If you want a one-hour audit of your current WhatsApp Business setup — invoice, templates, sequences, BSP markup, and a quantified migration plan — that is something we do for Indian SMBs every week. Reach out via our contact page and we'll send you the standard audit template before the call.