AI on WhatsApp: what Meta now allows, and what it does not

Since 15 January 2026, Meta’s WhatsApp Business Solution Terms prohibit AI model providers from using the platform to distribute general-purpose assistants. A ChatGPT-style bot that answers anything cannot run on the Business Platform. A bot scoped to your own business — order status, bookings, product questions, support — remains permitted.

The distinction is not about whether you use AI. It is about whether the AI is the product or the plumbing.

What exactly did Meta change?

Meta added a section addressing “AI providers” to its Business Solution Terms. It prevents providers of AI and machine-learning technologies — large language models, generative AI platforms, general-purpose assistants — from using the WhatsApp Business Solution where that technology is the primary functionality being offered, rather than incidental to a business service.

The terms took effect on 15 January 2026 for all users, having already applied to new API registrations from 15 October 2025.

Meta’s stated reasoning is that the Business API was built for companies to communicate with their customers, not to serve as a distribution channel for standalone AI assistants. Assistants from providers including ChatGPT, Perplexity, Luzia and Poke were reported as affected.

Where is the line?

Not permitted	Permitted
An open-domain assistant that answers any question	A bot answering questions about your products and services
AI capability sold as the service itself	AI supporting a defined business process
A general assistant distributed to consumers via WhatsApp	Order tracking, bookings, support, notifications
“Ask me anything” as the core proposition	Structured workflows with AI handling language

A practical test: if a customer asked your bot for a recipe or help with their homework, what should happen? A compliant business bot says that is outside what it can help with. A general-purpose assistant answers. If yours would answer, that is the problem.

Does this affect most businesses?

Directly, no. The policy targets AI providers distributing assistants, not ordinary businesses automating their own customer conversations.

Indirectly, it matters more than it appears. Plenty of businesses have built support bots by connecting a language model to WhatsApp with a loose instruction and no boundaries. Those bots answer whatever they are asked, because nobody constrained them. That is a general-purpose assistant in everything but intention.

Worth checking if any of these are true of your setup:

• The bot will attempt any question rather than declining out-of-scope ones
• There is no defined scope written down anywhere
• It was built by pointing a model at WhatsApp with a short prompt
• Customers use it for things unrelated to your business, and you find that amusing rather than concerning

Scoping such a bot properly is not a large project. It is a boundary instruction, a refusal behaviour and a handover route — the same three things that make a bot useful anyway.

What else changed for AI bots on WhatsApp?

Something that will affect your costs more than the policy does.

From 1 October 2026, messages sent inside the 24-hour customer service window become chargeable, having been free. For an automated agent that is a direct cost increase, because bots send more messages than humans do — acknowledgements, clarifying questions, follow-ups.

A bot that resolves a query in six messages where a person would have taken two has just become three times more expensive. The metric to watch is messages per resolved conversation, not conversations handled — and most bot dashboards do not report it. We have written about the billing change here.

What should a WhatsApp bot actually do?

Fewer things, well.

Answer within a stated scope. Your products, your policies, your orders. Decline everything else politely and hand over.

Reach conclusions in few messages. Ask for everything needed in one message rather than three sequential questions. Better service, and now cheaper too.

Hand over cleanly. With the conversation attached, and quickly — a customer who has asked twice for a person should get one.

Say when it does not know. The behaviour that keeps you compliant and keeps customers trusting it, which happen to be the same behaviour.

Last verified: 22 August 2026. Platform terms change. Check Meta’s current WhatsApp Business Solution Terms before relying on this summary.

Common questions

Can we still use a language model on WhatsApp at all?

Yes, provided it serves a defined business function rather than being offered as a general assistant. Support, sales, bookings and order tracking are all explicitly the sort of use the platform exists for.

What happens if we are non-compliant?

Enforcement is at Meta’s discretion and can extend to restriction of the account. Given that your WhatsApp number is often a primary customer channel, this is not a risk worth carrying for the sake of an unscoped bot.

Does this apply to the WhatsApp Business App?

The terms concern the Business Solution — the API. The free app has always had limited automation and is not the target of the change.

Should we move our bot to another channel?

Only if your use genuinely is a general assistant. For business support, WhatsApp remains where Indian customers actually are, and a properly scoped bot is compliant. Scoping it is cheaper than migrating your customers.

More on this: building a chatbot that answers from your documents and should your business use AI for support. See also WhatsApp Business API.