Place one controlled outbound call from a prepared Voice agent through a connected phone number or SIP trunk. The result is an answered conversation you can verify in Voiceflow, not just a successful dial request. For a complete agent-building example, use the pickup-reminder walkthrough.
Before you begin
- A reviewed Voice agent, access to its test Environment and a separate test phone whose recipient expects the call.
- A connected Twilio, Vonage, Telnyx or Voiceflow number assigned to that agent, or an assigned SIP connection with its outbound route configured. Use the relevant Telephony manual for provider prerequisites.
- Workspace credits and production call capacity. A runtime API key authorized for the assigned project’s read/version-read permissions when using the API; Studio testing also needs an administrator able to resolve that key.
For Telnyx, configure its account-owned outbound voice profile before calling. Vonage ignores the generic AMD/overrides fields; use its documented number and application setup. Keep provider-specific configuration with the Twilio, Vonage, Telnyx or Voiceflow manual.
If calls arrive through a forwarded RingEX, Zoom Phone or Teams Phone business line, select the independent Voiceflow caller connection here. The inbound forwarding rule does not authorize that business number as the outbound caller ID. Keep the test recipient separate from the forwarded business entry line.
Make and verify the call
Prepare what the agent will say
Define the business identity, reason for the call, allowed information and when to end or transfer. For a controlled callback, for example, have the agent introduce the business, confirm it reached the intended person, ask whether now is a good time and answer the approved support question. Give it a brief closing for a wrong person or someone who does not want to continue.
Studio
Open the Voice project’s Agent. Review its Global prompt, Instructions and Behaviour → Voice input / Voice output. Use browser Run to check the conversation, then test the actual phone connection in the following steps. Browser Run alone does not verify the carrier route or phone audio.
Code
Read the intended agent/Environment, review its instructions and speech configuration, and compile the test Environment after changes. Keep matching agent variables ready if a phone-number request will pass context. SIP’s calling request has no variables field, so arrange needed context through the agent’s existing tools or data before relying on it.
Confirm the caller connection and release
The saved connection determines the agent, Environment and version. For a controlled Draft test, pin the test Environment and Draft; for customer traffic, publish the reviewed Environment and deliberately select Published. An all-environments route follows Published traffic splitting. Publishing alone does not move a connection pinned to Draft.
Studio
Open Phone numbers and inspect the number or SIP connection. Verify its provider, name and assigned agent. In Environment, select the controlled test release and Save. For SIP, check the outbound destination, credentials where required, transport and Caller ID with the phone-system administrator. An inbound IP allowlist does not supply outbound routing.
Code
For a phone number, retain PHONE_NUMBER_ID from creation. If necessary, list the workspace’s numbers with a management bearer credential and identify the owned caller number. Set WORKSPACE_ID, PROJECT_ID and E.164 CALLER_NUMBER to the intended workspace, Voice project and caller. VF_TOKEN is a management credential with workspace number-list access, separate from VF_API_KEY:
Inspect the matched record’s voice.environmentAlias and voice.version; resolve any incorrect assignment through Connect and route phone numbers before dialing.
For SIP, create/configure and assign the connection in Studio first. Retain SIP_CONNECTION_ID from the connection-specific Outbound call API → View URL, and inspect its saved Environment/version. The ID is not the public number or SIP hostname. The stable phone-number management endpoints do not create or maintain SIP records.
Send one request to a controlled destination
Studio
For Twilio, Vonage, Telnyx or an outbound-enabled SIP connection, open View in Outbound call API. Enter a separate E.164 test phone in Test call, then choose Call once. Studio resolves the project key and compiles before posting the request. Outbound call sent means the request was accepted.
The example shows the SIP Test call panel for the same Northstar phone-support workspace.
A Voiceflow number has no View or Test call panel. Use the page’s Code path with the assigned number’s ID/runtime key, or have your backend implementer send that request while you answer and verify it. BYO PBX extensions also require the API path; Studio’s SIP test input accepts E.164 phones.
Code
Set VF_API_KEY to the assigned project’s runtime API key and TEST_RECIPIENT to a separate E.164 test phone. Keep the key on your backend. Choose the request that matches the caller connection:
Use the Voiceflow resource ID for the connected Twilio, Vonage, Telnyx or Voiceflow number. The initial test uses an empty variables object. For contextual calls, add only string-valued variables the prepared agent expects. amd:false disables answering-machine detection for this initial test. Detection and override behavior remains provider-specific in the phone calling contract.
Voiceflow SIP requires E.164. BYO SIP additionally accepts a one-to-fifteen-digit PBX extension through this API when its peer routes that destination. SIP accepts only to, with no variables, AMD, arbitrary SIP URI or Environment override. See the SIP outbound contract.
The number endpoint returns empty 201; SIP returns empty 200. Neither response supplies a call ID, and neither selects a different agent/release. Send one request and inspect its result before making another attempt.
Answer and inspect the result
Answer the test phone. Confirm the expected business identity, opening, speech in both directions and intended task. If you sent number-request variables, check that the agent uses the expected context without inventing it. Match the call’s time, number and agent with its Transcript and, for a backend workflow, call events.
Run a separate wrong-recipient test only after the first call ends. Confirm the agent closes without disclosing customer information. For customer traffic, publish the approved release, update the connection’s saved assignment deliberately and verify a fresh call.
Verify the result
The separate destination rings, the intended agent conducts the expected conversation, and the matching Transcript/call events show its outcome. An HTTP success or a sent notification is not proof that the recipient answered.
Recover from a rejected or uncertain call
For a rejected request, check the actual provider error, assignment, outbound route, credits and production capacity. 402 indicates a credit problem; 429 indicates unavailable call capacity. Check E.164 formatting and your SIP peer’s permitted destinations where applicable.
If a timeout or connection loss leaves the outcome unknown, inspect provider records/call events before retrying; the first request may already have dialled. Do not assume an idempotency key prevented a duplicate or that an HTTP response returned a call ID. Use Voice troubleshooting for diagnosis.
For ongoing application or CRM triggers, use the backend calling workflow. Scheduling, recipient selection, preferences and retries belong in that owning application; this controlled test and the dial endpoint do not create a campaign scheduler.