WhatsApp's Business Platform has gone through real structural change over the past year: Meta has retired the older On-Premises API in favour of the Cloud API, it is rolling out a Calling API that lets approved businesses make and receive voice calls over WhatsApp, and regulators outside India have started questioning how Meta treats rival AI chatbots on the platform. None of this is speculative — these are documented platform and policy shifts that directly affect how businesses in India should plan their WhatsApp integrations.

The On-Premises API is gone — Cloud API is now the standard

Meta has sunset the On-Premises API, which used to require businesses or their partners to host and maintain their own WhatsApp Business API servers. New integrations are only possible through the Cloud API, which Meta hosts directly. For businesses still running legacy on-premises setups through older BSP (Business Solution Provider) relationships, this means migration is no longer optional — it is a prerequisite for continued access to WhatsApp messaging at scale.

For most Indian businesses working with a BSP such as a CRM or marketing platform layered on top of WhatsApp, this shift is largely invisible day-to-day, since providers have already migrated backend infrastructure. But if you or your IT team manage a direct, self-hosted integration, this is worth confirming with your solution provider now rather than during an outage.

Voice is becoming a business channel

WhatsApp has introduced a Calling API, extending the platform beyond messaging into business-initiated and business-received voice calls. This is a meaningful expansion of what