Manage phone number routing and release

What you'll achieve

You can manage a number from reservation to release and distinguish saved settings from an active call path.

Check access and available actions

Sign in as a workspace owner or administrator. Other roles cannot load the number list or perform these actions.

Number availability, purchase and activation depend on provider access, compliance and billing checks. Displayed status is not a successful test call or proof of audio quality.

Open a number and review its saved state

A reserved number may appear before it has a billing entry. Read the number's individual state. Reservation or a pending outcome does not mean the number is active.

Manage phone number routing and release: Open a number and review its saved state
  1. Open Admin > Channels > Phone. The Channels hub recovery link for a phone number also opens this list.

  2. Select a number. Review its Status, Compliance, Inbox, Brand, Speech language and any Release date and time. To add a number, start with availability search above the list.

  3. Use the settings heading back control or browser Back to return to the list. Refresh reloads number status. If routing resources fail to load, use Refresh beside that warning to retry the Inbox and brand resources.

Find and activate a number

Manage phone number routing and release: Find and activate a number
  1. Choose a country in the searchable country control: type a country name or calling code, then select the matching option. Select Search provider availability. Only available voice-capable results can be reserved. No results or a pending provider state do not mean a number has been acquired.

  2. Choose Reserve number, then open the reserved number in the list. Check the reservation expiry and the displayed monthly price. If the price is unavailable, refresh before continuing.

  3. Review the activation and automatic package-purchase consent, then choose Purchase and activate. Wait for the saved result. A pending or unknown result must use Retry the same request, not another purchase.

Save and check voice settings

Manage phone number routing and release: Save and check voice settings
  1. Open the number and edit its available voice settings. Choose the speech language and inbound call mode, then enter the business name and greeting. Human mode rings one available Inbox operator while AI mode answers through the voice assistant. Review the recording and fallback options before enabling them.

  2. Choose Save voice configuration, then compare the saved desired settings with the effective state. Saving a destination does not verify it. Pending settings are not a working call path.

  3. After activation and routing are confirmed, test a call before sharing the number. Check the greeting, reply language and handoff. When a recording is ready, open the call bar transcript to review speaker labels, source language, timestamps and any recording gaps. Use Edit transcript segment to correct an operator-reviewed segment, then Save correction. A saved configuration alone does not prove these work.

Review and share a call summary

Sharing is an explicit operator action. A missing recording, incomplete transcript, expired customer portal link or revoked conversation access keeps the customer view private.

Manage phone number routing and release: Review and share a call summary
  1. Open a completed conversation with a ready recording and transcript. In the conversation context, choose Generate summary. The first result stays internal.

  2. Review the reason, facts, unresolved items and proposed actions against the transcript. Do not share internal notes or private evidence.

  3. Choose Share with customer only when the summary is safe for the customer. The customer portal shows only the explicitly shared summary and transcript plus an available recording through the private link.

Review recording access and retention

Retention expiry and deletion follow the workspace retention and legal-hold policy. A Help screenshot can demonstrate the available and failed-transcription states, but it is not evidence of a live retention deletion job or provider recording receipt.

Manage phone number routing and release: Review recording access and retention
  1. Open the completed call in the call bar or Conversation context. A ready recording is played through the authorized audio control. The application does not expose a public storage URL.

  2. Use the audio controls to review the recording. Playback is re-authorized for the workspace and conversation on every request and is delivered with private no-store headers.

  3. If the recording is missing or removed, the audio control stays unavailable. If post-call transcription cannot finish after its bounded retries, the call keeps the recording and shows the typed transcript-unavailable state instead of inventing text.

Transfer a live operator call

Configured destinations are workspace-owned settings. Saving a destination does not prove that it is reachable, approved or supported by the provider.

