There are two problems with almost every WhatsApp Business API pricing guide you will find today.
The first is that the numbers are stale. Meta raised the India marketing rate by roughly ten percent during the first half of 2026, and a large share of the pages ranking for this term still quote the old figure. One of the results sitting high on that page has 2025 in its own URL. If you built a budget from it, your budget is wrong.
The second problem is bigger, and almost nobody is writing about it. On 1 October 2026, Meta starts charging for service messages. Those are the ordinary, free-form replies your team sends inside the twenty-four hour window after a customer writes to you. Today they cost nothing. In about seven weeks they become a line on your invoice, and Meta has not published the rates yet.
If your WhatsApp usage is mostly answering people, your bill is currently close to zero and you have no idea what it is about to become. That is the single most important fact about WhatsApp pricing in 2026, and it appears in none of the rate cards ranking for this keyword.
This guide gives you the current India numbers, the three cost layers that never appear in the same table, what changes on 1 October, and what to do about it before it lands.
In this guide
- How WhatsApp charges you now
- The India rate card, August 2026
- The 2026 rate rise most guides missed
- What is still free until 30 September
- 1 October 2026: free support ends
- What that does to a support-heavy business
- Volume discounts: what exists and what does not
- The three layers nobody adds up
- What three real businesses actually pay
- The 24-hour window is now a cost centre
- Nine ways to cut the bill
- If you resell WhatsApp CRM, your cost of goods just moved
- Repricing client packages without losing them
- Questions to ask a BSP before you sign
- The pricing mistakes that cost the most
- What to do in the next seven weeks
- Frequently asked questions
How WhatsApp charges you now
Start here, because a lot of confusion comes from people mixing two different pricing models that were both true at different times.
Until the middle of 2025, WhatsApp billed per conversation. You paid once for a twenty-four hour window and could send as many messages inside it as you liked. That model shaped every piece of advice written before it, and a surprising amount of that advice is still online.
Since 1 July 2025 Meta charges per message. The charge triggers when a template message is delivered, not when it is sent and not when it is read. Each delivered template is its own line item.
That change quietly broke a common tactic. A four-step drip campaign used to cost one conversation. It now costs four messages. If you copied a campaign structure from a 2024 playbook and never revisited it, you are paying up to four times what that playbook assumed, and nothing in your dashboard told you.
Messages fall into categories, and the category decides the price:
- Marketing — promotions, offers, launches, re-engagement, follow-up on a click-to-WhatsApp ad. The most expensive category by a wide margin.
- Utility — order confirmations, shipping updates, payment reminders, appointment alerts. Cheap, and free in some circumstances.
- Authentication — one-time passwords and verification codes. Priced like utility domestically, with a separate and much higher international rate.
- Service — free-form replies inside an open window. Free today. Not free from 1 October 2026.
Meta assigns the category when it approves your template, and it does not always agree with you. A template you wrote as a utility message that mentions a discount will be recategorised as marketing, and it will be billed as marketing. This is one of the most common reasons a real invoice comes in above a forecast built from a rate card.
One more thing worth knowing before the numbers: none of this changes based on where the message is sent from. Whether your messages originate in a HubSpot, Salesforce, Zoho or Shopify integration, Meta bills the same rates on the same categories. What the tool changes is the markup on top and how much visibility you get into which category you are actually paying for.
The India rate card, August 2026
These are Meta’s own per-message rates for India as of August 2026. They exclude GST and they exclude anything your provider adds.
| Category | Rate per message | When it is charged |
|---|---|---|
| Marketing | ₹0.8631 (~$0.0107) | Always, on delivery |
| Utility | ₹0.115 (~$0.0014) | Only outside an open 24-hour window |
| Utility inside the window | ₹0 | Free while a customer service window is open |
| Authentication (domestic) | ₹0.115 | Always |
| Authentication-international | around $0.035 | OTPs sent to Indian users from a non-Indian business account |
| Service messages | ₹0 until 30 Sep 2026 | Free-form replies inside an open window |
Three things in that table are worth pausing on.
Marketing costs roughly seven and a half times what utility costs. That ratio is the most useful number in WhatsApp economics. It means the difference between a message Meta reads as promotional and one it reads as transactional is not a rounding error — it is most of your bill. Teams that shave their marketing volume and move genuinely transactional content into properly written utility templates see the invoice fall by a lot more than they expect.
Authentication-international is around thirty times the domestic authentication rate. If your WhatsApp Business Account is registered outside India but you send OTPs to Indian numbers, you are on that rate. Plenty of businesses are, without realising, because someone set the account up under a foreign parent entity. It is worth ten minutes to check which entity owns your WABA.
India is genuinely cheap. Indian rates sit far below most Western markets. That is why India is where WhatsApp-first business models work and why the same idea often fails to pencil out in Europe. It also means advice written for a US or EU audience about “keeping WhatsApp costs down” is solving a problem you may not have, while ignoring the GST layer that you definitely do.
The 2026 rate rise most guides missed
The India marketing rate went from ₹0.7846 to ₹0.8631 per message — an increase of about ten percent. Utility and authentication stayed roughly where they were.
Two things about this are worth saying plainly.
First, providers disagree about the date. Some tell their customers the change landed on 1 January 2026. Others say April. We are not going to pretend to resolve that for you, because it does not matter as much as the thing that does: check your own invoices. Pull the last eight months of provider statements, divide the marketing charge by the marketing message count, and you will see the month it changed on your account. That number is the only one that governs your budget.
Second, a ten percent rise on the most expensive category is not a small event if marketing is most of your volume. A business sending two lakh marketing messages a month went from about ₹1.57 lakh to about ₹1.73 lakh in Meta charges alone, before GST and before the provider’s cut. That is roughly ₹1.9 lakh a year of new cost that appeared without a contract change, an email, or a line in anyone’s plan.
The reason this matters for planning is not the ten percent. It is what the ten percent tells you: Meta’s rates are not a fixed input. They move, per country, per category, on Meta’s schedule. Any business model with WhatsApp messaging as a large cost line and a fixed price to the customer is carrying that risk whether or not it has noticed. We come back to this in the reseller section, where it is sharpest.
What is still free until 30 September
Four things cost nothing today. Three of them survive 1 October. One does not.
Customer messages are free, permanently. You are never charged for what people send you. Only for what you send.
The 72-hour free entry point survives. When someone starts a chat by tapping a click-to-WhatsApp ad or a Facebook page button, you get a seventy-two hour window in which everything you send is free — templates included. This is the most underused mechanic in WhatsApp pricing and we come back to it in ways to cut the bill.
Utility templates inside an open service window survive. If a customer messaged you in the last twenty-four hours, your order confirmation costs nothing. The same template sent to a silent customer costs ₹0.115.
Service messages are free — until 30 September 2026. This is the one that ends.
Note what those exemptions have in common. Meta discounts messages that happen because the customer engaged first. It charges full price for messages you initiate into silence. Every worthwhile cost optimisation on WhatsApp is a version of getting more of your sending to happen inside a window the customer opened.
1 October 2026: free support ends
Here is the change, as clearly as we can state it.
From 1 October 2026, a service message is billable. A service message is a non-template reply you send to a customer inside an open twenty-four hour window — a support agent typing an answer, a chatbot replying, an AI assistant handling a query. Providers are telling their customers these will be billed at the same per-message rate Meta already applies to utility and authentication templates, set per market. Meta is expected to publish the per-country rates before 1 September 2026.
What does not change:
- The twenty-four hour window itself still works the same way. It opens and resets each time the customer writes to you.
- You still need a template to re-engage someone outside that window.
- The seventy-two hour click-to-WhatsApp entry-point window stays free.
- Incoming customer messages stay free.
What does change is the shape of the whole cost model. Until now, WhatsApp had a genuinely free tier for the thing businesses actually do most: reply to people. That tier is closing. Any calculation, business case, or vendor pitch built on “support conversations are free on WhatsApp” has a shelf life of about seven weeks.
We want to be careful about how firmly we state this. Meta’s public pricing documentation is, at the time of writing, still describing the current model and has not yet posted service rates. What we have is a consistent account from a large number of providers who have been briefed and are telling their customers to prepare. Treat the direction as settled and the numbers as unknown, and plan accordingly.
If you take one action from this guide, make it this one: find out how many outbound service messages your business sent last month. Your provider can give you that number. It is currently a figure nobody looks at, because it has never had a price. From October it is a line item, and if you do not know it now you will find out from an invoice.
Want to see what your own numbers look like before October? Lion CRM gives you the outbound message counts by category, per agent and per campaign, in one place — so you can price the change instead of discovering it. Explore Lion CRM or read WhatsApp CRM vs WhatsApp Business API if you are still working out which layer you need.
What that does to a support-heavy business
Numbers make this concrete. Take a mid-sized Indian e-commerce brand.
They get about 12,000 customer enquiries a month on WhatsApp. Their team and their bot send an average of six replies per enquiry. That is 72,000 outbound service messages a month, and today the cost of all of it is zero.
If service messages are priced at the current utility rate of ₹0.115, that becomes ₹8,280 a month in Meta charges. Add 18% GST and it is ₹9,770. Add a provider markup and call it about ₹11,000. Roughly ₹1.3 lakh a year on a line that has always read zero.
That is survivable. Now change one variable. Suppose their bot is chatty — it acknowledges, it asks a clarifying question, it confirms, it offers a follow-up. Twelve outbound messages per enquiry instead of six. The same business is now at 144,000 service messages and about ₹22,000 a month all-in. And that chattiness cost nothing to build, because until now there was no price signal telling anyone to keep the bot terse.
This is the part that deserves attention. The businesses most exposed are the ones that automated support most enthusiastically. An AI assistant that sends four messages where a human would send one has been free and will not be. Every deflection metric anyone has ever presented — “our bot handled 80% of queries without a human” — was calculated in a world where bot messages were free. From October, deflection has a cost per interaction, and some of those deflections will be more expensive than the ticket they avoided.
Three things to do about it, in order of return:
- Count your outbound service messages per resolved conversation. If it is above four, there is easy money in it.
- Make your bot answer in one message instead of three. The acknowledgement message, the “let me check that for you” message and the “is there anything else?” message are all about to have a price.
- Look at where you use messages as UI. Multi-step menu trees that ask a question, wait, then ask another, are elegant and are about to be metered. Interactive list and button messages that collect several answers in one send do the same job for one charge.
None of this is an argument against automating support. A WhatsApp AI chatbot that resolves a query in two messages is still cheaper than a human doing it in six. It is an argument for measuring bots on messages per resolution rather than on deflection rate alone, which is a better metric anyway and nobody had a reason to adopt it while sending was free.
Volume discounts: what exists and what does not
Meta applies volume tiers, but only where most people do not expect them.
Utility and authentication messages get volume discounts. As your delivered volume in a calendar month to a given country crosses Meta’s thresholds, the per-message rate steps down. Providers report discounts reaching around twenty-five percent at the highest tiers. The tiering is incremental — cross a threshold at message 100,000 and message 100,001 is discounted, not the hundred thousand that came before it. Tiers reset each month, so a business with lumpy volume never settles into a cheaper band.
Marketing messages get no volume discount at any volume. This is deliberate. Meta does not want cheap promotional blasting, and the pricing says so more clearly than any policy document. Your marketing rate at ten million messages a month is the rate at ten.
Service messages are expected to sit outside the tier system too, at a flat per-message rate regardless of volume, once they become chargeable.
Put those together and the strategic reading is straightforward. Meta’s pricing rewards transactional, high-volume, customer-triggered messaging and penalises promotional blasting and verbose support. Businesses that align with that grain get cheaper as they grow. Businesses that fight it pay full rate forever.
There is a practical trap in the monthly reset. If your volume straddles a threshold — say you cross the tier boundary in the third week most months — moving a batch of non-urgent utility sends from the first days of one month into the last days of the previous one can put more of your volume in the discounted band. It is a small optimisation and it only pays at real scale, but it is free.
The three layers nobody adds up
Every rate card you will read quotes one layer. Your invoice has three.
Layer one: Meta’s per-message rate. ₹0.8631 marketing, ₹0.115 utility and authentication. This is what gets published, compared and argued about.
Layer two: your provider. You cannot buy from Meta directly at any normal scale — you go through a Business Solution Provider. Indian BSPs charge in one of three shapes, and the shape matters more than the headline number:
- Markup per message. Meta’s rate plus a margin, commonly ten to thirty percent. One provider publishes ₹0.9500 per marketing message against Meta’s ₹0.8631 — a markup of ₹0.0869. Transparent, and it scales with your volume forever.
- Flat platform fee. A fixed monthly subscription, messages passed through at Meta’s cost. Better as you grow, worse when you are small.
- Bundled plans. A monthly price including a message allowance. Almost always the most expensive per message once you look at it, and the hardest to compare, which is generally the point.
Layer three: 18% GST. In India these services are classified as OIDAR and attract GST at eighteen percent, on Meta’s charges and on the platform fee. It is recoverable as input credit if you are registered, so it is a cash-flow cost rather than a real one for most businesses — but it is absent from every published rate card, and a marketing message quoted at ₹0.8631 lands at ₹1.0185 before your provider has taken anything.
Stack the layers on one marketing message: ₹0.8631 from Meta, plus roughly ₹0.09 provider markup, plus GST on both, is about ₹1.12. That is thirty percent above the number in the rate card. For a business sending five lakh marketing messages a month, the gap between the quoted rate and the real rate is around ₹1.3 lakh a month — enough to change whether a campaign was worth running.
Whenever you compare providers, insist on a landed cost per message including all three layers. Any vendor who will not give you that number is telling you something.
What three real businesses actually pay
Rate cards are abstract. Monthly bills are not. Three shapes, using August 2026 rates, at 18% GST, with a fifteen percent provider markup, and a projection of what October adds if service messages land at the current utility rate.
A D2C brand doing marketing at volume. 300,000 marketing messages, 40,000 utility, 25,000 outbound service. Meta charges about ₹2.59 lakh marketing and ₹4,600 utility. With markup and GST, roughly ₹3.57 lakh a month. October adds about ₹3,900. Barely visible — because marketing dominates everything.
A logistics company running notifications. 5,000 marketing, 400,000 utility, 60,000 outbound service. Meta charges about ₹4,300 marketing and ₹46,000 utility, less whatever the volume tiers return on that utility count. Roughly ₹68,000 a month all-in. October adds about ₹9,400 — around fourteen percent on top. Noticeable, and worth engineering for.
A services business that mostly answers people. 2,000 marketing, 8,000 utility, 150,000 outbound service. Today: about ₹2,600 all-in, a rounding error, which is exactly why nobody has ever examined it. October adds about ₹23,400 a month. The bill roughly multiplies by ten.
The pattern is the point. The less you spend on WhatsApp today, the harder October hits you in proportional terms. Businesses with big marketing spend will not feel it. Businesses that adopted WhatsApp because support on it was free are the ones who need to model this now, and they are the least likely to be reading pricing guides, because pricing has never been their problem.
If you are in the third group, the honest framing is not “how do we absorb this”. It is “we have been running a support channel with no unit cost, and we are about to find out what our cost per resolved conversation really is”. That is a useful thing to learn even though the reason for learning it is unwelcome.
The 24-hour window is now a cost centre
The twenty-four hour customer service window has always been explained as a policy rule: outside it, you need an approved template. From October it is also the main lever on your bill, and it is worth understanding as an economic object rather than a compliance one.
Every customer message opens or resets a twenty-four hour window. Inside that window, utility templates are free and — until October — everything you send is free. Outside it, everything you send is billable, at the marketing rate if Meta reads it as promotional.
Three consequences follow.
Timing beats content. The same message costs ₹0 or ₹0.115 or ₹0.8631 depending only on when it is sent and how it is categorised. A shipping update sent while the customer is mid-conversation is free. Sent two days later to someone who has gone quiet, it costs money. Being able to schedule WhatsApp messages so notification batches fire when windows are open is pure margin, and almost nobody does it because until now the saving was small.
Re-engagement is where the money goes. The expensive message is always the one sent into silence. Businesses that keep conversations alive — that reply promptly, that give people reasons to write back — pay dramatically less per outcome than businesses that broadcast into a cold list. Response time is a cost control, not just a service metric, and a disciplined WhatsApp follow-up sequence that lands inside open windows costs a fraction of the same sequence sent cold.
Click-to-WhatsApp ads are underpriced as an acquisition channel. The seventy-two hour free entry-point window means a conversation started from an ad is free for three full days, templates included. If you run Meta ads at all, routing a share of them to WhatsApp instead of a landing page gets you a longer free window than any other entry point on the platform. That advantage grows in October, when the ordinary route stops being free and this one stays free.
If your CRM cannot tell you which of your outbound messages landed inside an open window and which did not, you cannot manage any of this. That is a genuine gap in most WhatsApp tooling and it becomes an expensive one in seven weeks.
Cost control on WhatsApp is a tooling problem before it is a pricing problem. Lion CRM tracks window state, message category and per-conversation cost on a WhatsApp Kanban board, so your team can see which sends are free and which are not before they hit send. See what a whitelabel WhatsApp CRM is if you are evaluating the category.
Nine ways to cut the bill
Ordered by return, not by effort.
1. Recategorise everything that is genuinely transactional. The gap between marketing and utility is 7.5x. Order updates, appointment reminders, payment confirmations and delivery alerts belong in utility. If a template got classified as marketing, look at the wording — a single promotional sentence appended to an otherwise transactional message is usually what did it. Rewriting that sentence out is the highest-return hour of work available.
2. Send utility templates inside open windows. Free instead of ₹0.115. Requires your system to know window state, which is the tooling point above.
3. Cut outbound messages per conversation. This is the October fix. Combine the acknowledgement, the answer and the follow-up prompt into one message. Use interactive buttons and lists rather than multi-turn question trees.
4. Prune your marketing list by engagement, not by size. Marketing gets no volume discount, so a large unengaged list has no economy of scale — it is just full-price messages to people who will not reply, and it damages your quality rating too, which costs you again in limits. The discipline in sending bulk WhatsApp messages without getting banned is now a cost discipline as well as a safety one.
5. Route paid traffic through click-to-WhatsApp. Seventy-two free hours per conversation, and it survives October.
6. Check which entity owns your WABA. If it is a foreign entity sending OTPs to Indian numbers, you are on authentication-international at roughly thirty times the domestic rate. Moving to an Indian WABA is a real project — the Meta WABA approval playbook covers what it involves — and at OTP volume it pays back fast.
7. Reply faster. Every reply resets the free window. Slow replies push your next message outside it and turn a free send into a paid one. There is now a rupee value on response time, which makes it much easier to justify WhatsApp auto reply — provided the auto-reply is one message, not four.
8. Move volume across the tier boundary where you can. Only relevant at scale, and only for utility and authentication. Free money if your volume straddles a threshold.
9. Renegotiate the markup layer, not the Meta layer. You cannot change Meta’s rate. You can absolutely change a fifteen percent per-message markup once your volume is worth keeping. Most Indian BSPs will move on this and very few customers ask.
If you resell WhatsApp CRM, your cost of goods just moved
This section is for agencies, consultants and SaaS resellers selling WhatsApp messaging to clients. If that is not you, skip to the mistakes.
Everything above is a cost line for a business. For you it is cost of goods sold, and two things happened to it this year that you need to have an answer for.
The marketing rate rose about ten percent. And in October a category that was free becomes billable.
If you sell fixed-price monthly packages with a message allowance — the standard shape in this market — then you carry both changes yourself. A client on a package priced against ₹0.7846 marketing is now costing you ₹0.8631 to serve, and you cannot bill them for it because the number on the contract has not changed. Every one of those contracts lost margin silently, and most resellers found out at renewal, if at all.
October is the same problem with a much larger blast radius, because it hits packages where the client’s usage is mostly support. Those are the accounts that look most profitable right now — low message volume, high subscription — precisely because the messages they send have been free. In October those become your most exposed accounts.
Work out your exposure before it arrives:
- List every client contract with a fixed message allowance. Note which ones were priced before this year’s marketing rise.
- For each, get the outbound service message count. That number is currently invisible and it is your October liability.
- Reprice at the landed cost, not Meta’s rate. Meta’s rate plus your BSP’s markup plus GST, with headroom for the next move. How to price a whitelabel WhatsApp CRM on cost-plus versus value works through the arithmetic properly.
- Put a rate-change clause in every new contract. Something plain: message pass-through costs are set by Meta and adjust when Meta adjusts them. Almost nobody has this and everyone needs it. There is a worked example in the whitelabel reseller agreement template.
- Make sure you can actually see per-client usage. If your platform reports messages at the account level rather than the tenant level, you cannot bill pass-through at all. Multi-tenant licence management is the capability this depends on.
The structural fix is to stop selling messages at a fixed price at all. Sell the platform, the setup, the automations and the support at a fixed price, and pass messages through at cost plus a stated percentage. Your margin then stops depending on decisions Meta makes without telling you. Whitelabel WhatsApp CRM pricing models for agencies covers the shapes that hold up, and the margins resellers actually make has the numbers from people doing it.
There is an opportunity in this too, and it is worth naming. Most of your competitors will not read anything about October until an invoice surprises them in November. Walking into a client conversation in September with their own service-message count and a plan is the kind of thing that renews contracts. It is also, straightforwardly, the right thing to do for them.
Repricing client packages without losing them
Raising prices on existing clients is the part everyone dreads. A few things make it go better.
Lead with their number, not yours. “Your account sent 47,000 outbound service messages last month, and from 1 October those are billable” is a fact about their business. “Our prices are going up” is a fact about yours. The first one starts a conversation about how to reduce 47,000; the second starts a conversation about alternatives.
Show the reduction before the increase. If you can take their service message count down by a third by tightening the bot flows, do that work first and present the new price against the reduced volume. You are then selling a smaller increase and a piece of value delivered.
Split the bill. Move to platform fee plus pass-through, and the increase becomes something you are both subject to rather than something you decided. This is easier to do at a rate change than at any other moment, which makes September a genuinely good time to restructure contracts you have wanted to restructure anyway.
Give the smallest clients a grace period. The businesses hit hardest in proportional terms are the small support-heavy ones, and they are also the ones most likely to churn over a surprise. Absorbing one quarter for accounts under a threshold costs little and buys a lot.
Two related guides go deeper: how to price whitelabel WhatsApp CRM clients and how to reduce client churn.
Questions to ask a BSP before you sign
Provider pricing pages are built to be hard to compare. These questions cut through.
What is my landed cost per marketing message, including your markup and GST? One number. If they answer with Meta’s rate, they are hiding the markup.
Do you pass Meta’s volume discounts through to me? Some do not, and keep the tier savings on your volume. This is entirely legitimate and entirely worth knowing.
What will you charge for service messages from 1 October? The honest answer today is “Meta has not published rates”. What you are testing is whether they know the change is coming and have a plan. A provider who has not heard of it in August is not a provider you want in October.
Is there a minimum monthly commitment or an unused-allowance rollover? Bundled plans frequently have both, and both cost you.
Can I see per-category, per-template message counts? If you cannot see which templates got recategorised as marketing, you cannot control the biggest line on your bill.
What happens to my number and templates if I leave? Your WABA and your phone number should be yours. Some setups make migration painful in ways that only become apparent when you try. WhatsApp Cloud API versus on-premise covers the hosting side of this, and the WhatsApp Business API reseller guide covers account ownership.
What is your rate-change notice period? Meta changes rates on its own schedule. You want to hear about it from your provider before you hear about it from an invoice.
The pricing mistakes that cost the most
Budgeting from Meta’s rate card. It is layer one of three. Real cost runs about thirty percent higher.
Assuming your template categories are what you wrote them as. Meta decides, and it recategorises. Audit the assigned category on every template, not the intended one.
Treating the twenty-four hour window as a compliance rule. It is the main lever on your bill.
Copying campaign structures written before July 2025. Per-conversation billing is gone. A four-message sequence costs four messages.
Optimising the wrong category. Teams spend weeks shaving utility costs while marketing — at 7.5x the rate and with no volume discount — goes unexamined.
Buying a bundled plan without doing the division. Take the monthly price, divide by the allowance, compare to landed cost per message. Bundles usually lose, which is why they are sold as bundles.
Ignoring the entity behind the WABA. Authentication-international at roughly thirty times the domestic rate is the most expensive filing error available on this platform.
Planning for October in October. Rates are expected before 1 September. The work — counting service messages, tightening bot flows, restructuring contracts — takes longer than the notice period will give you.
What to do in the next seven weeks
A short, ordered list. None of it needs new software.
This week. Get last month’s outbound message counts broken down by category, including service. Most people have never asked for this. It is the baseline everything else is measured against.
Next week. Audit your templates. For each one, note the category Meta assigned rather than the one you intended. Rewrite the mis-categorised ones. This is the largest saving available and it is available today, independent of October.
Two weeks out. Count outbound service messages per resolved conversation. If it is above four, the bot or the macro set is verbose, and every extra message becomes a charge in October.
Three weeks out. Rework the worst offenders. Merge acknowledgement messages into answers. Replace multi-turn menus with interactive lists. Aim to cut outbound service messages by a third — that is usually achievable without touching resolution quality.
Early September. Meta’s rates should be published. Model your actual bill against your real counts. Now you have a number rather than a worry.
Mid September. If you resell, talk to clients. Their numbers, your plan, the new structure. Before the change, not after.
Late September. Move any fixed-price message contracts onto pass-through. Add rate-change clauses. Check your click-to-WhatsApp routing is capturing the free entry-point window on paid traffic.
1 October. Watch the first week’s costs against your model and correct.
If you do the first two items and nothing else, you will still be better off than most businesses on the platform, because template recategorisation is where the money already is and almost nobody audits it.
Running this on spreadsheets does not scale past a few thousand conversations. Lion CRM is a whitelabel WhatsApp CRM built for Indian teams and the agencies who resell to them — message categorisation, window tracking and per-client cost reporting included. See the whitelabel WhatsApp CRM comparison for India 2026 or start with Lion CRM.
Frequently asked questions
How much does the WhatsApp Business API cost in India in 2026?
Meta charges about ₹0.8631 per marketing message and ₹0.115 per utility or authentication message, as of August 2026. Those are Meta’s rates only. Add your provider’s markup, commonly ten to thirty percent, and 18% GST on both. A marketing message quoted at ₹0.8631 typically lands at around ₹1.12 once everything is included.
Is the WhatsApp Business API free?
No, but several things on it are. Incoming customer messages are always free, utility templates sent inside an open twenty-four hour window are free, and everything sent inside the seventy-two hour window opened by a click-to-WhatsApp ad is free. Service messages are free until 30 September 2026 and become billable on 1 October 2026.
What changes on 1 October 2026?
Meta starts charging for service messages, which are the free-form replies your team or your chatbot sends inside an open twenty-four hour window. Providers report they will be billed per message at the same rate Meta applies to utility and authentication templates. Exact per-country rates are expected to be published before 1 September 2026. Businesses whose WhatsApp usage is mostly support will see the largest proportional increase.
Did WhatsApp raise prices in India in 2026?
Yes. The marketing rate rose from ₹0.7846 to ₹0.8631 per message, an increase of about ten percent. Utility and authentication rates stayed broadly stable. Providers disagree about whether the change took effect in January or April, so check your own invoices to see which month it landed on your account.
What is the difference between marketing, utility and authentication messages?
Marketing messages are promotional and cost roughly 7.5 times what utility messages cost. Utility messages are transactional — order confirmations, delivery updates, payment reminders — and are free when sent inside an open service window. Authentication messages are OTPs and verification codes, priced like utility domestically but far higher when sent to Indian numbers from a business account registered outside India. Meta assigns the category when it approves your template, and it does not always assign the one you intended.
Does WhatsApp charge per message or per conversation?
Per message, since 1 July 2025. The older per-conversation model let you send unlimited messages inside a twenty-four hour window for one charge. That is gone, which means any campaign structure copied from a pre-2025 guide may cost several times what that guide assumed.
Are there volume discounts on WhatsApp Business API pricing?
Yes, for utility and authentication messages. The per-message rate steps down as your monthly delivered volume to a country crosses Meta’s thresholds, reaching around twenty-five percent off at the highest tiers. The discount is incremental and tiers reset every month. Marketing messages get no volume discount at any volume, and service messages are expected to stay at a flat rate once they become chargeable.
How do I reduce my WhatsApp Business API bill?
The largest single saving is usually recategorising templates that Meta reads as marketing but which are genuinely transactional, because the rate gap is 7.5x. After that: send utility templates inside open service windows where they are free, reduce the number of outbound messages per support conversation, route paid traffic through click-to-WhatsApp ads to capture the free seventy-two hour window, and renegotiate your provider’s per-message markup once your volume is worth keeping.
Do I have to pay GST on WhatsApp Business API charges in India?
Yes. These services are classified as OIDAR and attract 18% GST on both Meta’s charges and your provider’s platform fee. It is recoverable as input tax credit if you are GST registered, so for most businesses it is a cash-flow cost rather than a real one — but it is missing from every published rate card, so budgets built from rate cards come in 18% light before the provider markup is even counted.
What does this mean if I resell WhatsApp CRM to clients?
Meta’s rates are your cost of goods sold, and they moved twice this year. Any fixed-price package with a message allowance lost margin when the marketing rate rose, and packages serving support-heavy clients are exposed again on 1 October. The durable fix is to price the platform and the service at a fixed rate and pass messages through at cost plus a stated percentage, with a rate-change clause in the contract.
Related guides
- WhatsApp Automation Tool: A 2026 Buyer’s Guide — the full India rate card behind every automation quote
- WhatsApp CRM Software: A 2026 Buyer’s Guide — what the software layer on top of those rates actually costs
- WhatsApp Marketing Software: A 2026 Buyer’s Guide — how to choose the software that spends those rates efficiently
- WhatsApp CRM Pricing for Resellers 2026 — what to charge clients once you know what the messages cost you.
- WhatsApp Business API Reseller Guide 2026 — account ownership, Meta approval and the setup decisions that are hard to reverse.
- WhatsApp CRM vs WhatsApp Business API — the difference between the channel Meta bills you for and the software you run on it.
- Whitelabel WhatsApp CRM Pricing Models for Agencies — the contract shapes that survive a rate change.
- WhatsApp Cloud API vs On-Premise — the hosting decision underneath all of this pricing.
- Whitelabel WhatsApp CRM Comparison India 2026 — the platform view if you are choosing rather than optimising.