Salesforce Lead Routing SOP
A Salesforce Lead Routing SOP that shows exactly how to review inbound leads, apply routing criteria, assign ownership, and escalate exceptions without missing SLA timing.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: B2b Saas · Professional Services · Manufacturing · Healthcare Services
Overview
This Salesforce Lead Routing SOP template defines how an inbound lead moves from review to ownership in Salesforce, including criteria matching, assignment, SLA verification, reassignment handling, stakeholder notification, and exception escalation. It is designed for teams that need a repeatable process for deciding who owns a lead and when that ownership must be confirmed.
Use this template when lead volume is high enough that manual, ad-hoc assignment creates delays, duplicate outreach, or missed follow-up windows. It is also useful when routing depends on territory, product line, account tier, source, language, or lead score. The SOP gives the operator a clear sequence of steps, plus verification points for timing and ownership so the team can spot deviations before they become non-conformances.
Do not use this template as a substitute for designing the routing rules themselves. If your criteria are still changing every day, or if the lead data is too incomplete to make a reliable assignment, the process will need a decision owner and escalation path before it can run cleanly. It is also not meant for broad sales process management; it is specifically for the lead routing handoff and the records that prove the handoff happened.
Standards & compliance context
- This SOP supports ISO 9001-style documented information practices by making routing decisions, ownership changes, and exceptions traceable.
- If lead handling includes regulated customer data, the template can be adapted to match internal privacy, access control, and retention requirements.
- The verification and escalation steps help teams maintain consistent process control, which is useful in audited sales operations environments.
- If routing affects service commitments, the SLA timing checks can be aligned with internal service management practices and documented response targets.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Steps
This section matters because it defines the exact routing workflow, from record review through escalation, so ownership changes are consistent and auditable.
-
Review the inbound lead record
The Salesforce administrator or routing specialist opens the new lead record and verifies the minimum routing fields are populated, including lead source, geography, product interest, company size, and priority flags. The actor confirms the record is eligible for routing and notes any missing or conflicting data.
-
Match the lead to the routing criteria
The routing specialist compares the lead attributes against the approved routing criteria and determines the correct owner, queue, or territory. The actor applies the most specific matching rule first and documents the rule used when multiple criteria could apply.
-
Assign the lead in Salesforce
The Salesforce administrator updates the lead owner or queue assignment in Salesforce and confirms the assignment is saved successfully. The actor ensures the assignment timestamp is recorded and that the lead is visible in the correct work queue or owner view.
-
Verify SLA timing and response ownership
The sales operations lead verifies that the assignment occurred within the required SLA window and that the assigned role is responsible for the next customer response. If the SLA is at risk or already breached, the actor records the deviation and triggers escalation.
-
Handle reassignment requests
The sales manager reviews any reassignment request, ownership conflict, or territory dispute and determines whether the request is valid under the routing policy. The actor documents the reason for reassignment, updates Salesforce if approved, and rejects requests that do not meet policy criteria.
-
Update ownership and notify stakeholders
The Salesforce administrator updates the lead owner or queue and notifies the affected sales representative, manager, or queue owner of the reassignment. The actor confirms the new owner acknowledges receipt when required by the SLA.
-
Escalate routing exceptions
The sales operations specialist escalates unresolved routing conflicts, missing data, duplicate assignments, or policy exceptions to the designated manager or system owner. The actor records the issue, the impact on SLA, and the corrective action required.
How to use this template
- 1. The sales operations owner reviews the template sections and configures the routing criteria, SLA target, escalation path, and notification recipients for the team.
- 2. The assigned operator checks each inbound lead record for required fields, source, territory, product fit, and any data gaps that could affect routing.
- 3. The operator matches the lead to the documented routing criteria, assigns the correct owner or queue in Salesforce, and verifies that the record reflects the change.
- 4. The operator confirms SLA timing, records the response owner, and sends the required notification to the rep, manager, or queue watcher.
- 5. The operator handles reassignment requests by validating the reason, updating ownership, and escalating any exception that falls outside the approved routing rules.
Best practices
- Define the routing criteria in the SOP before the team starts using it, and keep the criteria aligned with the actual Salesforce fields in use.
- Require the operator to verify ownership after every assignment or reassignment so a stale record does not create a missed follow-up.
- Use a single escalation path for exceptions such as missing territory, conflicting account ownership, or incomplete lead data.
- Document the SLA start point and stop point clearly so timing checks are consistent across shifts and managers.
- Keep reassignment requests tied to a reason code so recurring routing problems can be reviewed later.
- Notify the next owner only after the Salesforce record has been updated, not before.
- Review routing exceptions regularly and convert repeated manual decisions into explicit criteria or automation.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this Salesforce Lead Routing SOP cover?
It covers the full handoff from inbound lead review through routing criteria matching, assignment in Salesforce, SLA verification, reassignment handling, stakeholder notification, and exception escalation. It is meant for teams that need a repeatable process for lead ownership, not a generic CRM checklist. Use it when routing decisions affect response time, territory coverage, or queue ownership. It also helps document who is responsible when a lead does not fit standard rules.
Who should run this SOP?
This SOP is usually run by sales operations, revenue operations, a sales development manager, or a designated lead router. In smaller teams, a competent person with Salesforce access and routing authority can own it. The key is that the role understands the routing criteria, escalation path, and SLA expectations. Ownership should be explicit so reassignment requests do not create delays or duplicate follow-up.
How often should lead routing be checked?
Lead routing should be checked continuously during business hours and reviewed at a defined cadence, such as daily or per shift, depending on volume. High-volume teams often add a monitoring step for unassigned or stale leads. The SOP should also define when SLA timers start and what counts as a deviation. If routing rules change often, a scheduled review of the criteria is important.
Does this template help with SLA compliance?
Yes, the template includes a step for verifying SLA timing and response ownership so the team can see whether the lead was assigned within the required window. That makes it easier to spot delays before they become missed follow-ups. It also supports documented information practices by keeping the routing decision and owner change traceable. If your organization tracks service levels internally, this SOP gives you a clear audit trail.
What are the most common mistakes in lead routing?
Common mistakes include routing from incomplete lead data, using outdated territory rules, assigning to the wrong queue, and failing to confirm ownership after reassignment. Another frequent issue is notifying stakeholders before the record is actually updated in Salesforce. Teams also miss exceptions when a lead falls outside normal criteria, which creates delays and duplicate work. This SOP is designed to surface those failure points early.
Can this SOP be customized for different routing models?
Yes, it can be customized for territory-based routing, round-robin assignment, account-based routing, product-line routing, or queue-based triage. You can add fields for region, company size, industry, source, or lead score depending on your rules. The structure stays the same even if the criteria change. That makes it easy to adapt while keeping the verification and escalation steps intact.
How does this compare to ad-hoc lead assignment?
Ad-hoc assignment depends on memory, inbox messages, or whoever sees the lead first, which makes ownership inconsistent and hard to audit. This SOP turns routing into a documented process with clear steps, verification points, and escalation criteria. That reduces missed leads, duplicate outreach, and confusion during reassignment. It is especially useful when multiple reps, territories, or queues are involved.
Can this template connect to other tools or workflows?
Yes, it can be paired with Salesforce automation, Slack or email notifications, lead scoring tools, and service desk or ticketing workflows for exceptions. If your team uses routing rules in Salesforce, the SOP can document the trigger conditions and the manual fallback steps. It also works well alongside onboarding checklists for new sales reps and sales operations runbooks. The goal is to make the handoff visible across systems, not just inside the CRM.
Related templates
Ready to use this template?
Get started with MangoApps and use Salesforce Lead Routing SOP with your team — pricing built for small business.
