Nodes
Transfer
Transfer the call to a human, queue, number, SIP URI or Phone Book.
Not available yet. The Transfer node does not appear in the node picker:
without a telephony leg there is no
call_sid to transfer, so the node used to
publish and then fail every time. This page describes the intended behaviour; it
becomes selectable again once call telephony exists. See
Nodes coming soon.The Transfer node (transfer) passes the call to a human destination. Transfers can be cold or warm.
Destination types
| Type | Description |
|---|---|
phone | Phone number in E.164 format. |
sip_uri | SIP URI, e.g.: sip:extension@domain.com. |
phone_book | Entry from a configured Phone Book. |
queue | Queue or team (when supported by the phone system). |
call_transfer | Preconfigured Call Transfer action. |
Transfer modes
| Mode | Description |
|---|---|
cold | Transfers immediately. |
warm_message | Announces the call to the recipient with a fixed message. |
warm_summary | Announces the call with a contextual summary. |
Messages
- Before transfer: what the Agent says before transferring.
- Transfer failed: what is said if the transfer is not successful.
- Unavailable: what is said outside human availability hours.
Human availability
You can define office hours per weekday. Outside those hours, the unavailable message is played.
Validation
- Error if the destination is missing.
- Error if the phone number, SIP URI, Phone Book entry or Call Transfer action is missing according to the selected type.