Meta Business Agent on WhatsApp: what it can and can't do (UK guide, 2026)

Short answer: Meta Business Agent (MBA) is Meta's own AI agent for WhatsApp business numbers. Once you switch it on for a number, it becomes the first responder. It answers from the information you give it, calls your systems to do things like look up an order, and hands the conversation to your team when it decides it should. It is quick to start and cheap to run. It is also less configurable than most people assume, especially around handing over to humans, running many numbers, and what happens when your own systems are slow.

This guide covers MBA on the WhatsApp Business Platform (the Cloud API version most mid-sized and larger businesses use).

Can your business use it?

Work through these before you plan anything. If one fails, MBA is either off the table or blocked until you fix it.

1. Your WhatsApp number runs on the WhatsApp Business Platform, directly or through a provider. A number that only lives in the WhatsApp Business phone app doesn't qualify until it's moved across.
2. Your business category isn't excluded. Meta's current list excludes finance, government, health, alcohol, gambling, over-the-counter drugs and matrimony services. Eligibility is judged on the category set on your WhatsApp Business profile, not on what you plan to use the agent for.
3. Your account is in good standing, with no restrictions or bans on the WhatsApp account or the business behind it.
4. Nothing else automated is answering on that number, or you're willing to switch it off.
5. Your business has completed Meta's verification.
6. Someone with authority accepts the MBA terms in WhatsApp Manager. The Meta Business Agent tab only appears there if one of your numbers is eligible.
7. A Meta credit line is attached to your Business Agent account. Since 1 August 2026, messages aren't delivered without one. This fails silently: the agent looks set up, tests pass, and customers get nothing.

A warning about Meta's own documentation. Two versions of Meta's eligibility rules are in circulation and they contradict each other. One lists five sectors and 182 countries; the current one excludes the sectors above and allows everything else. Meta's eligibility check on your specific number is the final word, but it only answers yes or no. It doesn't tell you why.

What it can do

• Answer from your information. You can load:
  • core business details in fixed fields (payment methods, returns, delivery, contact details and opening hours)
  • FAQs
  • documents (PDF, Word, PNG and JPG, plus CSV and Excel if extraction is enabled)
  • website pages, by giving it a URL
  • your product catalogue, managed in Meta's Commerce Manager
• Follow your tone and rules. "Skills" are written instructions that shape how it behaves and sounds.
• Use rich WhatsApp features, such as carousels, lists, buttons, location sharing and WhatsApp Flows (in-chat forms).
• Act in your systems. Connectors let it call your APIs to check an order, book an appointment or look up an account. Your customer's WhatsApp number can be passed to your system automatically, so the agent doesn't have to type it.
• React to events. Your systems can push updates into a live conversation, such as "payment received" or "document verified".
• Pilot safely. You can restrict the agent to a named list of customers before opening it to everyone.
• Be tested before launch. A test tool runs the full agent without charge, and an evaluation tool scores conversations.

What it can't do (the list that surprises people)

It's set up one phone number at a time. Every setting, document and connector belongs to a single number. There's no bulk setup, copying or template. Forty numbers means forty separate set-ups, and forty sets of changes every time something updates.

You can't choose when it hands over to a human. Meta lists three signals: the agent isn't confident, it detects an integrity problem, or the customer asks for a person. There's no way to add rules like "always hand over complaints" or "escalate orders over £500". Anything like that has to be detected by your own systems, which then take over the conversation.

There's no rules engine or routing dashboard. If you're expecting something like a helpdesk's escalation settings, it isn't there.

Knowledge has sharp edges.

• FAQs work less well beyond a few hundred entries, and each one is read on its own, so "see the answer above" breaks.
• If your opening hours appear in a document, an FAQ and a web page, nothing decides which one wins. Keep one source for each topic.
• Website crawling takes only a URL. You can't set how deep it goes or how often it refreshes, and JavaScript-heavy or bot-blocking sites may return nothing.
• Uploaded documents can't be updated, only deleted and uploaded again.

Connectors are limited.

• Your systems must accept an API key, OAuth client credentials, or no authentication. Logins that need a person to sign in (three-legged OAuth) and basic username-and-password authentication aren't supported.
• Meta doesn't document a timeout, a retry policy, or what your customer sees when your system is slow or down.
• There's no "ask a person first" step before the agent acts. Keep anything irreversible out of its reach, and make sure a repeated request can't create a duplicate order.
• Assume the agent sees everything your system sends back, so return only what it needs.

You can't see MBA spend in Meta's analytics yet. There's no reporting for MBA messages, so plan your own cost tracking.

Switching it off and on isn't symmetrical. Turning it off stops the agent in every conversation at once. Turning it back on only applies to new conversations.

What it costs

• Meta charges by the token: US$2.00 per million, covering both the AI and message delivery, and only for delivered messages.
• A typical message uses 20,000 to 25,000 tokens, roughly 4 to 5 US cents. Meta's examples put a simple four-message enquiry at about 16 to 20 cents and a ten-message troubleshooting chat at about 40 to 50 cents.
• Billing is monthly, against a Meta credit line. Non-USD accounts are charged at the daily exchange rate.
• Watch out if your chats start from Click-to-WhatsApp ads. Most WhatsApp message types are free for 72 hours after someone messages you from an ad. MBA messages aren't.
• When your team takes over, their replies are charged as standard WhatsApp service messages (chargeable from 1 October 2026).

Meta's June 2026 announcement also mentions paid subscription plans to come, so expect pricing to change.

If you're using an agency or partner

• Only a Meta "Solution Partner" can bill you for your Meta usage. If your partner is a "Tech Provider", Meta bills you directly and you'll need your own payment method set up.
• Partners can onboard 10 new businesses a week until Meta verifies them, then 200. If your launch date depends on a new partner, ask where they are in that process.
• Meta's documentation doesn't yet say whether a partner can switch MBA on for your number, or whether only you can. A good partner will test this before promising a date.
• You keep full access to your own WhatsApp account. A partner can't lock you out, and shouldn't try.

Questions to answer before you start

1. How many WhatsApp numbers are in scope now, and in a year?
2. What must a person always handle, and does each of those fit one of Meta's three handover signals?
3. Which actions should the agent take, and does each have an API that uses a supported login method?
4. How many FAQs do you have, and who will cut them down to what customers actually ask?
5. Which single source is the authority for prices, opening hours, returns and stock?
6. Is a credit line attached to your Business Agent account?
7. What share of your chats start from Click-to-WhatsApp ads?
8. What should a customer see if your system is down?
9. What's your WhatsApp messaging limit? Limits are shared across every number in your business portfolio. A new portfolio can start conversations with 250 people per 24 hours, and adding numbers doesn't add capacity.

How we'd approach it

Start with one number, a short list of real customers and a small set of FAQs. Choose one source of truth for each topic. Put only safe, repeatable actions behind connectors. Test the gaps Meta doesn't document, such as a slow API or a repeated request, before you launch, not after a customer finds them. Measure what the agent resolves, what it hands over, and what it costs per conversation, and only then add more numbers.

Twisthand Intelligence helps UK businesses work out whether Meta Business Agent fits, and set it up so it holds up with real customers. See how we work with Meta Business Agent.

Frequently asked questions