Question
How can a blind transfer be executed with Twilio Studio?
Product
Studio
Answer
A blind transfer (also known as an unattended transfer) redirects an active caller directly to a new recipient—such as a specific phone number, SIP endpoint, or agent—without an intermediate agent speaking to the recipient first. In Twilio Studio, blind transfers are handled using the Connect Call To widget.
1. Executing the Blind Transfer
To execute a blind transfer, drag a Connect Call To widget onto your canvas and link it to the appropriate step in your Flow (e.g., after an incoming call or an IVR menu prompt).
Depending on your architecture, you can configure the transfer target using one of the following options:
Single Number: Forwards the call directly to a external standard phone number in E.164 format (e.g.,
+1234567890).Multiple Numbers (Simulring): Dials up to 10 numbers simultaneously; the first party to answer gets the call.
Client User: Connects the call to a specific Twilio Client identity (e.g., a WebRTC browser agent).
SIP Endpoint: Forwards the call to an external SIP URI or Twilio Programmable Voice SIP Domain.
Conference: Instantly drops the caller into a specified Conference SID.
2. Tracking and Logging the Transfer
If you're looking to track that a blind transfer has been performed, you must trigger tracking mechanisms before or during the transition phase.
To log that a blind transfer was initiated or completed:
Log Before Transferring: Insert a Make HTTP Request widget immediately before the Connect Call To widget. Send the Call SID and transfer target payload to your web server or CRM to log the intent.
-
Track Outcomes via Transitions: Attach a Make HTTP Request widget to the specific transition output nodes of your Connect Call To widget:
Call Connected / Ended: Fires when the transfer successfully connects and finishes.
Busy / No Answer / Failed: Fires if the destination endpoint fails to connect.