WhatsApp ended 2025 with three developments Indian businesses using the Business API should track: Meta opened a Calling API for business voice calls, Italy's competition authority ordered Meta to suspend a policy that blocked rival AI chatbots from WhatsApp, and industry trackers are flagging Cloud API changes expected around April 2026. None of these are rumours — they come from Meta's own changelog, a Mobile Ecosystem Forum report, and TechCrunch's coverage of the Italian ruling. Here is what each one actually means for a business sending WhatsApp messages in India today.
WhatsApp's Calling API: voice joins the messaging stack
In December 2025, Meta introduced a Calling API for WhatsApp Business, extending the platform beyond text, media, and template messages into business-initiated voice calls. This is a meaningful shift for the platform's positioning: WhatsApp has been a messaging-first channel for support and marketing in India, and voice calling opens it up as a channel for use cases that genuinely need a live conversation — collections follow-ups, appointment confirmations, high-value sales conversations, or escalations that a chatbot can't resolve.
For Indian businesses, the practical question is sequencing: calling will likely roll out through Business Solution Providers (BSPs) rather than as a self-serve toggle, similar to how templates and flows were introduced. If your business already runs support or sales over the WhatsApp Business API, it's worth asking your BSP when calling access will be available and what it will cost, since Meta has historically priced new capabilities separately from conversation-based messaging.
Italy's ruling on rival AI chatbots — why it matters even outside Italy
Also in December 2025, Italy's competition authority (AGCM) directed Meta to suspend a WhatsApp policy that restricted rival AI chatbots from operating on the platform, according to TechCrunch. The underlying policy had limited how competing AI assistants — distinct from Meta AI — could be deployed inside WhatsApp, and Italian regulators found this restricted competition.
This is an Italy-specific enforcement action, not a global policy reversal, so Indian businesses should not assume immediate changes to what's permitted on WhatsApp in India. But it is a signal worth watching: regulators in one major market pushing back on platform-level restrictions around AI chatbots often precedes similar scrutiny elsewhere, and it affects how any business integrating third-party AI assistants (beyond Meta's own AI) into their WhatsApp presence should think about platform risk going forward.
Cloud API changes expected around April 2026
Several industry blogs tracking Meta's developer changelog are flagging further Cloud API adjustments expected around April 2026, with early signals pointing toward privacy-related changes to how business data and message metadata are handled. Meta has a pattern of rolling out API and policy changes with a notice period through its official developer changelog rather than through press releases, so the most reliable source remains Meta for Developers directly rather than secondary write-ups.
The practical takeaway: if your business runs WhatsApp API messaging through a BSP like Hyyper, this kind of change is typically absorbed at the platform level with advance notice — but it's still worth asking your provider now whether any account configuration, opt-in flows, or data handling on your end will need adjustment before April.
What Indian businesses should do now
- Ask your BSP about Calling API availability and pricing timelines rather than waiting for a public announcement.
- If you use any third-party AI chatbot layered on top of WhatsApp (not just Meta AI), keep an eye on how platform policy in other markets evolves — it can signal future restrictions or freedoms in India.
- Check your BSP's changelog monitoring process for the April 2026 Cloud API changes, and confirm data handling practices are already compliant with India's data protection expectations.
- Continue treating Meta's official developer changelog as the primary source of truth over social media summaries or unofficial roundups.
