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

Templates

Lead Routing Rules Template

A lead routing rules template: each source and lead type, the account match, the assignment rule, owner and fallback, response target, rejected leads and tests.
Templateintermediate13 min readUpdated

What this template is for

Write the routing rules when inbound leads start passing from marketing to sales or to any other team, and rewrite the affected rows before a new form or source goes live, when territories are redrawn, when the scoring model changes and when someone joins or leaves. The inbound lead handling playbook runs lead handling as a shared motion, capture and enrich, route and assign, respond and qualify, nurture the not-ready and close the loop, with marketing operations owning the routing logic and checking the queues every day. This template is the written rule set that motion assumes. The lead routing QA checklist tests each route with test leads before it goes live; the rule set is the list it tests against.

Several neighbouring documents each supply one rule or check the result. The lead scoring model template sets scores and thresholds and says where a lead is routed at each; this rule set records which routes depend on a score and which version. The nurture sequence plan template plans the sequences that take leads not yet ready. The lead management audit scorecard scores routing and response at one moment, and its findings are a good reason to rewrite a row. The tutorial on reassigning CRM records when someone leaves moves routing slots when someone goes. And when the complaint is that leads are never contacted, the diagnosis of sales not following up on leads checks routing before effort; the rule set is the first thing it will ask to see.

The template

Copy the table into a spreadsheet and turn the field names into columns, one row per route. A route is one source and lead type with one assignment rule, so a single form that sends demo requests and content downloads to different people is two rows.

FieldWhat to write
Source and formEach form, lead form, call or chat source, and the hidden fields and source values it passes to the CRM
Lead type and stageWhat the person asked for, such as a demo request or a content download, and the stage the record enters at
Existing account checkHow the record is matched to an existing company, contact or open deal before assignment, and who keeps a matched record
Assignment ruleThe rule that picks the owner, by lead type, territory, company size or existing account ownership, written simply enough to explain
Score dependenceWhether the route depends on a score or threshold, and which version of the scoring model it uses
Owner, fallback and coverThe owner or queue for each route, the fallback queue someone checks and the deputy or team queue that receives leads and alerts during absence
Response target and alertThe response target agreed with sales for the route, the task and notification created, and where the response is measured
Rejected and recycled leadsWhere leads rejected by sales go, the reason recorded, and the nurture that takes those not ready, with marketing as the default owner
Leavers and territory changesWhat happens to routing slots, queues and owned records when a seller leaves or a territory changes
Rule owner, test and change recordWho owns each rule, when it was last tested with test leads, and the dated record of each change

Above the table, keep the date of the last full test, the name of the person who owns the rule set and a link to the service levels agreed with sales. Below it, keep a short list of the fallback queues and who checks each one.

How to fill each section

Source and form

List every way a lead arrives: each website form, each native lead form on an ad platform, calls, chat and any list import. For each, write the hidden fields it fills and the source values it passes. The guide to connecting the CRM to ads and analytics sets out what a form should capture and persist, campaign parameters, click identifiers, landing page, referrer, form name and timestamp, and why forms that do not pass hidden fields break the loop back to the platforms. The playbook adds that a lead without a source cannot be credited later, so a row whose source values are blank is a row to fix before any rule is written.

Lead type and stage

Name what the person asked for, in their terms: a demo request, a quote, a content download, a support question, a partnership enquiry. Then write the Lifecycle Stage the record enters at. The guide to lead stages and the pipeline defines each stage with an entry definition, an exit criterion and an owner, agreed by both teams, and describes the hand-off as a workflow that changes the stage, assigns an owner by the agreed rule, creates a task and notifies the owner. Lead type is the field that most often decides the route, since the playbook routes a demo request and a content download differently, and some enquiries, such as support questions, should never reach sales at all.

Existing account check

Write how the record is matched to an existing company, contact or open deal before it is assigned, and who keeps a matched record. The guide to matching contacts to company records explains why this comes first: routing sends people to the owner of the company they are attached to, so a wrong match sends a lead to the wrong seller. It sets out the cases, a domain that matches no record, a subsidiary sharing the parent's domain, a personal address waiting in a review queue, and says the matching and routing rules must be designed together, with each exception written as a rule. Record the match rule, the review queue for records that cannot be matched and its owner, and the rule for a matched record: the account owner keeps it, or another seller takes it with the account owner told.

Assignment rule

