Skip to main content
Phone-number assignment selects the agent and configuration context intended for calls to that number. Use the update operation carefully: omitted fields and explicit null values can have different effects.

Change the assignment

1

Inspect the current record

Read Get phone number. Record its agent assignment, branch, environment, and trunk settings before preparing a change.
2

Choose the intended configuration

Select an agent in the same workspace. If you choose a branch, confirm it belongs to that agent and review its published version through versioning. Review the environment variables needed by the deployment.
3

Apply a focused update

Use Update phone number with only the fields you intend to change. Read the returned record and then retrieve it again to confirm the assignment you saved.

Assignment rules

The update also accepts a label, environment, trunk configuration, and SIP-message storage preference. Treat nested trunk objects as complete candidate configurations and read them back; do not assume every omitted nested value is preserved by a partial update.

Review the call experience

Configure instructions, first message, tools, and speech settings on the selected agent. Keep the greeting appropriate for the number’s purpose and review call consent and AI disclosure before deployment. A saved assignment does not start a call or establish that the selected version can execute. After the runtime is released and configured, verify routing to the intended version, resolved environment values, greeting, two-way audio, and end behavior with an authorized test call.

Frequently asked questions

No. The update validates branch ownership against the assigned agent.
No. Clearing the assignment and canceling a number are separate operations. Review the cancellation workflow and provider state before relying on service termination.