Guide · AI on WhatsApp · For the owner whose agent has gone quiet
When Meta's AI agent on WhatsApp goes quiet or answers the wrong people: the causes Meta's troubleshooting page lists
Meta keeps a troubleshooting page for its AI agent on the WhatsApp Business Platform. Most of it is written for developers, but the common problems it lists are ones an owner notices first: the agent says nothing, answers only the test list, or starts taking chats the business's own system used to handle. Here they are in plain words.
Published 7 October 2026
First: is it Meta, or is it the setup?
Meta's status page has its own section for the platform behind Meta Business Agent, with any open incident and a history of past ones. Meta's rule of thumb: when many requests fail at once, or something that worked a moment ago stops, check the status page first. When the trouble is limited to one number or one connection, it is usually the setup. How to read the status page is in the status page guide.
The common problems Meta lists
- It answers the test list, but not other customers
- The agent's audience is still set to the test list. Meta says answering everyone needs a payment method attached in Meta's billing; without one, the agent cannot be switched on for everyone.
- It worked in testing, then went silent with real customers
- Meta calls this a common cause: the business's own system sent a message in that chat. Any message from the system takes the conversation over, and the agent stays quiet in that chat until the system hands it back.
- It does not answer at all
- Either the agent has not been switched on, or its knowledge and instructions have not been set up yet.
- It took over chats our system used to handle
- Once switched on, the agent becomes the first responder for every new conversation on that number, and the existing system steps back to watching. Meta says the system can take a chat over when needed and hand it back afterwards, or the agent can be switched off entirely.
- The agent tab is missing in WhatsApp Manager
- None of the numbers in the WhatsApp account is eligible for the agent yet.
- Nothing works and the error mentions terms
- Meta's terms for the agent have not been accepted in WhatsApp Manager. Providers building on the agent must also accept Meta's terms for them.
The audience setting, switching off and eligibility are in the settings guide; feeding it knowledge is in the knowledge guide; and the test list is in the testing guide.
When the agent cannot reach your own systems
An agent that checks stock or books appointments does it through connections to the business's own systems. Meta lists why those calls fail: the business's system rejected the agent's login, the login works but lacks permission, the system cannot be reached from the internet, the record asked for does not exist, the request was badly formed, or the system was asked too often or too many times at once.
Each connection also shows a state: connected and healthy, waiting for someone to finish signing in, expired, or in error. An expired login is the one an owner can prevent, by knowing when the keys to the business's own systems are due to be renewed. Connections are explained in the skills and connectors guide, and where tool failures show up in the agent reports guide.
What to send your provider
Meta says every reply from the agent's platform carries a reference code for that request, and asks for it when anyone contacts Meta's support. Our reading: when something goes wrong, note the time, which conversation it was and what the customer saw, and ask the provider to find the reference code for that moment. It is the fastest way for Meta to trace one failed request.
Questions
Why does Meta's agent answer our staff but not our customers?
Its audience is most likely still the test list. Meta says answering everyone needs a payment method attached in Meta's billing.
The agent stopped replying in one chat after our system sent an order update. Is it broken?
No. Meta says any message from the business's own system takes that conversation over, and the agent stays quiet in it until the system hands it back.
We switched the agent on and our old chatbot stopped getting messages. Why?
Meta says the agent becomes the first responder for all new conversations on the number, and the existing system steps back to watching. The system can take chats over when needed, or the agent can be switched off.
How do we know if the problem is on Meta's side?
Check the Meta Business Agent section of Meta's status page. Meta says failures across many requests at once point there; trouble on one number is usually the setup.
Sources
- Meta's developer documentation: Troubleshooting Meta Business Agent, read 7 October 2026.
More plain-language notes like this one are on the guides page.
Want every chat in one place you own?
We set up a business's WhatsApp number on a system its team runs, so every customer conversation sits in one place the business owns. A short call is the easiest way to see how that would work for you.
Book a demo