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

# Start an outbound voice call

> For connection selection and controlled Studio/API testing, use Make an outbound call. This page focuses on the backend dial request and call-event correlation.

For connection selection and controlled Studio/API testing, use [Make an outbound call](/docs/documentation/deploy/phone/outbound-calling). This page focuses on the backend dial request and call-event correlation. Voiceflow numbers use the API because they have no Studio Test call panel.

## Before you begin

- An assigned Twilio, Vonage, Telnyx or Voiceflow-provisioned number, or a configured SIP connection with outbound enabled.
- Its connection/phone-number ID and a server-side API key authorized for the assigned agent.
- Workspace credits, production concurrency capacity and a test destination you control.

## Place and verify a call

### 1. Choose the correct contract

| Connection | Endpoint | Context and detection |
| --- | --- | --- |
| Connected phone number | [`POST /v1/phone-number/{phoneNumberID}/outbound`](/docs/api-reference/agent-runtime/voice/phone-calls) | String-valued `variables`; provider-specific AMD behavior. |
| SIP trunk | [`POST /v1/sip-connection/{sipConnectionID}/outbound`](/docs/api-reference/agent-runtime/voice/sip/outbound) | Only `to`; no `variables` or `amd` fields. |

Voiceflow-provisioned numbers also support outbound calling. Do not send the phone-number request body to the SIP route.

### 2. Send one dial request

```bash title="Dial through a connected phone number"
curl --fail-with-body --silent --show-error --request POST \
  'https://runtime-api.voiceflow.com/v1/phone-number/YOUR_PHONE_NUMBER_ID/outbound' \
  --header "Authorization: $VF_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{"to":"+14165550123","variables":{"customer_name":"Alex","order_number":"1042"},"amd":false}'
```

Replace the fictional destination with your test number. `amd: false` disables answering-machine detection for this test. A successful phone-number request returns **201**; the SIP operation returns **200**. Both have an empty body, not a call ID.

### 3. Verify the answered call

Answer the phone and complete the task. If a phone-number request included variables, check the agent uses that expected context; SIP calling does not pass request variables. Correlate the call through [call events](/docs/guides/developers/voice/call-events) and its Transcript. HTTP success only means the provider accepted the dial request.

## Verify the result

Confirm the correct destination rang, the intended agent answered, any supported context was used as expected, and the final call outcome appears in your receiver or Transcript.

## Handle rejected or uncertain requests

On **402**, resolve workspace credits; on **429**, wait for concurrency capacity. On a timeout or connection loss after sending, inspect provider/call events before dialing again: an unknown HTTP outcome can still have placed a call. No idempotency guarantee is documented for this operation.
