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

# Twilio native integration

> Prepare the supported Twilio phone import and identify the credential, routing, and execution checks required before calling.

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](/agents-platform/overview#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](https://www.twilio.com/docs/sip-trunking) for trunk-based designs.

## Prepare and inspect the import

<Steps>
  <Step title="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.</Step>
  <Step title="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.</Step>
  <Step title="Save the intended record">Use [Import phone number](/api-reference/agents-platform/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.</Step>
  <Step title="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.</Step>
</Steps>

## 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](/agents-platform/legal/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

<AccordionGroup>
  <Accordion title="Does API-key import finish inbound webhook authentication?" id="twilio-native-faq-webhook">No. The separate webhook credential field is currently rejected, and runtime handoff remains a release requirement.</Accordion>
  <Accordion title="Will the imported number receive SMS conversations?" id="twilio-native-faq-sms">No. SMS must remain disabled. Read [SMS conversations](/agents-platform/deploy/telephony/twilio/sms-conversations) for the preparation boundary.</Accordion>
</AccordionGroup>


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