WhatsApp's Business Platform has seen three significant developments recently: the introduction of a Business Calling API, new terms restricting general-purpose AI chatbots, and the ongoing sunset of the older On-Premises API. If your business sends WhatsApp messages for support, sales, or marketing, each of these affects how you should plan your WhatsApp strategy over the next few months.
WhatsApp Business Calling API
Meta has extended the WhatsApp Business Platform beyond messaging into voice. The Business Calling API lets approved businesses make and receive voice calls with customers directly through WhatsApp, using the same phone number already verified for business messaging. Reported use cases include click-to-call support, voice-based OTP verification, and outbound calls for sales or service follow-ups initiated from within a WhatsApp conversation.
For Indian businesses, this matters because a large share of customer support and sales conversations already happen over phone calls, often alongside a WhatsApp chat. Being able to move between text and voice on the same number, without asking a customer to switch apps or numbers, can simplify support workflows for sectors like banking, logistics, healthcare, and e-commerce delivery coordination, where voice confirmation is still common.
New Terms Restrict General-Purpose AI Chatbots
WhatsApp has updated its platform terms to bar general-purpose AI chatbots — that is, bots designed to hold open-ended conversations on any topic, similar to a standalone AI assistant — from operating on WhatsApp. The policy is aimed at keeping the platform focused on business messaging use cases: customer support, order updates, appointment reminders, catalog browsing, and similar transactional or service-oriented conversations tied to a specific business.
This does not affect the vast majority of businesses using WhatsApp API for legitimate customer service or marketing automation. A support bot that answers questions about your orders, products, or bookings is a business use case and remains fully permitted. What the policy targets is the use of WhatsApp as a distribution channel for general-purpose conversational AI products unrelated to a specific business's operations. If your WhatsApp automation is scoped to your own business's customer interactions, this change should not require any action.
On-Premises API Continues Its Sunset
Meta has been phasing out the older On-Premises API in favour of the Cloud API for several years now, and the sunset process continues. Businesses still running On-Premises API deployments should treat migration to the Cloud API (or to a Business Solution Provider that manages Cloud API access, such as Hyyper) as a priority rather than something to defer. Meta's own developer documentation lays out the sunset timeline and migration steps, and businesses that wait until the last possible date risk service disruption.
The Cloud API is hosted and maintained by Meta, which means faster access to new features (including things like the Calling API above), fewer infrastructure responsibilities for the business, and generally simpler onboarding through official partners.
What This Means for Indian Businesses
None of these three changes require most businesses to overhaul their WhatsApp strategy, but they are worth factoring into near-term planning:
- If you still run an On-Premises API setup, plan your migration to the Cloud API now rather than waiting for a deadline notice.
- If you are exploring AI-powered WhatsApp bots, keep them scoped to your own products, services, and customer interactions rather than building an open-ended assistant.
- If voice support is a meaningful part of your customer journey, keep an eye on Calling API availability for your business category and region, since it could reduce the need for separate calling infrastructure.
As with most platform-level changes on WhatsApp, the practical impact depends on how a business is currently using the API. Businesses working with an established WhatsApp Business Solution Provider typically have these transitions handled as part of ongoing platform maintenance.