Skip to main content
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.

​
Prepare and inspect the record

1

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

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

Import and read back

Use the Exotel variant of Import phone number. Inspect the saved identity and assignment. Credential metadata is redacted; readback is not provider authentication evidence.
4

Keep runtime release separate

Require provider-specific execution, credential delivery, callbacks, and an executable agent version before changing the existing call flow.
See Exotel’s number-to-flow reference 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

No. Import and provider execution are separate. The current shared outbound path does not support Exotel fulfillment.
No. It records the supplied configuration. Review the applet with the provider account owner.