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

# Exotel

> Prepare Exotel account, region, and applet fields for phone import while identifying the current outbound execution limit.

The phone API accepts an Exotel import record. It does not validate the provider credentials, configure an applet, or release Exotel calling. The current shared outbound service requires Twilio fulfillment, so the existence of an Exotel outbound operation is not proof of working execution.

## Collect the import fields

Use the account's API settings to obtain credentials, following [Exotel's getting-started guide](https://developer.exotel.com/docs/call-support/basics/getting-started).

| Field | Preparation |
| - | - |
| `phone_number`, `label` | Intended number and a recognizable workspace label. |
| `account_sid` | Account owning the number and flow. |
| `api_key`, `api_token` | Matching account credentials. |
| `api_subdomain` | Account host: `api.in.exotel.com` or `api.exotel.com`. |
| `app_id` | Intended Exotel applet identifier. |
| `applet_url` | Optional explicit flow URL override; review before supplying. |

## Prepare and inspect the record

<Steps>
  <Step title="Confirm the flow">Exotel's number-to-flow operation calls a number and then connects it to an applet after answer. Confirm the correct flow in the provider account; do not confuse it with a two-number call.</Step>
  <Step title="Check account and region">Ensure the SID, credentials, API host, number, and app ID belong to the same intended configuration. Avoid constructing a flow URL from an unrelated account.</Step>
  <Step title="Import and read back">Use the Exotel variant of [Import phone number](/api-reference/agents-platform/import-phone-number). Inspect the saved identity and assignment. Credential metadata is redacted; readback is not provider authentication evidence.</Step>
  <Step title="Keep runtime release separate">Require provider-specific execution, credential delivery, callbacks, and an executable agent version before changing the existing call flow.</Step>
</Steps>

See [Exotel's number-to-flow reference](https://developer.exotel.com/docs/voice-v1/api-reference/connect-to-flow) for the relationship between the called number, caller ID, and applet URL.

## Failure handling

For import validation, inspect the API host enum and required fields. For an unsupported-fulfillment error during outbound initiation, stop retrying: changing account credentials cannot enable an unimplemented provider execution path.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can I call immediately after Exotel import succeeds?" id="exotel-faq-execution">No. Import and provider execution are separate. The current shared outbound path does not support Exotel fulfillment.</Accordion>
  <Accordion title="Does import create my Exotel applet?" id="exotel-faq-applet">No. It records the supplied configuration. Review the applet with the provider account owner.</Accordion>
</AccordionGroup>


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