> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/routing/outbound-routing/routers.md).

# Outbound routers

An Outbound Router defines who can arrange a meeting, what information they collect, how Distro selects a host, and which scheduling options they can share. **Workspace admins configure routers; allowed bookers use them.**

Have a [published Outbound Form](https://help.distro.so/routing/outbound-routing/forms), a reusable event type, a fallback team, and calendar-ready hosts before activating a router.

![Outbound Router canvas in dark mode with the Sales demo handoff configuration.](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FmR22wZck7htNBXraCG3o%2Foutbound-router-canvas-dark.png?alt=media\&token=80633068-e932-4d0d-9092-dda4740eafcb)

### Create and configure a handoff

{% stepper %}
{% step %}

#### Create the router and choose bookers

Open **Outbound routing → Outbound Routers → New Outbound Router**. Give it a recognizable name.

Open **Booker starts handoff** and select the **Allowed bookers**. Review **Allow eligible bookers to host** if sellers should be able to choose **Assign to me**. Being allowed to start a handoff does not automatically make someone an eligible host. Save.
{% endstep %}

{% step %}

#### Pin the form and review identity handling

Open **Outbound Form** and select the intended published form version. A newer form version is never selected automatically.

Open **CRM identity & prefill**. Choose whether multiple CRM matches require the booker to select a record or allow explicitly treating the prospect as new. Explicit answers from an authorized booker or prospect take precedence over CRM prefill. Save each panel.
{% endstep %}

{% step %}

#### Configure routing and mandatory fallback

Open **Lead Routing**. Choose **Strict** to name one provisional assignee before availability, or **Flexible** to keep an eligible pool and choose for the selected slot.

Add ownership and distribution rules. Ownership runs first, followed by distribution; reorder within each group by dragging or using **Alt + arrow keys**. The activated revision uses snapshots of these rules.

Open **Mandatory fallback** and choose a team plus all members or selected participants and weights. Fallback is required even when rules usually match. With no rules selected, it handles every route. Save.
{% endstep %}

{% step %}

#### Set the meeting, attendance, and sharing

Open **Display Scheduler** and choose the router's event type. Outbound routing uses this fixed event type; rules cannot override it.

Open **Booking & sharing**. Set whether booker attendance is **Optional**, **Required**, or **Excluded**, and review the sharing options below. Required or excluded attendance overrides the optional default. Save.

Use the **+ after Booking & sharing** to configure a supported booking-side CRM action when needed. CRM meeting creation runs after a successful booking; testing, routing, availability, and link creation do not create a CRM meeting or change CRM ownership.
{% endstep %}

{% step %}

#### Test and activate

Choose **Test route**. Enter synthetic answers and, when relevant, a synthetic CRM owner and record type. Check an ownership match, distribution, and fallback.

This is a safe routing simulation. It does not change credits, assignment history, CRM records, calendar events, or bookings, and it never calls your CRM. Separately check the real seller flow and calendar availability with controlled test details.

Choose **Activate** for a new router, **Publish changes** for an active router's draft, or **Publish & activate** when publishing a paused router. Resolve the visible configuration errors if the action is disabled.
{% endstep %}
{% endstepper %}

![Outbound Test route dialog in dark mode showing synthetic form answers and CRM context.](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FqKNrikhmvcJtFe05QJ1B%2Foutbound-test-route-dark.png?alt=media\&token=f6e42479-db1f-4acb-8a52-76dbe0986a05)

*Use simulation to inspect routing, then check the seller experience separately.*

### Choose sharing capabilities

![Booking and sharing configuration in dark mode with attendance, prepared links, reusable links, and Magic Slots.](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FZ26FpFISyHFxRJ2uWh6g%2Foutbound-sharing-settings-dark.png?alt=media\&token=caad8327-18e7-46e6-abcd-4e5123195eda)

| Setting in Booking & sharing                  | Result                                                                                                             |
| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Prepared links → Allow Share availability** | Enables recipient-specific dedicated links. Set expiry from 1–30 days, never beyond the session expiry.            |
| **Allow reusable scheduling links**           | Lets allowed bookers create reusable links through the Chrome extension. Each recipient starts a separate session. |
| **Allow Magic Slots**                         | Lets bookers propose 2–5 times. Set proposal expiry from 1–14 days, never beyond the source session expiry.        |

The prepared-link switch uses the label **Allow Share availability**. In the seller workspace, **Share link** creates a dedicated link; the separate **Share availability** action opens Magic Slots. See [Outbound links](https://help.distro.so/routing/outbound-routing/share-links) and [Magic Slots](https://help.distro.so/routing/outbound-routing/magic-slots).

Reusable links require a form that a prospect can complete. A required booker-only or locked field without a usable value can prevent activation; review the form's audience and defaults.

### Manage a live router

| Action                         | Effect                                                                                                                               |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
| Save a panel                   | Changes the draft configuration; existing publication remains active.                                                                |
| **Pause**                      | Stops new sessions and freezes uncommitted sessions. Draft changes stay unpublished.                                                 |
| **Resume**                     | Restores the last published revision without publishing the draft.                                                                   |
| Three-dot menu → **Versions**  | Inspect publication history and rollback options.                                                                                    |
| Three-dot menu → **Audit**     | Review configuration changes and their actors.                                                                                       |
| Three-dot menu → **Duplicate** | Creates a separate draft with configuration and pinned form version, without sessions, links, bookings, analytics, or audit history. |

Follow [Router versions](https://help.distro.so/routing/router-versions). After publishing a new form, select that version here and publish the router before new handoffs use it.

### If activation or access fails

Check the allowed-booker list, published form version, fixed event type, fallback team and participants, supported rules, and reusable-link field requirements. A seller who cannot find the router should also confirm the workspace and active status.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.distro.so/routing/outbound-routing/routers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.