In Workflows, tool nodes support result-based routing. Configure the Transfer to number node, then draw its Failure edge to the node you want as the fallback (e.g., back to a Subagent node or an End node). This Failure path is taken when the tool execution fails. (elevenlabs.io)
The Transfer to number feature itself is provided by the transfer_to_number system tool; set up the target number(s) there as usual. (elevenlabs.io)
If you also need server-side automation specifically when the destination doesn’t pick up, enable Post‑call Webhooks and handle call_initiation_failure events with failure_reason "no-answer". (elevenlabs.io)
Where to click:
Add a Transfer to number node in your workflow and configure its transfer rules/number. (elevenlabs.io)
From that node, add two outgoing edges:
Success → wherever you want the flow to proceed after a successful handoff.
Failure → your fallback branch (e.g., a Subagent node that informs the caller and collects details, or an End node). The Workflows doc describes tool-node Success/Failure routing. (elevenlabs.io)
(Optional) Turn on Post‑call Webhooks to catch "no-answer" programmatically for external actions (CRM note, re-dial queue, etc.). (elevenlabs.io)
noble folio
median whale