For headless configuration, use Configure call transfers through the API. A browser microphone session is not a phone call and cannot be transferred by Socket.IO alone.
Before you begin
- A phone agent, test number or SIP connection, and project edit access.
- A destination your support team can answer.
- For SIP-address destinations, a phone system that accepts the required REFER transfer.
Configure and verify the handoff
Choose the handoff condition
Decide when the agent should transfer: for example, when the customer asks for a person or an order exception requires a support specialist. Keep that condition in the agent or Playbook instructions.
Configure the transfer
In a Workflow, add Call forward and connect it to the handoff branch. Set the destination phone number or SIP address. For agent-directed transfers, enable Call forward in the agent’s system tools and configure its destination and usage description.

An extension and caller-ID passthrough depend on the connection provider. Review the Call forward settings before relying on them.
Test over the actual call connection
Call the test number and trigger the handoff condition. Confirm the destination rings and your support team receives the call. Test SIP transfers through the actual PBX: it must accept SIP REFER. A prototype run cannot verify telephony transfer.
Verify the result
Confirm the customer reaches the intended destination and the agent stops speaking after transfer. Transfer acceptance does not prove a human answered. This workflow does not provide a warm-transfer briefing or a busy/no-answer recovery branch.
If transfer fails
For a failed transfer, inspect the provider result or call end reason. A rejected SIP transfer ends the call; use SIP transfer troubleshooting to check REFER acceptance and the destination.