What is lead routing? Assignment is a measurement boundary

A lead can be captured at 09:04 and still have no meaningful owner at 09:30. It can be assigned to the right queue but wait behind a full workload. It can receive a fast response and still become a canceled opportunity rather than a competitive loss. The assignment record comes before the commercial outcome.

Lead routing is the rule that assigns an eligible lead to an owner or queue under a declared population and time boundary. It answers who receives the lead, when the assignment happens, and which rule made the decision. It does not tell you whether the lead was high quality or prove that the routing rule caused a later conversion.

What does lead routing mean?

The word lead often compresses several events. Capture records arrival. Qualification decides whether the record belongs in the eligible population. Routing assigns the eligible record to an owner or queue. Follow-up records an action. Reassignment records a change in ownership. Outcome records what happened by a declared window. These are connected objects, but they are not one field.

Lead management is the wider process around these objects. CRM adoption asks whether the system’s definitions and routines have become part of selling work. The CRM adoption article owns that integration question. This page owns the assignment boundary inside the process.

Which fields make a routing decision reproducible?

A routing rule is reviewable when the record preserves the decision inputs as well as the assigned owner. Start with the trigger and timestamp. Then record the eligibility rule, its reason, the active rule version, the candidate queue, the capacity state at assignment, the assigned owner, the first response event, any reassignment and reason, and the outcome window.

The capacity field matters because a route can be valid and still produce a fallback assignment. A full queue is not the same as an unassigned lead. The fallback path is part of the rule’s behavior, not a detail to reconstruct after the reporting period.

The effective time matters too. If rule R1 and rule R2 operate in the same week, a report that stores only the latest rule cannot tell which decision created the assignment. Store the rule version on the lead, not only in a current configuration screen.

Why does routing change the comparison set?

Routing sits between eligibility and outcome. A conversion rate can change because the eligible population changed, because the owner mix changed, because the queue capacity changed, or because the response window changed. The number can move even when the underlying selling process did not improve.

Virtanen, Parvinen, and Rollins studied 4,194 sales leads from one large IT solutions company and about 500 business customers. Their mixed-method design combines salesperson interviews, CRM analysis, and executive discussion. The useful measurement boundary is that the leads remain won, lost, or canceled rather than being reduced to one undifferentiated loss state (Virtanen et al., 2015). The study is one company setting. It does not supply a general close-rate benchmark or explain any individual lead.

The same discipline applies before the outcome. If a new qualification filter removes difficult leads, the observed conversion rate may rise because the denominator became narrower. If a new rule sends complex leads to a senior queue, the owner mix changed before the outcome was recorded. These are reasons to inspect the assignment record, not reasons to declare a routing effect.

What does a routing worksheet look like?

The following worksheet is designed around six synthetic lead IDs. Five are eligible under rule R2. The sixth is captured but excluded before assignment. The response window is 24 hours and the outcome window is 30 days. The rows are prompts for a reviewable record, not a service level or a commercial benchmark.

The worksheet above is the review instrument. The filled example below makes the six synthetic rows and their arithmetic visible. It is not a CRM export, a service level, or a commercial benchmark.

The eligible population is five, not six. Under the declared rules, assignment coverage is 5 / 5 = 100%, response completion within 24 hours is 3 / 5 = 60%, opportunity creation is 4 / 5 = 80%, wins per eligible lead are 1 / 5 = 20%, and wins per created opportunity are 1 / 4 = 25%. These are synthetic rates. They describe this rule window and nothing beyond it. The worksheet does not show that R2 performs better than R1.

L-02 and L-05 make capacity visible. Both reach a fallback queue, but their response events differ. That difference belongs in the routing review before anyone labels one owner slow or one lead weak. L-06 makes the denominator visible. A captured record can be validly excluded before assignment, but the exclusion rule must be recorded.

What do the studies contribute to a routing review?

The held research does not give the page a routing algorithm. It supplies boundaries for interpreting the record.

Keep outcome types separate

Virtanen, Parvinen, and Rollins define a lost lead as one where the customer made an alternative purchase decision. A canceled lead is one where no purchase decision was made and the opportunity was stopped by the supplier or customer (Virtanen et al., 2015). That distinction changes the follow-up question. A competitive loss and an opportunity stopped before a decision do not belong to the same outcome denominator by default.

