Quick answer: WhatsApp Business API is priced per conversation, not per message. A conversation is a 24-hour window of messages between business and customer, opened by the first message in the window. Each conversation is categorised as Marketing, Utility, Authentication, or Service — with rates that vary by category and by country. Service conversations (customer-initiated) are the cheapest; Marketing conversations are the most expensive. India rates differ from US rates differ from Brazil rates.
WhatsApp Business API pricing is one of the most-asked, most-misunderstood numbers in martech. Meta has revised the pricing model multiple times — from session-based to conversation-based — and adjusted the category definitions and rates several times since then. If you're scoping a WhatsApp Business deployment in 2026, here is the working model and the variables that move the bill.
In plain language: WhatsApp Business API is priced per conversation, not per message. A conversation is a 24-hour window of messages between business and customer, opened by the first message in the window. Each conversation is categorised as Marketing, Utility, Authentication, or Service — with rates that vary by category and by country. India rates differ from US rates differ from Brazil rates, etc. Service conversations (customer-initiated) are the cheapest; Marketing conversations are the most expensive.
The conversation categories
| Category | Trigger | Use case | Relative cost |
|---|---|---|---|
| Marketing | Business initiates with a marketing template | Promotional offers, campaign messages | Highest |
| Utility | Business initiates with a utility template | Order confirmation, shipping update, account alert | Medium |
| Authentication | Business initiates with an authentication template | OTPs, verification codes | Medium (between Utility and Service) |
| Service | Customer initiates the conversation | Customer support replies within 24-hour window | Lowest (often free under certain conditions) |
The category is determined by the opening message of the conversation. A Marketing template opens a Marketing conversation; a customer-initiated message opens a Service conversation. Once opened, the 24-hour window can carry further messages of any kind without additional billing.
Country-specific rates
WhatsApp publishes per-conversation rates per category per market. India rates are typically among the most discussed because India is one of the largest WhatsApp markets globally.
[VERIFY 2026] Meta has revised pricing multiple times — most recently announced changes have phased in by category and market. Re-confirm the operative India per-conversation rates for Marketing, Utility, Authentication, and Service before publishing.
What costs what — practical scenarios
(Rates are illustrative — re-verify before publishing)
Scenario A — E-commerce with order updates and occasional promo
- 10,000 daily orders → 10,000 Utility conversations/day (order confirmation)
- 2,000 daily shipping updates → many fall within the existing Utility window; new windows where the previous expired
- 1 weekly promotional campaign to 100,000 opt-ins → 100,000 Marketing conversations
The dominant cost is Marketing. Order-update Utility costs scale with volume but per-conversation rate is lower.
Scenario B — Fintech with high OTP volume
- 500,000 OTPs/day → 500,000 Authentication conversations
- Small Utility volume for account alerts
- Minimal Marketing
Dominant cost is Authentication, at scale. Optimising OTP delivery (e.g., reducing retries, using SMS or in-app fallback for failed WhatsApp delivery) compounds savings.
Scenario C — Support-heavy SaaS
- 5,000 customer-initiated support conversations/day → 5,000 Service conversations
- Outbound utility low; minimal marketing
Dominant cost is Service — and per-conversation rates here are the lowest, with potential free-tier benefits depending on operative pricing terms.
Pricing levers — how to bring the bill down
- Consolidate sessions. If a customer interacts multiple times within 24 hours, you pay for one window. Avoid splitting unnecessarily.
- Pick the right category. Mis-categorising as Marketing what could legitimately be Utility costs more. Mis-categorising Marketing as Utility risks rejection and account quality.
- Reduce template re-sends. Failed template deliveries that retry generate billable conversations.
- Use Authentication templates only for what's authentication. Don't dress up a marketing message as authentication; templates get rejected.
- Combine messages within sessions. Send the order confirmation and shipping ETA in one window when timing aligns, not as two windows.
- Use SMS or in-app as the fallback for messages that can be sent on cheaper rails.
Cost vs. SMS — the comparison
For pure transactional content, India SMS is typically cheaper per message than WhatsApp per conversation. But:
- WhatsApp delivers richer content (images, buttons, media)
- WhatsApp has higher read rates than SMS
- WhatsApp supports interactivity (button clicks back to your webhook)
- WhatsApp opt-in rates are different from SMS
The cost decision is about what message on what channel for what outcome, not "which is cheaper per send."
Free-tier and conversation entry points
Meta has, at various times, made certain conversation types free under specific entry points (e.g., conversations initiated from click-to-WhatsApp ads, free service conversations within certain quotas).
[VERIFY 2026] Re-confirm the current operative free-tier rules before quoting.
Billing model — pre-paid line of credit
WhatsApp Business API typically operates on a pre-paid line of credit through Meta's payment system or through your BSP. You fund the account, conversations debit the balance, you top up. Watch for:
- Low-balance alerts (campaign mid-send failures are expensive in reputation)
- Currency-of-billing differences (USD billing for India accounts is common)
- BSP markup that varies by tier
Common pricing mistakes
- Treating WhatsApp pricing as per-message. It's per-conversation; volume math is different.
- Sending a daily campaign instead of weekly. Each daily send opens a new Marketing conversation; weekly compounds engagement and reduces conversation count.
- Failing to use the existing 24-hour window for follow-up messages.
- Choosing the wrong category. Marketing for what's actually Utility, or vice versa.
- Ignoring opt-in quality. Cheap blasted lists generate spam reports that degrade account quality, which drives delivery rates down — increasing effective cost per delivered conversation.
Modelling your bill before you launch
Before you launch, build a model:
- Expected Marketing conversations per period × Marketing rate
- Expected Utility conversations per period × Utility rate
- Expected Authentication conversations per period × Authentication rate
- Expected Service conversations per period × Service rate (often near-free)
- BSP platform fee (if applicable)
- Buffer for retries and failed templates
Compare against the SMS-only or hybrid alternative. Make the channel decision data-driven.
CTA: OpenMalo's WhatsApp Business module includes conversation analytics and category-aware send routing — so you don't pay Marketing rates for what should be Utility. See the module →
Closing
WhatsApp Business API pricing rewards teams that understand the conversation model and punishes teams that don't. Model the conversations, not the messages. Pick categories correctly. Consolidate sessions. The teams that internalise this run sustainable WhatsApp programmes; the teams that don't end up with WhatsApp bills they didn't budget for.
