WhatsApp Business API Pricing & Setup in India

Since 1 July 2025 Meta bills the WhatsApp Business Platform per message, not per conversation. The charge lands when a template message is delivered, and the rate depends on the template’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.

Three things follow from this, and they are the three that surprise people on their first invoice:

• Marketing templates are always charged.^[1]There is no window in which promotional sends are free.
• Utility templates are charged only outside an open customer service window. Delivered inside one, they are free.^[1]An order update sent while the customer is mid-conversation costs nothing; the same template sent two days later does.
• Authentication templates are priced by volume tier, which is assessed across your whole business portfolio rather than per WhatsApp Business Account.^[1]

Non-template messages — plain text, images and so on — sent inside an open customer service window are not charged.^[1] Neither is anything sent inside a 72-hour Free Entry Point window, which opens when a customer reaches you through an ad that clicks to WhatsApp or a Facebook Page call to action.^[1]

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]

The variable that dominates a WhatsApp budget is not the per-message rate. It is the mix — what proportion of your sends are marketing templates (always charged), versus utility templates landing inside an open service window (free). Two businesses sending identical volumes can differ several times over in cost on that split alone.

To estimate honestly, you need four numbers from your own operation:

1. Monthly volume of marketing template sends — the unavoidable cost floor.
2. Monthly volume of utility template sends, split by whether they typically land inside or outside a service window. Order confirmations sent seconds after a purchase usually land inside; dormant re-engagement does not.
3. Monthly authentication volume, which determines your tier.^[1]
4. What share of inbound conversation arrives via a Free Entry Point, since everything inside that 72-hour window is free.^[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.

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:

1. Register as a developer and create the Meta app with the WhatsApp use case.^[2]
2. Select or create the business portfolio.^[2]
3. Connect the WhatsApp Business Account in API Setup.^[2]
4. Generate a temporary access token and send a test message.^[2]
5. Stand up a webhook endpoint to receive message status callbacks.^[2]
6. Create a system user in Business Settings and issue a permanent token with business_management, whatsapp_business_messaging and whatsapp_business_management.^[2]

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.

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]

• 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 — which is also where the free messaging sits, so response speed is a cost lever as well as a service one.