> ## Documentation Index
> Fetch the complete documentation index at: https://www.voiceflow.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrate your contact center

> Connect an existing contact-center customer journey to a Voiceflow agent without replacing your customer-facing phone number or staff workspace.

Connect an existing contact-center customer journey to a Voiceflow agent without replacing your customer-facing phone number or staff workspace. Use a test route first, then keep your current route available while you validate the integration.

## Before you begin

- A contact-center administrator who can change a test call flow or customer messaging route.
- A working Voiceflow agent and a non-production [Environment](/docs/documentation/deploy/environments) with permission to publish. Building the agent is a separate task.
- A staffed destination for human support, and a test customer record containing only information you permit the receiving system to use.
- For Code, a server-side [API credential](/docs/api-reference/authentication) and [project ID](/docs/api-reference/project/get-project), plus the test Environment alias.

## Connect the customer journey

### 1. Choose the customer route

Keep the existing public number or chat entry point. Your administrator changes the contact center's internal routing, not the number customers already know.

- **Phone:** route a test branch to a Voiceflow number or SIP connection. Use a separate destination to transfer callers back to the contact center; pointing both directions at the same entry route can create a loop.
- **Chat:** use the Voiceflow widget, or connect your own interface through [Chat agents](/docs/api-reference/agent-runtime/chat). A contact-center inbox alone does not deliver Voiceflow responses to a customer.
- **Staff assistance:** leave the human in the customer conversation and follow [Integrate agent assist](/docs/guides/integrations/contact-centers/agent-assist) instead.

Confirm that your provider supports the chosen route and that your account can configure it. Provider-specific SIP settings and routing belong in that provider's Integration manual; a Chat Handoff connector does not establish a phone connection.

### 2. Assign the test agent and Environment

#### Studio

Open [Agent studio](https://creator.voiceflow.com) and select your project. In **Phone numbers**, open the test number's Environment assignment and select the Environment and version to exercise. The capture shows **Main → Draft** for testing; select **Published** when validating the released version.

Phone number Environment assignment with Main and Draft selected — Assign the test line to the intended Environment and version before calling it.

For a SIP route, create and assign the connection using [Connect with SIP](/docs/documentation/deploy/phone/connect-with-sip). For Chat, install the [Chat widget](/docs/documentation/deploy/widget/embedding-the-chat-widget) on your test page and check which project and Environment it targets.

#### Developer

For phone calls, complete [SIP connection setup](/docs/api-reference/agent-runtime/voice/sip/settings) and assign the intended agent, Environment and version. Your contact-center administrator must route the test call flow to that connection. Retain the previous routing configuration; the API cannot configure the provider's call flow for you.

For a custom Chat interface, create a session for the test Environment on your server:

```bash title="Start a test customer session"
curl --fail-with-body --silent --show-error --request POST \
  "https://general-runtime.voiceflow.com/v4/project/$VF_PROJECT_ID/environment/$VF_ENVIRONMENT_ALIAS/session" \
  --header "Authorization: $VF_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{"userID":"contact-center-test-customer-001"}'
```

Save the returned `sessionKey` for this customer conversation. Send `launch`, then customer `text` actions through [HTTP Streaming](/docs/api-reference/v4interact/interact-non-stream#streaming-action), and render the [returned traces](/docs/api-reference/agent-runtime/chat/responses). Keep the project credential on your server. A new session with the same user ID ends the previous one, so allocate a different ID to an independent test customer.

### 3. Map identity and routing context

Agree on the minimum data crossing each boundary: customer identity, reason for contact and receiving team. Use a fictional case such as `CC-1042` and a test queue, rather than real customer information.

- **Phone:** map only the supported [SIP context headers](/docs/api-reference/agent-runtime/voice/sip/settings) or caller information your connection actually supplies. The receiving system must interpret those fields.
- **Chat:** populate customer variables before the [Handoff step](/docs/documentation/build/steps/handoff), then select Full transcript, a prepared Custom summary, or None. A queue field is not proof that the provider routed to that queue.
- **Staff workspace:** use its authenticated backend to load the current case. Never treat a browser-supplied customer ID as permission to read that customer's records.

Write down the sender, receiver and expected value for each mapped field. This becomes the integration acceptance check.

### 4. Connect the human route and make one test contact

Follow [Set up AI-to-human handoff](/docs/guides/integrations/contact-centers/transfer-calls) for the chosen channel. Make one contact through the actual test entry point and have a teammate answer. Confirm the intended AI answers first, the customer reaches the intended human team, and the mapped test context arrives.

Keep the test branch isolated if any of those checks fail. Complete [Test and launch your integration](/docs/guides/integrations/contact-centers/test-connection) before changing your main customer route.

## Completion check

You have a named test entry point, a known Voiceflow Environment/version, a separate human destination, and one successful customer contact through that route. Record those values with your field mapping and the previous provider route. A saved connection alone does not complete this guide.
