Skip to main content

​
Use Twilio when you want mature number inventory and programmable telephony.

​
Prerequisites

  • Twilio account and credentials
  • A telephony connection configured for the tenant
  • Approved inbound and outbound countries
  • Ops owner for number health monitoring
1

Create telephony connection

Configure Twilio connection in Callaro and verify credentials with a connection test.
2

Provision number inventory

Use phone_numbers/available, purchase, or import_owned depending on ownership model.
3

Configure webhook and callback paths

Validate call status and inbound routing callback compatibility before launch.
4

Run supervised smoke tests

Execute inbound and outbound test calls and verify session logs, recordings, and webhook delivery.

​
Mapping guidance

  • Twilio call SID should be stored as external reference for debugging.
  • Map Twilio number inventory labels to campaign and region ownership.
  • Keep provider-level webhook secret rotation in ops runbook.

​
Validation checklist

  • Number can place and receive test calls.
  • Call status reaches voice_sessions consistently.
  • Recording links resolve where recording is enabled.
  • Retry behavior is acceptable during temporary provider failures.

​
Known limits

  • Carrier behavior differs by geography and can affect answer rates.
  • Rapid high-volume ramp without warm-up increases spam risk.
  • Provider-side webhook latency can impact near-real-time automations.
When Twilio is your primary provider, tie number-health alerts to campaign velocity controls.