> 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/5.-go-live.md).

# 5. Go live

Don't flip the agent on for every customer at once. Release it to a small, controlled set of numbers first, watch how it behaves on real conversations, and fix what you learn. That's what the **allowlist** is for.

## How the allowlist works

The agent's audience is controlled by the `ai_audience` setting:

* **`ALLOWLISTED_ONLY`** — the agent responds only to consumers whose numbers are on the allowlist. Everyone else is handled as if the agent weren't there.
* **`EVERYONE`** — the agent responds to all consumers (that's [full rollout](/docs/mba/meta-business-agent/6.-roll-out-to-everyone.md)).

## Turn on a controlled launch

{% stepper %}
{% step %}

## Add your test numbers to the allowlist

```bash
curl -s -X POST https://waba-v2.360dialog.io/agent_config/allowlist \
  -H "D360-API-KEY: <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{ "phone_number": "+49123456789" }'
```

[Add to allowlist](/docs/mba/api-ref/onboarding/add-to-allowlist.md)
{% endstep %}

{% step %}

## Enable the agent and set the audience to allowlist-only

```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": "ALLOWLISTED_ONLY"
  }'
```

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

Now only the numbers you added will talk to the agent.
{% endstep %}
{% endstepper %}

## Iterate

Treat the controlled launch as a feedback loop:

1. **Message the agent** from allowlisted numbers on real WhatsApp.
2. **Watch the replies** — on the phone, or by logging the `standby` webhook events. Is it grounded, on-brand, and handing off when it should?
3. **Refine** skills, FAQs, and business info based on what you see.
4. **Expand the allowlist** gradually — add colleagues, then friendly customers.
5. Repeat until you're confident.

{% hint style="warning" %}
**Reminder: `agent_test` won't return replies under `ALLOWLISTED_ONLY`.** During the allowlist phase, validate by messaging from allowlisted numbers on WhatsApp rather than the test endpoint. See [Test your agent](/docs/mba/meta-business-agent/4.-test-your-agent.md) for why.
{% endhint %}

{% hint style="success" %}
**You can monitor the allowlist phase over webhooks.** While the agent holds a chat, consumer messages and agent replies arrive on the `standby` field of your number's webhook — so you can log and review real conversations instead of reading them off the phone. See [Webhooks](/docs/mba/webhooks.md).
{% endhint %}

{% hint style="info" %}
**Have your human-handoff path ready before you go live**, even in the allowlist phase. Once the agent hands a chat to a human it stops replying — so make sure a human can actually pick up. See [handoff](/docs/mba/meta-business-agent/3.-configure-your-agent.md).
{% endhint %}

When the agent performs well for your allowlist, you're ready to [roll out to everyone](/docs/mba/meta-business-agent/6.-roll-out-to-everyone.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 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/5.-go-live.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.