Skip to main content
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.
Recording pending for Review phone number configuration. No playable video is available yet.

Recording pending: Review phone number configuration. Follow the written guide below.

​
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 to find an existing record. If you have not imported one, review 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

1

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

Inspect the workspace record

Use Get phone number to read its metadata and identifier. Confirm that it belongs to the intended workspace and provider before changing its assignment.
3

Review the assigned agent

Check the agent identifier and saved voice configuration. Keep the relevant branch and version IDs with your configuration review.
4

Read changes back

After using Update phone number, inspect the number record and agent assignment again.
The Delete phone number operation 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

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.
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, models and voices, and conversation inspection.

​
Frequently asked questions

No. Import and assignment are configuration operations. Provider support and runtime execution must be verified separately.
The public operation follows cancellation. Confirm the result and provider release or billing effects separately.
The documented outbound routes currently return HTTP 501. Do not build an execution workflow around them yet.