Keep buyer and seller evidence separate

Friend, Curasi, Boles, and Bellenger examined 35 post-mortem cases with 58 decision makers from 35 key-account buying organizations connected to two US Fortune 250 industrial service organizations. Their recurring dimensions were adaptability, relationship potential, and cost considerations (Friend et al., 2014). The useful lesson for routing is narrower than importing those dimensions as reason codes: a seller’s explanation is a different evidence layer from the buyer’s account. A route can be correctly recorded while the reason for a later failure remains incomplete.

Keep early exit separate

Friend, Ranjan, and Johnson describe failing fast as collecting prospect intent, interpreting it, and deciding to stop pursuing a prospect early. Across their studies, the direct relationship between failing fast and sales performance was not statistically significant, and the moderator results were mixed (Friend et al., 2019). An early exit can be an effort-allocation decision. It is not evidence by itself that the routing rule worked or that the seller predicted the final outcome correctly.

Which rates can a team name?

The following are author conventions for keeping the measurement boundary visible. They are not universal industry definitions.

assignment coverage = eligible leads assigned / eligible leads × 100
response completion = eligible leads with first response inside the stated window / eligible leads × 100
opportunity creation = eligible leads with an opportunity record / eligible leads × 100
win rate among eligible leads = won opportunities / eligible leads × 100
win rate among opportunities = won opportunities / opportunities created × 100

Write the population and window beside each rate. Assignment coverage is a process measure. Opportunity creation and win rate are downstream outcomes. They should not be collapsed into a single routing score.

Before comparing two rule versions, hold the following conditions visible: the eligible criteria, the lead grain, the assignment unit, the capacity and fallback definition, the response window, the outcome categories, and the observation period. If one of these changes, the comparison may still be useful, but it is a comparison of systems rather than a clean estimate of a routing effect.

What is lead routing not?

Lead routing is not lead scoring. A score may rank or prioritize records; routing assigns a record to an owner or queue. It is not qualification, because qualification decides eligibility before the route. It is not territory design, because territory design sets a wider coverage boundary. It is not CRM adoption, because adoption concerns integration of a system into work.

It is also not a measure of lead quality by itself. If one queue receives more wins, the difference may reflect the eligible population, account mix, capacity, response time, owner experience, or outcome definition. Nor is it a measure of owner productivity. The assignment record tells you what the rule did; it does not isolate everything the owner did afterward.

Finally, routing is not a causal lift claim. A higher conversion rate after R2 begins may be useful evidence for a further test. It is not a causal result until the comparison design accounts for who was eligible, who was assigned, what capacity was available, and when the outcome was observed.

How should a team review a routing rule?

Use the review as a record check before turning it into a performance score.

1. Define the entry event. Name the capture event, timestamp, lead grain, and source system.
2. Define eligibility. Record the qualification rule and the reason an item is included or excluded.
3. Version the route. Store the rule version and effective time on every assigned record.
4. Record capacity. Keep the candidate queue, capacity state, fallback path, and assigned owner together.
5. Record response and reassignment. Define the first response event and window. Preserve every ownership change with its reason.
6. Close the outcome. Keep won, lost, canceled, and no-opportunity states visible at the declared horizon. Then compare rule windows only after the populations and definitions are aligned.

Can lead routing improve conversion?

It can be a candidate process change, but the assignment ledger cannot identify the effect by itself. If a routing rule is changed, preserve the old and new versions, define the eligible population before the comparison, and keep the same outcome and response windows. If assignments depend on lead attributes, compare within a declared population or use a design that makes the assignment contrast credible. A raw before-and-after rate is a starting observation, not a causal verdict.

The pipeline coverage article shows why a total can hide different stage distributions. The sales-cycle definition article shows why start and stop events change the number. Lead routing comes earlier: it fixes who enters the next process path and under which rule.

Lead routing becomes useful when the assignment is observable before success is interpreted. Keep the eligible population, rule version, capacity state, owner, response event, reassignment, and outcome window together. Then a conversion number can start a question without pretending to answer it.