WhatsApp Business API pricing in India for 2026, explained

WhatsApp Business API pricing in India for 2026 works on a per-template-message model, not a per-conversation one. Meta charges you each time you send a business-initiated template message, and the rate depends on the template category: utility and authentication messages cost roughly ₹0.13 to ₹0.20 each, while marketing messages cost roughly ₹0.91 and up. Any reply you send to a customer inside 24 hours of their last message is free. That shift, from conversation-based billing to per-message billing for templates plus a free service window, is the thing most Indian SMBs get wrong when they budget for WhatsApp.

If you run a business in India and you are looking at the WhatsApp Business API, here is what you are really paying for and how to keep the bill predictable.

How WhatsApp Business API pricing in India is structured

There are two layers to your cost, and people routinely confuse them.

The first layer is what Meta charges. This is the messaging cost, billed in your WhatsApp account currency. In India this is set at Meta's India rates and applies whether you go through Plivo, Twilio, Gupshup, or any other provider. Meta's rate is the same regardless of who your provider is.

The second layer is what your provider, the BSP (Business Solution Provider), charges on top: platform fees, per-message markups, or a monthly subscription. This part varies widely. Some BSPs add a markup per message; some charge a flat platform fee and pass Meta's rate through at cost. When you compare quotes, separate these two layers or you will compare apples to onions.

The Meta layer is the one with fixed, published India rates, so that is what the rest of this post covers.

The three template categories, and what each costs

Every business-initiated message you send through the API uses a pre-approved template, and each template is tagged with a category. The category decides the price. This is the single most important thing to understand about WhatsApp Business API pricing in India.

Utility templates, roughly ₹0.13 to ₹0.20

Utility messages are tied to a transaction or an action the customer has already taken. Order confirmations, shipping updates, payment receipts, appointment reminders, account notices that are not pure authentication: these are utility. At roughly ₹0.13 to ₹0.20 per message, this is the cheapest paid category and where most of your volume should sit if you are running operations rather than promotions.

A practical example: a Jaipur boutique sending "Your order #4821 has been packed and ships today" pays the utility rate. That message is cheap precisely because it serves the customer rather than sells to them.

Authentication templates, roughly ₹0.13 to ₹0.20

Authentication messages are one-time passwords and verification codes, the "Your login code is 4827" messages. In India these are priced in the same band as utility, roughly ₹0.13 to ₹0.20 per message. If your app or store sends OTPs over WhatsApp instead of SMS, this is the line item to watch, because OTP volume scales directly with logins and checkouts.

One note for anyone comparing channels: WhatsApp OTPs at this rate are often competitive with transactional SMS, and the delivery and open behaviour is usually better. But verify the actual delivered cost against your SMS rate before you switch. The gap is narrower than vendors suggest.

Marketing templates, roughly ₹0.91 and up

Marketing is anything promotional: offers, new-arrival announcements, festival sales, re-engagement nudges, "we miss you" campaigns. At roughly ₹0.91 per message and up, marketing costs several times what utility does. This is by design. Meta wants the channel to stay useful, so it prices promotion to discourage spray-and-pray blasts.

The math matters here. Sending a marketing template to 10,000 contacts at the marketing rate is a real spend, well over ₹90,000 before any BSP markup. Sending the same 10,000 a utility update costs a fraction of that. So the discipline is simple: if a message can honestly be framed as a transactional or service update, categorise it as utility. If it is a promotion, accept the marketing rate and make the campaign earn it.

Meta polices categorisation. If you send a marketing message dressed up as a utility template, it can get reclassified and re-priced, or the template can be rejected outright. Categorise honestly the first time.

The free 24-hour service window

This is the part that makes WhatsApp economical for support and sales, and it is the most misunderstood piece of WhatsApp Business API pricing in India.

When a customer messages you, a 24-hour service window opens. Inside that window, you can reply with free-form messages, no template required and at no per-message cost from Meta. Service replies inside the window are free. You can have a full back-and-forth conversation, send images, answer questions, close a sale, and pay nothing in messaging fees, as long as each of your replies lands within 24 hours of the customer's last message.

The window resets every time the customer sends a new message. So an active conversation can run for days at zero messaging cost, provided the customer keeps responding and you reply inside each 24-hour clock.

The moment the window closes, when the customer goes quiet for more than 24 hours, you can no longer send free-form text. To re-open contact you must send a paid template, and that template's category sets the price. This is why a well-run WhatsApp operation tries to handle as much as possible inside live conversations and uses paid templates only to start or restart them.

What this means for your monthly bill

Put the pieces together and a sensible cost model looks like this:

• Inbound-led support and sales: mostly free, because you are replying inside the 24-hour window.
• Transactional notifications: utility templates at roughly ₹0.13 to ₹0.20 each, predictable and cheap.
• OTPs and verification: authentication templates in the same low band.
• Campaigns: marketing templates at roughly ₹0.91 and up each, the one place costs add up fast, so budget per campaign, not per month.

For most Indian SMBs, the bill is dominated by utility messages and the occasional marketing push, with support running essentially free. If your WhatsApp spend is high and it is not from campaigns, you are probably sending templates when you could be replying inside a window, or mis-categorising utility as marketing.

Things that quietly change the number

A few realities that the rate card does not spell out:

• BSP markup is the wild card. Meta's India rates are fixed, but your provider's fees are not. Ask for the all-in delivered cost per message by category, not just the platform fee.
• Failed and undelivered messages. Clarify with your BSP whether you pay for messages that do not deliver. Policies differ.
• Template approval is free but gated. Creating and submitting templates costs nothing; you only pay on send. But poorly written templates get rejected, so factor in a little setup time.
• GST applies on top. The rates above are messaging costs. Your provider's invoice will add GST in India.

How this plays out in a CRM

Pricing is only half the problem. The other half is keeping conversations, windows, and template categories straight without a spreadsheet. This is where running WhatsApp through a CRM rather than a raw API console pays off. It tracks which contacts are inside their 24-hour window, nudges you to reply for free before the window closes, and stops you from firing off a paid marketing template when a free service reply would do. Pariq handles WhatsApp inside its CRM with a wallet that meters spend per message so you can see exactly where the money goes, by category, in real time.

The takeaway for 2026: utility and authentication are cheap, marketing is the expensive lever, and the free 24-hour service window is the part that makes the whole channel viable for support and sales. Build your WhatsApp habit around replying inside that window, send paid templates with intent, and your bill stays small and predictable.

If you want WhatsApp billing that is visible per message instead of a surprise at month-end, take a look at how Pariq meters it.