Meta's WhatsApp AI Chatbot Policy 2026: What Actually Changed

On 15 January 2026, ChatGPT, Microsoft Copilot and Perplexity all went dark on WhatsApp. By the European Commission's own account, users had previously been able to reach "Meta's own assistant, or those of others such as ChatGPT, Perplexity or smaller ones like Luzia or Poke"; from that date, "only Meta's assistant" remained (European Commission, 9 June 2026). Ever since, a rumour has circulated in business groups that Meta "banned AI bots on WhatsApp." That is not what the rule says, and the difference matters enormously if you run customer conversations on the platform.

Here is what Meta's updated WhatsApp Business Solution Terms actually prohibit, what they expressly permit, what a compliant business-specific AI agent has to look like in practice, and how regulators in Italy, Brussels and Brazil have responded so far.

What exactly did Meta change in its WhatsApp AI policy?

Meta added an "AI Providers" clause to the WhatsApp Business Solution Terms in mid-October 2025 that bars general-purpose AI assistants from being the primary product distributed over the WhatsApp Business Platform. It does not restrict businesses from using AI to serve their own customers.

The operative text reads: "Providers and developers of artificial intelligence or machine learning technologies, including … large language models, generative artificial intelligence platforms, general-purpose artificial intelligence assistants … ('AI Providers'), are strictly prohibited from accessing or using the WhatsApp Business Solution … when such technologies are the primary (rather than incidental or ancillary) functionality being made available for use, as determined by Meta in its sole discretion" (WhatsApp Business Solution Terms, 2026).

Two phrases carry all the weight. The first is "primary (rather than incidental or ancillary)". If the AI is the product you are distributing, you are an AI Provider and you are out. If the AI is a means of delivering your actual business — answering questions about your services, taking a booking, checking an order — the AI is ancillary and you are in scope of normal business use. The second is "as determined by Meta in its sole discretion", which is the part nobody likes: the line is drawn by Meta, not by a published test.

The dates are staggered. The updated terms applied immediately to new API users from 15 October 2025, with enforcement against existing users from 15 January 2026 (WhatsApp Business Solution Terms, 2026; TechCrunch, 18 October 2025). That three-month gap is why the visible fallout — assistants going offline — clustered in January rather than October.

Meta's stated rationale, given to TechCrunch by a spokesperson, was narrow and consistent with the text: "The purpose of the WhatsApp Business API is to help businesses provide customer support and send relevant updates" (TechCrunch, 2025). The platform was built as a business messaging channel, and Meta's position is that redistributing an open-domain assistant through it was never the intended use.

Is it true that Meta banned AI chatbots on WhatsApp?

No. Business-specific AI on WhatsApp is expressly permitted, and Meta said so publicly at the time. What is banned is an AI provider using WhatsApp as a distribution channel for a general-purpose assistant.

TechCrunch's reporting on the change is unambiguous: "Meta confirmed this move to TechCrunch and specified that this move doesn't affect businesses that are using AI to serve customers on WhatsApp. For instance, a travel company running a bot for customer service won't be barred from the service" (TechCrunch, 18 October 2025).

The permitted category, as described across Meta's documentation and BSP guidance, covers exactly the things most businesses want:

• Customer service and FAQ handling — answering questions about your products, hours, policies and prices.
• Order management and tracking — status lookups, delivery updates, returns.
• Appointments and reservations — checking availability and booking a slot.
• Transaction notifications — confirmations, reminders, receipts.
• Lead qualification — asking your screening questions and routing the enquiry.

Every one of those is a business using AI on its own conversations. None of them involves reselling an assistant. The practical test to apply to your own setup is simple: if a customer asked your AI to write a poem about the weather in Reykjavik, should it answer? If the honest answer is yes, you are running an open-domain assistant and you are near the line. If it politely declines and returns to your business, you are on the right side of the rule.

Where the myth does bite is in do-it-yourself builds. If you were planning to wire a raw general-purpose model directly into the WhatsApp Business API and let customers talk to it about anything, that route is closed. The compliant path is a purpose-scoped agent that answers from your business's own content. For the field of tools that do this in a Hong Kong context, see our comparison of the best WhatsApp AI tools for Hong Kong businesses in 2026.

Which AI assistants actually disappeared from WhatsApp?

The consumer-facing general-purpose assistants went first, and they went on the enforcement date rather than the announcement date. OpenAI severed ChatGPT's WhatsApp connection in January 2026; Microsoft told Copilot users to migrate before the 15 January 2026 cutoff; Perplexity's WhatsApp number went silent the same day (TechCrunch, 2026; The Verge, 2026; ghacks.net, 2026).

Smaller assistants were caught in the same net. The European Commission's account of the market names Luzia and Poke alongside ChatGPT and Perplexity as assistants users could previously reach on WhatsApp, and records that after 15 January 2026 only Meta AI remained (European Commission, 2026). For a channel that Meta reports is used by billions of people, that is a meaningful consolidation of a distribution surface — which is precisely what drew regulatory attention.

