On this page
Too long? Read this
- Meta Business Agent is Meta's own AI agent. You switch it on in WhatsApp Manager, not in your CRM, and Meta bills you directly at $2 per 1 million tokens
- A typical reply uses 20,000 to 25,000 tokens, so it works out at roughly 4 to 5 US cents, about Rs 4, per reply
- While Meta's agent is answering a conversation, that conversation does not reach your CRM inbox, and your flows, chatbots and automations do not run on it
- It only replies. It never starts a conversation, so broadcasts, sequences and templates still run from your CRM as normal
- Seven verticals are excluded outright, including health and matrimony, and you get one agent per number with no shared knowledge between numbers
Meta Business Agent is Meta's own AI agent for WhatsApp. You switch it on in WhatsApp Manager, Meta hosts it, and Meta bills you directly at $2 per 1 million tokens, which works out at roughly Rs 4 per reply. The part nobody mentions: while it is answering a conversation, that conversation does not reach your CRM inbox, and none of your flows or automations run on it.
That trade is worth understanding before you switch it on, because the setup flow does not explain it and nothing in your CRM will look broken when it happens.
What is Meta Business Agent?
It is an AI agent that Meta runs on your WhatsApp number. You give it knowledge (business information, FAQs, files, a website to read), you write instructions for how it should behave, and it answers customers in your brand's voice. It can send buttons, lists, media carousels and WhatsApp Flows, and it can call your own APIs to look up an order or book a slot.
There are two different products sharing one name, and most of the confusion online comes from mixing them up.
| WhatsApp Business app version | Platform version (Cloud API) | |
|---|---|---|
| Where you set it up | In the app, under Tools | APIs only, no configuration screen |
| Knowledge | Learns from your chats, Page and website | You supply every source yourself |
| Who it answers | Everyone, or new customers only | An allowlist you manage by API |
| Cost | Free | $2 per 1M tokens, billed by Meta |
| Who it suits | Solo operators and micro businesses | Teams with developers |
If you are on the WhatsApp Business API through a provider, you have the Platform version. It has no configuration interface at all: WhatsApp Manager shows you a checklist where every item links to developer documentation.
Meta announced global availability on 3 June 2026 and presented it to Indian businesses at WhatsApp's Business Summit in Mumbai on 7 and 8 July 2026. Swiggy uses it for delivery partner onboarding, and Treebo runs it for hotel enquiries.
What does Meta Business Agent cost?
Meta has charged for the agent since 1 August 2026, at $2.00 per 1 million tokens, input and output combined, with cached tokens free. It is a flat global rate with no India adjustment.
The number that matters is tokens per reply. A single agent reply consumes 20,000 to 25,000 tokens, because your knowledge, your instructions and its tool definitions all go into every single turn. So:
| Cost per AI reply | Who bills you | |
|---|---|---|
| Meta Business Agent | About Rs 3.50 to Rs 4.40 | Meta, on your Meta invoice |
| VGraple CRM AI replies, 1,000 pack | Rs 0.40 | VGraple CRM |
| VGraple CRM AI replies, 5,000 pack | Rs 0.34 | VGraple CRM |
| VGraple CRM AI replies, 20,000 pack | Rs 0.30 | VGraple CRM |
At 5,000 AI replies in a month, that is around Rs 1,700 with us against roughly Rs 20,000 with Meta, on one number.
Watch out
Meta bills you directly for the agent, against a credit line or card in Billing Hub, and messages are not delivered at all if no payment method is attached. It does not pass through your provider, so nobody can mark it up, absorb it, or include it in a plan. It will not appear on your VGraple CRM invoice, and your provider cannot see or cap that spend.
For context on what messages themselves cost, which is separate and unchanged, see Meta conversation charges and billing. Meta's agent charge sits on top of those.
Credit and debit cards became a payment option on 8 September 2026. Before that it required a credit line, which is why many smaller businesses could not enable it at all.
What happens to your inbox when you switch it on?
This is the part to read twice. When Meta Business Agent is rolled out on a number, Meta's agent becomes the primary responder. While it holds a conversation:
- Those messages do not arrive in your CRM inbox.
- Your flows do not fire on them, including keyword triggers and catch-all flows.
- Your AI chatbot and AI replies do not run on them.
- Your automation rules do not see them.
- No conversation assignment, tagging, lead scoring or analytics happens for them, because as far as your CRM is concerned the message never arrived.
Technically, inbound moves off the messages webhook field and onto a different field called standby, which is only for apps that are monitoring rather than answering. Nothing errors. Nothing retries. Nothing appears in any log, because nothing failed.
The result, from where you sit, is a WhatsApp number that has gone quiet. That is the single most common support question this feature creates, and it is why VGraple CRM now detects it and says so on the channel itself.
Note
There is a second effect worth knowing if you write your own integrations. Any message your app sends takes control of the conversation back from Meta's agent, and simply stopping sends does not hand it back. An auto-reply that fires at the wrong moment will silence Meta's agent until your app explicitly releases the thread. Meta names this as the most common cause of agents that go mute in production.
What can Meta's agent not do?
It is worth being precise, because this defines what you still need a CRM for.
It only replies. It never starts a conversation. No broadcasts, no sequences, no follow-ups, no scheduled campaigns, no segmented marketing. Everything outbound still runs from your CRM, and none of it is affected by the agent being on.
Beyond that:
- One agent per number, with no knowledge shared between numbers. Three numbers means building and maintaining three separate agents.
- No team inbox, no assignment or routing, no roles.
- No CRM. It does not create contacts, leads or appointments, and does not read your history.
- No attribution. It will not tell you which conversation came from which click-to-WhatsApp ad or which ended in a sale. See revenue tracking for what that reporting normally looks like.
- Handoff is Meta's call. It decides when to hand a conversation over. You can change the handoff message, not the trigger. If you have firm rules about when a human must step in, check AI escalation to human for what configurable handover looks like.
- Greeting and away messages stop working once the agent is enabled, and restoring them means deleting the agent.
- The language is not selectable. It follows the phone number rather than your choice.
Should you use it?
An honest answer, including where it wins.
Meta's agent is genuinely easier to start. Point it at your website and a list of FAQs and it works, with no flow to build and no prompt to write. If you have never configured any automation and do not intend to, that is a real advantage and you should weigh it.
Where it costs you is everything after that first hour: roughly ten times the price per reply, conversations that leave your inbox, no reporting you can act on, no control over handover, and a per-number agent you rebuild for every number you add.
The sensible reading for most businesses on the API: if you are already paying for a CRM to hold your inbox, contacts, broadcasts and reporting, running the AI somewhere that cannot see any of that is the expensive way round. If you are not, and you have a single number and simple questions, Meta's free in-app version is a reasonable place to start before you move up to the API.
Tip
Testing is free. Set the audience to allowlisted numbers only, add your own phone, and Meta does not charge for those conversations and does not require a payment method. That is the cheapest way to judge the quality yourself rather than taking anyone's word for it, including ours.
What VGraple CRM does about it
We do not sell, resell or manage Meta Business Agent. It is configured in WhatsApp Manager, Meta bills you directly, and there is nothing for us to add in the middle. What we do is make sure it never silently confuses you:
- We check each connected number against Meta once a day and record whether the agent is eligible, switched on, and whether it is answering everyone or only your allowlisted test numbers.
- We tell you once, clearly, when the agent goes live on a number: what changed, that your broadcasts and sequences are unaffected, roughly what Meta will charge you, and how to turn it off.
- We show it on the channel in Settings, so anyone on your team wondering why a number is quiet can see the reason in one place. See channel health for the other signals on that card.
- We never answer over the top of it. Our automations only act on real inbound messages, so we cannot accidentally take the conversation away from Meta's agent while it is mid-answer.
- Your outbound keeps working. Broadcasts, sequences, templates and flows triggered by anything other than an incoming message are unaffected, because Meta's agent never sends first.
If you want AI on WhatsApp without giving up the inbox, our AI chatbot and AI replies run inside your flows, on your data, at Rs 0.30 to Rs 0.40 a reply, with every conversation still in one team inbox. New workspaces get 100 AI replies free to try it. You can also bring your own AI key if you would rather pay your model provider directly.
How do you turn Meta Business Agent off?
In WhatsApp Manager, on the Meta Business Agent tab for that number. Once it is off, conversations arrive in your CRM inbox again and your flows resume.
One detail that catches people out: after a disable and re-enable, Meta's agent answers new conversations only, not ones that are already open. So a test cycle leaves a tail of conversations behaving differently from the rest, which is worth knowing before you use a live number to experiment on.
If your number went quiet and you are not sure whether the agent is the cause, open Settings, then WhatsApp channels, and use Check with Meta on the number. If the agent is not the cause, webhook not receiving messages and messages delayed or held cover the other possibilities.