Meta puts an AI agent inside the WhatsApp Business app for Indian small businesses

The chat thread is the whole interface

Meta's announcement describes Business AI as living entirely inside the WhatsApp Business app — no separate dashboard, no external console, no third-party platform. The customer sees a normal WhatsApp conversation; the business owner sees the same thread with an AI answering on their behalf.

This matters because the frontend the small business already uses every day is the frontend the AI ships into. There is no new surface to learn. The customer-facing experience is the message bubble, and the operator-facing experience is the same message bubble plus a takeover control.

Meta's own framing leans on how central messaging already is: it cites a Kantar 2025 study finding 91% of online adults in India chat with a business weekly. The product bet follows the behavior — put the agent where the conversation already happens rather than asking businesses to route customers elsewhere.

Setup is a guided flow, not an integration project

The configuration path is deliberately shallow. Meta says eligible businesses go to the Tools tab, select 'Your Business AI,' and follow a few guided steps. The AI draws on what the business has already added — its profile and catalog — rather than requiring a fresh data model.

One of the cited operators, Tuba Siddiqui of Soil Concept, describes uploading a product catalog and documents and having the AI learn the details and tone. Meta repeats the 'no coding, no complex third-party software' claim in its takeaways. The point of the frontend here is to hide the entire ML pipeline behind a document upload.

To my surprise, it was an easy process — within a few hours, Business AI learned everything about my business and was able to reply to customers on my behalf, exactly how I would.Montana Labs

Human takeover is a first-class control, not an afterthought

The announcement is explicit that the business owner can step in at any time. For a more complex query or specific need, the owner takes over the conversation from the AI agent, and can adjust how Business AI works or turn it off entirely.

That handoff is a real interface requirement, not a slogan. Because the AI and the human share the same thread, the takeover has to be visible and immediate — the operator needs to know when the agent is speaking and be able to seize the conversation mid-flow. Meta frames control as staying with the business 'at all times.'

UPI-in-chat is the piece that changes the stakes

Meta says Business AI will 'starting soon' be able to facilitate payments directly within a WhatsApp chat using UPI. This is the line that turns a support agent into a transaction agent. Today the AI answers questions, recommends products, and captures leads; adding payment closes the loop without the customer ever leaving the thread.

That is also where the frontend design carries the most weight. An agent that answers a pricing question wrong is recoverable; an agent that initiates a payment inside the conversation raises the bar for how clearly the interface signals what the AI is about to do and where the human's confirmation sits. The announcement does not detail those controls for the payment path — it only names the capability as forthcoming.

What shipping into an existing app implies

The specific implication of this launch is that Meta is treating an installed-base messaging app as the deployment target for an AI agent, rather than building a new product around the model. The setup, the customer conversation, the human override, and eventually the payment all resolve inside one app the business already runs.

For teams building agent frontends, the constraints Meta accepted are the interesting part: eligibility gating, all native Indian languages, catalog-as-training-data, and a takeover switch that has to coexist with the AI in the same thread. The self-reported results — Soil Concept citing an 80-90% conversion rate, The Purple Sunset citing a 40% sales increase and 6-7 orders closed daily — are business claims, not Meta's audited figures, and should be read as such.