> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementum.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up Phone Integrations for Agents

> Configure phone providers, SIP trunking, and organization-wide voice telephony in Organization Settings

## Overview

Organization Admins configure voice telephony in **Organization Settings** → **Voice**: phone providers (**Twilio** or **SIP Trunking**), SIP domains and ingress regions, and org-wide visibility into numbers and voice agents.

After a provider is configured, app builders [build a voice agent and add a phone number](/ai-agents/agents-phone-integration) in each app.

***

## Prerequisites

* **Organization Admin** access
* For **Twilio**: a Twilio account with Account ID and Auth Token (you provision and pay for telephony on your Twilio account)
* For **SIP Trunking**: credentials from your SIP trunk provider and access to configure a callback URL on that provider

***

## Choose a phone provider

|              | **Twilio**                                                                          | **SIP Trunking**                                                                                      |
| ------------ | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Best for** | Teams that want to provision numbers through a VoIP account connected to Elementum  | Organizations with an existing enterprise phone system and carrier                                    |
| **Numbers**  | Connect your Twilio account; platform provisioning creates **US toll-free** numbers | Bring your own numbers and point them at Elementum so calls route to the correct agent                |
| **Costs**    | Telephony charges stay on your Twilio account when you use your own credentials     | Telephony stays with your SIP/carrier provider; Elementum does not add pass-through telephony charges |

Both paths use the same agent and phone service setup in your apps, including outbound **Initiate Call** automations. Voice usage also incurs model/LLM cost for the conversation, separate from telephony.

***

## Add a phone provider

You must configure a phone provider before you can provision numbers or assign a provider to a phone service.

1. Go to **Organization Settings** → **Voice**.
2. Open the **Phone Providers** tab.
3. Click **+ Add Phone Provider**.
4. In the **Add Phone Provider** dialog, select a **Type** and complete the fields for that provider:

<Tabs>
  <Tab title="Twilio">
    * **Type**: **Twilio**
    * **Name**: A display name for this provider
    * **Account ID**: Your Twilio Account ID
    * **Auth Token**: Your Twilio Auth Token

    Elementum does not create or manage your Twilio account. For help locating or troubleshooting your Twilio credentials, see [Twilio's usage docs](https://www.twilio.com/docs/usage).
  </Tab>

  <Tab title="SIP Trunking">
    * **Type**: **SIP Trunking**
    * **Name**: A display name for this provider
    * Enter the **username** and **password** credentials for your SIP trunk provider
    * Copy the **callback URL** Elementum provides and use it to finish setup on your provider's side

    When you add a phone number in an app, select this provider so calls route through your SIP trunk. See [Configure a phone number in your app](/ai-agents/agents-phone-integration#configure-a-phone-number-in-your-app).
  </Tab>
</Tabs>

5. Click **Save**.

### Multi-Region SIP Domains

For SIP Trunking, Organization Admins can provision multiple SIP domains and select the ingress region closest to their SIP infrastructure. A nearer region lowers latency for voice calls and helps with global telephony deployments.

1. On the **Phone Providers** tab, open or add a SIP domain configuration.
2. Select the **ingress region** closest to your SIP infrastructure. Region options and setup instructions appear in the UI alongside the SIP domain fields.
3. Save your changes.

Use a separate SIP domain when you need distinct routing or regional ingress for different parts of your telephony footprint.

***

## Organization voice management

The **Voice** page has three tabs for org-wide management:

<Tabs>
  <Tab title="Phone Numbers">
    View, add, and edit every provisioned number across the organization. Each number shows its provider, type, gateway, and language at a glance, and the list is searchable and sortable.
  </Tab>

  <Tab title="Phone Providers">
    Configure Twilio and SIP trunk providers. Manage SIP domains, ingress regions, and allowed IP addresses, with validation as you enter them. See [Add a phone provider](#add-a-phone-provider) and [Multi-Region SIP Domains](#multi-region-sip-domains).
  </Tab>

  <Tab title="Voice Agents">
    See every voice-enabled agent along with its app, gateway, and assigned phone numbers. Voice gateways show active or inactive status and their number counts, and configuration gaps — such as an agent with no assigned number or no app — are surfaced rather than hidden.
  </Tab>
</Tabs>

***

## Next steps

<CardGroup cols={2}>
  <Card title="Agent Phone Integration" icon="phone" href="/ai-agents/agents-phone-integration">
    Build the voice agent, add a phone number in the app, and configure caller access.
  </Card>

  <Card title="Deploy apps between environments" icon="arrow-left-right" href="/administration/deploy-apps-between-environments#phone-services">
    Phone numbers are environment-specific and do not transfer with a deployment.
  </Card>
</CardGroup>