> 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

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)

{% hint style="info" %}
**Billing is still being defined by Meta.** As of now, how MBA usage is priced and charged — and how a payment method is added — isn't finalized, and MBA usage does **not** appear in the standard WhatsApp message billing analytics. Factor this uncertainty into any commercial rollout, and check back here for updates. See [Known limitations](/docs/mba/meta-business-agent/known-limitations.md).
{% endhint %}

### Managing thread control

Once you're live at full volume, your team or systems will sometimes need to step into a conversation the agent is handling — and hand it back afterward. The agent is the primary responder and holds each conversation by default, so while it's in control the consumer's messages and the agent's replies reach you on the `standby` field. The moment you send a message to that conversation, **you take control**: from then on the consumer's messages arrive on `messages` and the agent stays quiet. When you're done, hand control **back to the agent** using the Thread Control endpoint's `release` action:

```bash
curl -s -X POST "https://waba-v2.360dialog.io/business/whatsapp/phone_numbers/<PHONE_NUMBER_ID>/thread_control" \
  -H "D360-API-KEY: <YOUR_API_KEY>" \
  -H "X-API-Version: 1.0.0" \
  -H "Content-Type: application/json" \
  -d '{ "messaging_product": "whatsapp", "action": "release", "to": "<CONSUMER_PHONE>" }'
```

[Release thread control](/docs/mba/api-ref/operate/release-thread-control.md)

Every control change also emits a `messaging_handovers` webhook, so you can keep track of who currently holds a conversation — when `previous_owner_app_role` is `meta_business_agent`, the agent has just passed control to you. There's no endpoint to query the current owner, so rely on these events (together with the `standby` vs `messages` routing) to track control state. See [Webhooks](/docs/mba/webhooks.md) for the payloads. Note that `release` is the only supported action — you take control implicitly by sending a message, not through an explicit "take" call.

That's the full journey. For every gap referenced along the way, see the consolidated [Known limitations & workarounds](/docs/mba/meta-business-agent/known-limitations.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.