All articles
Compliance

WhatsApp AI Chatbot Policy 2026: What's Allowed

Meta bans general-purpose AI assistants on the WhatsApp Business API from 15 Jan 2026, but AI for your own support, sales and bookings is still allowed.

RichAutomate
10 min read 2 views
WhatsApp AI Chatbot Policy 2026: What's Allowed

Under Meta's 2026 WhatsApp rules, a business can still run an AI chatbot that answers its own customers about its own products, orders, bookings and support. What Meta prohibits is using the WhatsApp Business Platform to distribute a general-purpose AI assistant, such as a ChatGPT-style bot, when the AI itself is the main product being offered. That ban took effect for all existing users on 15 January 2026, with exceptions forced by regulators in a few markets.

Short answer. If AI helps you serve your customers (support, FAQs, order status, sales questions, appointments), it is "incidental or ancillary" to your business and remains allowed on the WhatsApp Business API. If your product is the AI assistant, meaning people message your number mainly to chat with a model, Meta classes you as an "AI Provider" and blocks that use outside a short list of markets where regulators have stepped in. Whatever the use case, the usual WhatsApp Business Policy still applies: opt-in, honouring opt-outs, and a clear route to a human.

What changed in Meta's WhatsApp terms

In October 2025 Meta added an "AI Providers" clause to the terms that govern the WhatsApp Business Platform (formerly called the WhatsApp Business Solution Terms). TechCrunch reported that the new terms would take effect on 15 January 2026 and would likely affect WhatsApp-based assistants from OpenAI, Perplexity, Luzia and Poke. By the January deadline, TechCrunch's update notes that OpenAI, Perplexity and Microsoft had announced their WhatsApp chatbots would stop working.

The clause now sits in Section 4.7 of the Meta Terms for WhatsApp Business Platform (the version we reviewed was last modified 23 September 2026). It defines AI Providers as providers and developers of AI or machine learning technologies, "including but not limited to large language models, generative artificial intelligence platforms, general-purpose artificial intelligence assistants, or similar technologies as determined by Meta in its sole discretion." Those providers are prohibited from using the platform to make such technologies available "when such technologies are the primary (rather than incidental or ancillary) functionality being made available for use."

Meta's stated reason, given to TechCrunch, was that "the purpose of the WhatsApp Business API is to help businesses provide customer support and send relevant updates," and that general-purpose chatbots created message volumes and support needs the company was not ready for.

The key test: primary versus incidental

The whole policy turns on one distinction. Meta does not ban AI on WhatsApp; it bans AI as the primary product delivered through the Business Platform. TechCrunch's reporting gives the example that a travel company running a customer-support bot is not restricted. In practice, ask yourself: would customers still message this number if the AI disappeared and a human answered instead? If yes, because they want your hotel room, your parcel or your refund, the AI is incidental. If the only reason the number exists is to give people access to a chatbot, you are likely in AI Provider territory.

Note that Meta reserves the final call "in its sole discretion" twice in the same sentence. There is no published checklist of borderline cases, so treat grey areas conservatively.

Allowed vs not allowed: a practical table

Use caseStatus under the 2026 termsWhy
AI agent answering customer support questions and FAQs for your own businessAllowedAI is incidental to the service you provide
AI handling order tracking, returns and delivery questions for your storeAllowedSupports your commerce, not a standalone AI product
AI booking appointments, tables or rooms for your clinic, restaurant or hotelAllowedBooking is the service; AI is the interface
AI qualifying sales leads and answering product or pricing questionsAllowedSales of your own offering is the primary purpose
Hiring an AI company as your Solution Provider (BSP) to build your botAllowed, with data limitsSection 4.7 says you "may retain an AI Provider as your Solution Provider," but restricts use of your WhatsApp data for training other AI models
A ChatGPT-style assistant on a WhatsApp number that answers anything for anyoneNot allowed (outside regulator-exempt markets)General-purpose AI is the primary functionality
An AI start-up distributing its LLM product to consumers through the Business APINot allowed (outside regulator-exempt markets)Matches the "AI Providers" definition directly
Feeding WhatsApp chat data into a model that a vendor reuses for other customersNot allowedData may only fine-tune an AI model "for your exclusive use"

