> ## 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.

# Release a voice integration

> For an interface-based release, use Release a voice agent from Studio. The new session resolves to the candidate’s published version, its audio and transfer paths work…

For an interface-based release, use [Release a voice agent from Studio](/docs/guides/studio/voice/go-live).

## Before you begin

- A tested candidate Environment and API key with publish/edit access.
- Its project ID and Environment ID or alias.
- A test phone/client and the previous published version or Environment.

## Publish and verify the integration

### 1. Verify the candidate over its actual transport

Run saved conversation tests, then test audio, interruption, keypad and transfer behavior through the actual provider or Socket.IO client. Test failure responses and disconnect cleanup. The transport checks remain necessary even when every scripted Test passes.

### 2. Publish through the Environment API

Use [Publish environment](/docs/api-reference/environmentpublicapi/publish-environment) for the candidate. Keep the publish operation in your backend. Read the Environment afterward and confirm its published version rather than treating an accepted request as proof that your client selected it.

### 3. Select the published route

For Socket.IO, send the candidate Environment choice during `client.start` on a **new** session. A saved session key resumes the previous conversation. For managed phone calls, verify the number/connection’s assigned Environment and Published version; explicit assignments bypass the traffic split.

### 4. Verify and observe production

Place a call through the production connection, complete a task, exercise its human-transfer destination and inspect the resulting events and Transcript. Track the same Environment and period in Analytics. Keep a known-good route available while comparing the candidate.

## Verify the release

The new session resolves to the candidate’s published version, its audio and transfer paths work, and the expected call/session artifacts are present.

## Recover a release

Route new sessions to the prior published Environment, or restore the prior version through your release process. Do not silently resume an uncertain in-flight action after a disconnect; inspect its effects before retrying.
