2025 was an eventful year for the WhatsApp Business API. Meta rolled out a Calling API for the platform, retired the older On-Premises API in favour of the Cloud API, tightened its rules on general-purpose AI chatbots, and changed how conversation-based pricing works. If your business runs customer support, marketing, or sales on WhatsApp, several of these changes directly affect your setup, your costs, or your compliance posture.
A native Calling API joins messaging
Meta introduced a WhatsApp Business Calling API, extending the platform beyond text, media, and template messages into voice. This lets businesses initiate or receive voice calls with customers inside WhatsApp itself, using the same number and business profile customers already recognise. For sectors like collections, appointment reminders, delivery coordination, and high-value sales follow-ups, this closes a real gap — until now, businesses had to push customers off WhatsApp to a phone call or a separate app to have a voice conversation.
For Indian businesses, this matters because WhatsApp is often the primary channel customers already trust. A voice option native to that same thread reduces friction, particularly for use cases like loan follow-ups, healthcare consultations, or logistics updates where a quick call resolves things faster than a chat exchange.
Meta restricts general-purpose chatbots
In October 2025, WhatsApp updated its terms of service to bar general-purpose AI chatbots — assistants designed to answer any question on any topic, unrelated to a specific business's products or services — from operating on its platform. The change is aimed at AI assistants that use WhatsApp as a generic chat interface rather than as a customer service or transactional channel for a specific business.
This does not affect business-specific automation: bots that handle order status, FAQs about your products, appointment booking, or support tied to your business remain fully compliant. But businesses that repurposed WhatsApp numbers to run broad, ChatGPT-style assistants unrelated to their core offering should review their bot's scope against Meta's updated terms to avoid enforcement action.
On-Premises API is being sunset — migrate to Cloud API
Meta has been retiring the older On-Premises API, its self-hosted version of the Business API, in favour of the Cloud API, which Meta hosts and maintains directly. Businesses and BSPs (Business Solution Providers) still running On-Premises deployments need to plan migration to Cloud API or a BSP-managed setup before their access is cut off. This shift also aligns with newer feature rollouts — including the Calling API and updated pricing categories — which are being built for Cloud API first.
If your business or your API provider is still on an On-Premises setup, this is worth confirming now rather than closer to any cutoff date, since migration involves re-verifying webhooks, message templates, and integrations.
Pricing shifted to updated conversation categories
Meta also updated its conversation-based pricing structure during 2025, refining the categories that determine how conversations are charged — broadly split between business-initiated (marketing, utility, authentication) and user-initiated (service) conversations. Businesses sending high volumes of marketing templates or OTPs should check current per-category rates with their BSP or on Meta's official pricing page, since rates and category definitions have been revised more than once through the year and vary by country.
What this means for your business
Taken together, these changes point to WhatsApp positioning itself more firmly as a business-first channel: richer capabilities like calling, clearer boundaries on what kind of AI can run on it, a single modern API path (Cloud API), and a pricing model that keeps evolving. Indian businesses using WhatsApp for support, marketing, or transactions should audit their current setup against each of these four areas — API version, bot scope, pricing category usage, and any pending feature access — rather than assuming last year's configuration still applies.
Frequently asked questions
Do I need to migrate off the On-Premises API immediately?
If you or your BSP are still running On-Premises, plan the migration soon — Meta has been actively sunsetting it, and new features are being built for Cloud API first, not the older system.
Does the chatbot policy change affect customer support bots?
No. The restriction targets general-purpose AI assistants unrelated to a specific business's offering. Support, FAQ, and order-tracking bots tied to your business are not affected.
Is WhatsApp voice calling available to all businesses right away?
The Calling API is a newly introduced capability on the WhatsApp Business Platform; availability and rollout pace can vary by BSP and account, so confirm access with your API provider before building it into your workflow.
Will my messaging costs change because of the pricing update?
Possibly. Conversation category definitions and rates have been revised during 2025, so check current pricing with your BSP rather than relying on older rate cards.