The data rule most businesses miss

Section 4.7 also contains a data restriction that is easy to overlook. If you retain an AI Provider as your Solution Provider, you may not allow WhatsApp Business Platform Data, including "anonymous, aggregate, or derived forms," to be used to "create, develop, train, or improve" any AI models. The one carve-out is that you may use that data "to fine-tune an AI Model that is for your exclusive use," as long as it does not end up improving any other model.

In plain terms: before you connect an AI vendor to your WhatsApp number, check its data-processing terms. If the vendor pools customer conversations to improve a shared model, that conflicts with the wording of Meta's terms. Ask for this in writing.

Where the ban does not fully apply: EU, Italy and Brazil

The policy has been challenged by competition regulators, and the result is a patchwork. Here is what we could confirm from the sources we read.

Stop overpaying on WhatsApp

Get the DPDP WhatsApp checklist

A founder-led WhatsApp reply with the DPDP consent + audit-log checklist for WhatsApp Business messaging. India-hosted. No spam.

DPDP-compliant · India-hosted · 1-min reply

Brazil

On 13 January 2026, two days before the deadline, Brazil's competition authority CADE ordered Meta to suspend the policy and opened an investigation, according to TechCrunch. CADE said there was "possible anti-competitive conduct of an exclusive nature." Meta then changed its terms to charge for messages sent by AI chatbots in Brazil. CADE's own announcement says its tribunal unanimously upheld a violation notice over this, finding Meta had sought to classify these players "as marketing messages, subject to per-message charges," and kept a daily fine of BRL 250,000 in place until full compliance.

European Union and Italy

TechCrunch reported that the EU and Italy were also investigating, and that Meta allowed AI providers to keep operating in Italy after 15 January. The European Commission opened its investigation in December 2025. According to the Law Society Gazette and a Houthoff analysis, Meta readmitted rival AI assistants in March 2026 but with fees, and on 9 June 2026 the Commission imposed interim measures ordering Meta to restore free access for rival general-purpose AI assistants on pre-October 2025 terms while its investigation continues. Commissioner Teresa Ribera said: "In rapidly evolving markets, competition can be lost long before a final decision is adopted."

What Meta's own pages say now

Section 4.7 now states that AI Provider technologies "may be made available to businesses in certain countries" and links to Meta's AI Provider pricing page. That page lists Brazil, Italy and a set of EEA countries with specific effective dates during 2026, and says that from 13 May 2026 Meta "will no longer charge 'AI Providers' for non-template messages delivered to users in certain markets." We could not fully reconcile the exact current charging status for each market from the pages alone, and these cases are still live. If you are an AI company targeting the EEA or Brazil, read that page and take legal advice rather than relying on any summary, including this one.

The markets this article is written for, Singapore, the UAE, the UK and the US, did not appear on the country list we reviewed. On that reading, the default rule applies there: general-purpose AI assistants as a primary product are prohibited, and business AI that is incidental to your service is fine.

Rules that still apply to every WhatsApp AI chatbot

Passing the AI Provider test does not exempt you from the rest of Meta's rulebook. The WhatsApp Business Policy (last updated 23 September 2026) has three requirements that matter most for automated agents.

1. A route to a human

The policy says: "You may use automation when responding during the 24-hour window, but must also have available prompt, clear, and direct escalation paths." The options it lists include in-chat human agent transfer, phone, email, web support, in-store visits or a support form. An AI agent that loops forever with no way out is a policy problem, not just a customer-experience problem.

2. Opt-in before you message

You may only contact people who have given you their number and from whom you have "received opt-in permission" confirming they want messages from you. An AI agent that replies to inbound chats is fine; an AI agent that starts cold outreach to scraped numbers is not.

3. Honour every opt-out

