> 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/reporting/outbound-reports/routing-insights.md).

# Routing insights

Track outbound handoffs, assignment conversion, and routing health.

Open **Outbound routing → Routing Insights** to see how outbound handoffs reach an eligible host. These reports are available to workspace admins.

Choose **Handoff date**, then use **Add filter** for **Router**, **Rule**, or **Launch surface**. The range follows when the handoff started, not when the meeting takes place. Launch surface tells you where it started, such as Distro, a CRM, or the browser extension.

| Metric               | Meaning                                                                 |
| -------------------- | ----------------------------------------------------------------------- |
| **Handoffs started** | Outbound handoffs started in the selected date range and filter scope.  |
| **Sessions routed**  | Handoffs in that scope that reached an eligible assignee.               |
| **Session → route**  | Sessions routed divided by handoffs started.                            |
| **Routing p95**      | The duration within which 95% of successful routing attempts completed. |

A routed session means Distro found an eligible assignee. It does not mean a meeting was booked.

## Compare periods and routing health

**Handoff volume over time** shows started handoffs. Use **Compare previous** to include the preceding period of the same length.

**Routing health** shows routing p50, p95, and p99: the durations within which 50%, 95%, and 99% of successful routing attempts completed. **No assignee** counts attempts with no eligible host; **Routing failed** counts technical failures. A handoff can have more than one attempt, so these counts are not unique-handoff totals.

For handoffs without an assignee, inspect the router's rules and eligible members. For technical failures, open **Outbound routing → Routing Logs**, find the handoff, and select it to review its ordered trace.

Use [Booking Insights](/reporting/outbound-reports/booking-insights.md) to follow routed handoffs through booking and delivery.


---

# 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/reporting/outbound-reports/routing-insights.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.