Yes—but for a custom WhatsApp Cloud API chatbot, human handoff is generally something you build into the connected application or support workspace. Your system receives WhatsApp messages through webhooks, tracks whether the bot or a person owns each conversation, and routes escalations to an agent. Meta’s API documentation describes messaging, webhooks and connections to agents or bots, but does not establish a universal handoff endpoint or standardized agent-assignment model. (Meta Cloud API overview; webhook subscription documentation.)
Choose how your WhatsApp chatbot will reach a person
The right setup depends on whether you need a simple AI feature in the WhatsApp Business app, custom control over routing, or a shared support-agent workspace.
As an Amazon Associate I earn from qualifying purchases.
| Option | How handoff works | Best fit | Important qualification |
|---|---|---|---|
| Meta Business Agent in the WhatsApp Business app | For eligible accounts, configure the AI agent in the app and manage its replies in individual chats. | Businesses that want an in-app option without building their own Cloud API routing. | Meta says the feature is rolling out gradually to select businesses and countries, and not all languages are supported. Check whether it appears on your account. WhatsApp Help Center |
| Custom Cloud API integration | Your backend or connected service system receives webhook events, maintains conversation state, and assigns escalations to agents. | Teams that need tailored escalation rules or integration with existing business systems. | Meta documents API and webhook capabilities, but the reviewed documentation does not define a universal handoff endpoint or assignment model. Cloud API overview; webhook subscriptions |
| Integrated support workspace | Agents handle WhatsApp conversations in a customer-service representative experience. | Teams already evaluating a support platform with WhatsApp channel support. | Microsoft documents WhatsApp as a channel in Dynamics 365 Customer Service. Confirm current licensing, regional availability, setup requirements and handoff behavior for your needs. Microsoft Learn |
Build a reliable handoff flow
For a custom integration, treat handoff as an ownership change in your application—not simply a message saying that an agent will join. The system should prevent the bot and agent from answering at the same time.
- Define escalation triggers. Offer a clear way to request a person. Also consider escalating when the bot cannot answer from approved business information, clarification attempts repeatedly fail, the customer expresses distress or dissatisfaction, or the request needs human judgment. These are configurable business rules, not Meta-mandated triggers. A Webex industry guide also identifies failed automation and high-priority queries as reasons to hand over.
- Switch conversation ownership before notifying the customer. Set a durable state such as “queued” or “human-owned,” then suppress AI replies for that conversation. Resume automation only when an agent closes the case or deliberately returns it to the bot.
- Send useful context to the agent. Include the recent conversation, why it escalated, what the bot already tried, and only the verified customer or order details needed to address the request. Apply your privacy and retention rules; avoid exposing unrelated sensitive information.
- Tell the customer what happens next. Confirm that a person has been requested and give a response timeframe or channel when known. If no agent is available, acknowledge the request and explain the next step rather than leaving the chat without a response.
- Account for the messaging window. Microsoft’s WhatsApp channel documentation describes a 24-hour customer-service session window and says an error appears when trying to message after that period expires. Before enabling later follow-ups, verify the current Meta policy and any approved-template requirements. Microsoft Learn
- Test exceptions as well as the happy path. Verify explicit requests for a person, low-confidence answers, agent unavailability, reassignment, duplicate webhook delivery, bot pause and resume, and an agent reply after the service window. These are recommended acceptance checks for the routing design, not reported test results.
Prepare the Cloud API connection
Meta’s Cloud API getting-started material lists a Meta business portfolio, a WhatsApp Business Account (WABA), and a business phone number as required assets. Registration guidance says to verify ownership of the phone number and set up two-step verification. The API collection also describes subscribing the application to the WABA so webhook events reach the configured endpoint. Cloud API getting started; phone-number registration.
#1 Best Overall
Plan credential handling as part of deployment. The API collection says user access tokens expire after 24 hours; system-user tokens may last up to 60 days or permanently depending on setup. Choose and secure credentials according to Meta’s current guidance rather than assuming a token will remain valid indefinitely.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Decide between custom routing and a support workspace
Compare the options on the work they require, not just whether they can send and receive WhatsApp messages.
Quick Recap
- Control: A custom integration lets your application define escalation triggers and routing, but your team must implement and maintain that logic.
- Operational effort: Custom routing requires webhook handling, conversation-state management and agent assignment. An integrated workspace may provide a representative experience, but confirm precisely what its current setup includes.
- Agent context: Check whether agents can see the relevant conversation history and business details without switching between systems.
- Eligibility and terms: Confirm account and regional availability, licensing, and any language or setup restrictions directly with the relevant vendor before committing.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