Businesses must "respect all requests (either on or off WhatsApp) by a person to block, discontinue, or otherwise opt out of communications." For an AI agent this means detecting "stop" or "unsubscribe" in whatever language the customer writes, and not letting the model talk them out of it.

A compliance checklist for businesses using AI on WhatsApp

  • Scope the bot to your business. Ground answers in your own catalogue, policies and order data. Politely decline unrelated requests ("write my essay", "who won the match") rather than acting as an open assistant.
  • Build the human handoff first. Make transfer to a person available on request and whenever the bot is unsure.
  • Check your vendor's data terms. Confirm your WhatsApp conversations are not used to train shared models.
  • Keep opt-in records and process opt-outs in every language your customers use.
  • Watch costs as well as rules. AI replies inside the customer service window and template messages are priced differently by country; see our WhatsApp API pricing by country guide or run the numbers in the WhatsApp pricing calculator by country.
  • Re-check the terms periodically. Section 4.7 has changed more than once since October 2025 and regulators are still involved.

How RichAutomate fits the 2026 rules

RichAutomate is built on Meta's official Cloud API and is designed for the use case Meta explicitly allows: a business answering its own customers. The AI agent handles support, FAQs, orders and bookings for your business and replies in the customer's language. When a conversation needs a person, it hands off to your team inbox, which covers the escalation requirement. You can shape the conversation with the visual no-code flow builder, and opt-out keywords are handled in multiple languages so "stop" means stop.

If you are planning AI-led campaigns as well as support, our 2026 WhatsApp campaign read-rate study shows what to expect, and RichAutomate international pricing lists plans for businesses outside India.

This article summarises public sources as of October 2026 and is not legal advice. Meta's terms and regulators' orders change; check the official pages linked above before making decisions.

Ready to ship this?

Get the DPDP WhatsApp checklist

A founder-led WhatsApp reply with the DPDP consent + audit-log checklist for WhatsApp Business messaging. India-hosted. No spam.

DPDP-compliant · India-hosted · 1-min reply
Tagged
WhatsApp Business APIAI ChatbotMeta PolicyCompliance
Written by
RichAutomate
Editorial team at RichAutomate. We build the WhatsApp Business automation platform Indian D2C brands, fintechs, and agencies use to ship campaigns and flows on the official Meta Cloud API.
FAQ

Frequently asked questions

Can my business still use an AI chatbot on WhatsApp in 2026?
Yes. Meta's terms only prohibit AI when it is the primary functionality being offered. A bot that handles support, FAQs, orders, sales questions or bookings for your own business is incidental to that business and remains allowed, subject to the normal WhatsApp Business Policy.
When did the WhatsApp general-purpose AI chatbot ban start?
Meta introduced the AI Providers clause in October 2025, and TechCrunch reported it took effect on 15 January 2026. OpenAI, Perplexity and Microsoft announced their WhatsApp chatbots would stop working around that date.
What counts as an 'AI Provider' under Meta's terms?
Section 4.7 defines AI Providers as providers and developers of AI or machine learning technologies, including large language models, generative AI platforms and general-purpose AI assistants, as determined by Meta in its sole discretion. They are barred when that AI is the primary, not incidental or ancillary, functionality.
Can I use an AI company as my WhatsApp Solution Provider?
Yes. Section 4.7 says you may retain an AI Provider as your Solution Provider. However, your WhatsApp Business Platform data may not be used to train or improve AI models, except to fine-tune a model for your exclusive use.
Does the ban apply in the EU, UK, UAE, Singapore and the US?
Regulators in Brazil, Italy and the EU intervened, and Meta's AI Provider pricing page lists Brazil, Italy and EEA countries. The UK, UAE, Singapore and the US were not on the list we reviewed, so the default rule appears to apply there. Check Meta's current page before relying on this.
Does my WhatsApp AI agent need a human handoff?
The WhatsApp Business Policy allows automation in the 24-hour window but requires prompt, clear and direct escalation paths, such as in-chat transfer to a human agent, phone, email, web support, store visits or a support form.
Is this article legal advice?
No. It summarises Meta's published terms, Meta's policy pages and news reports as of October 2026. The rules and regulator orders are still changing, so confirm with the official pages and your own legal counsel.
RichAutomate · WhatsApp BSP for India 2026

