BLOG · REGULATION

Brussels orders Meta to open WhatsApp to rival AI assistants — a lesson in channel risk

Regulation
  • #regulation
  • #antitrust
  • #whatsapp
  • #meta
  • #ai-assistant
  • #platform-risk
  • #operator-lens

On 9 June 2026 the European Commission imposed interim measures on Meta and ordered it to restore free access to the WhatsApp Business API for external AI assistants. It's an interim measure in a dispute Meta is appealing — and, along the way, a lesson for anyone building an AI assistant on someone else's channel: access to a platform isn't your property.

Adam WszendybyłAI operator-architect

What happened

On 9 June 2026 the European Commission imposed interim measures on Meta — the first such measures in an antitrust proceeding in over a decade — and ordered it to restore free access to the WhatsApp Business API for external general-purpose AI assistants, on the terms in force before 15 October 2025. Meta got five working days to comply, and delay carries a fine of up to 10% of annual worldwide turnover. The measures are to remain in force until the proceeding concludes.

The background to the events matters for judging how durable this access is. In October 2025 Meta blocked AI providers from using WhatsApp Business where artificial intelligence is the main service. In December 2025 the Commission opened a proceeding; in February and April 2026 it issued objections; and when Meta restored access in March 2026 — but for a fee — Brussels deemed the fee equivalent to the earlier block. Meta has announced an appeal, calling the decision excessive regulatory interference. That means one thing: we're talking about an interim measure in an ongoing dispute, not a final ruling.

Our thesis

The most important thing in this case isn't who beats Meta, but what it teaches anyone building an AI assistant on someone else's channel. Access to WhatsApp — like access to any large channel for communicating with clients — isn't your property. It's a permission a gatekeeper can narrow, price or revoke, and one that today rests on a regulator's decision being appealed to court. If your client contact via an AI assistant rests entirely on one such channel, your roadmap is someone else's political decision.

The practical takeaway is the same as with the dependency on a single cloud vendor we wrote about in the note "The EU Cloud and AI Development Act": the risk isn't which channel you operate on today, but how expensive it will be to move the assistant's logic elsewhere when the access terms change. Use the recovered access — but don't design the product as if that access were given forever.

Why it matters

Private Equity

For a fund, this is a new item in the diligence of companies whose customer-service model rests on one platform's messenger. The question isn't "do they have a WhatsApp integration," but "what happens to their revenue if the access terms change overnight." A company whose client contact has one entry point controlled by a gatekeeper has a quantifiable risk here — and it's worth pricing before signing, not after the first change of terms.

Enterprise

For a large organization, this is a signal to separate two layers that are easy to fuse into one: the assistant's logic (what it understands, which tools it calls, how it runs the conversation) from the channel through which it reaches the client. If those two layers are fused, every change on the platform's side means rewriting the product. If they're separated, changing the channel is a configuration, not a project. The same question we ask about the model vendor should be asked about the distribution channel.

SMB / mid-market

This hits hardest here, because for many smaller companies WhatsApp Business isn't one of the channels but the main way of talking to clients. The good news: the regulator has just sided with those who want to plug in their own assistant rather than pay the platform a toll. The less good: this access is fresh, contested and depends on the outcome of the appeal. If you're planning to automate service on WhatsApp, base it on a layer that can be ported to another channel — we write more about this under automations for SMBs.

One step you can take this week

Take a process where your assistant or automation talks to a client, and write down two things: which channel it goes through and what it would actually take to run the same thing through another channel. If the answer is "rewrite from scratch," you have a dependency that isn't under your control — and a topic for the coming quarter. The goal isn't to abandon WhatsApp, but to make sure the platform's decision or the appeal's outcome doesn't halt your customer service.

Describe your case

If your company's customer service rests on one channel and you want to know what it would cost to make it independent, bring one process and the name of the channel it runs on. We start from something concrete. Describe your case: mailto:[email protected]?subject=Rozmowa%20z%20Aurora%20AI.

LET'S START

Bring the process, not the slides.

If you read our blog and spot an area you want to improve in your own organization — write to us. We start every conversation from something concrete.