​

Use Exotel when regional telephony requirements or existing enterprise contracts make it the preferred carrier.

​

Prerequisites

• Exotel account credentials with required API access.
• Tenant telephony owner assigned.
• Approved regional routing and compliance constraints.

​

Setup workflow

1. Create Exotel telephony connection for each tenant.
2. Import or provision numbers and assign labels by use case.
3. Configure callback/webhook endpoints and verify authentication.
4. Run inbound and outbound smoke tests with supervised monitoring.
5. Validate call identifier correlation between Exotel and Callaro logs.

​

Field mapping guidance

• Persist Exotel call ID in CRM notes for support traceability.
• Standardize outcome mapping before enabling high-volume campaigns.
• Keep region and language tags in runtime variables for routing analytics.

​

Validation checklist

• Test calls succeed for both inbound and outbound directions.
• voice_sessions show matching identifiers and timestamps.
• Callback retries do not create duplicate downstream records.

​

Known limits

• Regional carrier quality may vary by time window.
• Number provisioning can have provider-side lead time.
• Heavy concurrency should be increased gradually.