# Booking Insights

Click Router Booking Insights is a visual dashboard for bookings generated by click-based routing.

Use it to monitor booking outcomes and workload distribution.

{% hint style="info" %}
Use this page when you need answers like:

* “Who is getting the most click-router meetings?”
* “Are cancellations or no-shows trending up?”
* “Did performance change vs last week?”
  {% endhint %}

### Open Booking Insights

{% stepper %}
{% step %}
Open **Click Routers** from the left sidebar.

<figure><img src="/files/veksLUMvzllApayjQug0" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click **Booking Insights**.
{% endstep %}
{% endstepper %}

### Recommended workflow

Run this flow weekly. It keeps analysis consistent.

{% stepper %}
{% step %}
Set your scope with filters.
{% endstep %}

{% step %}
Scan status KPI cards for volume and mix.
{% endstep %}

{% step %}
Review distribution across owners.
{% endstep %}

{% step %}
Enable period comparison to spot trend changes.
{% endstep %}

{% step %}
Click into bars to inspect booking lists.
{% endstep %}
{% endstepper %}

### KPI cards (booking status)

<figure><img src="/files/kouHkfywErknZMqsGAsm" alt=""><figcaption></figcaption></figure>

The dashboard shows one KPI card per booking status.

| Status          | Description                                 |
| --------------- | ------------------------------------------- |
| **Scheduled**   | Upcoming meetings that haven’t happened yet |
| **Completed**   | Meetings that took place as scheduled       |
| **Rescheduled** | Meetings moved to a different time          |
| **Cancelled**   | Meetings cancelled before occurring         |
| **No show**     | Meetings where the guest didn’t attend      |

Each card shows the total count for the selected date range.

### Booking distribution chart

<figure><img src="/files/IfcsQ7MX7bdyZsSY43rU" alt=""><figcaption></figcaption></figure>

The main chart is a stacked bar chart.

It shows how click-router bookings are distributed across team members.

#### Understanding the chart

* **X-axis**: team members (name or email).
* **Y-axis**: number of bookings.
* **Segments**: each color is a booking status.
* **Hover**: tooltip shows the per-status breakdown.

Team members are sorted by total bookings (descending).

#### Reading the chart

1. Taller bars mean a team member receives more click-router bookings.
2. Segment size shows status mix for that person.
3. Compare totals to validate workload balance.

### Compare vs previous period

<figure><img src="/files/hAuVxu42yxTVpZ1rOsHz" alt=""><figcaption></figcaption></figure>

Toggle **Compare vs Previous Period** to see current vs prior performance.

* Last 7 days compares to the 7 days before.
* Last 30 days compares to the prior 30.
* Side-by-side bars show current (solid) and previous (faded).

#### What changes when comparison is enabled

* KPI cards show percentage deltas.
* Previous totals appear below current totals.
* Trend changes become obvious fast.

### Set your scope (filters)

Filters control everything on the page.

* **Booking owner**: focus on one or more team members.
* **Router**: analyze one or multiple click routers.
* **Rule**: filter by the matching rule applied at booking time.
* **Date range**: last 7/30/90 days, or a custom range.

### Drill into details

<figure><img src="/files/01LQqIwg0pKSrsnvcfny" alt=""><figcaption></figcaption></figure>

Click any bar segment to open a details panel.

Use it to review:

* Booking list for that team member.
* Guest name and email.
* Booking date and time.
* Router and matching rule.
* Current booking status.
* Routing logs link (if available).

### Click Router vs Form Router booking insights

Both dashboards look similar. The context differs.

| Aspect         | Click Router                     | Form Router                      |
| -------------- | -------------------------------- | -------------------------------- |
| **Source**     | Click-based routing links        | Form submissions                 |
| **Rule types** | Matching and ownership logic     | Ownership and distribution rules |
| **Context**    | URL params and direct link flows | Form data and field matching     |

### How to interpret the data

#### Understand distribution

Click routers often route based on URL parameters or ownership checks.

Distribution tells you:

* Which team members rules are matching.
* Whether ownership logic is overriding expected routing.

#### Track performance trends

Monitor the status mix over time.

* High **completed** share usually means healthy scheduling.
* Rising **cancelled** or **no show** often needs follow-up.
* Compare routers to identify best-performing configurations.

#### Optimize click router rules

Use insights to:

* Confirm rules are distributing fairly.
* Adjust ownership settings if workload is skewed.
* Tighten or loosen rule conditions based on outcomes.

### Best practices

{% tabs %}
{% tab title="Regular monitoring" %}

* Review weekly.
* Use comparison mode by default.
* Investigate anomalies immediately.
  {% endtab %}

{% tab title="Balance workload" %}

* Watch for owners with outsized volume.
* Adjust matching and ownership logic as needed.
* Account for capacity and availability changes.
  {% endtab %}

{% tab title="Improve outcomes" %}

* Review cancelled and no-show bookings.
* Look for patterns by router, owner, and time.
* Improve confirmation and reminder workflows.
  {% endtab %}
  {% endtabs %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.distro.so/routing/click-router/reporting/booking-insights.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.