Lead Routing

The rules assigning each inbound lead to a specific owner — by territory, segment, product, account ownership or round-robin.

What routing decides

Which owner a record gets, and how quickly. It sits between marketing and sales and depends on data quality owned by a third party, which is why it surfaces structural problems that exist elsewhere but are harder to see.

Check the inputs before the rules

Before tuning routing logic, measure the null rate — at the moment routing fires, not after enrichment finishes — for every field the rules read. It is common to find rules keyed on fields populated on a minority of inbound records. Tuning logic against missing data produces new rules that also cannot fire.

Four measures that locate the problem

  1. Null rate at fire time for every field the rules read. This is the first test and it resolves a large share of routing complaints on its own.

  2. Default-queue volume and age. Records landing where no rule matched, and how long they sit there. Nothing errors when a record arrives here, so it is invisible without being asked for.

  3. Time from creation to assignment, as a distribution. Report median and ninetieth percentile — the mean hides the tail, and the tail is the loss.

  4. Reassignment rate. Records routed then moved. Each reassignment is a rule that fired on incomplete or wrong information.

Ownership

Routing typically spans three functions, which makes it a reliable place to find the ownership gaps described in responsibility mapping: steps with no owner, steps with two, and steps whose failure is invisible. A step with two owners produces contradictory configuration and silent overwrites; a step with none simply waits.

Design principles

  • Enforce completeness before routing rather than after. Routing on incomplete records generates the reassignment work above.

  • Give every rule set an explicit fallback with a named owner, so the default queue is somebody's responsibility rather than a place records go to wait.

  • Instrument failure. A routing step with no alerting fails silently, which is why routing problems typically surface as a customer complaint.

  • Keep the rules readable by the people accountable for the outcome. A routing model only its builder can explain cannot be governed.

RELATED TERMS

COMMON QUESTIONS

Why do leads not get routed correctly?
Most often because the rules read fields that are empty at the moment routing fires. The logic is usually correct; the inputs are missing, and rewriting rules against missing data produces new rules that also cannot fire.
Who should own lead routing?
One accountable owner for the outcome, even though execution spans marketing, sales operations and a systems administrator. Routing is a reliable place to find ownership gaps precisely because it crosses those boundaries.
How fast should leads be routed?
Fast enough that routing is not the constraint on response time. Measure the distribution rather than the mean — the median is usually fine and the ninetieth percentile is where the loss occurs.
What is a routing default queue and why does it matter?
Where records land when no rule matches. It is the most common place for mis-routed leads to accumulate unnoticed, because nothing fails when a record arrives there and nobody is alerted.

FURTHER READING

Learn how to apply this: CRM Admin 101

Definitions are the vocabulary. The courses are where you learn to operate it, with the interactive audit tools.

See the course