Ship WhatsApp campaigns + flows on a transparent, compliance-ready BSP.

₹0 platform fee. DPDP audit log included. Visual flow builder. Multi-tenant from day one.

Start free trial
Want this for your brand?

Get a free 24-hour BSP audit

Send us your last invoice. We line-item it against Meta's published rates and benchmark against three alternatives.

Limited Spots Available

Get a Free
Automation Audit

Stop leaving revenue on the table. Get a custom roadmap to automate your growth.

Secure & Confidential

Continue reading

All articles
Compliance

WhatsApp Dark Patterns & CCPA Compliance India 2026

India's CCPA dark-patterns guidelines name a specific list of prohibited deceptive designs (commonly cited as 13 patterns), and nearly every one has a direct analogue inside a WhatsApp commerce journey — false urgency timers, basket sneaking in order edits, forced-bundled opt-ins, subscription traps, confirm-shaming buttons, disguised ads, drip pricing, bait-and-switch, nagging, interface interference, trick questions, SaaS billing and rogue links. This guide maps all 13 patterns onto WhatsApp with compliant alternatives, gives a journey-stage self-audit checklist and side-by-side dark-vs-compliant message copy, explains the CCPA + DPDP Act 2023 double-consent rule, hedges the penalties/enforcement reality, and provides a 30-day audit runbook. As of 2026 — general information, not legal advice.

Read article
Compliance

WhatsApp Business Account Restricted? Appeal & Fix 2026

Why Meta restricts a whole WhatsApp Business account (WABA), how it differs from a single-number ban, and exact Account Quality appeal steps to reinstate it.

Read article
Compliance

WhatsApp Opt-In Evidence: What Meta Asks in a Review 2026

When Meta or your BSP reviews a template appeal or account, "we had their number" is not opt-in evidence — they want per-contact proof: timestamp, source, exact wording and scope. This 2026 guide covers what triggers a review, the record fields that make consent defensible, retention, what WhatsApp already stores vs what only you can log, and a 24-hour evidence-pack checklist. RichAutomate logs consent at capture: WABA you own, ₹0 platform/setup/monthly, Client Pay ₹0.10/msg or SaaS Pay ₹1.50 marketing / ₹0.50 utility.

Read article
Compliance

GST on WhatsApp API Charges 2026: 18% RCM & ITC Guide

WhatsApp API charges carry 18% GST in India: BSP fees under forward charge, Meta per-message fees under RCM with ITC claimable. Client Pay vs SaaS Pay decoded.

Read article
Compliance

Telecom Act 2023 and WhatsApp OTT Messaging: India 2026

A scenario map for Indian business senders on whether WhatsApp business messaging acquires telecom-style obligations — authorisation, KYC, lawful-interception readiness — under the Telecommunications Act 2023 rollout and TRAI's OTT consultation. Covers what the Act is and what is still open, the core is-it-a-telecom-service question, why this is distinct from the TCCCPR/DLT commercial-comms rules, three landing scenarios with sender impact, the authorisation/KYC/interception watchlist, the lawful-interception-vs-DPDP-confidentiality tension, and no-regrets compliance moves that pay off under every outcome. Every regulatory, Meta and legal specific is evolving and hedged — verify as of 2026. General information, not legal advice.

Read article
Compliance

AI Disclosure & Labelling for WhatsApp Bots India 2026

A practical, transparency-first guide for Indian businesses running AI bots, GenAI replies, and synthetic voice/image creatives on WhatsApp: when you must disclose you are an AI, how to label AI-generated media, consent for AI-processing of messages under DPDP 2023, a copy-ready disclosure-pattern library, high-risk pitfalls, a self-audit checklist, and a 30-day compliance runbook. India's AI-governance landscape (MeitY advisories, IT Rules synthetic-media obligations, DPDP Act 2023, ASCI) is evolving — all specifics hedged, verify as of 2026.

Read article