Automations
Trigger handoff automatically with the Pause Replies action.
Every project runs an AI Agent that answers inbound WhatsApp messages automatically with your automations and replies. Handoff is how a human takes over a single conversation: while handoff is on, automated systems are paused for that contact and your team owns the replies.
A conversation is always in one of two states:
| State | Who replies |
|---|---|
| AI Agent (default) | Automations, external webhooks, and public API outbound sends can run. |
| Handoff on | Automations, external webhooks, and public API outbound sends are paused. A teammate handles the conversation in the inbox. |
Handoff is per-conversation — turning it on for one contact never affects the rest of your inbox.
When handoff is on for a conversation, Wabery will not:
POST /v1/messages; the API returns
409 ai_handoff_active instead.Manual teammate replies from the dashboard inbox still work. Handoff stays active until someone turns it off, so a human conversation is never taken back by an automation mid-reply.
Handoff turns on automatically when either happens:
/inbox). Sending a manual message
means a human is now handling the thread, so the AI Agent steps back.refund → Pause
Replies, so a teammate takes over.A teammate can also flip it on directly from the Handoff toggle in the conversation’s details panel.
Open the conversation in the inbox and switch Handoff off (or use Turn off handoff in the conversation banner). The AI Agent resumes and answers new inbound messages again.
Handoff stays on until someone turns it off — there is no automatic timeout, so a conversation a human picked up is never taken back mid-reply.
Automations
Trigger handoff automatically with the Pause Replies action.
Conversations & history
Pull thread history to give a teammate context before they reply.