WhatsApp is expanding beyond messaging into business voice with a new Calling API, while Meta continues to phase out the older On-Premises API in favour of the Cloud API. If your business still runs WhatsApp Business API on-premises infrastructure, or you're evaluating voice as a new customer contact channel, both changes are worth understanding before they affect your operations.
WhatsApp's New Calling API
Meta has opened what industry observers are calling a new front in business voice: a Calling API that lets approved businesses initiate and receive voice calls with customers directly through the WhatsApp Business Platform, alongside existing messaging capabilities. This puts WhatsApp in more direct competition with traditional telephony and cloud contact-centre providers, many of which already serve as the backbone for customer support and sales calls in India.
For Indian businesses, this matters because a large share of customer interactions — order confirmations, delivery updates, collections calls, appointment reminders — still happen over phone calls that sit outside any unified conversation history. A Calling API integrated with WhatsApp messaging could let businesses keep both channels in one thread, with the same customer profile, opt-in status, and conversation logs.
What to check before adopting it
- Consent and opt-in: Voice calling on WhatsApp will likely require explicit customer consent, similar to template message rules — do not assume existing messaging opt-ins cover calls.
- Business Solution Provider support: Confirm with your BSP or platform (including Hyyper) whether Calling API access is available for your business vertical and account, since Meta typically rolls out new capabilities in phases.
- Use case fit: Calling makes sense for time-sensitive, high-context conversations (loan follow-ups, delivery exceptions, appointment confirmations) rather than blanket outreach.
The On-Premises API Sunset Continues
Separately, Meta has been steadily retiring the On-Premises API — the self-hosted version of WhatsApp Business API that many enterprises adopted in the platform's early years — and pushing all businesses toward the Cloud API, which Meta hosts and manages directly. Meta's own developer documentation confirms this sunset is an ongoing process, not a single cutover date.
Businesses still running On-Premises deployments should treat this as an active migration item rather than a future concern. Cloud API generally offers faster feature rollout (new message types, templates, and now voice), lower infrastructure overhead, and direct alignment with Meta's roadmap. Businesses that delay migration risk losing access to new features first, and eventually losing API access altogether once a given on-premises version is deprecated.
What This Means for Indian Businesses
Two practical takeaways: first, if you or your BSP still operate On-Premises API infrastructure, start planning a Cloud API migration now rather than waiting for a forced cutover — most BSPs, including Hyyper, can support this transition with minimal disruption to existing chatbots, templates, and customer data. Second, keep an eye on Calling API availability in your account; even if you don't plan to use voice immediately, understanding the consent and access requirements now will save time if you decide to pilot it later, particularly for sectors like BFSI, healthcare, and logistics where voice remains a primary channel.
Frequently Asked Questions
Do I need to migrate from On-Premises API immediately?
Meta has not published a single hard deadline for all versions, but the sunset is progressive — older on-premises versions lose support first. Businesses should plan migration to Cloud API proactively rather than waiting for forced deprecation.
Will WhatsApp Calling API cost extra?
Meta has not published detailed India-specific pricing for the Calling API at this time. Businesses should confirm costs and billing structure with their BSP before enabling it, since WhatsApp typically prices new capabilities separately from conversation-based messaging fees.
Does moving to Cloud API affect my existing chatbot or templates?
A well-planned migration should preserve your approved templates and business profile, but chatbot logic, webhooks, and integrations tied to on-premises infrastructure will need to be reconfigured for the Cloud API's endpoints. Work with your BSP to test this before cutover.
