Build with

Send a customer from a Voiceflow agent to the right contact-center team, with the context that team needs. Phone calls use Call forward; Chat uses a Handoff step and a live-message connection. Configure and validate them separately.

Before you begin

  • A working test entry point from Integrate your contact center, a non-production Environment and a staffed receiving destination.
  • For Phone, a transfer number or SIP destination supplied by your contact-center administrator. Keep it separate from the number or route that sends calls into Voiceflow.
  • For Chat, a connected Genesys, UJET or Dixa messaging integration, or a deployed Custom Handoff service. Obtain the actual receiving queue/menu and test customer identity before configuring the step.
  • For Code, the project ID, Environment alias and server-side API credential. Retain the current agent and Workflow configuration before changing them.

Set up the human route

1

Choose when to hand off and what to send

Use a clear condition such as a customer asking for a person or needing an exception the AI cannot approve. Choose the receiving team and minimum useful context: the customer’s verified identity, reason for contact and unresolved task.

For Chat, prepare a summary string before Handoff or choose Full transcript or None explicitly. For SIP, agree which transfer context headers the receiver accepts and how it maps them. Context delivery does not establish a live customer-message connection.

2

Configure the channel's transfer

Studio

Open Agent studio, select the project and test Environment, then open Agent → System tools → Call forward. Enable it, select Phone number or SIP, enter the staffed test destination and describe when the agent should transfer.

Set the human destination and the condition that should select Call forward. Photo:

Use a Workflow Call forward step instead when a fixed branch should make the transfer decision.

Code

Read the agent with Get agent and retain its current callForwardTool. Update only that tool in the test Environment:

Set a staffed phone destination

Replace the example number with your staffed test destination. For SIP, set addressType to "sip" and use your administrator’s destination in address; see destination formats. Read the agent back, then compile the test Environment. Confirm the phone connection targets that Environment and version.

A custom telephony client must implement the call-forward trace. An audio-only browser session has no provider call to transfer.

3

Verify the receiving side

Make a test contact through the actual customer entry point and trigger the human route. Have a teammate answer the designated queue or number. Verify the customer identity and permitted context in that workspace, then exchange speech or public messages in both directions.

For Genesys, the integration sends a queue-name attribute that your provider routing flow must interpret; Queue ID is used for the wait estimate. For Dixa, creation can succeed even when the requested queue transfer fails. In both cases, check the receiving team rather than treating conversation creation as successful routing.

Complete the failure, closure and release checks in Test and launch your integration.

Completion check

The customer reaches the intended human team once, the agreed context arrives, and the AI stops contributing while the human handles the conversation. For Chat, verify closure in the same customer session. For Phone, verify an answered call, not just an accepted transfer request.

Phone transfer boundaries

This Call forward path does not provide a warm-transfer briefing or an automatic busy/no-answer recovery branch. A rejected transfer can end the call. Staff the test destination and inspect SIP transfer results before releasing the route.

Use the up and down arrow keys to select a result, Enter to open it, and Escape to close the search.