> 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.md).

# Outbound routing

Use outbound routing when a teammate is arranging a meeting for a prospect and Distro should choose the host. An **allowed booker** starts the handoff; an **eligible host** receives the meeting. They can be different people.

### Start with your task

| I want to…                                        | Guide                                                                            |
| ------------------------------------------------- | -------------------------------------------------------------------------------- |
| Set up a handoff for the sales team               | [Outbound routers](https://help.distro.so/routing/outbound-routing/routers)      |
| Design questions and control who sees each answer | [Outbound Forms](https://help.distro.so/routing/outbound-routing/forms)          |
| Arrange a meeting for a prospect                  | [Sales handoffs](https://help.distro.so/routing/outbound-routing/book-a-meeting) |
| Let one or many prospects choose later            | [Outbound links](https://help.distro.so/routing/outbound-routing/share-links)    |
| Put two to five proposed times in a message       | [Magic Slots](https://help.distro.so/routing/outbound-routing/magic-slots)       |

![Sales demo handoff in dark mode, showing allowed bookers, the pinned form, CRM identity, routing, fallback, and scheduling.](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)

*Admins configure the handoff. Sellers complete it from Distro or a supported extension launch surface.*

### How a handoff works

The booker supplies prospect details using a published **Outbound Form version**. Distro resolves CRM identity, evaluates ownership rules, then distribution rules, then the **mandatory fallback**. The router uses a fixed event type.

The booker can confirm a meeting, share a dedicated link, or propose times when enabled. A reusable link lets each recipient supply their own identity and start a separate session. Viewing availability or sharing an offer does not reserve a host or time; eligibility and availability are checked again when booking.

Outbound routing and its sharing capabilities must be enabled for the workspace. A seller must be an allowed booker on an active router. If a handoff is missing, check both access and active status.

### Review results

Workspace admins can use these pages under **Outbound routing**:

| Page                                                                                   | What it answers                                                                                                |
| -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| [Routing Insights](https://help.distro.so/reporting/outbound-reports/routing-insights) | Are handoffs reaching an eligible route, and where are they getting stuck?                                     |
| [Booking Insights](https://help.distro.so/reporting/outbound-reports/booking-insights) | Which routed sessions turn into bookings, through which channels?                                              |
| **Routing Logs**                                                                       | What happened in this individual handoff: router, rule, status, assignee, launch surface, and booking channel? |

Insight date ranges follow when the handoff started, not the scheduled meeting date. Compare routing and booking results using the same period and filters.

A session that has no eligible host or availability is a routing problem to investigate; it does not mean the prospect was disqualified.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.