Summarise this article with:
On this page7 sections
Since 15 January 2026, Meta’s WhatsApp business terms bar AI providers from using the WhatsApp Business Platform when AI is the primary functionality they sell, such as a general-purpose assistant. Your own AI agent answering your customers about your orders, bookings and products is a different case: there, AI is incidental to your business, and that use stays open.
The rule is short, but it decides whether an AI product can exist on WhatsApp at all. This post covers what the clause says, how the primary-versus-incidental test reads in practice, why the countries where Meta has relaxed it do not include India, and how to scope an AI agent so it stays on the allowed side.
What the AI providers clause says
The clause sits in section 4.7 of the Meta Terms for WhatsApp Business Platform, the document the old WhatsApp Business Solution Terms address now redirects to (last updated 23 September 2026). Meta’s own AI providers page dates the definition to the terms “updated on January 15, 2026”.
Read closely, the clause has four parts:
- Who it covers. Providers and developers of AI or machine learning technologies, with large language models, generative AI platforms and general-purpose AI assistants named as examples. The terms call this group “AI Providers”.
- What it bars. They are “strictly prohibited from accessing or using the WhatsApp Business Platform, whether directly or indirectly” to make those technologies available.
- When it bites. Only where the AI is the “primary (rather than incidental or ancillary) functionality” on offer.
- Who decides. Meta, “in its sole discretion”.
Two sentences in the same section matter to ordinary businesses. You may retain an AI provider as your solution provider, so hiring an AI vendor to build your bot is allowed. And you may not let WhatsApp Business Platform data be used to create, train or improve AI models, with one exception covered below.
For the wider contract around this clause, see InfiQ’s glossary entry on the WhatsApp Business Solution Terms.
Primary or incidental: which side your bot is on
The test is about what the customer is getting. If they message you to buy shoes, book a scan or track a parcel, and AI helps answer, the AI is incidental to that service. If the thing they come for is the AI itself, an assistant that will answer anything, the AI is the primary functionality.
Meta has not published a list of rulings, so the readings below are ours, not Meta’s. They are hypothetical businesses, chosen to show where the line falls.
| Hypothetical bot | What the customer comes for | Likely reading |
|---|---|---|
| A Pune D2C skincare brand’s agent answering order, return and ingredient questions | The brand’s products and orders | Incidental: allowed |
| A Jaipur travel agency’s agent quoting packages and taking booking details | Holiday bookings | Incidental: allowed |
| A coaching institute’s agent answering batch timings, fees and admission steps | Admission to the institute | Incidental: allowed |
| An edtech startup selling an AI tutor subscription delivered on WhatsApp | The AI tutor | Primary: barred |
| A startup offering an “ask me anything” assistant on its own number | The AI assistant | Primary: barred |
The grey zone is scope creep. A retail agent that also writes cover letters, solves homework or chats about the news is drifting from incidental towards primary, because a growing share of what it does has nothing to do with the business. Keep the agent on your catalogue, your policies and your customers’ transactions, and have it decline everything else.
The exemption list does not include India
Meta’s AI providers page covers the markets where Meta says it is legally required to support AI providers’ use of the platform, and the per-message charges that apply there. It lists Italy (from 16 February 2026), Brazil (from 11 March 2026), the remaining EEA countries (from 11 March 2026) and Türkiye (from 15 October 2026).
India is not on the list. For an Indian business, and for an AI provider trying to reach Indian users on the Business Platform, the section 4.7 bar applies in full. Meta’s page also states that even in the listed markets, service messages can only be sent in response to users during an open 24-hour customer service window.
What an allowed bot must still do
Passing the AI providers test is necessary, not sufficient. Three other obligations apply to any AI agent on the platform.
Offer a human route. The WhatsApp Business Messaging Policy (last updated 23 September 2026) says you may use automation when responding during the 24-hour window, but must have “prompt, clear, and direct escalation paths”. Its listed options are an in-chat transfer to a human agent, a phone number, email, web support, in-store visits or a support form. An AI agent with no way out breaks the policy however accurate it is. InfiQ’s glossary covers the mechanics of a human handoff.
Reply inside the window. The same policy allows replies without a template only inside the 24-hour customer service window, which opens and resets with each user message. Outside it, only approved templates can be sent, so an agent cannot start conversations or chase customers with free-form text.
Keep the data out of shared models. Section 4.7 bars using WhatsApp Business Platform data, including any anonymous, aggregate or derived form, to create, develop, train or improve AI systems. The one exception is fine-tuning a model for your exclusive use, provided that does not end up training anyone else’s model. A vendor that pools transcripts from all its clients to improve one shared model puts its clients in breach.
How to scope an AI agent so it stays allowed
Use this as a pre-launch checklist and keep the answers on file. If Meta ever questions the deployment, a written scope is the evidence that the AI serves your business rather than being the business.
- Write a one-line purpose. For example: “answers customers of our 14 stores about orders, returns, store timings and products we sell.” If you cannot write it without the word “anything”, the scope is too wide.
- Ground it in your own content. Answers should come from your catalogue, policies, FAQs and order data, not from the model’s general knowledge.
- Instruct it to decline off-topic requests. Essays, homework, coding help and general trivia get a polite refusal and a pointer back to what the agent can do.
- Put a human route in every conversation. A visible “talk to a person” option, plus automatic handoff on repeated failures, complaints and sensitive topics.
- Review your vendor contract. Confirm in writing that your chats are not used to train or improve any model other than one for your exclusive use.
- Watch the cost of verbosity. Every reply inside the window is a service message, charged per message since 1 October 2026 under Meta’s non-template pricing. On InfiQ’s India rate card that is ₹0.145 per delivered message, ex-GST, so an agent that splits one answer into four messages costs four times as much.
Where Meta’s own Business Agent fits
Meta announced Meta Business Agent on 3 June 2026 as an agent that answers questions about the business, recommends products from a catalogue, books appointments, qualifies leads and lets the business decide when a team member steps in. Its existence is the clearest signal of where Meta draws the line: AI that serves a business’s customers is a product Meta itself sells.
It comes with its own conditions. Meta’s developer overview excludes the Finance, Government, Health, Alcohol, Gambling, over-the-counter drug and matrimony verticals, requires the business to be based in an authorised country, and says an active authorised-agent integration on a number blocks Meta Business Agent. Section 1.3 of the platform terms adds that separate Business Agent terms apply when you enable it.
If you are an NBFC, a hospital or a pharmacy, the vertical exclusion applies to Meta’s agent, not to AI on WhatsApp in general. A custom agent for your own customers can still be built, subject to section 4.7, the messaging policy and your sector regulator. The cost side of Meta’s agent is covered in InfiQ’s post on Meta Business Agent pricing.
Where InfiQ fits
The InfiQ AI Agent is built on Meta Business Agent, with handoff to the shared team inbox; the page lists the Business Agent integration as live and other Meta-announced capabilities as upcoming. For journeys that should not involve AI at all, InfiQ Flows builds rule-based bots from drag-and-drop blocks, including a hand-off-to-a-human block with an optional SLA.
