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

> Review existing Twilio phone configuration and prepare messaging or call workflows with clear runtime and webhook boundaries.

Threetone already exposes Twilio-specific phone-number configuration. Use it to inspect provider ownership and agent assignment while preparing the separate delivery and execution requirements.

<Note>
  Availability is mixed. Phone configuration can be saved and read back. Twilio is absent from the general native integration catalog, and outbound calls remain blocked by the agent runtime gate. General messaging and live call demonstrations are not established by an imported number.
</Note>

## Review configuration and prepare delivery

You need the provider account owner, an approved number, permission to manage workspace phone resources, and the intended agent identifier.

<Steps>
  <Step title="Read the number configuration" id="twilio-number-config">
    Follow [phone integration](/agents-platform/deploy/telephony/overview) and its provider-specific import reference. Inspect the existing record's provider, number, workspace, and assigned agent. Read any saved change back. Keep credentials out of prompts and configuration screenshots.

    For import preparation, current validation requires `enable_sms: false` and rejects a non-null `account_auth_token`. The presence of those fields in the public schema does not establish SMS routing or secure webhook-signature credential handoff.
  </Step>

  <Step title="Review the receiver separately" id="twilio-webhook">
    An application-owned receiver must follow [Twilio request validation](https://www.twilio.com/docs/usage/security). Validation uses the request signature and actual request URL and data; account for reverse-proxy URL handling. A workspace webhook configuration does not establish callback delivery or a receiver implementation.
  </Step>

  <Step title="Define the future execution test" id="twilio-runtime-test">
    Confirm the sender, recipient, call or message purpose, and applicable consent before an authorized test. Keep request and provider identifiers for duplicate detection. Distinguish accepted requests from connected calls or delivered messages, and reconcile uncertain outcomes before retrying.
  </Step>
</Steps>

The immediate result is a reviewed phone record and test plan. Check [current availability](/agents-platform/overview#current-availability) before attempting runtime verification. A saved voice configuration also does not establish voice publication eligibility.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does importing a Twilio number enable outbound calls?" id="faq-twilio-import">No. Import and assignment are configuration operations. The outbound route still encounters the runtime gate.</Accordion>
  <Accordion title="Does acknowledging a webhook mean delivery succeeded?" id="faq-twilio-webhook-ack">No. Acknowledgement confirms receipt by your receiver. Track the provider's actual call or message outcome separately.</Accordion>
</AccordionGroup>


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