Routing and human handoffs
Control which integration handles each conversation.
Routes connect customer-defined conditions to customer-owned integration endpoints. They do not run a hosted model or choose a business's takeover policy on its behalf.
Routing inputs
Use project, phone number, optional outlet group, labels and explicit conversation assignment. Evaluate ordered rules deterministically and keep the winning rule visible in event diagnostics.
Multiple agents
Give each agent only the projects, numbers and operations it needs. Route sales to one endpoint and support to another, or let a customer-owned orchestrator make that choice. Share conversation context through your own application rather than exposing another organization's messages.
Explicit handoff
Assign a conversation, pause automation, resume automation or transfer it through the inbox, API or MCP. An agent should respect the latest assignment before it sends. A human's reply does not imply a universal takeover rule; configure the behavior required by the business.
Provider-app ownership
Internal assignment and Meta thread control are different. An assignment to an internal agent does not grant permission to respond when another provider application owns the Meta thread. Passive events remain passive until the upstream control rules permit a response.
Failure behavior
Failed endpoint deliveries are retried and then exposed for replay or operator action. A route must not silently fall back to another customer's endpoint. Loop prevention uses event provenance and stable IDs, not assumptions about message text.