The playbook
Lead Routing: Metrics and Measurement
Measure lead routing by defining unassigned eligible inquiries precisely enough that two people can reproduce the result from the same records. Keep the reporting unit, date basis, and scope visible. Without those definitions, a change in the report may reflect a changed calculation rather than a changed customer outcome.
Put the task in context
Specify territory, service, account ownership, availability, and fallback rules in priority order. Test a lead matching two rules and a lead matching none. A monitored exception queue is preferable to an apparently successful assignment to an unavailable user.
Create a metric definition
| Definition field | What it must explain |
|---|---|
| Measure | unassigned eligible inquiries |
| Unit | What one customer or opportunity record or completed outcome represents |
| Included records | The scope identified by lead type and rule |
| Date basis | The event date or period used to include a record |
| Exclusions | Tests, duplicates, or other records outside the agreed definition |
| Source owner | sales manager |
Separate delivery checks from outcome measures
A delivery check asks whether the team completed a specific task, such as define routing rules by need territory and ownership. An outcome measure asks what happened for the user or business afterward. Keep both visible. Completing the task is useful evidence of execution, but it does not by itself prove that the broader outcome improved.
Worked arithmetic example
Suppose an illustrative review includes 80 eligible records, and 60 satisfy the explicitly defined completion condition. The completion share is 60 ÷ 80 × 100 = 75%. This is hypothetical arithmetic, not an industry benchmark or a predicted improvement. It describes only the population and condition you defined.
For lead routing, explain the condition before applying that calculation. If the question is whether the team can test duplicate and incomplete submissions, a record counts only when the evidence demonstrates that condition. Do not replace missing outcomes with successful ones just to complete a report.
Compare like with like
Keep the scope, date basis, and exclusions consistent between observations. If rule changes meaning between periods, note the change and rebuild a comparable view where possible. A rate can also move because the composition of the underlying group changed, even when individual performance did not.
Investigate an unexpected result
- Check whether the underlying lead type records are complete.
- Look for this known failure: assigning leads to an inactive user without an alert.
- Verify that the process still includes: provide a fallback when the preferred owner is unavailable.
- Reconcile a sample with the original record before changing the operating plan.
Use the report to choose an action
If the evidence supports a correction, use monitored fallback queues and reassignment rules. Record when the change occurred and what should be checked next. Keep uncertainty visible when the sample is small or the observation period is incomplete. The purpose of measurement is a better decision about unassigned eligible inquiries, not a favorable-looking number.
Distinguish a person, an organization, and an opportunity. One contact can participate in several buying decisions, and one company can have several contacts. Keep identifiers and relationships clear when reviewing counts or moving records.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now