Transfer Configuration Pieces
Transfer behavior can be defined at flow node or version level.| Piece | Purpose |
|---|---|
| Transfer destinations | Numbers the agent can attempt to reach. Flow setups can use a dynamic variable for destinations. |
| Representative brief | Context the agent should provide before bridging the caller. |
| Hunt mode | Parallel or priority style selection where configured. |
| Sequential delay | Delay between attempts when using ordered destinations. |
| Hunt timeout | Total time allowed for finding an available destination. |
| Customer bridge timeout | How long the caller waits while the bridge is created. |
| Post-merge speech timeout | Validation window after merge to ensure the representative speaks. |
Transfer Evidence In Call History
The transfer tab explains what happened after the agent tried to hand off.Transfer sessions
Shows transfer id, status, timing, and high-level result.
Leg details
Shows each attempted destination and answer timing.
Status descriptions
Explains outcomes such as connected, no answer, rejected, hunt timeout, bridge failed, or customer disconnected.
Original transcript
Shows why the agent decided to transfer.
Test A Transfer Path
Test reachable and unreachable destinations
A transfer only tested with a perfect answer is not tested.
Related Reading
Conversational Flow Agents
Use transfer nodes.
Default Variables
Set transfer destination defaults.
Transfer Review
Inspect transfer evidence.