> 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/booking-insights.md).

# Booking insights

Track outbound booking conversion, channel performance, and delivery health.

Open **Outbound routing → Booking Insights** to review how outbound handoffs become booked meetings. These reports are available to workspace admins.

Set **Handoff date**, then use **Add filter** for **Booking owner**, **Router**, **Rule**, **Booking channel**, or **Launch surface**. The range uses the date the handoff started, not the meeting's start time.

| Metric                     | Meaning                                                              |
| -------------------------- | -------------------------------------------------------------------- |
| **Sessions routed**        | Handoffs in the selected scope that reached an eligible assignee.    |
| **Meetings booked**        | Handoffs in that scope that completed a booking.                     |
| **Route → book**           | Booked handoffs divided by routed sessions.                          |
| **Prepared links created** | Recipient-specific booking links created for handoffs in that scope. |

A prepared link is not a completed booking. This report measures booking conversion and delivery; it does not show the completion, cancellation, or no-show rates used in inbound and campaign booking reports.

## Compare channels and periods

**Booked handoffs over time** groups booked handoffs by the date each handoff started. Use **Compare previous** to include the preceding period of the same length.

**Booking channel performance** compares **Direct**, **Prepared link**, **Reusable link**, and **Magic Slots**. Each channel shows booked meetings out of started handoffs for that channel. Its conversion rate uses started handoffs, while **Route → book** uses routed sessions.

**Booking channel** describes how the booking was made. **Launch surface** describes where the handoff started. A handoff launched from the browser extension can still result in a direct booking or a prepared-link booking.

## Review booking and delivery health

**Booking and delivery health** shows availability speed, no-availability outcomes, slot conflicts, suppressed duplicates, expired or revoked links, and technical availability or booking failures.

**Delivery succeeded**, queued deliveries, and delivery failures describe downstream booking delivery. A booked meeting can still have a delivery problem. These counts track attempts, links, or delivery records rather than unique handoffs.

Open **Outbound routing → Routing Logs** and select a handoff to inspect its routing, availability, booking, and delivery trace. Check the recorded failure before retrying or changing configuration.

Return to [Routing Insights](/reporting/outbound-reports/routing-insights.md) to investigate assignment. Keep the same handoff-date range and shared filters when comparing the two reports.


---

# 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/booking-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.