Chapter 5 — BlockFlow · Node Reference

5.2.7 Transfer node

Hands the conversation over to a human agent or another destination outside the automated flow. It is the controlled exit used when a request cannot be resolved automatically, when the user asks for a person, or when policy requires human handling.

The Transfer node in the BlockFlow designer.

• Destination — the VDN number, extension or queue the call or conversation is transferred to. The project-level redirect destination is configured under Project settings and can be overridden on the node.
• Transfer message — the message played or displayed before the handover, so the user knows they are being redirected.
• Context handover — variables collected so far and the conversation transcript are passed on, so the receiving agent does not start from nothing.
• Conditional transfer — typically connected to a fallback branch, a repeated-failure condition or an explicit user request, evaluated by a preceding logic node.
• Flow termination — once the transfer is initiated the automated scenario stops processing further nodes.

Typical uses: escalation after an unrecognised request, routing a complaint to a specialised queue, handing a caller to sales or support, and fallback during maintenance mode.