Handover
Pause and hand the chat to a chat profile, optionally a specific member.
Type
chat.handoverFolder
chatChannels
Chat
Pipe
Value
Scope
Any
Human-in-the-loop
Yes
Handover pauses the run and offers the conversation to a chat profile (any member in the queue, or a specific member). The workflow continues only after a human handles the chat and releases it back.
This type belongs on chat workflows. Attach the same capability as an agent tool when the model should escalate mid-run.
Configure
| Setting | Description |
|---|---|
| Target | Chat profile to hand over to (required) |
| User (optional) | Specific profile member. Disabled until a profile is selected |
Create and staff profiles under Configuration → Chat Profiles. Handover needs members assigned so someone can pick up the work.
Handles
| Handle | Role |
|---|---|
| In (target) | Incoming connection |
| Out (source) | Continues after the human releases the chat |
Pipe schema
The next block reads this on the data pipe (pipe.value).
| Field | Type | Description |
|---|---|---|
handledBy | text | User id of the person who released the chat |
sessionId | text | Session that was handed over |
messages | object | Window of messages during handover |
messages includes:
| Field | Type | Description |
|---|---|---|
start | text | First message id in the window (may be empty) |
end | text | Last message id in the window (may be empty) |
count | number | How many messages were in the window |
Use case
- Escalate billing or exceptions to a human team, then resume automation after they finish.
- Route to a named operator when you already know who should take the chat.