Overview
Once a phone number is connected to your project, incoming calls are automatically routed to your agent. The same applies to calls your own phone system sends to a SIP connection.
How it works
When someone calls your connected phone number, Voiceflow routes the call based on how the number is configured:
When someone calls your connected phone number, Voiceflow routes the call based on how the number is configured:
- Assigned to an environment: every call goes to that environment, using either its Published (live) version or its Draft, depending on which you picked when assigning.
- No fixed Environment: the number remains assigned to its Voice agent, and calls follow the Published traffic split configured in Settings → Environments, just like chat sessions and API conversations.
To change a number’s assignment, click the environment label next to the number in the Phone numbers tab. See Routing calls to an environment for the full flow.

Caller identification
When a call comes in, the caller’s phone number is automatically set as the user_id variable.
When a call comes in, the caller’s phone number is automatically set as the user_id variable. The caller number is separate from the runtime identity used to retain variables. In Behaviour → Session & timeout, Remember callers across calls selects phone-number identity or a new identity per call. See Returning callers. A presented phone number does not authenticate a customer.
For calls that arrive over a SIP connection, the runtime uses the original caller identity forwarded by the SIP proxy, reduced to the SIP address’s user part. Withheld or anonymous callers receive a unique anonymous- ID per call. See Caller identity and context.
Testing draft changes by phone
While you’re working on a change, point a non-production phone number at the environment’s draft version.
While you’re working on a change, point a non-production phone number at the environment’s draft version. Calls to that number use your unpublished work, so you can dial in and verify the change yourself before publishing. A phone number that real callers use should never be pointed at a draft.
Testing changes with real callers
When you want to validate a change against Main using real call data, use a traffic split.
When you want to validate a change against Main using real call data, use a traffic split. Clone Main, make and publish your change in the new environment, then route a small percentage of phone traffic to it. Compare the results in Analytics and Transcripts, and once you’re confident, merge the environment back into Main.