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

# Phone integration

> Review provider-backed phone number configuration, agent assignments, and the current limits of outbound and channel execution.

Phone configuration records connect workspace resources to provider-backed numbers. Review the provider, number, credentials, and assigned agent separately from whether a call can execute.

<Frame caption="Recording pending: Review phone number configuration. Follow the written guide below.">
  <img src="https://mintcdn.com/threetonelabs-c2efc9c8/RV32i5440UZIaFHA/images/tutorials/recording-pending.webp?fit=max&auto=format&n=RV32i5440UZIaFHA&q=85&s=55f66d2eef49d8c92c9ac46f84bace35" alt="Recording pending for Review phone number configuration. No playable video is available yet." width="1600" height="900" className="w-full h-auto aspect-video" loading="lazy" noZoom data-path="images/tutorials/recording-pending.webp" />
</Frame>

## Before you begin

This review assumes an existing imported phone-number record in your workspace. You need access to its provider account, permission to manage workspace phone resources, and the identifier of the intended agent. Keep provider credentials in the supported credential workflow and out of documentation, logs, and browser bundles.

Use [List phone numbers](/api-reference/agents-platform/list-phone-numbers) to find an existing record. If you have not imported one, review [Import phone number](/api-reference/agents-platform/import-phone-number) and its provider-specific fields first.

The public reference contains phone-number configuration for Twilio, Exotel, and SIP trunks. These are distinct provider request shapes. A number imported for one provider does not establish that every call direction or outbound route supports it.

## Configuration review

<Steps>
  <Step title="Identify the provider and number">
    Confirm which account owns the number and which provider configuration you intend to use. Review the provider-specific fields in [Import phone number](/api-reference/agents-platform/import-phone-number).
  </Step>

  <Step title="Inspect the workspace record">
    Use [Get phone number](/api-reference/agents-platform/get-phone-number) to read its metadata and identifier. Confirm that it belongs to the intended workspace and provider before changing its assignment.
  </Step>

  <Step title="Review the assigned agent">
    Check the agent identifier and saved voice configuration. Keep the relevant branch and version IDs with your configuration review.
  </Step>

  <Step title="Read changes back">
    After using [Update phone number](/api-reference/agents-platform/update-phone-number), inspect the number record and agent assignment again.
  </Step>
</Steps>

The [Delete phone number operation](/api-reference/agents-platform/delete-phone-number) follows the number cancellation workflow rather than simply removing a record. Check its result and the provider's cancellation or release process before assuming the number was released or provider billing ended.

## Current execution limits

<Warning>
  Outbound-call routes are currently blocked by the documented agent runtime gate. The general outbound implementation additionally requires a managed PSTN configuration and currently selects Twilio fulfillment. An imported Exotel or SIP number does not make that route available.
</Warning>

WhatsApp outbound call and message routes currently return HTTP `501`. Batch creation, export, and retry are also unavailable. Workspace webhook management does not currently establish persisted subscriptions or callback delivery.

This guide covers phone configuration. It does not establish inbound SIP availability or a successful call, batch job, WhatsApp message, or delivered callback.

## Plan the later call test

Once the relevant released execution path is available, validate the provider credentials, destination format, agent configuration, and call direction with a controlled test. Use E.164 destination numbers where the request requires them. Confirm the applicable consent, disclosure, and recording requirements before placing that test call.

Keep provider logs and Threetone request identifiers with the test result, with credentials and personal information removed. A saved phone number or agent assignment is configuration evidence, not proof of a connected call.

Continue with [agent configuration](/agents-platform/configure/agent-behavior/overview), [models and voices](/overview/models), and [conversation inspection](/agents-platform/monitor/conversations).

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does importing a number enable calling?" id="faq-phone-import-runtime">No. Import and assignment are configuration operations. Provider support and runtime execution must be verified separately.</Accordion>
  <Accordion title="Does deleting a number just remove a record?" id="faq-number-delete-cancel">The public operation follows cancellation. Confirm the result and provider release or billing effects separately.</Accordion>
  <Accordion title="Are WhatsApp outbound calls and messages available?" id="faq-phone-whatsapp">The documented outbound routes currently return HTTP 501. Do not build an execution workflow around them yet.</Accordion>
</AccordionGroup>


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