What did not disappear is instructive. Customer-service deployments, booking agents, order bots and lead-qualification flows run by ordinary businesses continued operating through the January cutoff without interruption. There has been no reported wave of enforcement against business-specific agents. The policy did exactly what its text said it would do, and nothing more.

It is worth separating this policy from the reasons WhatsApp Business accounts actually get restricted, because in owner forums the two get blurred. Meta's published causes of bans and limits are, roughly in order of frequency: broadcasts without opt-in; high block and report rates driving your quality rating from green to amber to red; unofficial tools such as GB WhatsApp or non-Meta APIs; mis-categorised templates; sudden volume spikes; and scraped contact lists (Meta, "About account bans," 2026). Running a general-purpose assistant joins that list from 15 January 2026 — but at the bottom of it. If your account is at risk, it is far more likely to be your broadcast hygiene than your AI.

What does a compliant business-specific AI agent have to look like?

It has to be scoped to your own business, honest about being AI, and one message away from a human. Those three properties cover the substance of what Meta's terms and its BSP guidance require of a business-specific agent.

In practice, that breaks down into five operating rules:

1. Scope the conversation to your business. The agent answers from your content — services, prices, policies, availability — and declines open-domain requests. This is the single distinction the AI Providers clause turns on.
2. Do not impersonate a human. Say plainly in the first message that the customer is talking to an AI agent for your business. Beyond Meta's rules, this is also becoming a legal duty in some markets — the EU AI Act's Article 50 transparency obligations have applied since 2 August 2026 and reach non-EU businesses whose output is used in the EU, with fines up to €15 million or 3% of worldwide turnover (EU AI Act Article 99; European Commission, 2026). We cover the detail in our guide to EU AI Act transparency duties for AI customer service.
3. Provide a one-step human handoff that carries the context. The customer should be able to say "I want a person" and get one, with the conversation history intact rather than starting again.
4. Respect the messaging rules underneath. Opt-in before you broadcast, categorise templates honestly, and respect the 24-hour customer service window. Your AI does not exempt you from any of it.
5. Do not pass customer messages to an AI provider for training or for anything beyond serving that customer. This is the data condition that sits alongside the functional one, and it is the one most self-built stacks quietly fail.

None of these is exotic. Most established platforms implement all five by default, because they were built as business messaging tools in the first place. Our own product, Omago, is an AI sales agent scoped to a single business's website and WhatsApp — it answers from that business's real content, qualifies the enquiry and books the appointment, at a flat US$49–99 a month, and is explicitly not a general-purpose assistant. The point is not that one tool is compliant and others are not; it is that the compliance question has a simple shape, and you should be able to answer it about whatever you use.

What have regulators done about it, and could the rule be reversed?

Regulators moved harder and faster on this than on almost any recent platform change, and parts of the policy have already been suspended in specific markets. The rule is in force globally, but it is not settled.

The sequence is worth reading in order:

The AGCM's finding was blunt: the terms "introduced on 15 October and … set to become fully effective by 15 January 2026, completely exclude Meta AI's competitors from the WhatsApp platform," and Meta was ordered to suspend them in Italy (AGCM press release A576, 24 December 2025).

Brussels went further still. On 9 June 2026 the European Commission imposed interim measures requiring Meta to restore free access for competing general-purpose AI assistants on pre-15-October-2025 terms — only the second time in its history that the Commission has used its interim-measures power under Regulation 1/2003, the first being Broadcom in 2009 (European Commission, IP_26_1276, 2026). Executive Vice-President Teresa Ribera framed it directly: "Today we are requiring Meta to restore access to WhatsApp for competing AI assistants while we investigate whether the restrictions violate EU competition rules."

Meta's March 2026 attempt to settle the issue by re-admitting rival assistants for a fee did not resolve it; the Commission's position is that a high enough fee can foreclose the market as effectively as an outright ban, and Ribera stated the fees were set so high that competitors could not sustain them (reported via competition-law press, 2026). By May 2026 Meta had dropped the non-template message charges for AI Providers serving EU/EEA users, while keeping them in Brazil, where CADE is conducting its own fast-track review.

The honest status, as of this writing: the AI Providers clause remains in force in most of the world, is suspended or modified in Italy and the EEA under interim measures, and is exempted in Brazil. Hong Kong, Singapore, Taiwan and the rest of Asia are inside no exemption. If you operate outside the EU and Brazil, the rule applies to you in full.

What does this mean if you run a business on WhatsApp in 2026?

For the overwhelming majority of businesses, the answer is: nothing changes, keep going — but pair the policy question with the cost question, because that is where 2026 actually bites.

