​

Voice preferences

The Me → Voice preferences page (/me/voice-preferences) is the per-user home for where your own inbound calls ring. It is not an account-level routing surface — it answers the question “when a call is addressed to me personally, what rings?” for one specific member of the organization. This page is reference for the semantics; the how-to walkthrough lives in Configure your voice preferences, and the raw HTTP contract lives in Per-user call forwarding.

​

1. What the page owns

Three per-user constructs sit on this page and nowhere else:

• The call-forwarding rule — one mode + an ordered destination list.
• The voicemail greeting — the audio a caller hears once the ladder ends in voicemail.
• Delegation — a teammate who catches your calls when you cannot.

Queue claims, DID routing, and inbound queue assignment still happen above this page — the page only owns calls that already resolved to you.

​

2. The five forwarding modes

Pick exactly one. All five read the same ordered destination list and the same ring timeout; they differ in how the dashboard softphone and the destinations combine. The mode is none by default, so PSTN destinations stored on the list do not ring until you opt in to a non-none mode.

​

3. The destination list

The list is an ordered array of entries. Each entry is one of:

• PSTN — an E.164 mobile or landline (+14155551234), stored with an optional label like “Mobile”.
• SIP — an internal SIP URI (sip:alice@orbit.devotel.io) for a SIP door desk phone or a softphone endpoint you want the call to extend to.

Ordering matters:

• forward_all uses destinations[0] only — the head of the list.
• forward_after_timeout also uses destinations[0] after the browser timeout.
• sim_ring rings every entry in parallel.
• sequential walks the list in order.

There is a cap on list length and a maximum ring-budget enforced at save time; the editor reads those bounds off the server and reflects them in the UI instead of erroring on save.

​

4. The voicemail greeting

The greeting asset is what plays before a caller leaves a voicemail when the ladder ends without an answer. Three sources, in priority order:

1. Upload — an .mp3 or .wav file.
2. Generate from text — type the greeting and it renders as synthesized speech; stored exactly like an upload.
3. Tenant default — the organization’s fallback greeting.

Uploaded and generated greetings are ordinary tenant-owned media files — they live in the same workspace media bucket everything else uploads to, and you can browse or delete them from Settings → Media. See Media Library for the console and Media Library cookbook for the Files API calls. Reverting to the tenant default does not delete the uploaded file; it is kept in cold storage in case you re-enable it later.

​

5. Delegation

Delegation hands a teammate (inside your organization) the right to catch your calls when you are away — the classic out-of-office or boss-admin arrangement. You pick:

• Which teammates are granted.
• Which actions they may perform (answer, screen, transfer, monitor, place on behalf).
• How the calls ring the two of you — screen first (assistant answers and announces), simul-ring (both at once), assistant first, or executive first.

Inbound calls ring the delegate in whichever stage the ring mode places them, and the ladder ends in the delegate’s voicemail if delegated answering was the last live branch.

​

6. Per-user vs per-account routing

Two voice surfaces exist and the split is deliberate:

• /me/voice-preferences (this page) — per-user rules: ring mode, destination list, delegation, greeting. Every signed-in user edits their own; an administrator may set another user’s rule through the same page with a user selector, the way the guide describes supervisor review and reset.
• Account-level voice routes under Settings → Voice — channels, softphone enablement, voicemail boxes, inbound DID routing templates, global caller-ID allowlists, softphone credential policy. Admin-owned; affecting every member.

When a teammate reports “calls ring the wrong place,” check this per-user page first — its rules beat the org surface for troubleshooting because every user owns theirs.

​

7. Find-me / follow-me parity (legacy-PBX replacement)

This page and its sibling editors close the Find Me / Follow Me gap that used to keep a parallel legacy PBX alive for mobile-first reps:

• Sim-ring a cell alongside the desktop softphone — the RingCentral/Zoom Phone/8x8 class feature.
• Sequentially roll through a list of destinations — the Dialpad-class try-order ladder.
• Boss-admin delegation with screen-and-announce — the assistant screening flows legacy PBX callers expect.

For mobile-first staff, the two old reasons to keep a legacy PBX (FMFM and boss-admin) were the deal-breakers; once these live as per-user settings, no parallel system is needed.

​

Where to go next

• Configure your voice preferences — the guide for the how-to walkthrough.
• Per-user call forwarding (API reference) — the HTTP surface behind every editor on this page.
• Self-service per-user scorecards — the same “per-user owns it” convention, applied to QA scorecards.
• Voice call lifecycle — how fallbacks and the no-answer path resolve across ring modes.
• Media Library — browse the greeting asset and the rest of the tenant media bucket.