Meta has made three notable changes to the WhatsApp Business Platform this year: it fully sunset the older on-premises API in favour of the Cloud API, it opened a new Calling API that lets businesses place and receive voice calls through the platform, and it added new tools aimed at business discoverability and customer engagement. Together, these changes push every business still on legacy infrastructure to move to the Cloud API, and they expand what "messaging" on WhatsApp actually means for support and sales teams.
The on-premises API is being phased out
Meta's official developer documentation confirms that the on-premises WhatsApp Business API is being sunset, with businesses directed to migrate to the Cloud API (or a Business Solution Provider running on Cloud API infrastructure). For businesses in India that built integrations years ago on the older on-premises setup — common among larger enterprises that wanted to host the API on their own servers — this is not optional housekeeping. Once support ends, unpatched on-premises deployments stop receiving updates and eventually stop working reliably.
If your business (or your IT vendor) still runs an on-premises WhatsApp instance, the practical next step is to plan a migration to Cloud API, either directly through Meta or through a Business Solution Provider like Hyyper that handles the technical migration, message templates, and number verification on your behalf.
A Calling API is now part of the platform
According to reporting from the Mobile Ecosystem Forum, Meta has extended WhatsApp's business tools beyond text and media messaging into voice, with a Calling API that lets businesses initiate and receive calls with customers directly through WhatsApp. This is a meaningful shift: until now, the WhatsApp Business Platform was built almost entirely around messaging (text, images, documents, template notifications). Voice calling opens the door for use cases where a phone conversation is faster than a chat thread — collections follow-ups, appointment confirmations, or support escalations that need a human voice.
For Indian businesses, this matters because WhatsApp is already the default messaging app for most customers, and many support workflows currently jump out to a regular phone call when chat isn't enough. A native Calling API means that jump can happen inside the same WhatsApp thread, with the same customer identity and conversation history, rather than switching to a separate calling system.
New tools for discoverability and engagement
Meta's official business blog (about.fb.com) announced in September 2025 a set of new tools aimed at helping businesses boost engagement, customer support, and discoverability on WhatsApp. While the specifics of each tool matter less than the direction, the pattern is consistent with what Meta has been doing all year: making WhatsApp less of a pure notification channel and more of a place where customers can discover a business, ask questions, and get resolved without leaving the app.
What this means for businesses in India
- Audit your setup. If you're not sure whether you're on the on-premises API or the Cloud API, ask your BSP or check your integration documentation. This is the single most urgent action item from this year's changes.
- Don't rush into Calling API without a plan. Voice calling through WhatsApp is new and will likely need clear opt-in and consent handling, similar to how template messages require pre-approval. Treat it as a new channel to pilot, not a default to switch on for every customer.
- Re-evaluate your WhatsApp presence as a discovery channel, not just a support channel. If Meta is investing in discoverability features, businesses that keep their WhatsApp catalog, profile, and business description up to date stand to benefit more than those treating WhatsApp purely as a support inbox.
None of these changes require an immediate overhaul of how your business uses WhatsApp. But they do mean the platform is moving fast, and businesses that treat their WhatsApp Business API integration as "set up once, ignore forever" risk falling behind on both migration deadlines and new features that competitors will adopt first.
Frequently asked questions
Is the on-premises WhatsApp API still usable?
Meta has officially announced the sunset of the on-premises API and is directing all businesses toward the Cloud API. If you're still running on-premises, you should plan a migration rather than wait for a hard cutoff notice.
What is the WhatsApp Calling API and can Indian businesses use it?
It's a new capability, reported by industry press covering Meta's announcements, that lets businesses place and receive voice calls through the WhatsApp Business Platform rather than only exchanging messages. Availability and rollout details should be confirmed with your Business Solution Provider before enabling it.
Do I need a BSP like Hyyper to migrate to Cloud API?
You can integrate directly with Meta's Cloud API if you have in-house engineering resources, or you can migrate through a Business Solution Provider that manages the technical setup, template approvals, and number migration for you.
