The AI Chatbot on Your WhatsApp Business Does Not Belong to You
The AI chatbot on your WhatsApp Business does not belong to you. It belongs to whoever controls the API — and in October 2025, Meta tried to make that exclusively their AI.
In October 2025, Meta updated its WhatsApp for Business API terms to ban third-party AI assistants from the platform. ChatGPT integrations, Microsoft Copilot connections, custom AI chatbots built on OpenAI or Anthropic APIs — all blocked from accessing the WhatsApp Business API. Only Meta AI would remain. For Malaysian businesses that had built AI customer service workflows on WhatsApp using third-party tools, this was a silent rule change affecting live deployments.
In Europe, the EU Commission launched a formal investigation in December 2025 and on June 9, 2026, issued interim measures ordering Meta to restore access within five working days. The EU called it an abuse of Meta’s dominant position. Meta called it regulatory overreach and is appealing. The order covers EU markets. Malaysia is still under Meta’s October 2025 terms.
Who this really matters to:
→ Malaysian businesses using third-party AI chatbots — Tidio, Freshdesk, custom GPT-based bots — through the WhatsApp Business API: Meta’s October 2025 change restricted this; the EU ruling restored it for European deployments only; Malaysian deployments remain on the restricted terms → Malaysian e-commerce sellers and service businesses whose customer conversations on WhatsApp are handled by AI tools not built by Meta: check which API access tier your vendor currently operates under — it may have changed since you went live → Malaysian agencies that built WhatsApp AI integrations for clients: those integrations were built under terms that existed before October 2025; confirm current access status with your API vendor before assuming the original setup still holds → Malaysian businesses planning WhatsApp-native AI customer service infrastructure: the platform’s API access rules are under active legal dispute in Europe; what you build around today may not be the rules in place when you scale
MULTIPLE PERSPECTIVES
Meta’s position has commercial logic. The WhatsApp Business API is Meta’s infrastructure. Allowing OpenAI and Microsoft to run AI assistants through it puts competing products on Meta’s distribution network at Meta’s cost. The EU’s problem is not the competitive instinct — it is that WhatsApp holds dominant market position in enough countries that restricting API access becomes a gatekeeper decision, not a product choice. The Digital Markets Act gives the EU Commission the authority to force that back open. Malaysia has no equivalent legislation.
In Malaysia, WhatsApp holds the same dominant position it holds in the European markets where the EU ruled against Meta. The regulatory power to enforce openness does not travel with the technology. Malaysian businesses are building AI workflows on a platform whose access rules changed once without warning and could change again. The EU ruling created a temporary European exception. It did not change Meta’s long-term product direction — which, from October 2025 until June 9, was unambiguous.
The practical gap most businesses miss: platform terms are contractual documents that update. If you have not re-read the WhatsApp Business API terms since October 2025, you are operating on a mental model that predates the last major change. And you would not necessarily know when the next one lands.
If the platform your AI customer service runs on changed its terms while your deployment was live — would your business know within a week?
If your WhatsApp AI runs through an official API vendor — 360dialog, Twilio, MessageBird — your vendor absorbed the October change first. Confirm with them what your current access tier and terms look like.
If you built a direct or custom WhatsApp Business API integration in-house or through a smaller agency — the October 2025 terms are the operative document. Read them.
Building customer infrastructure on someone else’s platform means you are a tenant. Read your lease.

— Tony
Sharing what I learn building real things with AI.