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

# Inbound calls

> Launch an inbound phone agent for Northstar Supply, a fictional retailer. It will answer shipping and returns questions from an approved policy and transfer callers to…

Launch an inbound phone agent for Northstar Supply, a fictional retailer. It will answer shipping and returns questions from an approved policy and transfer callers to your support team when they need a person or an order-specific action. Start with a test number, verify the actual phone experience, then route customer calls to the published agent.

For an existing PBX or contact centre, [Connect with SIP](/docs/documentation/deploy/phone/connect-with-sip) covers that connection. This walkthrough uses an imported Twilio number.

## Before you begin

- Voiceflow access to create a project and manage phone numbers.
- A Twilio account with a voice-capable test number, its **Account SID** and **Auth token**. Choose a number that does not currently serve customers; importing it changes its call handling.
- A separate support-team phone number that someone can answer during the test. Do not forward the agent back to its own number.
- Approved support policies, a test phone and [credits for calls](/docs/documentation/account-management/billing/credits-pricing-table).

## Build the phone support agent

### 1. Create a Voice project

From **Projects**, click **New project**. Name it **Northstar Phone Support**, choose **Voice**, then **Start from scratch**. Open **Agent** and keep **Main** selected.

### 2. Import the support policy

Open **Knowledge base → Add data source → Plain text**, enter your approved support policy and click **Import**. For practice, use these fictional rules:

- Standard delivery takes **3–5 business days after dispatch**, within Canada.
- Unused items in their original packaging can be returned within **30 days of delivery**.
- A person must handle order lookups, replacement decisions and refunds.

Wait for processing to finish. Return to **Agent** and enable **Knowledge base** under **System tools**.

### 3. Define the phone conversation

In **Global prompt**, enter:

#### Phone agent role

```markdown
You are Northstar Supply’s phone support assistant. Answer shipping and returns questions using the Knowledge base.

Use short, natural replies and ask one question at a time. Do not read formatting or links aloud.

Do not invent order status, approve a refund or promise a response time. If the caller asks for a person or needs an order-specific action, use Call forward.
```

In **Instructions**, enter:

#### Phone support instructions

```markdown
Greet callers: ‘Thanks for calling Northstar Supply. I’m the automated assistant. How can I help?’

Search the Knowledge base before answering shipping or returns questions. State the applicable conditions briefly.

If the caller asks for a person, requests an order lookup or needs an action you cannot perform, say you will connect them to support and use Call forward. Do not claim a transfer has succeeded before the call is forwarded.
```

### 4. Choose speech settings

Open **Behaviour → Voice output → Voice** and choose the voice callers will hear. In **Voice input**, select the recognizer and language for your callers. Use [Voice configuration](/docs/documentation/build/voice) for the exact speech and turn-taking controls.

Voice output controls for Northstar Phone Support — Choose the voice for your support line in Behaviour.

Keep call recording off for this walkthrough. [Review voice calls](/docs/guides/studio/voice/review-calls) covers recording controls.

### 5. Configure the human transfer

Under **System tools**, turn on **Call forward**, then open its settings. Keep **Phone number** selected and enter the support-team destination with its country code. Use a real destination you control; the screenshot’s number is fictional.

In **Trigger**, describe the condition: “Forward the caller to the support team when they ask for a person or need an order lookup or an action that this agent cannot perform.”

Call forward settings with a support destination in the Northstar phone agent — Set the support destination before testing a human transfer.

This is a direct transfer, not a warm handoff with a private briefing. It does not provide a busy/no-answer recovery branch. Arrange for the destination to be answered during testing. See [Call forward](/docs/documentation/build/steps/call-forward#configuration) for extensions and caller-ID behavior.

## Connect and test the support line

### 1. Import the test phone number

Open **Phone numbers → Create number** and select **Twilio**. Enter the **Twilio phone number**, **Twilio account SID** and **Twilio auth token**; give it a recognizable name such as **Support test line**. Complete the import and confirm it is assigned to this agent.

Importing a number changes where its calls are handled. Use a dedicated test number and keep the existing customer support line unchanged during setup. [Phone-number setup](/docs/documentation/deploy/phone/connect-a-phone-number#adding-a-phone-number) covers other supported providers.

### 2. Point test calls at the draft

Open the number’s **Environment** setting. Select **Main**, choose **Draft** under **Version** and click **Save**. The explicit assignment makes this number answer with the draft you are changing, rather than using the agent’s traffic split.

Update environment dialog with Main and Draft selected — Choose Main and Draft for the isolated test number, then save the assignment.

Keep this number private to your test team while it points at Draft.

### 3. Call and check policy answers

Dial the imported number from your test phone. Use the actual inbound call, rather than the prototype **Call** button, for transfer acceptance.

- Ask “How long does standard delivery take?” Check that the reply preserves **after dispatch** and the Canada-only scope.
- Ask “Can I return an unused item after 20 days?” Check that the reply includes the original-packaging requirement and 30 days from delivery.
- Interrupt a reply and speak again. Confirm the agent hears your next request and the voice is intelligible.

After hanging up, open **Transcripts** and locate the call by time and caller. Compare the recorded exchange with what you heard. A text Run test cannot establish audio quality.

### 4. Verify the human transfer

Call again and say “I need to speak to a person about my order.” Have a teammate answer the configured support number. Confirm it rings, both people can hear each other and the agent stops speaking after transfer.

A transfer event alone does not prove a person answered. If the call fails, inspect the destination and provider result before trying again. [Transfer troubleshooting](/docs/guides/studio/voice/transfer-calls#if-transfer-fails) covers the handoff boundary.

## Launch the published support line

Replace the fictional policy and business details with approved information. Click **Publish**, review the Main release and confirm publication. For the phone number that will serve customers, change **Environment → Main → Published** and **Save**. This changes which version answers new calls.

Place a new inbound call and repeat a policy question and human transfer. Confirm the published agent answers and the support team receives the caller. Only then update your website or call-centre routing to direct customers to that number.

Use [Review voice calls](/docs/guides/studio/voice/review-calls) for ongoing Transcript, recording and Evaluation checks. For a custom application instead of phone-number setup, start with [Voice agents](/docs/api-reference/agent-runtime/voice).
