WhatsApp Business API Pricing & Setup in India
On 1 October 2026 Meta began charging for two things that had been free, and most of what is written about WhatsApp pricing online still describes the older model. This explains what triggers a charge now, what is still free, and the setup decisions that are expensive to reverse.
Source documentation checked on . Meta and Google revise these pages; verify anything you are budgeting or building against before you rely on it.
How billing actually works
Since 1 July 2025 Meta bills the WhatsApp Business Platform per message, not per conversation. The charge lands when a message is delivered — Meta does not charge for messages that are sent but never arrive — and the rate depends on the message’s category and on the recipient’s country calling code.[1] This matters for budgeting because the old conversation-based model charged once per 24-hour window regardless of how many messages you sent inside it; the current model does not work that way.
There are five categories, not three. Three are template messages — marketing, utility and authentication. Two are not: service messages, which are ordinary replies such as plain text and images, and Meta Business Agent messages.[1]
- Marketing templates are always charged.[1]There is no window in which promotional sends are free, and marketing is the one template category with no volume tiers.[1]
- Utility templates are now charged too. Until 1 October 2026 a utility template delivered inside an open customer service window was free; Meta ended that exemption on that date.[4] An order update sent seconds after a purchase now costs the same as one sent two days later.
- Utility and authentication templates are priced by volume tier — both categories, not authentication alone — assessed across your whole business portfolio rather than per WhatsApp Business Account, and reset monthly.[1]
- Service messages are free for the first 1,000 delivered per business phone number per month. From the 1,001st, they are charged.[4] The allowance resets monthly and does not roll over, and it is per phone number — so the same total volume costs different amounts depending on how it is spread across your numbers.
- Meta Business Agent messages are priced per token, not per message, at one global rate rather than a per-country one. They have neither volume tiers nor a free allowance.[1]
The customer service window still matters, but it now governs permission rather than price: it is what lets you send a free-form reply at all instead of a template. It no longer makes that reply free.
The one window in which messages are genuinely free is the Free Entry Point window. It opens when a customer reaches you through an ad that clicks to WhatsApp on the Android or iOS app — desktop and web do not qualify — and you reply inside the customer service window. It can remain open for up to seven days.[1]Marketing, utility, authentication and service messages are all free inside it; Meta Business Agent messages are still charged.[1]
Correction — what changed on 1 October 2026
What is specific to India
Two India-specific things are worth knowing before you plan a budget.
Billing is localised to INR. Meta’s documentation records billing localisation for India effective 1 January 2026, with a migration deadline of 31 December 2026.[1] If your account was created before localisation, check which currency it actually bills in rather than assuming — this is the kind of detail that only surfaces at reconciliation.
Rates move on a published schedule. Meta’s pricing documentation notes rate changes for marketing in January 2026 and for authentication-international in April 2026, with current rate cards effective 1 July 2026 and further market rates dated 1 October 2026.[1]
Why there are no rupee figures on this page
Building a cost estimate that survives contact with reality
The variable that dominates a WhatsApp budget is not the per-message rate. It is the mix — specifically, what proportion of your sends are marketing templates. In India, marketing is several times the rate of utility or authentication, so two businesses sending identical volumes can differ several times over in cost on that split alone.
Note that this used to be true for a second reason as well: utility templates landing inside an open service window were free, which made the timing of a send a cost lever. That stopped on 1 October 2026.[4] The mix still dominates, but now because of the rate gap between categories rather than because any template category has a free path.
To estimate honestly, you need four numbers from your own operation:
- Monthly volume of marketing template sends — the unavoidable cost floor, and the most expensive category.
- Combined monthly volume of utility and authentication template sends. Both are volume-tiered, and the tier is assessed across the whole business portfolio, so these aggregate rather than counting separately.[1]
- Monthly service message volume, and how it is distributed across your business phone numbers — each number carries its own allowance of 1,000 free delivered service messages per month.[4]
- What share of inbound conversation arrives via a Free Entry Point, since messages inside that window — which can stay open for up to seven days — are free in every category except Meta Business Agent.[1]
Nobody can give you a credible monthly figure without those four inputs. If a quote arrives before anyone has asked you for them, it is a price list rather than an estimate. Once you have them, our WhatsApp Business API pricing calculator turns them into a line-by-line monthly figure at Meta’s published rates, and carries the full rate card for all 47 markets.
Why nobody can quote you an exact tiered rate
Setup: what you actually need before you start
Meta’s Cloud API onboarding requires a Meta or Facebook account, a Meta app created in the App Dashboard with the WhatsApp use case, a business portfolio, and a WhatsApp Business Account connected to that app.[2] The documented order is roughly:
- Register as a developer and create the Meta app with the WhatsApp use case.[2]
- Select or create the business portfolio.[2]
- Connect the WhatsApp Business Account in API Setup.[2]
- Generate a temporary access token and send a test message.[2]
- Stand up a webhook endpoint to receive message status callbacks.[2]
- Create a system user in Business Settings and issue a permanent token with
business_management,whatsapp_business_messagingandwhatsapp_business_management.[2]
The temporary token is the single most common cause of a broken go-live
One number that is not interchangeable: the phone number you attach. A number already registered to the consumer WhatsApp or WhatsApp Business app has to be migrated before it can be used with the API, and that is a decision worth making deliberately rather than discovering mid-launch.
Templates: the part that delays launches
Template messages are the only way to message someone outside a customer service window.[3] Every template is classified as authentication, marketing or utility, and that classification drives both what you are allowed to send and what you are charged.[3]
Templates are reviewed automatically on creation or edit. Review can take up to 24 hours, and a template sits In-Review and cannot be sent during that time.[3] Build that into launch planning: a campaign that needs a template edited on the morning of send day may simply not go out.
Approval is not permanent. Templates carry a quality rating derived from usage, customer feedback and engagement, and an already-approved template can be paused because of recurring negative feedback or low read rates.[3] A disabled template cannot be sent at all.[3]
This is the real constraint on WhatsApp marketing
Decisions that cost money later
- Choosing the phone number carelessly. Migrating a number already in use on the consumer app is work, and changing it after launch means everything printed, embedded or linked pointing at the old number is wrong.
- Categorising templates for price rather than purpose. Utility is cheaper than marketing, which creates an obvious temptation. Meta reviews classification, and mis-categorised templates get rejected[3] — usually at the least convenient moment.
- Building without webhooks. Skipping the webhook endpoint gets you sending faster and leaves you with no delivery or read status, which means no way to diagnose anything later.[2]
- Treating WhatsApp as a broadcast channel. The quality system is designed to punish exactly that.[3]
- Leaving replies to a human inbox. Message costs are usually the smaller half of the bill. The larger half is the staffing needed to answer inside the service window. Since 1 October 2026 those replies are themselves charged beyond the first 1,000 per number per month,[4] so reply volume is now a direct cost line as well as a staffing one — which is the main reason to route repetitive questions to automation rather than people.
Sources
Every factual claim above about Meta’s or Google’s behaviour comes from their own documentation, listed here so you can check it.
Related services
We implement this directly — number provisioning, permanent tokens, webhooks and template sets — as WhatsApp Business API integration. Where the goal is campaign sending and journeys rather than platform integration, that sits under WhatsApp marketing automation. If replies need to route into a system rather than an inbox, the connective work is business automation and API integration.