Salesforce lead routing for SaaS teams
We set up Salesforce lead assignment that sends each lead to the right owner by territory, segment or rotation, matches leads to existing accounts, and alerts reps immediately. We agree those matching and assignment rules with your team before anything goes live.
Native options
Salesforce covers lead assignment on its own, using assignment rules, queues and Flow.
- 01
Lead assignment rules
Rules that read a lead's fields and send it to an owner or queue when a condition matches
- 02
Queues
Pools of unassigned leads a team works from, or that rules route into by segment or region
- 03
Flow
Automation that runs custom assignment logic, such as rotation across a defined group of owners
Lead-to-account matching
Matching each new lead to an existing account first keeps known accounts with the owner who already has them.
- 01
Match on company or domain
Each incoming lead is checked against existing accounts by company name or email domain
- 02
Assign to the current owner
A matched lead goes to the owner of that account rather than into the general rotation
- 03
Fall back to the rules
Leads with no account match are assigned by the territory or rotation rules instead
How to set up lead assignment rules in Salesforce
Lead assignment in Salesforce starts with ordered rule entries, clear owners and tests for every lead source.
- 01
Define the rules
Agree territory, segment and source criteria, the order they run in, and the fallback owner.
- 02
Prepare owners and queues
Confirm the receiving users are active. Create lead queues and add the team members who should work from them.
- 03
Create an assignment rule
In Setup, search for Lead Assignment Rules, select New, name the rule and save it.
- 04
Add ordered rule entries
Add criteria and assign each matching entry to a user or queue. Salesforce evaluates entries in order and uses the first match; add an email template if an assignment notification is needed.
- 05
Activate and configure intake
Activate the intended rule and confirm the default lead owner in Lead Settings. Manual entry must use Assign using active assignment rules; check the assignment-rule settings for each import or API integration separately.
- 06
Test before rollout
Create test leads for each territory, an overlapping match and no match through every intake path. Verify ownership, fallback behavior and alerts, and check that later updates do not unexpectedly reassign leads.
When Salesforce's native lead routing isn't enough
We add lead routing automation in Flow or n8n when ordered assignment rules cannot cover the required data, rotation or cross-system logic.
- 01
Enrichment before assignment
Company and contact data is added first, so the rule uses firmographics and ICP fit rather than the raw form fill
- 02
Routing across multiple systems
When a lead must update more than Salesforce, a single run can write to every system involved
- 03
Availability and round robin
Assignment rules do not rotate owners on their own. Use Flow or a routing tool for rotation, capacity checks, absence coverage and escalation.
Related services
The same routing rules apply whether they run inside Salesforce or in an automation layer above it.
Salesforce lead routing FAQ
These are the questions we answer most often before setting up routing in Salesforce.
Do Salesforce assignment rules support round robin?
Not on their own. Round robin is usually built with Flow or a routing tool.
What is the difference between a lead and a contact in Salesforce?
A lead is an unqualified prospect. A contact belongs to an account, usually after qualification.
Can routing use territories?
Yes, by region, segment, or account size.
Start with a GTM Audit.
We review your Salesforce setup, ownership rules and lead sources, then define the routing your team needs.