Lead routing exception playbook for lean sales teams
A practical way to catch, assign, and learn from leads that fall outside normal routing rules.
lead routing exception playbook
A routing rule works until a lead arrives with two territories, an unknown company, a missing product interest, or an owner who is away. Those cases should enter one visible exception queue. Email threads and private messages make the same lead look unowned to everyone else.
Give the queue a named coordinator and a response window. The coordinator checks the source record, preserves the original submission, and assigns a temporary owner when the final decision needs more context. The coordinator does not change territory policy while clearing a live request.
Sort the exception before assigning it
Use a short reason list such as missing data, conflicting territory, duplicate account, capacity limit, or unsupported segment. Add free text only when the list cannot explain the case. A clean reason field lets the revenue operations owner see repeated failure patterns without rereading every note.
Keep the buyer's stated need beside the exception. A technically correct reassignment can still produce a poor handoff when the new owner receives only a name and email address. Preserve the campaign, requested action, relevant account history, and time the request first reached the team.
Choose a temporary owner
When ownership is disputed, speed and permanence are separate questions. Give the next response to a temporary owner who can serve the buyer now. Put the account-policy question in a separate review with a deadline. That keeps an internal disagreement from becoming the buyer's waiting room.
Require an explicit acceptance
The receiving rep should accept or return the lead with a specific reason. Silence is not acceptance. If the rep is unavailable, the coordinator uses the documented backup path rather than waiting for a manager to notice the delay. The buyer should not have to submit another form.
Review returned leads weekly. A genuine mismatch belongs back with the routing owner. A data problem belongs with the system or form owner. A coaching issue belongs with the sales manager. Sorting the causes prevents every routing complaint from becoming an argument about the assignment model.
Read the exception ledger
Count exception reasons, time to ownership, returns, and duplicate touches. Look for a stable pattern before changing the main rule. One unusual enterprise inquiry may justify careful handling without proving that the territory structure is broken for the rest of the market.
When a rule changes, save the old condition, the new condition, the decision owner, and the effective date. Test known examples before release, then watch the exception queue for a week. A useful repair reduces a named failure without creating a quieter failure elsewhere.
Test the repaired route
Replay a small set of known examples before publishing the rule: a clean match, a duplicate, an absent owner, and the exception that prompted the change. Record where each one lands. The test belongs with the rule record so the next editor can see what the team meant to preserve.
Sources
- Manage Leads, Salesforce Trailhead. Explains lead qualification and routing by criteria such as territory, deal size, and product.
Related GTM guides
Frequently asked questions
Who should own the exception queue?
Assign a coordinator who can inspect records and apply documented rules. Territory design, capacity policy, and disputed account ownership stay with the accountable revenue leader.
Should every unusual lead change the routing rules?
No. Resolve the live case, label the reason, and look for a repeated pattern. Change the main rule only when the evidence shows a consistent failure.