Meta has rolled out several significant changes to the WhatsApp Business API covering pricing, infrastructure, AI policy, and new communication features. This post summarises the changes that matter most for Indian businesses running WhatsApp-based marketing, support, or sales, and explains what each one means in practice.
Pricing model has shifted away from conversation-based billing
For years, WhatsApp Business API pricing was based on 24-hour conversation windows — a business paid once per conversation category (marketing, utility, authentication, service) regardless of how many messages were exchanged inside that window. Meta has been moving this model toward per-message pricing for template-based conversations, particularly for marketing messages. In practice, this means businesses that send multiple template messages within a single conversation window may now be billed per message sent rather than a flat conversation fee.
For Indian businesses, the practical takeaway is that message volume and template usage now matter more directly to your monthly bill. It is worth auditing how many marketing templates you send per customer conversation and whether some of that volume could shift to free-form service replies within an existing 24-hour service window.
The on-premises API has been sunset
Meta has officially discontinued the on-premises WhatsApp Business API, the self-hosted version that many larger enterprises used before the Cloud API existed. Businesses still running on-premises infrastructure need to migrate to the Cloud API or work through a Business Solution Provider (BSP) that has already made this move. If your business or vendor has not migrated yet, this should be treated as an operational priority rather than something to defer, since Meta is no longer maintaining the on-premises stack.
WhatsApp is opening up business voice calling
Meta has introduced a Calling API that lets businesses initiate and receive voice calls with customers directly through WhatsApp, extending the platform beyond text and template messaging. This is a meaningful expansion for use cases like appointment confirmations, delivery coordination, and support escalations where a phone conversation is faster than a chat thread. Businesses evaluating WhatsApp as a full customer communication channel — not just a messaging channel — should watch how calling rolls out to BSPs and what verification or opt-in requirements apply.
New terms restrict general-purpose AI chatbots
Meta updated WhatsApp Business terms to bar general-purpose AI chatbots — assistants designed to answer open-ended questions on any topic, rather than serve a specific business purpose — from operating on the platform. This is directly relevant to any business building AI-driven WhatsApp automation: the API is intended for business-specific use cases such as order support, bookings, and product queries, not as a general-purpose consumer chat interface. Businesses building AI agents on WhatsApp should scope bots narrowly around their own products, services, or support flows to stay within policy.
Meta's own AI agent tools for business are now global
Meta has made its AI agent building tools for WhatsApp Business available globally, allowing businesses to set up AI-driven customer interactions using Meta's native tooling rather than relying solely on third-party platforms. This gives businesses another route to add automated responses on WhatsApp, alongside BSP-built solutions, and is worth evaluating against existing automation setups for cost and control trade-offs.
What Indian businesses should do now
- Review your conversation and template usage to understand exposure to per-message pricing changes.
- Confirm with your BSP or IT team that you are fully migrated off the on-premises API.
- If you use or plan to use an AI chatbot on WhatsApp, make sure its scope is tied to your specific business use case, not general-purpose conversation.
- Keep an eye on Calling API rollout timelines if voice is relevant to your customer journey.
Frequently asked questions
Does the pricing change affect service conversations too?
The shift toward per-message pricing has primarily affected template-based conversation categories such as marketing. Free-form service replies within an existing 24-hour window are generally treated differently, but businesses should confirm current category rules with their BSP since Meta continues to refine this structure.
Is the on-premises API still usable at all?
No. Meta has sunset the on-premises API, meaning it is no longer supported or maintained. Businesses still on it should prioritise migration to the Cloud API.
What counts as a "general-purpose" chatbot under the new terms?
Broadly, an assistant built to answer open-ended questions unrelated to a specific business's products or services. A support bot that answers order status, booking, or product questions for your business is not what the restriction targets.
Is WhatsApp voice calling available to all businesses yet?
The Calling API is a newer capability and availability depends on rollout through BSPs. Businesses interested in voice should check with their WhatsApp API provider on current access.
