Meta now runs its own AI assistant on WhatsApp business numbers. Not a chatbot you build, not a flow you draw: an agent that lives inside Meta’s infrastructure, answers your customers in natural language, and bills per token on your WhatsApp Business Account. ChatMaxima now supports Meta Business Agent end to end, so you can check eligibility, create the agent, teach it your business, give it real abilities, test it, and roll it out from one page in your dashboard.
This guide walks through the whole thing. Not the marketing version, the real one, including the two prerequisites that stop most businesses on day one and the hard rule about one responder per number that nobody warns you about until it bites.
If you are still deciding whether Meta’s agent is the right thing to run at all, read the Meta Business Agent platform explainer first. This post assumes you have decided to try it and want to set up Meta Business Agent properly.
What Meta Business Agent Actually Is
Meta Business Agent is Meta’s AI assistant running on your WhatsApp number. You do not host it, you do not choose the model, and you do not write the prompt that runs the conversation. You configure it: what it knows, how it behaves, what it is allowed to do, and who it is allowed to talk to.
The important architectural fact is who answers first. When the agent is on, Meta is the primary responder on that number. A customer sends a message, Meta’s agent reads it and replies, and your platform sits in a standby role watching the conversation rather than driving it.
That is not a limitation ChatMaxima invented. It is Meta’s handover protocol, the same ownership model that has governed Messenger apps for years. One participant owns the thread at a time. While the agent owns it, your automation does not answer on top of it.
This is why Meta Business Agent is not a replacement for a bot builder and not a competitor to your inbox. It is a third thing: a first-line responder supplied by the platform itself, with your team behind it.
Who Can Use It Right Now
Meta has not opened Meta Business Agent to everyone. Availability depends on two things you do not control: the country your business is registered in, and the vertical Meta has classified you under.
At the time of writing, the open verticals are Automotive, CPG, Professional Services, Retail and Ecommerce, and Travel. If your business sits outside those, the eligibility check will come back negative and there is nothing to configure yet. That is a Meta gate, not a ChatMaxima one, and it changes as Meta expands the programme.
ChatMaxima reads the verdict straight from Meta’s eligibility endpoint for the specific phone number, so you get the real answer for that number rather than a generic “contact sales” page. A number that is not eligible shows exactly that, with the reason.
One nuance worth knowing: eligibility is evaluated per phone number, not per business. A business portfolio can easily have one eligible number and one that is not.
The Three Things Meta Needs Before You Start
Most setup attempts fail on one of these three, and all three are outside the dashboard you are configuring. Clear them first and the rest takes about twenty minutes.
1. The Meta Business AI Terms, accepted per WhatsApp Business Account
Meta requires the Meta Business AI Terms to be accepted for the WhatsApp Business Account that owns the number. Not per app, not per business portfolio, per WABA. Until that happens, Meta refuses even to answer the eligibility question, returning a 403 that says the terms must be accepted for this WhatsApp Business Account.
ChatMaxima detects that specific refusal and shows it as its own state, Terms pending, with a direct link to the right place rather than a dead button. Where you accept them depends on how the number is connected:
- Cloud API numbers: WhatsApp Manager, then Phone numbers for that WABA. The acceptance prompt appears there.
- Coexistence numbers (numbers still used in the WhatsApp Business app): the app itself, under Tools, then Meta Business Agent.
You need to be an admin of the business portfolio to accept. The Meta Business AI Terms themselves are plain legal text with no accept button on the page, which is why people get stuck reading them and assume that was the step.
2. A payment method on the WhatsApp Business Account
Meta bills agent conversations by token, directly, on the WABA. So Meta will not let you switch the agent on until that account has a payment method or credit line attached. Attempt it without one and Meta returns a blunt 400: a payment method is required to enable Meta Business Agent.
ChatMaxima turns that into a panel with a deep link to the Billing Hub account for agent billing, so you are not hunting through Business Manager for the right screen. If you have never set up WhatsApp billing on this account, our walkthrough on adding a payment method to WhatsApp Business covers the whole flow.
Worth repeating, because it saves people money: testing does not need a payment method. Everything in the Test chat tab runs the full agent pipeline unbilled. You can build and prove the entire configuration before you ever attach a card.
3. One responder per number
This is the rule that causes the most confusion. If you already have a ChatMaxima chatbot connected to that WhatsApp number, you cannot switch the Meta agent on while both are live.
The reason is mechanical, not philosophical. While Meta’s agent answers, the customer’s messages still arrive on your webhook. An assigned bot would happily reply alongside the agent, and the customer would get two answers to one question, sometimes contradicting each other.
ChatMaxima refuses the switch before it ever calls Meta, names the bot that is in the way, and locks the toggle. Turning the agent off stays allowed in every case, so a number that somehow ends up with both can always be recovered. Voice bots are ignored by this check, because they answer calls, not chats.
So the decision is explicit: on a given number, either your bot answers first or Meta’s agent does. Many businesses end up splitting by number, which is a perfectly good outcome.
Step 1: Open the Meta Business Agent Page
In ChatMaxima, go to Settings, then WhatsApp. Find the number you want the agent on, open its Actions menu, and choose Meta Business Agent. The menu entry carries an On or Off badge, so at a glance you can see which of your numbers currently have an agent running.
That opens a dedicated page for that number, not a cramped modal. You get a breadcrumb back to Channels, a tab strip across the top, the configuration form on the left, and a Test chat panel pinned on the right that stays visible while you work. Every change you make can be tried against the agent without leaving the form.
Across the top of the page is a three stage rail: Eligible, Set up, Live. Completed stages show a green tick instead of the step number, so the page tells you where you actually are rather than making you infer it.
Step 2: Check Eligibility
The page checks the number with Meta as soon as it loads. Three outcomes:
- Eligible. The Set up button is live and you continue to step 3.
- Terms pending. The Meta Business AI Terms are not accepted for this WABA. Use the link on the page, accept them as a portfolio admin, then reload.
- Not eligible. Meta has not opened the programme for this number’s country and vertical. Nothing to configure yet.
There is no partial state to work around here. Meta’s verdict is the gate, and retrying the check after accepting the terms is the only thing that changes it.
Step 3: Create the Agent
One click on Set up agent. ChatMaxima calls Meta’s onboarding endpoint for that phone number, Meta creates the agent and returns its identifier, and ChatMaxima stores it against the number.
Two things to note. First, the agent is created off. It exists, it is configurable, and it is answering nobody. Nothing reaches a real customer until you deliberately switch it on in step 8.
Second, the agent is already not empty. Meta seeds it from your business profile and your website, so the very first Test chat message usually gets a coherent answer about your business before you have added a single FAQ. That is a useful baseline and a useful warning: check what it says about you out of the box, because that is what customers would have seen.
Step 4: Teach It What Your Business Knows
The Knowledge tab is what the agent can look things up in. Three kinds of material, and the distinction between them matters more than it looks.
FAQs are explicit question and answer pairs. Use them for the answers you want worded exactly one way: refund windows, delivery timelines, warranty terms, what is included in a service. If there is a sentence your team is tired of retyping, it belongs here.
Websites are pages you hand to Meta to crawl. Add the URL and Meta crawls it in the background and keeps it as reference material. The page shows the crawl status and page count, and because a running crawl otherwise looks frozen, there is a Refresh crawl status control that re-reads the state from Meta on demand. If a crawl fails, Meta’s reason is displayed under the status rather than leaving you with a silent failure.
Files are documents: PDF, DOC, DOCX, PNG, JPG, CSV, or XLSX. Price lists, policy documents, spec sheets, service catalogues. The page states the real upload ceiling it can accept rather than a marketing number, so you know before you pick a file whether it will go through.
A practical sequence that works: add your two or three highest traffic pages as websites, upload the one document your team quotes from most, then write FAQs only for the questions where a crawled page gives a technically correct but commercially wrong answer. Knowledge changes apply to new conversations, not to ones already running.
Step 5: Shape Behaviour With Skills
Knowledge is what the agent knows. Skills are standing instructions about how it behaves. Each skill has three parts: a short name, a description telling the agent when the skill applies, and the instructions themselves.
Use skills for the things that are judgement rather than fact. Always ask for an order number before discussing a delivery. Never quote a discount that is not on the price list. If a customer mentions a complaint about a previous order, escalate rather than explain. Keep the tone formal in Arabic and casual in English.
Meta’s field rules are strict and ChatMaxima enforces them before save rather than letting the API reject you: the name is lowercase letters, numbers and hyphens only up to 64 characters, the description is up to 1,024 characters, and the instructions can run to 20,000.
Drafting a skill with MaxIA
Writing a good skill blind is harder than it looks, because a new instruction can quietly contradict an FAQ you already loaded, duplicate an existing skill, or fight your handoff policy. So the Skills tab has MaxIA, our assistant, wired into it.
Describe the behaviour you want in plain language. MaxIA reads the number’s actual configuration first: the skills already in place, the knowledge loaded, the current agent settings. It can also try a draft against the live agent using the unbilled test endpoint to see how the wording actually lands.
Then it proposes. MaxIA never writes to your live agent. It renders a card with a suggested skill, tells you if it replaces an existing one, and fills the form when you apply it. You still click Add skill to save. A model does not change live customer-facing behaviour on its own.
Step 6: Give the Agent Actions
An agent that can only talk is a better FAQ page. Actions are what turn it into something useful: the operations it is allowed to perform mid-conversation.
ChatMaxima is the connector. When you enable your first action on a number, we provision a single connector with Meta for that number, authenticated with your own API key. Each action you switch on becomes a tool the agent can call. The design point is blunt and deliberate: the agent only ever receives a ChatMaxima API key. Your Shopify, HubSpot, and Google credentials never leave ChatMaxima.
The built-in actions need nothing connected:
- Look up a contact by phone or email, so the agent stops asking for details you already hold.
- Save or update a contact, writing name, phone, email and company into your contact hub.
- Open a support ticket when the agent cannot resolve something, logged for your team with the customer’s own description of the problem.
The rest use accounts you have already connected under Integrations:
- Shopify: order status with payment, fulfilment and tracking, plus product search with price and availability.
- WooCommerce: order status with items and totals, plus product search with price and stock.
- Google Calendar: free slots between two dates, and booking an appointment on your primary calendar with the customer invited.
- HubSpot: find a contact by email or phone, create a new lead.
- Zoho CRM: find a contact by email, create a new lead.
Each action is off until you switch it on, per number. Enable the two that matter for your business rather than all of them: every tool you expose is another thing the agent can decide to do in front of a customer. An action takes effect from the next conversation.
Step 7: Test Before Anyone Real Sees It
The Test chat panel is the single most useful part of this setup, and it is the part people skip.
It runs the full agent pipeline: the same knowledge, the same skills, the same actions, the same model. It reaches no real customer. And Meta does not bill it. So there is no reason to guess.
Chat with it exactly as a customer would. Replies render with real WhatsApp formatting, so bold, lists and paragraph breaks appear the way they will in the customer’s chat rather than as raw markers. Quick replies the agent offers appear as clickable buttons. When the agent decides to hand off to a human or deliberately not reply, you see that as a labelled chip with the reason, which is how you find out your handoff rules are too aggressive or not aggressive enough.
Reset the conversation from the panel header to start clean. Things worth testing before you go anywhere near a customer:
- Your three highest volume real questions, word for word from your inbox.
- A question you do not want answered, to confirm your never-say phrases hold.
- An order or booking request end to end, to confirm the action actually fires and returns real data.
- A frustrated customer, to confirm the handoff triggers instead of the agent looping.
Step 8: Roll Out to Test Numbers First
Before flipping the agent on for the world, the Settings tab lets you decide who it is allowed to answer. Two audiences: Everyone, or Only test numbers.
Set it to Only test numbers and add your own phone and a colleague’s on the Test numbers tab in international format. The agent now replies to those numbers and nobody else. Everyone else on that number is handled exactly as they were before.
This is a real conversation on a real WhatsApp number, billed like one, which is the point. Test chat proves the configuration. A test number proves the experience: notification timing, how the reply reads on a phone in a hurry, whether the agent’s handoff lands in your inbox the way you expect.
While you are in Settings, configure the rest of the behaviour:
- Hand off to your team. Lets the agent transfer a conversation to your inbox when a customer asks for a person or the agent cannot help. You choose the message style: Meta’s default wording, let the agent phrase it, or your own custom message. Turn this on. An agent with no exit is the single fastest way to make a customer angry.
- Follow up inactive customers. An optional nudge after a chosen interval from 5 minutes to 24 hours, with your own message. Useful for abandoned enquiries, easy to overdo.
- Never say. One phrase per line that the agent will avoid. Competitor names, claims your legal team will not stand behind, discounts that do not exist, anything regulated in your industry.
Step 9: Switch the Agent On
Flip Agent is on and save. If the WABA has no payment method, this is where Meta refuses and ChatMaxima shows the Billing Hub link. If a chatbot is still connected to this number, this is where the switch stays locked with the bot named.
With both cleared, the agent is live. Move the audience from Only test numbers to Everyone when the test numbers have convinced you, and Meta’s agent is answering your customers first.
Turning it off is one toggle, always available, with no Meta gate in the way.
What Happens in Your Inbox While the Agent Answers
This is the part that decides whether Meta Business Agent is usable for a real support team, and it is why ChatMaxima’s support for it took a webhook rewrite rather than a button.
ChatMaxima subscribes to Meta’s handover protocol. While Meta’s agent owns a conversation, the messages arrive on a standby channel instead of the normal inbound path, and ChatMaxima tracks who owns each thread: your app, or the Meta agent. Your automation deliberately does not answer on a thread the agent owns, which is the whole reason two answers never reach one customer.
What that gives your team: conversations the agent handles stay visible in ChatMaxima, with the agent’s replies recorded as the Meta agent rather than as one of your people. The inbox remains the single place the conversation lives.
And the handover works both ways. Any message your team sends takes the thread back. Reply from the inbox and control returns to you, silently and immediately, with no special command. Meta’s protocol treats the act of sending as taking control, and ChatMaxima records the ownership change when it happens. The agent stops answering that conversation; your agent is in it.
That is the honest mental model: Meta’s agent handles the first line, your team reaches in whenever a human is needed, and the act of replying is the handover.
What It Costs
Meta bills agent conversations by token, directly on your WhatsApp Business Account, separately from the per-message and per-conversation pricing you already know. That is why the payment method is mandatory and why the billing account is a Meta screen rather than a ChatMaxima one.
ChatMaxima does not resell or mark up those tokens. You configure the agent in ChatMaxima, Meta bills you for running it, and your ChatMaxima plan covers the inbox, the automation, the integrations, and everything else on the number. Our own pricing is unchanged by switching the agent on.
The cost question people actually want answered is whether Meta’s agent is cheaper than running your own. It depends on volume, on how much of your traffic is genuinely repetitive, and on how much control you need over what gets said. We worked through that comparison properly in Meta Business Agent vs a custom AI agent, including the case for running both on different numbers.
What to Do Next
The setup is short once the prerequisites are clear, so work them in this order:
- Confirm the number’s country and vertical are in the open list.
- Accept the Meta Business AI Terms for that WhatsApp Business Account, as a portfolio admin.
- Open Settings, WhatsApp, Actions, Meta Business Agent for the number and create the agent.
- Load two or three websites, one document, and your most repeated FAQs.
- Add two or three skills, drafting them with MaxIA so they do not fight your existing setup.
- Enable only the actions you will actually use.
- Break it in Test chat, for free, until it holds.
- Run it on test numbers for a few days.
- Attach a payment method, switch it on, move the audience to Everyone.
The decision that deserves the most thought is not in the dashboard at all. It is step 3 of the prerequisites: which of your numbers should have Meta answering first, and which should keep your own bot and your own flows. Most businesses with more than one number will end up doing both, and that is the right answer rather than a compromise.
Meta Business Agent support is live in ChatMaxima now, on every WhatsApp number in your workspace that Meta has opened it for. If you are already running WhatsApp with us, the entry point is sitting in the Actions menu next to the number.