> 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/2.-enable-your-agent.md). # 2. Enable your agent Enabling MBA on a number is two things: a one-time terms acceptance in Meta Business Manager, and an onboarding call that prepares the agent. The MBA stays locked until the terms are accepted. {% hint style="info" %} **You don't need a payment method yet.** You can enable, configure, test, and go live on an allowlist (steps 2–5) without one. A payment method is only required before you open the agent to `EVERYONE` — see [Roll out to everyone.](/docs/mba/meta-business-agent/6.-roll-out-to-everyone.md) {% endhint %} ## Accept the Meta Business AI Terms of Service The **Meta Business AI Terms** are accepted per WABA, in **Meta Business Manager → WhatsApp Manager → Business AI tab**. {% hint style="info" %} Business AI tab may be hidden, but you can always access it using the following urll: [`https://business.facebook.com/latest/whatsapp_manager/business_ai?business_id={BUSINESS_PORTFOLIO_ID}&asset_id={WABA_ID}`](https://business.facebook.com/latest/whatsapp_manager/business_ai?business_id={BUSINESS_PORTFOLIO_ID}\&asset_id={WABA_ID}) where `business_id` is the Business Portfolio ID and `asset_id` is the WABA ID {% endhint %} {% hint style="warning" %} **Only someone with access to the WABA's *****owning***** Business Manager can accept the terms.** You can open the Business AI page by passing your own Business Manager ID, but the **Accept** action only works if you have access to the business that owns the WABA. If a client owns the WABA, the client (or an admin on the owning BM) must accept. Plan for this in partner setups — it's a common blocker. {% endhint %} {% hint style="danger" %} **API calls return `403 Forbidden` until the terms are accepted.** The error reads: *"The Meta Business AI Terms of Service must be accepted for this WhatsApp Business Account before using this API."* If you see this 403, the terms haven't been accepted for that WABA yet. {% endhint %} ## Add a valid payment method Since 1 August, Meta requires a client credit line for Meta Business Agent usage. Meta plans to support credit-card payments in September. Use Billing Hub to manage the credit line for your Meta Business Agent account: * If you already have a credit line, add the account in [Billing Hub](https://business.facebook.com/latest/billing_hub/credit_lines/). * If you need a credit line, apply in [Billing Hub](https://business.facebook.com/latest/billing_hub/credit_lines/). {% hint style="warning" %} Credit-line management may not yet be available in the Meta UI. Contact Meta support if Billing Hub does not offer the required action. {% endhint %} ## Onboard the number Once the terms are accepted, onboard the number to create the agent's configuration and knowledge scaffolding. This is a required step before you can turn the agent on. You can do it two ways. **Option A — in WhatsApp Manager (no code).** Right after you accept the terms, an **Onboard** call-to-action appears in the Business AI tab. Click it to onboard the number. {% hint style="warning" %} **The "Onboard" button sometimes shows an error even when it worked.** If the CTA returns an error, the number is often onboarded anyway. Wait about a minute and refresh the page before retrying — you'll usually see it's already onboarded. {% endhint %} **Option B — via API:** ```bash curl -s -X POST "https://waba-v2.360dialog.io/agent_onboarding?channel=whatsapp" \ -H "D360-API-KEY: " ``` [Create an onboarding session](/docs/mba/api-ref/onboarding/create-an-onboarding-session.md#post-agent_onboarding) Onboarding schedules some background preparation, so it may take a moment before configuration endpoints are fully ready. {% hint style="info" %} **Onboarding ≠ live.** After onboarding, the agent still won't reply to customers. It only starts responding once you enable it and set its audience — see [Go live](/docs/mba/meta-business-agent/5.-go-live.md) and [Roll out to everyone](/docs/mba/meta-business-agent/6.-roll-out-to-everyone.md). Configure it first ([Step 3)](/docs/mba/meta-business-agent/3.-configure-your-agent.md). {% endhint %} --- # 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/2.-enable-your-agent.md?ask=&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.