Skip to main content
Twilio phone records can be imported today. A complete calling integration still requires credential handoff, a configured runtime route, and an executable agent version. See current availability.

Before you begin

Prepare a Twilio number you control, its workspace label, and credentials belonging to the intended account. Confirm whether your design uses Programmable Voice or Elastic SIP Trunking; they have different routing configuration. Start with Twilio’s SIP documentation for trunk-based designs.

Prepare and inspect the import

1

Pair the credential fields

Use an Account SID with its Account Auth Token, or an API Key SID with its API Key Secret, in the import’s sid and token fields. Do not mix the two pairs.
2

Apply the current restrictions

Set enable_sms explicitly to false. Omit account_auth_token: the current validator rejects that field until webhook-signature credentials have a secure runtime handoff. The default SMS value is not usable.
3

Save the intended record

Use Import phone number with the Twilio variant. Read back the resulting record and check its number, label, and agent assignment. Import does not authenticate Twilio or provision carrier resources.
4

Review the calling requirements

The outbound service requires managed PSTN with Twilio fulfillment, a platform-managed SIP trunk, and an executable agent configuration. Stored status alone does not satisfy these requirements. Keep an existing working route until a supported deployment passes acceptance checks.

Known request limits

The current Twilio outbound handler accepts but ignores call_recording_enabled; do not use it to establish recording behavior. Carrier answering-machine-detection configuration is rejected. Review call consent separately from configuration. If import fails, check the credential pair and rejected fields first. If a later operation reports a provider or runtime error, repeated imports will not provision the missing runtime.

Frequently asked questions

No. The separate webhook credential field is currently rejected, and runtime handoff remains a release requirement.
No. SMS must remain disabled. Read SMS conversations for the preparation boundary.