Manage phone number routing and release: Transfer a live operator call
  1. During a connected human call, choose Transfer in the call bar, select Cold transfer or Warm transfer and review the configured E.164 destination before continuing.

  2. Choose Transfer call only after confirming that the selected destination is the intended approved handoff. A warm transfer calls the destination while you stay on the active call and lets you cancel before it is answered. A cold transfer hands the customer off immediately.

  3. After the transfer result, check the conversation timeline and call state. A completed warm transfer keeps the operator in the call while a completed cold transfer ends the operator leg. A failed or unavailable provider result must remain visible for recovery instead of being treated as success.

Handle voicemail and fallback outcomes

The internal voicemail destination is a server-managed phone mailbox, not an external forwarding address. Public requests cannot assert that a fallback is verified, and the customer-facing path must fail closed when the notice, routing or delivery prerequisites are missing.

Manage phone number routing and release: Handle voicemail and fallback outcomes
  1. In the phone configuration, choose a verified fallback and review the recording-consent setting before saving. Internal voicemail becomes effective only when the workspace phone route, Inbox mailbox and localized notice are all ready and recording is set to Always with notice.

  2. If a call reaches the fallback path, the customer hears the configured localized notice before any voicemail recording starts. Human, callback and text or email outcomes use their own configured delivery path. Do not treat a pending provider result as a completed handoff.

  3. Review the conversation timeline for the fallback outcome and recording state. A ready recording is linked only after server validation. Missing or unavailable recordings remain failed or pending and are retried only through the bounded same-recording retry path.

Assign an active number to an Inbox and brand

Assignment does not purchase a number. Active calls keep their existing routing. An unresolved earlier request must be handled before another action can be submitted.

  1. Open an active number and choose an Inbox and an active brand from the current workspace.

  2. Select the confirmation checkbox then choose Save assignment.

  3. Wait for the server result and the refreshed saved state. If the assignment is rejected, refresh and review the number before starting a new action.

Request an updated provider status

  1. Open the number and locate Check provider status. This action is not offered while searching or after release.

  2. Select the confirmation checkbox then choose Check provider status.

  3. Read the returned result and refreshed number state. A pending response remains pending. The button does not place a test call or verify speech quality.

Resolve a pending or unknown outcome

Retry identity is saved in this browser session, not guaranteed across another browser or cleared site storage. If it is lost or retry remains unresolved, ask support to inspect the request before repeating a potentially destructive action.

  1. If the result is pending or unknown, keep the original request. Do not submit a replacement action with different values.

  2. Choose Retry the same request when it is available. This reuses the saved request identity rather than creating a second intent.

  3. If the server reports a conflict or rejection, refresh and review the saved state before explicitly starting a new action. If the retry identity cannot be saved safely, no new request is sent.

Schedule release of an active number

Release may remove access to this number. Scheduling is not confirmation that release has already completed and this guide does not promise a refund or a billing adjustment.

  1. Open an active number and enter a future Release date and time using your local time.

  2. Review the number and date, select the confirmation checkbox then choose Schedule release.

  3. Wait for the confirmed result and refreshed Release scheduled state and date. An unknown or pending result must use the same-request retry path.

Cancel a scheduled release

  1. Open a number whose saved state is Release scheduled.

  2. Select the confirmation checkbox then choose Cancel scheduled release.

  3. Wait for the server result and refreshed state. Do not assume the schedule is cancelled while the outcome is pending. If the number has already been released, this view cannot restore it.

Recover a browser call safely

A failed permission check, expired recovery window, revoked access or confirmed customer hangup ends the resume path. Use the conversation timeline for the final state instead of assuming that a browser connection means the call is still active.

Manage phone number routing and release: Recover a browser call safely
  1. When an eligible operator receives a browser call, use the call bar to review the customer and conversation before choosing Answer.

  2. If the connection drops, keep the call bar open while it shows Reconnecting. The same call can be rejoined only within the bounded recovery window and after the browser permission and account checks pass.

  3. After a reload, choose Resume on the recovered call. The browser may ask for microphone permission again. DobroDesk does not start the microphone automatically.

  4. A second tab is read-only until you explicitly choose Take over. End the call from the call bar when the conversation is finished. Closing a panel is not a substitute for an explicit termination.

Keep going