> 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:

* **Today:** a direct credit line. Use Billing Hub to manage it — apply for one if you don't have it yet, or add your existing account.
* **From 8 September 2026:** credit-card support as an alternative, rolling out gradually (some accounts may see it before others).

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** yet appear in the standard WhatsApp message billing analytics — see Controlling your Agent for how to track and cap spend in the meantime.
{% 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 "Content-Type: application/json" \
  -d '{
    "rollout": { "enabled": true },
    "ai_audience": "EVERYONE"
  }'
```

[Update AI agent settings](/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.

### 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 to new conversations, or drop back to `ALLOWLISTED_ONLY` to narrow the audience again. Configuration is preserved.

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

[Get AI agent settings](/docs/mba/api-ref/onboarding/get-ai-agent-settings.md)

***

That's the full journey. Once you're live, see [Controlling your Agent](/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](/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.