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

# Provider integrations

> Prepare Twilio, Exotel, or SIP import fields and understand the provider checks that remain outside a saved phone record.

Choose the import variant that matches the number or trunk you control. The current API accepts Twilio, Exotel, and SIP configuration, but import does not authenticate the provider account, provision a number, or verify live calling.

## Choose an import variant

| Provider | Required preparation |
| - | - |
| Twilio | Number, label, `sid`, its paired `token`, and `enable_sms: false`. |
| Exotel | Number, label, account SID, API key, API token, account API subdomain, and app ID. |
| SIP trunk | Routing identifier, label, and the inbound or outbound settings needed by your deployment. |

Use the full [Import phone number schema](/api-reference/agents-platform/import-phone-number) for optional fields and exact request types. An optional `agent_id` must identify an agent available in the workspace.

### Twilio preparation

The `sid` field accepts an Account SID or API Key SID. Pair it with the corresponding Account Auth Token or API Key Secret. The current validator requires `enable_sms: false`; its default value of true is rejected. It also rejects `account_auth_token` until a secure webhook-signature credential handoff is available.

These restrictions mean you must not describe an import as enabling SMS or completing an API-key-based inbound webhook setup. For carrier-side trunk requirements, use [Twilio's official SIP documentation](https://www.twilio.com/docs/sip-trunking).

### Exotel preparation

Collect the account SID and API credentials from the account's API settings. Confirm the region-specific API host and the intended app ID. Exotel's [getting-started guide](https://developer.exotel.com/docs/call-support/basics/getting-started) explains where these account details originate. An Exotel record in Threetone does not prove that an applet, callback, or outbound runtime has been configured.

### SIP preparation

Use the [SIP trunk guide](/agents-platform/deploy/telephony/sip-trunk) to review routing direction, address restrictions, transport, media policy, and credentials with the trunk operator.

## Verify the result

<Steps>
  <Step title="Import only the intended configuration">Submit the appropriate variant from a trusted server or authorized dashboard workflow. Keep credentials out of screenshots and issue reports.</Step>
  <Step title="Inspect the saved record">Read the returned phone-number ID. Confirm the provider, routing identity, assignment, and configuration. Import stores redacted credential metadata, so it is not proof of a usable runtime secret.</Step>
  <Step title="Review runtime readiness">Verify credential handoff, the provider-specific route, and the selected executable agent version separately. The general outbound route requires managed PSTN with Twilio fulfillment; an Exotel or SIP import does not satisfy that requirement.</Step>
</Steps>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Why does a basic Twilio import fail validation?" id="provider-integrations-faq-sms">Check that enable\_sms is explicitly false and account\_auth\_token is omitted. The current implementation rejects both SMS enablement and the separate webhook credential field.</Accordion>
  <Accordion title="Does deleting the Threetone record stop provider charges?" id="provider-integrations-faq-charges">Do not assume that it does. Deletion follows a cancellation workflow with provider-specific requirements. Verify the final provider state separately.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.