First, read one misrouted lead back through its record history and the rules in order
Start with one lead that reached the wrong person: one an account manager complained about, or one a seller passed to a colleague. Settle what the right owner was from the written rule set, not from whoever complained. The lead routing rules template writes one row per route with its existing account check, assignment rule and fallback; if no such document exists, nobody can say which owner was wrong, and writing the rows is part of the fix.
Then collect, as they stood at the moment of assignment, the owner field's history (which person, workflow or integration set each value, and when), the company record the contact was attached to with its domain and owner, every other record holding the same address or domain, the raw and clean values of every field the rules read, and the rules in the order the workflow actually reads them, which is not always the order the document lists.
Now ask why, and keep asking. The five whys moves from the failure people noticed to the condition that allowed it, with evidence behind each answer, and ends at something the team can change (a process, a rule or a check) and never at a person. The regional seller received the lead because the rotation assigned it. The rotation assigned it because the existing-account rule found no owner. It found none because the contact sat on a different company record from the customer's, and it sat there because matching trusted an email domain several organisations share, which nobody had listed as shared. The fix belongs at that last answer; "the seller should have checked" fixes nothing.
The method follows one path, and misrouting often has several. Once the first chain is complete, read a sample of recent leads reassigned by hand through the same questions. If they share the step, the first chain found the main fault; if they split, each group is a cause of its own, and the table sorts them.
This page starts where the owner field holds a present, active person who is simply not the right one. A lead that reached no owner, sat with someone who has gone or was never worked belongs to the diagnosis of sales not following up on marketing leads, and a routing workflow that assigned nobody to the diagnosis for a CRM workflow that is not running.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Leads from a known account reach the rotation or another account's owner | The company the contact sits on, its domain and owner, and whether the address is personal or shared | The contact is matched to the wrong company record, or to none, so it inherits another account's owner or falls to the rotation | Correct the match; list shared domains; send personal addresses to review |
| The contact sits on the right company, yet a territory or rotation seller received the lead | The order the workflow reads its rules in, and which rule caught the lead | A general territory or rotation rule is read before the existing-account rule, so the first match wins and the account owner never sees the lead | Read the existing-account rule first, with a fallback at the end |
| Leads from one country, region or size band land with the fallback or the territory next door | The raw and clean values on the lead against the values the rule lists | The country, region or size value arrives in a spelling the rule does not list, so the lead falls through to a fallback or a neighbouring territory | Route on a standardised clean field; send unknown values to review |
| Leads reach someone who moved team, or follow a redrawn territory map | Each rotation group's members and each rule's territories against today's team | A territory, team or rotation changed, or someone left, and the routing groups and rules still describe the old arrangement | Update groups and rules on the day of the change and test each route |
| The lead's record has a different owner from the record the account owner works | Every record holding the address or the domain | A duplicate contact or company with a different owner catches the lead before the record the account owner works | Merge by written rules and close the entry point that made the copy |
| The owner history shows the right person first and someone else later | Which user, workflow or integration wrote each owner value | The owner was set correctly and then rewritten by the sync or by a second workflow that also assigns | One owning system and one assigning workflow for the owner field |
Fix, verify and prevent each cause
A contact matched to the wrong company, or to none
Routing hands a contact to whoever owns their company record, so the guide to matching contacts to company records designs matching and routing together. A wrong match is confidently wrong; no match sends the contact past the existing-account check into the rotation. The guide's rules: personal addresses wait unmatched for review, in a queue a named person owns, and are routed by territory meanwhile; shared domains are listed and reviewed; every domain a company uses sits on its one record; subsidiaries that buy separately get linked records of their own. Accuracy is one of the principles the GDPR sets out, and a contact held against a company they do not work for is a record that is wrong about a person, so correct the match, not only the lead's owner.
Fix: move the contact to the right company, find every other contact the same rule matched the same way, list shared domains, add missing domains to their records, and deduplicate companies before rematching anyone.
Verify: a test sign-up from a customer's second domain reaches the customer's owner; one from a shared domain lands in review.
Prevent: keep the matching rules in the routing rule set's existing account check field, give the review queue an owner, and include personal-address and subsidiary leads among the test leads.
A general rule read before the existing-account rule
The first rule that matches wins. The lead routing rules template orders rows so the most specific rule, such as the account owner, comes ahead of broader rules, with a stated outcome for a lead that matches nothing. Put territory or a round-robin first and a customer's enquiry is caught by its region before the account rule is read: the usual way customer enquiries reach new-business sellers. The template also names assignment before matching as a mistake, since a lead assigned before it is attached to its company finds no account owner whatever the order. The playbook for inbound lead handling prefers simple rules everyone understands over clever rules nobody can explain, because complex logic breaks silently.
Fix: write the order down (open deal and existing account, written exceptions such as a product outside the account owner's range, territory and size, rotation, fallback), make the workflow read it that way, and let matching finish first.
Verify: test leads from an existing account in each territory reach the account owner, and every other test lead is resubmitted, because the lead routing QA checklist warns that correcting one rule often changes which rule catches another.
Prevent: record each row's position in the rule set and treat moving a rule as a change with an owner, a test and a dated record.
A territory value the rule does not list
A value spelled in a way the rule does not list fails silently. The tutorial on standardising CRM field values warns that an unexpected spelling of a country drops the lead to the fallback owner, or to no one, and names country and region among the fields territory routing reads. A region added to the form but not to the rule does the same. The tutorial keeps the raw value and maps it, from a table drawn from what the CRMThe system that stores an organisation's contacts, companies, deals and interactions, and the processes built around it. already holds, to a standard value in a separate clean field; it points routing at the clean field and sends unmapped values for review, where a fallback owner sees them.
Fix: map every field a routing rule reads, point each rule at the clean field, and use a picklistA CRM field type that accepts one value from a defined list of permitted values, so that records can be reported on instead of typed in many spellings. wherever the business controls the form.
Verify: a new spelling of a known country reaches its territory; an unmappable value reaches the fallback and the review queue.
Prevent: change the rule's value list in the same change as any form or region list, and name an owner for the review queue who adds each new spelling to the mapping table.
Groups and rules that still describe the old arrangement
Routing describes the team as it was when the rules were written. The tutorial on reassigning CRM records when someone leaves removes the person from all assignment rules and rotation groups, names who receives what they used to, reassigns their records under the written owner rules and tests each affected route. Its warning about bulk moves applies too: when a leaver's companies all go to one replacement, the existing-account rule then sends each customer's next enquiry to that person, correctly by the rules and wrongly by territory. The routing rules template gives territory changes their own field: the person who redraws it, the person in sales who signs it off, which rows are retested.
Fix: compare every group's members and every rule's territories with today's team, update both, and move company ownership by account, territory or segment.
Verify: a test lead for each affected territory and moved account lands with someone still on the team, with a task created and an alert sent.
Prevent: make routing groups a step in every joiner, mover and leaver process, and rerun the leaver tutorial's week-later check for leads that still went to the old arrangement.
A duplicate with a different owner
A lead lands on whichever record matching finds, and a second company record from an import, owned by another seller or by nobody, can catch a customer's enquiry first. The CRM fundamentals guide notes that the record sales works may not be the one marketing nurtures, and prevents duplicates by matching contacts on email and companies on their web domain wherever records are created. Its merge rules, written before the first merge, settle the owner: the owner of the open deal keeps the record; without one, the earlier owner does.
Fix: merge under those rules, then find the entry point that created the copy with the diagnosis for duplicate contacts in the CRM.
Verify: a test lead from the address lands on the surviving record and reaches its owner.
Prevent: keep the duplicate persona in every routing test and the named weekly pass over the merge queue that makes deduplicationRemoving double counts when one conversion is reported by more than one source. routine.
An owner rewritten after assignment
Sometimes routing was right and the history shows the account owner set first and someone else later. The guide to syncing the CRM and the marketing platform gives the record owner one owning system, the CRM, carried to the marketing platform in one direction; if both systems can write a field, nobody owns it and the last save wins. Inside the CRM the same fault is a second workflow that also assigns, such as a hand-off workflow setting an owner at qualification after routing set one at creation. The diagnosis for CRM values changing back after a sync adds imports that overwrite owners on a match.
Fix: make the marketing platform read-only for the owner field, leave assignment to one workflow per route, and stop imports overwriting owners.
Verify: a seeded record keeps its owner after the next sync, every other workflow and a test import.
Prevent: treat any new writer of the owner as a reviewable change, with integrations signed in as their own named users so the history names them.
Prevention: rules read in order, test leads after every change and a weekly look at leads reassigned by hand
Each cause above is a rule that drifted from the business it was written for. Three habits keep the rules written, tested and watched.
Rules read in order, from one written set. The routing rules template is the reference: one row per route with its account check, assignment rule, fallback, owner and last test date. Keep the matching rules in the same document and the row order identical to the order the workflow reads. The inbound lead handling playbook gives marketing operations ownership of the routing logic, and simple rules are the condition for spotting one read in the wrong place.
Test leads after every change, not only before a launch. The routing checklist's personas, a lead for each territory or segment, an unmatched lead and a duplicate of an existing contact, are the fixtures; add a lead from each key account, a personal address, a shared domain and a subsidiary. Resubmit the whole set after any change underneath the routes and read the resulting records, not the rules screen.
| Change | What it can misroute | Retest with |
|---|---|---|
| A new form, lead form or source | Leads whose values the rules do not list | A test lead per territory from that source, plus one that matches nothing |
| A matching rule or domain list change | Customers, shared domains and subsidiaries | Leads from a second domain, a shared domain, a subsidiary and a personal address |
| A rule added, removed or moved | Leads a more general rule now catches first | The full set of test leads |
| A redrawn territory or changed rotation | Leads for the old and new territories | A test lead per affected territory and moved account |
| Someone joins, moves team or leaves | Rotation slots and the accounts they owned | A test lead through every route that names them |
| A sync, import or workflow that writes the owner | Owners rewritten after assignment | A seeded record whose owner must survive |
A weekly look at leads reassigned by hand. Every lead a seller passes on is a misroute the rules made and a person corrected, so a report of owners changed by hand soon after assignment is the running measure of this problem. Add it to the weekly review the playbook runs with sales and group the rows by the step that chose the first owner; a group that grows names the step that reopened. A reason from a short list on each hand reassignment keeps misroutes apart from hand-overs for cover or workload, which are the sales manager's question. Each pass also delays the right seller's first contact, and the playbook reads lead response timeAverage time between a new lead arriving and the first contact from sales. by lead type in the same weekly review, so a run of hand reassignments is worth reading beside it.
The glossary entry for lead routing gives the short definition, the CRM section holds the matching, syncing and leaver guides, and the marketing automation troubleshooting hub routes neighbouring symptoms to the page that diagnoses them.
A floor cleaning machine supplier finds why key account leads go astray (illustrative)
Thrimbolex Floorcare
Thrimbolex Floorcare, an invented supplier of floor cleaning machines to facilities firms, schools and hospitals, has 5 regional sellers and 3 key account managers for its 40 largest customers. The key account managers complain that requests from their accounts reach regional sellers, who call long-standing customers as if they were new. The sales operations lead reads the 64 leads reassigned by hand last quarter back through their owner histories and the rules in the order the workflow reads them.
Three routes explain 58 of them. In 31, the contact sat on the right company with the right owner, but the regional rule sat above the existing-account rule. 19 came from 6 hospitals in one group sharing an email domain, all matched to a single company record owned by the regional seller who had won a contract at one of them. 8 went to a seller who had moved to key accounts 2 months earlier and was still in the northern rotation. The other 6 were 4 duplicate company records from a trade show import and 2 new spellings of a region.
The supplier moves the existing-account rule to the top with a fallback queue at the end, puts the hospital group's domain on a shared-domain list for review, updates the rotation, merges the 4 duplicates by its written rules and maps the 2 spellings. Of 14 test leads, 2 fail at first because the reordering exposed an old size rule that caught large schools early; both pass once it moves below the account rule. A weekly report of leads reassigned by hand falls over the next quarter from about 5 a week to 2 or 3 a month, each traced to its step.
Common mistakes
- Reassigning the lead and closing the complaint. The step that chose the wrong owner keeps choosing.
- Starting from the rules screen. The owner history shows which rule caught the lead and what changed it later.
- Stopping the chain at a person. The cause is a match, a rule, a value, a group, a duplicate or a writer.
- Putting the rotation or territory first. The existing-account rule is read before the general ones.
- Assigning before matching. A lead routed before it is attached to its company finds no account owner.
- Routing on free text. Route on a clean field and review the unknown values.
- Changing the team but not the rotation. Update groups and territories on the day of the change.
- Retesting only the route that changed. Rules are read in order; resubmit every test lead.
