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

# Telephony

> Connect customer calls through a Voiceflow number, Voiceflow's hosted SIP endpoint or your existing phone provider.

Connect customer calls through a Voiceflow number, Voiceflow's hosted SIP endpoint or your existing phone provider. Keep a RingEX, Zoom Phone or Teams Phone user number with its provider and forward calls to an independently configured Voiceflow number. Use a Voice agent for calls, a Chat agent for an SMS conversation, or a messaging tool for a specific text follow-up. Each path has its own connection and verification.

In [Agent studio](https://creator.voiceflow.com), open the project's **Phone numbers** for calls or **SMS** for Chat-agent text support. Provider manuals include the required Studio setup and programmatic calling or tool-execution path.

Voiceflow-managed phone numbers with their saved agent release assignments — Start with a callable number, then select the agent and release that answer it.

## Choose your connection

| Starting situation | Start here | What you configure |
| --- | --- | --- |
| You need a new public phone number. | [Voiceflow numbers](/docs/guides/integrations/voiceflow-numbers) | Choose an available area code, provision a number and assign its Voice agent. |
| You already have a PBX or phone-system route. | [Voiceflow SIP](/docs/documentation/deploy/phone/connect-with-sip) | Create the hosted SIP endpoint, authenticate the sending system and route calls to the assigned agent. |
| You already hold numbers with a carrier. | [Twilio](/docs/guides/integrations/twilio/overview), [Vonage](/docs/guides/integrations/vonage/overview) or [Telnyx](/docs/guides/integrations/telnyx/overview) | Connect the provider account and number, then verify calls through that carrier. |
| You use an existing business phone system. | [RingEX](/docs/guides/integrations/ringex/overview), [Zoom Phone](/docs/guides/integrations/zoom-phone/overview) or [Teams Phone](/docs/guides/integrations/teams-phone/overview) | Forward a phone user's public number to a tested Voiceflow-connected number, with a separate line for teammate transfers. |

For independent SIP call directions or multiple outbound gateways, choose [Bring your own SIP](/docs/api-reference/agent-runtime/voice/sip/bring-your-own). SIP connections keep the public numbers with your phone system; they do not acquire a new number.

## Guides

- **[Connect and route phone numbers](/docs/documentation/deploy/phone/connect-a-phone-number)** — connect the number and verify its agent, Environment and version.
- **[Make an outbound call](/docs/documentation/deploy/phone/outbound-calling)** — prepare the agent and caller connection, call a separate destination, and verify the answered conversation.
- **[Send a text follow-up](/docs/guides/integrations/phone-messaging/send-text-follow-up)** — confirm the recipient and content, then send one notification and retain its result.
- **[Support customers over SMS](/docs/guides/integrations/phone-messaging/support-over-sms)** — receive texts with a Chat agent and verify a complete conversation.
- **[Troubleshoot SIP calls](/docs/api-reference/agent-runtime/voice/sip/troubleshooting)** — distinguish authentication, routing, media and destination failures.
- **[Create new integration](/docs/guides/integrations/create-new-integration)** — investigate a platform without a provider manual using existing Voiceflow capabilities.

## Explore integrations

| Connection | What to use it for |
| --- | --- |
| [Voiceflow telephony](/docs/guides/integrations/voiceflow-telephony/overview) | Get a number through Voiceflow or connect your phone system using the SIP setup that fits its routing needs. |
| [Twilio](/docs/guides/integrations/twilio/overview) | Receive and place calls, transfer callers, run SMS conversations and send SMS notifications. |
| [Vonage](/docs/guides/integrations/vonage/overview) | Receive and place calls, transfer callers and send notifications through an API tool. |
| [Telnyx](/docs/guides/integrations/telnyx/overview) | Receive and place calls, transfer callers and send notifications through an API tool. |
| [RingEX](/docs/guides/integrations/ringex/overview) | Forward user calls to the agent, manage RingEX user call handling and transfer callers to a separate RingEX line. |
| [Zoom Phone](/docs/guides/integrations/zoom-phone/overview) | Route a licensed phone user's calls to the agent, configure external forwarding and restore the original phone route. |
| [Teams Phone](/docs/guides/integrations/teams-phone/overview) | Forward a licensed user's public calls to the agent using Teams admin settings or PowerShell. |

Use [Connect and route phone numbers](/docs/documentation/deploy/phone/connect-a-phone-number) to verify the assigned agent, Environment and released route across number providers. Voiceflow numbers use the API for outbound calls; their Studio outbound-test panel is unavailable. The current SMS conversation path uses Twilio with a Chat agent. Provider messaging APIs send notifications separately from that channel.

For forwarded business lines, callbacks use the separately configured Voiceflow caller; forwarding does not automatically supply the business system's original caller ID. RingCX, Zoom Contact Center and other contact-center routing retain their [Contact Centers](/docs/guides/integrations/contact-centers) manuals.

## Build the customer journey

- **Answer support questions:** [build and test a phone support agent](/docs/guides/call-centre-automation), connect approved Knowledge and verify its answers through an actual call. Phone-provider setup does not import support content.
- **Call a customer:** follow [Make an outbound call](/docs/documentation/deploy/phone/outbound-calling) for the complete workflow. Use the [pickup-reminder example](/docs/guides/outbound-calls) to build a reminder agent and the [backend calling guide](/docs/guides/developers/voice/outbound-calls) for an application trigger. The calling endpoint does not create a campaign scheduler.
- **Reach your support team:** follow [Transfer a phone call](/docs/guides/studio/voice/transfer-calls) and the provider's transfer requirements. Provider-specific queues, authentication and mapping belong in [Contact Centers](/docs/guides/integrations/contact-centers).

## Runtime and network references

<a id="developer-setup" />

[Voice agents](/docs/api-reference/agent-runtime/voice) owns call lifecycle, audio and recovery contracts. Exact [phone calling](/docs/api-reference/agent-runtime/voice/phone-calls), [SIP outbound calls](/docs/api-reference/agent-runtime/voice/sip/outbound), [SIP network settings](/docs/api-reference/agent-runtime/voice/sip/settings) and [SMS behavior](/docs/documentation/deploy/sms/inbound) remain with their existing references.

<a id="studio-setup" />
<a id="twilio-actions" />

For an SMS action without a text conversation, use [Twilio Send SMS](/docs/guides/integrations/twilio/overview#sending-sms) or the [Vonage](/docs/guides/integrations/vonage/overview#sending-sms) and [Telnyx](/docs/guides/integrations/telnyx/overview#sending-sms) notification recipes.