Three cost changes matter more to your monthly bill than the AI policy ever will. First, Meta moved the platform from conversation-based to per-template-message pricing on 1 July 2025, with four categories — marketing, utility, authentication and service — priced by the recipient's country (Meta developer documentation, 2026). Second, Hong Kong and Singapore became standalone rate markets on 1 July 2026, moving out of the "Rest of Asia Pacific" bucket with higher utility and authentication rates (Meta developer documentation, 2026). Third — and this is the deadline to diary — from 1 October 2026 service messages become billable at the market's utility rate, with only the first 1,000 per month per phone number free (Meta developer documentation, 2026). Free-form replies inside the 24-hour window have been free since November 2024; that era is ending. The country-by-country numbers are in our WhatsApp Business API pricing guide for 2026.

There is one more line item worth knowing about: since 1 August 2026, Meta Business Agent messages are charged per token at US$2 per million tokens, roughly 4–5 US cents per message at typical message sizes (Meta developer documentation, 2026). AI on WhatsApp is being metered, not banned.

So the practical checklist for the rest of 2026 is short:

• Confirm your agent is business-scoped, discloses that it is AI, and hands off to a human on request. If all three are true, the AI Providers clause is not your problem.
• Check your broadcast hygiene before you worry about AI, because opt-in failures and quality-rating decline are what actually get accounts restricted (Meta, 2026).
• Budget for 1 October 2026. Model your monthly service-message volume against the first-1,000-free allowance and your market's utility rate.
• Watch the EU proceedings. If the interim measures are lifted or Meta's re-admission fee is struck down, the framing shifts again — though the "business bots are fine" half of the rule has been stable throughout.
• Prefer predictable pricing. With Meta's own per-message and per-token meters now stacked underneath every platform, a software bill that also scales with volume compounds the exposure. Our pricing page sets out the flat-fee alternative; the same logic applies to any tool you shortlist, and we compare the cheap DIY end of the market in Tidio vs Chatbase vs Crisp.

The broader read is that Meta is not hostile to AI on WhatsApp. It is hostile to other people's general-purpose assistants using WhatsApp as a distribution channel, and it is increasingly interested in metering the AI traffic that does run there. Those are commercial positions, not a technology ban — and a business answering its own customers' questions was never the target.

If you want to see what a business-scoped agent sounds like on your own site rather than in a demo, paste your URL on the homepage and ask it a question your customers actually ask.

Frequently asked questions

Did Meta ban AI chatbots on WhatsApp in 2026?

No. Meta's WhatsApp Business Solution Terms prohibit AI providers from using the platform when a general-purpose AI assistant is the primary functionality being distributed. Business-specific AI — customer service, order tracking, appointments, reminders and lead qualification — is expressly permitted, and Meta confirmed to TechCrunch that businesses using AI to serve their own customers are unaffected (TechCrunch, 18 October 2025).

When did the WhatsApp AI policy take effect?

The updated terms applied to new API users from 15 October 2025 and were enforced against existing users from 15 January 2026 (WhatsApp Business Solution Terms, 2026). ChatGPT, Microsoft Copilot and Perplexity all ceased operating on WhatsApp on the January date, leaving Meta AI as the only general-purpose assistant on the platform (European Commission, 2026).

Is the policy still in force everywhere?

Not everywhere. Italy's AGCM imposed interim measures suspending the terms on 24 December 2025, and Brazil was exempted on the enforcement date. On 9 June 2026 the European Commission imposed interim measures ordering Meta to restore free access for rival assistants across the EEA — only the second use of that power since Broadcom in 2009 (European Commission, IP_26_1276, 2026). Hong Kong, Singapore, Taiwan and most other markets fall under no exemption, so the rule applies in full there.

What does a compliant AI agent on WhatsApp need to do?

Keep the conversation scoped to your own business rather than answering open-domain questions, tell the customer plainly that they are dealing with an AI, offer a one-step handoff to a human that keeps the conversation context, follow the normal opt-in and template-category rules, and avoid passing customer messages to an AI provider for training or any purpose beyond serving that customer. Most established business messaging platforms do all five by default.

Will my WhatsApp costs change because of this?

The AI policy itself does not change your per-message costs, but three separate changes do. Per-template-message pricing began 1 July 2025; Hong Kong and Singapore became standalone, higher-rate markets on 1 July 2026; and from 1 October 2026 service messages become billable at the utility rate after the first 1,000 per month per phone number (Meta developer documentation, 2026). Meta Business Agent messages have also been charged per token at US$2 per million tokens since 1 August 2026.

Sources: WhatsApp Business Solution Terms (2026), TechCrunch (18 October 2025; January 2026), European Commission press release IP_26_1276 and EVP Teresa Ribera statement (9 June 2026), European Commission Article 102 investigation announcement (4 December 2025), AGCM press release A576 (24 December 2025), The Verge and ghacks.net reporting on assistant shutdowns (2026), Meta developer documentation on WhatsApp Business Platform pricing (2026), Meta "About account bans" help documentation (2026), EU AI Act Articles 50 and 99 (2026), competition-law press coverage of the March and May 2026 policy revisions. Policy positions are current as of the 2026-09-21 check date and several are subject to live proceedings; this is general information, not legal advice.