Meta has been reshaping the WhatsApp Business Platform on three fronts that matter directly to Indian businesses: how messages are priced, which API infrastructure businesses must use, and what channels are available beyond text. Marketing message pricing is shifting from a conversation-based model to per-message billing, the older On-Premises API is being phased out in favour of the Cloud API, and Meta has introduced a Calling API that lets businesses handle voice conversations inside WhatsApp. Businesses that haven't reviewed their setup against these changes risk unexpected costs or service disruption.

From conversation-based to per-message pricing

For years, WhatsApp Business API pricing was built around 24-hour conversation windows: a business paid once per open conversation, regardless of how many messages were exchanged inside it. Meta has been moving marketing-category messaging away from this model toward per-message pricing, meaning each individual marketing message sent is billed on its own rather than being bundled into a single conversation charge.

The practical effect is that businesses sending multiple marketing messages within the same window can no longer rely on one flat conversation fee to cover them. Utility and authentication messages, and free service conversations initiated by customers, continue to follow their own rules. Any business running WhatsApp campaigns at volume should recalculate its expected monthly spend under the new structure rather than assuming old conversation-based estimates still hold.

On-Premises API sunset: migration to Cloud API is mandatory

Meta has been retiring the original On-Premises API, the self-hosted version of the WhatsApp Business API that many larger businesses and BSPs ran on their own servers. Businesses still on this infrastructure need to migrate to the Cloud API, Meta's hosted version, to keep sending and receiving messages without interruption.

For businesses working through a Business Solution Provider like Hyyper, this migration is typically handled at the platform level, but it's worth confirming directly that your provider has completed the move. Businesses running their own on-premises setup need to plan the migration themselves, including re-testing webhooks, message templates, and any custom integrations built around the older architecture.

A new Calling API for voice conversations

Alongside text and media messaging, Meta has introduced a Calling API that allows businesses to initiate and receive voice calls with customers directly through WhatsApp, rather than only exchanging messages. This opens WhatsApp up as a channel for support calls, verification calls, and sales conversations without asking a customer to switch to a phone call outside the app.

This is still an emerging capability and adoption will depend on how BSPs expose it to businesses and how comfortable customers are with receiving business calls over WhatsApp. Businesses in support-heavy sectors — banking, insurance, healthcare, logistics — are the most likely early adopters once the feature is broadly available.

What this means for Indian businesses

Indian businesses using WhatsApp for marketing, order updates, and support should treat these changes as a prompt to audit their setup, not ignore them. Key actions:

• Recheck marketing spend forecasts against per-message pricing rather than old conversation-based averages.
• Confirm your BSP's Cloud API status if you were previously on an on-premises deployment, and ask what migration testing was done.
• Separate marketing from utility and service messages in your reporting, since each category is billed and governed differently.
• Watch for Calling API rollout in your BSP's product updates if voice support fits your customer service model.

How to prepare

Talk to your WhatsApp Business Solution Provider about which of these changes already affect your account and which are still rolling out. A good provider should be able to show you a breakdown of your message volume by category (marketing, utility, authentication, service) so you can see exactly where per-message pricing changes your costs, and confirm in writing that your account runs on the Cloud API rather than a legacy on-premises setup.

Frequently asked questions

Does per-message pricing affect all WhatsApp messages?

The shift primarily affects marketing-category messages. Utility, authentication, and free customer-service conversations follow separate pricing and policy rules, so it's worth confirming with your provider exactly which of your message types are affected.

Do I need to do anything if I already use a BSP like Hyyper?

In most cases your BSP handles the underlying Cloud API infrastructure, but you should still ask directly whether your account has been migrated and how the new pricing categories apply to your message volumes.

Is the WhatsApp Calling API available to all businesses now?

It is rolling out gradually rather than being universally available. Availability depends on your Business Solution Provider and Meta's rollout schedule, so check with your provider for a timeline specific to your account.