Write the rule that picks the owner in a sentence anyone in sales could repeat. The inbound lead handling playbook lists the usual bases, lead type, territory, company size and existing account ownership, and is plain that simple rules everyone understands beat clever rules nobody can explain. Where a rotation shares leads among a team, name the group and its members. Order the rows so that the most specific rule, such as an existing account owner, is read before the general one, and say what happens to a lead that matches no rule; the routing checklist tests exactly that case with a test persona that matches nothing. When live leads from known accounts still land with the wrong seller, the diagnosis for leads assigned to the wrong salesperson reads one back through its owner history and these rows in order to find the match, rule or group that chose it.

Score dependence

Say whether the route depends on a score or threshold, and if so which version of the scoring model it reads. The lead scoring guide describes thresholds as the score at which something happens, a contact entering nurture, being flagged for sales or being routed to an owner, and argues that a declared action such as a demo or quote request should be routed at once regardless of score. Write "none" for routes that do not depend on a score, and for those that do, name the threshold by reference to the lead scoring model template and its version, rather than copying the number here, so that a change to the model shows which routes need retesting.

Owner, fallback and cover

Name the owner or queue for the route, the fallback queue and the person who checks it, and the cover during absence. The playbook's rule is that every route needs a fallback: if the assigned person is away, the lead goes to a named queue that someone checks. The guide to sales alerts from marketing activity adds that a deputy or a team queue should receive alerts while the owner is away, and that the routing fields that decide lead routing should be the same ones that decide alert recipients. Write the owner, the fallback queue, who checks it and when, and the deputy or team queue in this field, and make sure the alert rule reads the same fields.

Response target and alert

Write the response target agreed with sales for this route, the task and notification the route creates, and where the response is measured. The target comes from the business's own SLA, which the guide to sales and marketing alignment describes as covering the time within which a lead is accepted or returned, the Lead Response Time and the attempts that follow. The playbook reserves the fastest targets for the highest-intent requests. This page sets no figure; if the two teams disagree about what speed is worth, the lead response time test routes leads at random to an immediate-response rota or the standard queue and reads meetings held per lead. Note the report where response by route is read, since the playbook measures it every day.

Rejected and recycled leads

Write where leads go when sales rejects them or finds them not ready, the reason recorded and the nurture that takes them. A lead accepted by sales becomes a Sales-Accepted Lead; one rejected needs a route back. The playbook asks for reason codes rather than "bad lead", for not-ready leads to return to marketing with their reason code, and for marketing to be the default owner of any lead with no other owner. The guide to nurture sequences has leads that sales rejects come back with a reason that feeds the scoring model, and the nurture sequence plan template records the sequence each reason enters. Name the sequence and the signal that brings a nurtured lead back to sales.

Leavers and territory changes

Write what happens to the route's slots, queues and owned records when a seller leaves or a territory changes. The tutorial on reassigning CRM records when someone leaves takes the person out of routing and round-robin groups, moves their records by the written owner rules, sends a test lead through each affected route and records the handover in the change log. Its warning is the reason this field exists: routing can keep working perfectly while sending leads to someone who has gone. For a territory change, name who redraws the rule, who agrees it in sales and which rows must be retested.

Rule owner, test and change record

Name the owner of each rule with a deputy, the date of its last test with test leads, and a link to its change record. The guide to automation governance treats routing as one of the actions a workflow takes and asks for a named owner with a deputy, testing before activation, a change log with the date, the person, what changed and why, and a way to roll back. Test each route with the lead routing QA checklist before it goes live and after any change underneath it. Where several teams build, approve, test and are told about routing changes, a short RACI matrix with one accountable role per rule keeps the ownership clear.

Filled example

Below, the rule set is completed for an invented business. The routes, times and names are illustrative and are not benchmarks.

Illustrative example — not a real result

Fobrunk Lifts: lead routing rules

Fobrunk Lifts is an invented firm that installs and maintains passenger lifts in offices and apartment buildings, with 3 service regions, a service desk, a sales team of 4 and a projects team of 2. Its marketing coordinator owns the rule set and wrote it after a breakdown call sat in a sales queue over a weekend. Four of its routes are shown.

