WhatsApp Business API pricing has shifted from the long-standing 24-hour conversation model to per-message billing for marketing messages, while utility, authentication, and service messages continue to follow their own rules. Meta has also retired the On-Premises API, meaning any business still running it must move to the Cloud API. Together, these two changes affect how Indian businesses should plan messaging budgets and technical infrastructure for WhatsApp in 2026.

From conversations to per-message billing

Since the Cloud API's global rollout in 2022, WhatsApp billed businesses per conversation — a 24-hour messaging window opened by either the business or the customer. All messages exchanged within that window, regardless of number, counted as one billable unit. Meta has since moved marketing-template messages to a per-message pricing model, meaning each individual marketing message sent is billed on its own rather than bundled into a 24-hour window. This is a meaningful shift for businesses that send high volumes of promotional or campaign messages, because the cost now scales directly with message count rather than with how many separate conversations those messages fall into.

Utility, authentication, and service conversations continue to operate under different rules, so the practical effect depends heavily on a business's message mix. A company sending mostly order updates and OTPs will see less change than one running frequent broadcast campaigns.

The four conversation categories still matter

Even with the pricing shift, WhatsApp continues to classify messages into four categories, and understanding them is essential to controlling costs:

• Marketing: Promotional messages, offers, and campaign broadcasts — now billed per message.
• Utility: Transactional updates tied to an existing order or account, such as shipping or payment confirmations.
• Authentication: One-time passwords and login verification codes.
• Service: Replies to customers who message the business first, within the 24-hour customer-initiated window. These have historically been free or heavily discounted, since they represent support conversations rather than outbound promotion.

For most Indian businesses, the practical strategy is unchanged in principle: keep as much conversation as possible inside the free or low-cost service window by encouraging customers to message first, and be deliberate about how many marketing template messages go out, since each one now carries its own individual cost.

On-Premises API is gone — migration is mandatory

Meta has sunset the On-Premises API, the older self-hosted version of WhatsApp Business API that many enterprises ran on their own servers before Cloud API existed. Businesses still operating on-premises deployments need to migrate to the Cloud API, either directly through Meta or through a Business Solution Provider. This isn't optional — on-premises installations are no longer supported, which means no security patches, no new features, and eventual service disruption for anyone who hasn't moved.

For businesses that migrated years ago, this changes nothing. For the smaller number still on legacy infrastructure — often larger enterprises with custom server setups — this is the deadline to plan a Cloud API migration through a verified BSP rather than deferring it further.

What this means for budgeting

Indian businesses running WhatsApp campaigns should now model costs at the message level rather than assuming conversation-based bundling will absorb volume. Segmenting campaigns, avoiding redundant marketing sends to the same customer, and pushing more interactions into customer-initiated service windows are the levers that actually control spend under the new model. Working with a BSP that provides clear per-category cost visibility makes it easier to see exactly where marketing spend is going before a campaign scales.

Frequently asked questions

Is the 24-hour conversation window gone completely?

No. It still applies to utility, authentication, and service messages. Only marketing messages have moved to per-message billing.

Are service conversations still free?

Service conversations — replies to customers who initiate contact — remain free or low-cost under WhatsApp's pricing model, encouraging businesses to prioritise inbound customer engagement.

What happens if my business is still on the On-Premises API?

You need to migrate to the Cloud API. The On-Premises API is no longer supported by Meta, so continuing to run it risks service interruptions and security gaps.

Does this pricing change affect authentication (OTP) messages?

No, authentication messages continue to follow their existing pricing structure separate from the marketing per-message change.