No. 08 · Lead Scoring and Routing

Routing rules tested on real leads before go-live

A change to how inbound leads match to parent accounts moves leads between accounts, and sometimes between owners. So before anything went live, we replayed 240 real leads through the new rules and showed the client which would move, and why.

Lead routingBacktestOctober 2026From The FullFunnel Dozen

Backtest result

94 of 200

Leads with a parent family that would land on a different account

Would move47%

Backtest in a test copy. Not live yet.

The short answer

We turned the client’s answers into a matching hierarchy, replayed two weeks of real leads through it in a test copy, and logged the reason behind every account match. The client could review the impact lead by lead and refine the rules before go-live.

MethodBacktest in a test copy

SampleSep 25 to Oct 9

IssueOctober 2026

How it worked

Problem, fix, proof

The problem

What was the risk?

The client wanted inbound leads matched to the right parent account. Any rule change would move leads between accounts, with no way to preview the effect in live routing.

The fix

What did we build?

A hierarchy built from the client’s answers, checked in order, within the same country only:

Partner accounts first
Then accounts with a territory
Then Customer accounts
Then a higher parent
An account selection reason column in the audit log, so every match explains itself

Every match records why it was made.

The proof

How did we test it?

We replayed 240 real leads from September 25 to October 9 in a test copy. The client reviewed which leads would move and refined the rules twice more in October. Alongside it, an SLA monitor for follow-up tasks runs in shadow mode: it watches the tasks but reassigns nothing yet.

The result

What changed?

The client saw the full impact before a single live lead moved, and kept refining the rules with real examples in front of them.

Audit log, illustrated

LeadMatched toSelection reason

Lead APartner accountPartner, same country

Lead BTerritory accountHas territory, same country

Lead CCustomer accountCustomer, same country

Lead DHigher parentNo closer match, same country

240

Real leads replayed

200

With a parent family

Would land on a different account

Customer leads would leave the shared pool

Example rows illustrate the log format. Figures are from the backtest, run in a test copy.

Sample

September 25 to October 9

Environment

Test copy, not live

Logging

Reason recorded per match

Sound familiar?

About to change your routing rules?

Talk to us about it

Leads land on the wrong account in a parent-child hierarchy.

Routing changes go live before anyone sees the impact.

Reps can’t tell why a lead was matched to an account.

FAQ

Frequently asked questions

What is a routing backtest?

Replaying real past leads through new routing rules in a test copy, so the impact is visible before go-live.

What does “leave the shared pool” mean?

Under the new rules, 33 leads from existing customers would no longer land in the pool shared across reps.

What is shadow mode?

Running a new automation alongside the live process without letting it act. The SLA monitor watches follow-up tasks but doesn’t reassign anything.

Are the new rules live?

Not yet. The client is still refining them.

←Previous · No. 07A lead score reps actually agree with Next · No. 09Document ads vs. single-image ads→

More wins

View all wins

Paid Media No. 09

Get 12 wins like these in your inbox every month.

A short monthly recap of the problems we solved for GTM teams. Every company stays anonymous.

Changing your lead routing?

We’ll test the new rules on your real leads first, so nothing moves until you’ve seen the impact.

Request a Consultation