FieldRoute 1: breakdown callRoute 2: maintenance contract enquiryRoute 3: new-installation quoteRoute 4: guide download
Source and formWebsite "report a fault" form and the phone line; hidden fields for page and form nameWebsite "maintenance contract" form; source, campaign, landing page and form name passed as hidden fieldsWebsite quote form and an ad platform lead form; source, campaign and click identifier passedGuide download form; source and campaign passed
Lead type and stageService request; never enters the sales pipelineContract enquiry; enters as lead, moves to MQL on submissionQuote request; enters as MQLContent download; enters as lead
Existing account checkMatched to the site record by postcode and building name; unmatched calls go to the service desk queue for reviewMatched by company domain and site address; if the site already has a contract, the account owner keeps itMatched by company domain; an existing customer's quote goes to the account owner with projects toldMatched by email; existing customers flagged and excluded from sales routing
Assignment ruleAlways to the service desk, never to salesUnmatched: by region of the site address to that region's sellerTo the projects team rotation (2 estimators)No assignment; enters nurture
Score dependenceNoneNoneNoneYes: hand-off to the region's seller at the threshold in scoring model v3
Owner, fallback and coverService desk; out of hours to the on-call engineer queue, checked every hourRegion seller; fallback: the "contract enquiries" queue, checked twice daily by the sales coordinator; deputy named per regionProjects rotation; fallback: projects manager; deputy when both estimators are away: the sales directorMarketing coordinator; fallback: the marketing queue, checked daily
Response target and alertAcknowledged within 1 hour, 24 hours a day; task and text message to the engineer on call; measured in the service desk reportFirst call within 4 working hours; task and email to the seller; measured in the weekly response reportFirst contact the same working day; task and email to the estimator; measured in the weekly response reportNo sales target; once routed at threshold, the contract enquiry target applies
Rejected and recycled leadsNot applicableRejected with a reason code; "not ready, contract ends next year" goes to the renewal nurture, owned by marketingRejected with a reason code; "budget not approved" goes to the projects nurture, owned by marketingNot applicable until routed
Leavers and territory changesService desk rota updated by the service managerWhen a region changes hands, the slot moves to the new seller, records move by the written owner rule, and routes 2 and 4 are retestedEstimator removed from the rotation on their last day; test quote sentRetested when scoring model changes version
Rule owner, test and change recordService manager, deputy: marketing coordinator; tested 3 March; change log row 14Marketing coordinator, deputy: sales coordinator; tested 3 March; rows 11 and 15Marketing coordinator, deputy: projects manager; tested 3 March; row 12Marketing coordinator, deputy: sales coordinator; tested 3 March; row 13

In May the north region's seller left. The coordinator moved the north slot to the sales coordinator as interim owner, sent a test enquiry for a north site through route 2 and a test download over the threshold through route 4, found the alert still going to the leaver's address, fixed it and logged the change before the leaver's account was closed.

Common mistakes

  • Rules nobody can explain. Logic built up in layers breaks silently when someone leaves or a territory moves. Write each rule in a sentence, and simplify any that cannot be written that way.
  • No fallback, or a fallback nobody checks. A queue that nobody reads is the same as no fallback. Name who checks it and when.
  • Alerts and routing reading different fields. When the rule that assigns the lead and the rule that alerts the owner disagree, the lead reaches one person and the alert another. Use the same fields for both.
  • Assignment before matching. Routing a lead before it is matched to an existing account sends it to the wrong seller and splits the customer. Match first, then assign.
  • Every request treated as a sales lead. Service requests, job applications and supplier pitches routed to sales waste their time and leave the person waiting. Give them their own routes.
  • Response targets copied from elsewhere. A target that sales never agreed is not measured and not met. Take it from the agreement both teams signed.
  • Rejected leads with nowhere to go. Leads rejected without a route back simply vanish. Make marketing the default owner and record a reason.
  • Leavers removed from the CRM before routing. Deactivating a seller first can break the routes that name them. Take them out of routing, test, then close the account.
  • Rules changed without a test or a record. A routing change that is not tested and logged is found by a customer. Test with test leads and log every change.

The lead scoring model, the nurture sequence plan and the other planning documents are in the templates library.

Frequently asked questions

Why write lead routing rules down if the CRM already holds them?

Because the CRM holds the rules as settings, not as decisions anyone can read. Assignment rules spread across workflows, round-robin groups and queues are hard to review, and when the person who built them leaves, nobody can say why a lead went where it did. A written rule set, one row per route, lets sales and marketing agree the routes, gives the routing test a list to check against, and shows what has to change when a seller leaves or a territory moves.

What is a fallback queue and why does every route need one?

A fallback queue is where a lead goes when the route's rule cannot place it: the owner is away or has left, no territory matches, or a field the rule depends on is empty. Without one, those leads sit unassigned or in the inbox of someone who will never read it, and nobody notices until a customer complains. The fallback only works if a named person checks it on a set routine, which is why the template records who checks it as well as where it is.

Who should own the lead routing rules?

Usually marketing operations, or whoever administers the CRM, owns the rules and the systems that run them, while sales agrees the routes and confirms that test leads reached the right person. Each rule still needs a named owner, a deputy and a record of when it was last tested and changed. Where several teams touch routing, a simple responsibility matrix for building, approving, testing and being told about a change avoids two people each assuming the other has it.

Terms used on this page

Frameworks

Where this page is used

Also related

Related