WhatsApp's Business Platform is moving beyond one-way and two-way text messaging. In the past year, Meta has introduced a Calling API for businesses, started testing a dedicated inbox folder for messages from large senders, and pushed Meta Business Agent as an AI layer on top of the existing Cloud API. At the same time, regulators in Europe are questioning how Meta controls which chatbots can operate on WhatsApp. None of this changes how the Cloud API works today, but it does change what businesses should plan for over the next few quarters.
WhatsApp Calling API: Voice Joins Chat
Meta has opened a Calling API that lets approved businesses place and receive voice calls with customers directly through WhatsApp, using the same phone number and business profile customers already recognise from chat. This is aimed at use cases where a conversation needs a human voice — support escalations, collections follow-ups, delivery coordination, or sales calls — without forcing the customer to dial a separate number or switch apps. For businesses that already route support through WhatsApp chat, this closes a long-standing gap: today, if a chat conversation needs a call, the business has to ask for a phone number and call outside the platform, losing context and audit trail.
What this means practically
- Voice and text can now sit inside the same customer thread, which matters for support teams that need a single record of interaction.
- Access is rolling out through approved Business Solution Providers rather than being open to every API user on day one.
- Businesses should expect calling to carry its own pricing and consent rules, separate from message-based conversation pricing.
A New Inbox Folder for High-Volume Senders
WhatsApp is also testing a separate folder inside the consumer app for messages from large businesses, distinct from the regular chat list. The intent appears to be giving users a way to see but not be overwhelmed by messages from brands, while keeping personal chats uncluttered. For businesses sending notifications, marketing templates, or OTPs at scale, this is worth watching closely: if a conversation lands in a secondary folder rather than the primary inbox, open rates and response times could shift, even though the message itself still gets delivered. This is still a test, not a global rollout, but it signals where Meta is heading with high-volume business messaging.
Meta Business Agent: An AI Layer on Top of the API
Meta Business Agent is positioned as an AI assistant that businesses can configure to handle catalog browsing, product recommendations, and routine queries on WhatsApp, sitting on top of the existing Business Platform rather than replacing it. For businesses already using the Cloud API with a chatbot or BSP-built automation, Business Agent is effectively a Meta-native alternative worth evaluating against existing vendor tooling, rather than a mandatory change.
Regulatory Scrutiny Is Increasing
Separately, Italian regulators have told Meta to suspend a WhatsApp policy that restricted rival AI chatbots from operating on the platform, arguing it unfairly favours Meta's own AI. This doesn't change anything for a typical Indian business using WhatsApp for support or marketing, but it is an early sign that regulators are starting to scrutinise how much control platform owners exert over what businesses and third parties can build on WhatsApp. Businesses relying on third-party AI chatbots for WhatsApp should keep an eye on how this plays out, since similar questions could surface in other markets.
On-Premises API: The Sunset Is Real
Meta has published a formal sunset plan for the legacy On-Premises API, the self-hosted predecessor to the Cloud API. Businesses still running On-Premises deployments need to migrate to the Cloud API or a BSP-hosted equivalent to keep receiving platform updates, including the features above. If your business or your current WhatsApp vendor has not confirmed which API version you're on, that's worth checking now rather than during a support outage.
What Indian Businesses Should Do
None of these changes require immediate action for most businesses already on the Cloud API through a provider like Hyyper. The practical steps are: confirm you're not still on the On-Premises API, ask your provider whether Calling API access is on their roadmap if voice matters to your use case, and watch template message performance over the coming months in case the new inbox folder affects delivery visibility for high-volume senders.
Frequently Asked Questions
Do I need to do anything if I'm already using the Cloud API?
No immediate action is required. The Cloud API continues to be the standard platform; Calling API and Business Agent are additions on top of it, not replacements.
Is WhatsApp Calling API the same as a normal phone call?
It uses VoIP through the WhatsApp Business Platform rather than the telecom network, tied to the business's existing WhatsApp number and profile, and is being rolled out through approved providers first.
What happens if I'm still on the On-Premises API?
Meta has set a formal sunset timeline for On-Premises deployments. Businesses on this legacy setup should plan migration to the Cloud API through a Business Solution Provider to avoid losing functionality or support.
Will the new inbox folder hurt my message open rates?
It's still being tested in limited markets, so the impact isn't confirmed. Businesses sending high volumes of template or notification messages should monitor delivery and read metrics closely if they notice changes.
