WhatsApp Business Platform

Prepare before enabling Meta Business Agent

Updated: Nov 3, 2026
Copy for LLM
Use this guide before enabling Meta Business Agent on a business phone number that already has another integration.
Important: If an effective routing configuration already exists and more than one partner or direct integration remains, you must choose the routing configuration in Meta Business Suite. An enablement attempt that requires this choice does not replace your existing routing. Confirm that the affected integrations are ready before saving any changes.

What changes when you enable Meta Business Agent

Setting up Meta Business Agent or using the Agent Test API does not change live message routing. The routing change occurs when Meta Business Agent is enabled for live conversations.
Where automatic routing setup is allowed when you enable Meta Business Agent:
  • Meta Business Agent becomes the primary responder for new conversations on the messaging entry points.
  • Previous primary responders move to standby and receive conversation traffic on the standby webhook field instead of the messages webhook field when they do not own the thread.
  • Incoming-call routing is preserved and remains separate from messaging thread ownership.
  • If no routing configuration exists, enabling the agent can create one. If phone-number-specific routing is enabled, the selected phone number joins a configuration initialized from the account default.
For Meta Business Agent setup and rollout guidance, see the Meta Business Agent quickstart.
If routing must be configured explicitly, you choose the messaging entry points that Meta Business Agent handles, the escalation partner, and standby visibility. Follow Routing setup required.

Before enabling the agent

  1. In Conversation Routing in Meta Business Suite, determine whether the selected phone number uses the account-default configuration or a phone-number-specific configuration.
  2. Identify every partner and direct integration in the affected scope. An account-default configuration applies to every phone number without a phone-number-specific override.
  3. Send the responsible partners and developers the integration readiness resources.
  4. Ask them to confirm that their integrations can receive the webhook fields and handle the ownership changes required for their roles.
  5. Enable Meta Business Agent only after every affected integration has confirmed readiness.
  6. After enabling the agent, review the account-default and phone-number-specific configurations that apply, then test message delivery and handoff behavior.
For agent onboarding, audience settings, and allowlisted testing, see Get started with Meta Business Agent and Test your agent.

Routing setup required

If enabling the agent returns Conversation routing setup required, an effective routing configuration already exists and multiple integrations require an explicit routing choice. The error links to this page. WhatsApp Manager can instead open Conversation Routing directly when you turn on Allow AI agent to respond.
Complete the routing choice in Meta Business Suite. Creating a configuration and repeating the same enablement request is not sufficient: select Meta Business Agent as a primary responder in the configuration that applies to the intended phone numbers.

Prepare Meta Business Agent

Complete Meta Business Agent setup for each intended number, including onboarding, terms acceptance, knowledge, and instructions. Set the audience and billing as described in Test your agent and Set up billing.
Confirm that the affected integrations are ready using the integration readiness resources.

Choose the routing scope

  • Selected numbers: In Conversation routing, select Create in the Alternate Routing group section if no group exists, or Manage to edit the existing group. Follow Create an alternate routing group. Select only the numbers that should use Meta Business Agent. Numbers outside the group retain the account default.
  • All numbers, or a single-number account: Edit the account routing using Path E in Get started. A single-number account does not show Alternate Routing group. Selecting every number in an alternate group instead replaces the account routing and removes the group.

Assign the agent and verify enablement

In the routing dialog for your chosen scope:
  1. For each messaging entry point the agent should handle, open the responder selector and select Meta Business Agent. Keep the intended responder on entry points handled by another integration.
  2. Review Calls with customers separately and retain the intended call responder. Review Thread control and Conversation visibility so handoffs and standby delivery match your integrations’ needs.
  3. Save the configuration using the group procedure or the account-default editor. Review any routing-change warning before confirming.
  4. Reopen the saved configuration and check the selected phone numbers and primary assignments. In WhatsApp Manager’s Meta Business Agent tab, open setup for each selected number and check that Allow AI agent to respond is on. Saving Meta Business Agent as primary attempts to enable it on the affected numbers; a saved routing configuration alone does not prove activation succeeded.
  5. Test a new or idle conversation through an entry point assigned to the agent, then test handoff and standby delivery. For allowlisted testing, follow Test your agent.
If the agent is still off after saving, review its setup, eligibility, terms, audience, and billing. Check the saved routing again and use Meta Business Agent troubleshooting if it remains disabled. Do not repeatedly retry the routing-required enablement request without changing the routing choice.

Integration readiness resources

Share these resources with each partner or developer responsible for an existing integration:
  • Prepare for Conversation Routing explains how routed message delivery differs from single-responder delivery and how to prepare an integration before routing applies.
  • Standby partners explains how to subscribe to standby webhooks, request standby visibility, and process conversations the integration does not own.
  • Thread control explains how to subscribe to ownership events, track thread ownership, and implement the actions required for the integration’s role.
If more than one integration handles calling for the WhatsApp account, also review Calling webhooks because call routing and webhook delivery are separate from messaging thread ownership.
Ask each responsible partner or developer to review the applicable resources and confirm readiness before you enable Meta Business Agent.