> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Per-user call forwarding (Find Me / Follow Me)

> Decide where your inbound calls ring — dashboard only, forward everything, ring desk and mobile together, or roll through destinations in order. Includes voicemail greetings and boss-admin call delegation.

# Per-user call forwarding

Every user controls where inbound calls to their own extension ring, from
**Me → Voice preferences** in the dashboard. No admin role is needed — each
person manages their own rule, and the rule applies only to calls addressed
to them.

This is the Find Me / Follow Me pattern familiar from RingCentral, Zoom
Phone, and 8x8: sim-ring a mobile alongside the desktop softphone, roll a
call through a list of destinations until someone answers, and let an
assistant screen an executive's calls. Until now these constructs were why
teams kept a parallel legacy PBX; here they are per-user settings.

***

## Forwarding modes

Pick one mode per user. Each mode answers "when a call comes in for me,
what rings?"

| Mode                    | What happens                                                       |
| ----------------------- | ------------------------------------------------------------------ |
| `none`                  | Dashboard softphone only (the default).                            |
| `forward_all`           | Skip the dashboard — every call goes straight to destination 1.    |
| `sim_ring`              | Dashboard and every destination ring at once. First answer wins.   |
| `sequential`            | Dashboard rings first, then destination 1, then 2, and so on.      |
| `forward_after_timeout` | Dashboard rings for the ring-timeout, then rolls to destination 1. |

**Destinations** are PSTN numbers in E.164 format (for example
`+14155551234`) or internal SIP URIs (`sip:alice@orbit.devotel.io`). A rule
holds up to 5 destinations, each with an optional label ("Mobile",
"Home office"). Modes other than `none` require at least one destination.

**Ring timeout** (5–120 seconds) sets how long each leg rings before the
call moves on. It applies to `sim_ring`, `sequential`, and
`forward_after_timeout`.

**Optional active window** — set `Active from` / `Active until` and the
rule applies only inside that window; outside it, calls fall back to the
dashboard softphone. Add a short note ("Vacation 6/10 – 6/20") so the
reason for the rule is visible later.

**Clear rule** reverts everything to `none` in one step: destinations,
active window, and note are removed after a confirmation.

### How each mode resolves

```text theme={null}
none        → dashboard softphone ──no-answer──> voicemail

forward_all → destination 1 (dashboard never rings)

sim_ring    → dashboard + dest 1 + dest 2 ... ring together
              first answer wins ──no-answer──> voicemail

sequential  → dashboard → dest 1 → dest 2 → ...
              each leg rings for the ring timeout ──no-answer──> voicemail

forward_after_timeout
            → dashboard rings N seconds → dest 1 ──no-answer──> voicemail
```

When every leg expires unanswered, the call follows the route's no-answer
path — typically the user's voicemail. See
[Voice call lifecycle](/concepts/voice-call-lifecycle) for how fallbacks
resolve.

<Note>
  Forwarding destinations are configuration only. The actual outbound leg
  to a PSTN destination is placed by the call router over the tenant's
  configured carrier — the page itself never dials.
</Note>

***

## Find Me / Follow Me ring ladder

The **Find me / follow me** card is a planner for a per-step reach order:
an ordered ladder where each step rings for its OWN window before rolling
to the next — the full RingCentral-class construct, beyond the flat
sequential mode's single shared timeout.

Build the ladder from steps of any mix: desk phone, mobile, softphone,
a PSTN number, or a SIP URI. Each step rings between the server-advertised
minimum and maximum window, and the ladder is capped at a maximum number
of steps and a total ring budget. A **End at voicemail** toggle decides
where an unanswered call lands after the last step.

As you type, the card previews the resolved timeline live — "rings desk
0–12s, mobile 12–32s, voicemail at 32s" — so the reach order is visible
before it matters.

<Note>
  The ring ladder is currently preview-only: it shows the reach order the
  call router applies at dial time, but the ladder itself is not saved yet.
  To persist call forwarding today, use the **Call handling** modes above.
</Note>

***

## Voicemail greeting

The **Voicemail greeting** card manages the audio callers hear when a call
reaches your voicemail box.

* **Upload** an `.mp3` or `.wav` file up to 2 MB.
* **Generate from text** — type up to 500 characters and the greeting is
  rendered as synthesized speech, stored exactly like an upload. When
  text-to-speech is not configured for the tenant this option reports
  unavailable and the upload path remains.
* **Revert** to the tenant default greeting at any time; the uploaded file
  is kept in cold storage but no longer plays.

Until you set a custom greeting, callers hear the tenant-wide default.
Any authenticated user manages their own greeting.

***

## Call delegation (boss-admin)

The **Call delegation** card lets an executive grant assistants the right
to act on their calls — the classic boss-admin arrangement. The executive
owns every call; saved assistants share control of it.

**Delegated actions per assistant** — grant any subset:

| Action          | The assistant can…                                     |
| --------------- | ------------------------------------------------------ |
| Screen          | Answer first and announce the caller before extending. |
| Answer          | Pick up the executive's inbound calls.                 |
| Place on behalf | Start outbound calls as the executive.                 |
| Transfer        | Move the call to a third party.                        |
| Monitor         | Listen to the executive's live calls.                  |

**Ring distribution** decides how inbound calls split between executive
and assistants:

* **Screen first** — the assistant answers, announces the caller, then
  extends to the executive. Requires at least one assistant granted the
  Screen action.
* **Simul-ring** — executive and all assistants ring together.
* **Assistant first** — assistants ring first; the call rolls to the
  executive on no-answer.
* **Executive first** — the executive rings first; assistants ring on
  no-answer.

Set the screen/alert window (how long the screening stage rings) and per-
assistant ring priority (lower alerts earlier within a stage). Up to the
advertised maximum number of assistants per policy.

**Shared ownership** — when enabled, an assistant who answers shares
control of the call with the executive: either can transfer, end, or
re-take it. When disabled, ownership stays exclusive to the executive.

The card previews the resolved ring stages live as you build the policy.
**Save policy** persists it — it takes effect on the executive's inbound
calls immediately. **Clear policy** removes it (after confirmation) and
calls revert to the executive's normal routing.

***

## Related references

* [Voice quickstart](/voice/quickstart)
* [Voice call lifecycle](/concepts/voice-call-lifecycle)
* [Hot-desking (shared-device sign-in)](/voice/hot-desking)
* [Voicemail in the Voice API reference](/api-reference/voice)