> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/docs/mba/meta-business-agent/6.-roll-out-to-everyone.md).

# 6. Roll out to everyone

{% hint style="warning" %}
**A payment method is required before this step.** Opening the agent to `EVERYONE` needs a valid payment method on file with Meta for the business that owns the WABA:

* **A credit line** — manage it in [Billing Hub](https://business.facebook.com/latest/billing_hub/credit_lines/): apply for one if you don't have it yet, or add your existing account.
* **A credit card** — Meta has been rolling out card payments gradually since September 2026. Check Billing Hub to see whether it's available for your account.

Until a payment method is attached, switching to `EVERYONE` returns `400`. Testing under `ALLOWLISTED_ONLY` (steps 1–5) does **not** require a payment method.
{% endhint %}

{% hint style="info" %}
**Billing mechanics:** MBA charges are **postpaid** — billed at the start of the following month, no prepayment and no mid-month charges. If you're on a credit line, hitting **100% utilization suspends MBA access** until it's resolved. MBA usage does **not** appear in the standard WhatsApp message billing analytics — see [Controlling your Agent](https://docs.360dialog.com/docs/mba/meta-business-agent/controlling-your-agent.md) to track and cap spend.
{% endhint %}

When the agent has proven itself with your allowlist, open it to all customers by switching the audience to `EVERYONE`.

```bash
curl -s -X PUT https://waba-v2.360dialog.io/agent_config/settings \
  -H "D360-API-KEY: <YOUR_API_KEY>" \
  -H "X-API-Version: 2.0.0" \
  -H "Content-Type: application/json" \
  -d '{
    "rollout": { "enabled": true },
    "ai_audience": "EVERYONE"
  }'
```

[Update AI agent settings](https://docs.360dialog.com/docs/mba/api-ref/onboarding/update-ai-agent-settings.md)

From now on, the agent is the primary responder for every new conversation on that number.

## If enabling the agent fails

| Response                                 | Cause                                                                                                                                                                                                  | What to do                                                                                                                      |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
| `400` mentioning conversation routing    | The number needs an explicit routing choice before the agent can be its primary responder. The agent stays disabled.                                                                                   | Follow the routing guidance linked in the error: select the phone number, assign the agent as primary, then verify it's active. |
| `400` mentioning WhatsApp Business Inbox | Meta's WhatsApp Business Inbox is still in use on this WABA, or on another WABA in the same business portfolio. Inbox and the agent handle the same incoming conversations, so only one can be active. | Remove Inbox from the account that still has it, then enable the agent again.                                                   |
| `400` when switching to `EVERYONE`       | No payment method on the Business Agent account.                                                                                                                                                       | Add a credit line or card (see above), then retry.                                                                              |
| `403`                                    | The Meta Business AI Terms aren't accepted, the business's vertical isn't eligible, or the capability isn't enabled for the account.                                                                   | Not temporary. Check terms and [eligibility](https://docs.360dialog.com/docs/mba/meta-business-agent/1.-check-eligibility.md).  |
| `404`                                    | The number has no agent.                                                                                                                                                                               | [Onboard the number](https://docs.360dialog.com/docs/mba/meta-business-agent/2.-enable-your-agent.md) first.                    |

### After you roll out

* **Keep iterating.** Real traffic surfaces new questions. Keep adding FAQs and refining skills as you see what customers actually ask.
* **Watch the handoff path.** At full volume, make sure humans can keep up with handoffs — the agent goes silent on a chat the moment it hands off.
* **Turn it off any time.** Set `rollout.enabled` to `false` to stop the agent responding, or drop back to `ALLOWLISTED_ONLY` to narrow the audience again. Configuration is preserved. Turning it back on makes it respond to new conversations only.

```bash
# Pause the agent
curl -s -X PUT https://waba-v2.360dialog.io/agent_config/settings \
  -H "D360-API-KEY: <YOUR_API_KEY>" \
  -H "X-API-Version: 2.0.0" \
  -H "Content-Type: application/json" \
  -d '{ "rollout": { "enabled": false } }'
```

### Check whether the agent is on

There's no webhook when the agent is switched on or off, so read the settings when you need to know. `GET /agent_config/settings` answers for the number your API key belongs to.

```bash
curl -s https://waba-v2.360dialog.io/agent_config/settings \
  -H "D360-API-KEY: <YOUR_API_KEY>" \
  -H "X-API-Version: 2.0.0"
```

* **No entry with `channel: "whatsapp"`** — the agent was never set up, or was deleted.
* **`rollout.enabled: false`** — the agent is set up but off.
* **`403`** — the Meta Business AI Terms aren't accepted, or the business's vertical isn't eligible.
* **`400`** — invalid phone number.

[Get AI agent settings](https://docs.360dialog.com/docs/mba/api-ref/onboarding/get-ai-agent-settings.md)

***

That's the full journey. Once you're live, see [Controlling your Agent](https://docs.360dialog.com/docs/mba/meta-business-agent/controlling-your-agent.md) for ongoing operation — usage budgets, taking over a conversation, and diagnosing individual replies — and [Known limitations & workarounds](https://docs.360dialog.com/docs/mba/meta-business-agent/known-limitations.md) for every gap referenced along the way.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.360dialog.com/docs/mba/meta-business-agent/6.-roll-out-to-everyone.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
