Handoff node
Stop automated execution and mark the workflow as waiting for a person.
Move WhatsApp conversations from automation to a person with Handoff nodes, inbox assignment, conversation history, workflow status, and real-time updates.
Good WhatsApp automation knows when to stop, preserve context, and make a human responsible.
Stop automated execution and mark the workflow as waiting for a person.
Give the human the WhatsApp thread and the context that led to escalation.
Make ownership explicit so the next response belongs to a person or team.
Notify external systems when workflow.execution.handoff happens.
Keep handoff, failed, and active states visible to operations.
Prevent more automated processing while the conversation is human-owned.
Keep escalation deterministic enough for operations and flexible enough for real conversations.
A customer asks, confidence drops, or business rules require review.
The workflow stops automation and marks the conversation for a human.
Inbox and webhooks route the conversation to the right team.
The human sees the thread, status, and workflow history before replying.
The goal is not to automate every conversation. Resolve the easy parts and move sensitive moments to a person quickly.
Use the inbox mode that matches where your team works.
For teams that need dashboard access and full project operations.
For support agents focused only on live WhatsApp conversations.
For products that need human takeover inside their own app.
Build WhatsApp agents and workflows that know when a human should take over.