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

# Booking insights

Track booking distribution and outcomes for Click Router traffic.

Open **Click routing → Booking Insights** to review meetings created by Click Routers. Personal links, group links, and Outbound Routers are outside this report's source scope.

Set **Meeting date**, then use **Add filter** for **Booking Owner**, **Router**, or **Rule**. The range uses the meeting's start time, not the submission or click date.

| Metric                          | Meaning                                                                  |
| ------------------------------- | ------------------------------------------------------------------------ |
| **Total routed bookings**       | Bookings from this router type in the selected meeting-date scope.       |
| **Completed meetings**          | Meetings marked completed.                                               |
| **Completion rate**             | Completed divided by completed, cancelled, and no-show meetings.         |
| **Cancellation + no-show rate** | Cancelled and no-show meetings divided by that same final-outcome total. |

Upcoming and unresolved meetings are excluded from the two outcome rates. A rate is not a percentage of every scheduled booking.

## Compare owners and periods

**Meeting outcomes by owner** starts in **Outcome rate**. Switch to **Volume** to compare booking counts. Use **Compare** to include the preceding period of the same length. Count changes are percentages; rate changes are percentage points.

Select an owner's status segment to open the matching records. Review the guest, booking status, source, and routing context before deciding whether an imbalance is a routing or attendance problem.

**Routed bookings over time** follows meeting dates. To understand how visitors reached those meetings, return to [Routing Insights](/reporting/reporting-1/routing-insights.md), which uses submission or click dates instead.


---

# 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/reporting-1/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.