> ## 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 agent from Studio

> For a headless release, use Release a voice integration. Place a call through the production route and confirm the published candidate answered.

For a headless release, use [Release a voice integration](/docs/guides/developers/voice/go-live).

## Before you begin

- A candidate Environment cloned from Main.
- A non-customer phone number assigned to its Draft.
- Defined success cases, failure cases and the prior published version.

## Validate and release

### 1. Run conversation checks

Run saved **Tests** and **Simulations** for your instructions, tools and handoff conditions. Include missing customer details and a failed tool response. These checks cover conversation behavior; they do not prove carrier routing or audio quality.

### 2. Test the actual phone path

Call the draft over each connection you will deploy. Verify two-way audio, speech pauses, interruption, languages, keypad entry, silence and duration limits. For human handoff, exercise the actual destination and confirm a human receives the call. [SIP transfer requirements](/docs/api-reference/agent-runtime/voice/sip/transfers) apply when a PBX owns the call.

### 3. Publish the candidate

Open **Environments** and publish the candidate. Point the test number at its **Published** version and repeat the call. A number pinned to an Environment bypasses traffic splitting.

Environments list with release and traffic controls — Publish the candidate before routing production calls.

### 4. Route and review customer calls

For split-routed numbers, assign a small traffic share to the published candidate. Inspect **Transcripts**, recordings and **Analytics** for that Environment. For a number explicitly assigned to an Environment, update that assignment instead.

## Verify the release

Place a call through the production route and confirm the published candidate answered. Verify a completed task and the human-transfer path, then inspect the matching Transcript.

## Recover a release

If the candidate fails, route new calls back to the prior published Environment or restore the prior version. Traffic changes apply to new sessions; existing sessions retain their selected Environment. See [traffic splitting](/docs/documentation/deploy/environments/traffic-split).
