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, a reusable event type, a fallback team, and calendar-ready hosts before activating a router.

Create and configure a handoff

1

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.

2

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.

3

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.

4

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.

5

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.

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

Choose sharing capabilities

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 and 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. 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.