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

# Outbound calls

> For the shared number/SIP workflow, use Make an outbound call. This worked example builds a pickup-reminder agent from scratch.

For the shared number/SIP workflow, use [Make an outbound call](/docs/documentation/deploy/phone/outbound-calling). This worked example builds a pickup-reminder agent from scratch.

Set up a pickup-reminder agent for the fictional Northstar Supply store, then make one test call from an imported number. The practice recipient has agreed to receive the call. Use a destination you control before connecting a customer-calling workflow.

For calls triggered by your backend or CRM, use [Start an outbound call](/docs/guides/developers/voice/outbound-calls). This guide prepares and verifies the agent in Studio.

## Before you begin

- A Voice project you can edit and workspace access to manage phone numbers. The Studio test action needs access to the project’s API key; use an authorized administrator.
- A voice-capable Twilio test number, its Account SID and Auth token, plus a separate test phone you can answer. Use a number that is not serving customers.
- [Credits for calls](/docs/documentation/account-management/billing/credits-pricing-table) and available call capacity.

**Warning:** Importing a number changes its call handling. Clicking Call places a real, billable call to the entered destination. Confirm the number and the recipient before testing.

## Prepare and place the call

### 1. Create the reminder agent

From **Projects → New project**, create a **Voice** project named **Northstar Pickup Reminder** and choose **Start from scratch**. Open **Agent**, with **Main** selected.

In **Global prompt**, enter:

#### Reminder role

```markdown
# Role
You are Northstar Supply’s automated pickup-reminder assistant. You are calling a test recipient who agreed to receive this reminder.

# Speaking style
Identify the business and reason for calling. Speak briefly and ask one question at a time.

# Boundaries
Do not disclose private order details, invent availability or promise an action. For a wrong number, apologize and give no order information.
```

In **Instructions**, enter:

#### Reminder instructions

```markdown
Say: “Hello, this is Northstar Supply’s automated pickup reminder. Is now a good time?”

If the recipient wants the reminder, explain that this practice order is ready for pickup today from 10 am to 6 pm. Ask if they need the collection instructions.

If they are not the intended recipient or do not want the call, apologize and give a brief closing. Do not continue the reminder or claim to update a calling preference in another system.
```

Pickup-reminder instructions in the Northstar Voice agent — Define the opening, reminder and wrong-recipient behavior before dialing.

### 2. Choose the speech settings

Open **Behaviour → Voice output** and choose a voice. Set the recognizer and language in **Voice input** for your test recipient. See [Voice configuration](/docs/documentation/build/voice) for the speech controls.

### 3. Connect the test number

Open **Phone numbers → Create number → Twilio**. Enter the test number, Account SID and Auth token, then complete the import and assign it to this agent. In the number’s **Environment** setting, choose **Main**, **Draft**, then **Save**. This makes the test exercise the draft you are editing.

Use an assigned Twilio, Vonage or Telnyx number for Studio outbound testing. Voiceflow-provisioned numbers support API calling but have no Studio Test call panel. [Connect a phone number](/docs/documentation/deploy/phone/connect-a-phone-number) covers the provider setup.

### 4. Open the outbound test

In **Phone numbers**, click **View** in the number’s **Outbound call API** column. In **Test call**, enter your separate test phone in international format, including its country code. Do not use the fictional number pictured below.

Native Outbound call API dialog with a separate test destination and Call button — Enter a separate phone you control in Test call before choosing Call.

The generated cURL is for server-side use. It is not code to put in a public website; use the [developer guide](/docs/guides/developers/voice/outbound-calls) when wiring a trigger.

### 5. Answer and verify the conversation

Click **Call** and answer the test phone. Confirm that the agent identifies Northstar Supply, asks whether now is a good time, then gives the practice pickup reminder.

Make a second test only after the first has ended. Say you are the wrong person: the agent should apologize and give no order information. A request being accepted or the **Outbound call sent** notification does not prove the destination answered.

After each call, find its time and number in **Transcripts**. Check the exchange against what you heard. If an attempt’s result is uncertain, inspect it before dialing again.

### 6. Prepare the published calling workflow

Replace the practice reminder with approved business content. Test it, **Publish** the Main draft and change the number’s assignment to **Main → Published → Save**.

Place a new test call and verify that the published agent gives the approved reminder. For scheduled or event-triggered calls, connect the server-side [outbound calling guide](/docs/guides/developers/voice/outbound-calls). Keep the calling audience, timing, retry policy and customer preferences in that owning system; this Studio test does not create a campaign or scheduler.

## Verify the result

- Your test phone receives the call from the intended number.
- The agent gives the expected reminder and handles a wrong recipient without disclosing order information.
- The conversation appears in the expected Environment’s Transcripts.
- A fresh test after publishing uses the released instructions.

### The call does not connect

Check the number, provider response and call capacity before retrying.

Confirm the destination’s country code, the number’s provider connection and its assignment to this agent. Check workspace credits and the specific error returned. An accepted request and an answered call are separate results. Use [Voice troubleshooting](/docs/api-reference/agent-runtime/voice/troubleshooting) for connection diagnostics.
