Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Lead Routing

Rules that assign each new lead to an owner, queue or next step based on territory, segment, score or source.
StrategyprocessUpdated

Definition

Lead routing is the automated assignment of a new lead to an owner and a next step. The owner may be a person, a team queue or a marketing programme; the next step may be a call, a review, a nurture sequence or a closed record with a reason. The rules run at the moment the record is created or changes state, usually in the CRM or the marketing automation tool, and they read the fields on the record to decide.

It is also called lead assignment or lead distribution, though "distribution" often means only spreading volume evenly across a team.

Routing by territory, segment, score and source

Most rule sets combine a handful of conditions, evaluated in order until one matches:

  • Territory. Country, region or postcode decides the owner, because sales teams are often organised geographically and some regions are not served at all.
  • Segment. Company size, industry or an existing account relationship sends the lead to the team that handles that kind of customer, so an existing client's new contact reaches their account manager rather than a stranger.
  • Request type. A demo request goes straight to sales; a guide download goes to marketing. The inbound lead handling playbook puts request type among its first cuts.
  • Score. A threshold from Lead Scoring decides whether the record is handed over at all. How the points are built is the subject of the lead scoring guide; routing only acts on the result.
  • Rotation. Within a team, leads are shared in turn (often called round robin) or by current workload, so that no one person is buried while another waits.

Because rules run in sequence, order matters: a broad rule placed above a narrow one catches the leads the narrow rule was written for.

In practice: fallbacks, notifications and service levels

A routing design is complete only when it says what happens in three uncomfortable cases. The first is a lead that matches no rule, because a field is blank or a value is new. The second is an owner who is away, has changed role or has left. The third is a lead that arrives outside working hours. Each needs a named fallback: a monitored queue or a person, never an inactive user record.

Assignment alone is not enough. The routing step should also create a task with a due time and alert the owner, because a lead that sits in a list without a prompt is treated as optional. The automation workflows section counts routing among the first workflows a team should build for exactly this reason: if it stopped, both sales and marketing would notice. The rules themselves, and the time within which an owner must act, belong in the agreement between the two teams that the sales and marketing alignment guide describes, so that a missed lead is a breach someone reports rather than a shrug.

Routing usually hands a record to sales when it becomes an MQL. The lead stages and pipeline guide defines those stages; routing is the machinery that moves records between their owners.

Testing routing after changes

Routing rules break without anyone touching them. A new form adds a field with different values, a territory is redrawn, a salesperson leaves and their user is deactivated, or an ad platform's lead form stops syncing. None of these raises an alarm. The defence is a routine: submit a clearly labelled test lead through each route whenever a form, field, territory or team changes, follow it to the owner it should reach, and delete it afterwards. The lead routing QA checklist sets out that end-to-end test, including a test persona that deliberately matches no rule so the fallback is proved too. Between changes, a daily look at unassigned leads and leads owned by inactive users catches what the tests miss.

Illustrative example — not a real result

A solar installer finds its silent route

Brightmarrow Solar Installers expanded into 3 new postcode areas in spring and added them to the routing rules, assigning all 3 to one salesperson. When he left in June, his user was deactivated but the rule was not changed. Over the next 5 weeks, 46 enquiries from those areas were assigned to the inactive user and nobody was notified. The gap surfaced only when a homeowner phoned to ask why nobody had called. The team added a fallback queue checked twice a day and began sending 1 labelled test lead through each of its 9 routes every Monday. Two months later, a renamed region field broke another route; the Monday test caught it within 4 days, and the 7 leads affected were reassigned before any went cold.

Lead Scoring produces the number many routing rules act on. An MQL is the stage at which routing usually passes a record to sales, and a Sales-Qualified Lead is what it becomes once a conversation confirms the need. Lead Response Time measures what happens after assignment, and slow routing shows up there first.

Common confusions

  • Routing is not scoring. A score ranks leads; routing decides who owns them. A lead can be routed correctly with no score at all.
  • Assignment is not notification. A lead assigned without a task or an alert is a lead nobody knows about.
  • Round robin is not fairness. Equal shares ignore holidays, workload and specialism; a rotation needs rules for absence like any other route.
  • Rules that look right in settings may not work on records. Only a test lead followed to its owner proves a route.

More terms to look up

Where this term is used

Related