The Routing Report

The Routing report is the companion to your ranked Leads list. Where Leads answers “which conversations should I follow up first?”, Routing answers “who are my leads, and where did each kind of lead get sent?” — at a glance, across a whole window of meetings instead of one conversation at a time.

You’ll find it under Routing in the left sidebar, right next to Leads. Two filters at the top scope everything on the page:

Segment — focus on a single segment (or All segments).
Date range — narrow to a From and To date.

Every figure on the page links straight through to the underlying meetings in your Leads list, carrying the same filters, so you can always go from a number to the conversations behind it.

What the report shows

Segment volume

Who your leads are. A bar chart and list of how your meetings resolved across lead segments — for example Senior buyer, Evaluator, Existing customer, or Student / job seeker — plus an Unsegmented bucket for conversations that didn’t resolve to a segment. This is your lead mix: at a glance you can see whether a week skewed toward senior buyers or evaluators. Select any segment to open its meetings.

Segment → destination flow

Where each segment was sent. For every resolved segment, the destinations its meetings were routed to and how many landed at each. Destinations are shown in plain terms:

Priority booking — routed to a priority booking path.
Standard contact — routed to a standard follow-up.
Self-serve resources — pointed at self-serve material.
No handoff — no onward handoff for this guest.
Default (routing abstained) — routing didn’t take a segment-specific action and fell back to the default.
Not routed — no routing outcome recorded for the meeting.

This is where you confirm the routing is doing what you intend: senior buyers flowing to priority booking, lower-intent segments to self-serve, and so on. Select any row to see those meetings.

Routing health

Two figures that tell you how sure and how disciplined the routing was over the window:

Low-confidence resolutions — how often the segment classification came back below the confidence your workspace acts on. A high rate is a signal that classification is shaky for your conversations — worth a look at whether your segment definitions fit how your calls actually go. The sub-line shows how many of the scored meetings were low-confidence (and how many were unscored).
Enforcement adherence — whether leads were routed to the destination their segment is supposed to go to. The target is 100%. Alongside it, Disallowed destinations counts any routing that broke the rule — you want this at 0 (“gate holding”). If it isn’t zero, a per-segment breakdown appears so you can see exactly where it leaked.

A withheld booking link is correct, not an error. When a guest doesn’t qualify for a human-booking path, that link is deliberately withheld — and that counts as correct enforcement, never a violation. So a non-qualifying guest with no priority booking is the routing working as designed.

Segment, tier, and routing — three different questions

If “segment”, “tier”, and “routing” feel like they overlap, they don’t — they answer three distinct questions about one guest:

Segment — who is this guest? (e.g. Senior buyer)
Tier — how soon should I act? (the P1 / P2 / P3 priority band)
Routing — where were they sent? (e.g. priority booking)

The Routing report is the routing view; your Leads list is where segment and tier live per lead. For the full explainer, see Segment, tier, and routing on the Leads page.

”Routing not enabled for this workspace”

The report is always available, but it only shows data once your workspace has lead routing configured. Until then — or for a workspace that doesn’t use segmentation — the page shows a “Routing not enabled for this workspace” message instead of empty charts. That’s expected, not a fault: once routing is set up, segment volume, destination flow, and the health figures start filling in for your meetings. If you’d like routing turned on for your workspace, contact us at hello@buzztrail.ai.

Not yet measured

Two routing signals aren’t instrumented yet. Rather than show a misleading zero, the report lists them under Not yet measured with a plain reason — so you always know the difference between “we measured this and it’s low” and “we don’t measure this yet.” Neither ever displays a number until it’s genuinely being captured.

Segment switch rate — how often a conversation’s segment changed as the call went on. We currently keep only the final segment for each meeting, not the in-conversation history, so there’s nothing to compute a switch rate from yet.
Misroute rate — how often a lead ended up at the wrong destination. Misroute tracking arrives alongside a future routing-recovery capability; once that’s capturing corrections, this figure lights up on its own.

When either signal starts being captured, it simply appears as a real figure here — no fabricated numbers in the meantime.

Last reviewed: 2026-07-20. Questions? Contact hello@buzztrail.ai for assistance.