Salesforce lead assignment rules automatically set the owner of a Lead to a user or a queue, based on criteria you define, such as country, lead source, or company size. You build them in Setup under Lead Assignment Rules: create a rule, add rule entries in priority order, and activate it. Salesforce checks the entries from the top down and assigns the lead using the first entry that matches. A lead that matches no entry goes to the Default Lead Owner.
This guide walks through the setup, example rules you can adapt, the limits, case assignment rules, and the reasons a rule doesn’t fire. The last part covers the routing work a rule can’t do on its own.
How lead assignment rules work
The mechanics are short enough to hold in your head:
- One active rule per object. You can create many lead assignment rules, but only one is active at a time. Activating a new one deactivates the old one (Salesforce: Set Up Assignment Rules).
- Rule entries run in sort order. Inside the active rule, each entry has criteria and an assignee. Salesforce stops at the first entry whose criteria match.
- Criteria or a formula. An entry either uses filter criteria on Lead fields (up to 25 per entry) or a formula that evaluates to true.
- Users or queues. The assignee is a single user or a queue. Queues let a group of reps pull from a shared list.
- Default Lead Owner catches the rest. Leads that match nothing go to the Default Lead Owner set in Lead Settings.
- The rule only sees what is on the record. It reads the Lead’s fields at the moment it runs. Data that arrives a minute later plays no part in the decision.
Which leads the rule runs on
Most “my rule isn’t working” problems come from this table. Whether the active rule runs depends on how the Lead enters Salesforce.
| How the Lead is created | Does the active rule run? |
|---|---|
| Created or edited by a user in Salesforce | Only when Assign using active assignment rule is selected on the create or edit page |
| Web-to-Lead form | Yes. With no active rule, web leads go to the default owner in Lead Settings |
| Data Import Wizard | Only when you choose to apply the active assignment rule during the import |
| REST API | Yes, by default. The Sforce-Auto-Assign header can turn it off or name a specific rule |
| SOAP API | Only when the call sets the AssignmentRuleHeader |
| Bulk API 2.0 | Only when the job is created with an assignmentRuleId |
| Apex | Only when the code sets the assignment rule option through Database.DMLOptions |
| Marketing automation and enrichment connectors | Depends on which API the connector uses and how it is configured. Check each one |
How to set up lead assignment rules in Salesforce
You need the Customize Application permission to create or change assignment rules. Salesforce lists the editions that include them on its Set Up Assignment Rules page.
Before you click anything, write the routing plan as a short table: which leads go where, in what order, and where unmatched leads land. Put exclusions (partners, existing customers, junk) at the top, specific segments in the middle, and broad territory rules at the bottom. Then:
- Create the queues you will assign to. In Setup, search for Queues, click New, add Lead as a supported object, and add the members.
- Open Lead Assignment Rules. In Setup, type “Lead Assignment Rules” in the Quick Find box. It sits under Feature Settings > Marketing.
- Create the rule. Click New and name it for its purpose (“Inbound Lead Routing v3” beats “Lead Rule”). To make it live now, select the checkbox that sets it as the active lead assignment rule, then save. Activating it deactivates whichever rule was active before.
- Add a rule entry. Click the rule name, then New in the Rule Entries section.
- Set the sort order. Enter the number that sets where this entry sits in the evaluation order. Most specific entries get the lowest numbers.
- Define the criteria. Choose whether the entry runs when criteria are met (pick field, operator, and value for each filter) or when a formula evaluates to true.
- Pick the assignee. Select the user or queue that gets the lead. Optionally choose an email template to notify the new owner. Save, then repeat for every entry.
- Add a catch-all entry last. An entry with no criteria at the bottom of the list sends every remaining lead to a triage queue you control.
- Set the Default Lead Owner. In Setup, open Lead Settings and choose an active user or queue. This is the safety net for anything the rule doesn’t place.
- Expose the assignment checkbox. On the Lead page layout, open Layout Properties and set the assignment checkbox to show on the edit page, and to be selected by default if you want manual leads routed. If Dynamic Forms is on for Leads, enable the option on the Lightning record page instead.
- Test before real inbound hits it. Create test leads that should match each entry, plus a few that should fall through, and confirm every owner.
Salesforce lead assignment rule examples
A working rule for a small B2B sales team might look like this:
| Sort | Criteria | Assign to |
|---|---|---|
| 1 | Existing_Customer__c equals TRUE | Account Manager queue |
| 2 | LeadSource equals “Partner Referral” | Partner Channel queue |
| 3 | Company equals “Test” OR Email contains “@example.com” | Junk queue |
| 4 | Country in (United Kingdom, Ireland) | EMEA Inbound queue |
| 5 | Industry equals “Healthcare” AND NumberOfEmployees greater than 500 | Healthcare Enterprise queue |
| 6 | No criteria (catch-all) | SDR Triage queue |
Row 1 shows the catch. The rule can only route existing customers if something has already set Existing_Customer__c before the rule runs. Most useful routing depends on getting the right field onto the Lead first.
Other patterns sales ops teams build with assignment rules:
- Territory routing by Country, State, or a custom Region field.
- Demo requests to SDRs by matching a form field or Lead Source, so high-intent leads skip the nurture queue.
- Enterprise accounts to AEs by employee count or annual revenue.
- Product-line routing by a picklist on the form.
- A holding queue for poor-fit leads, so an SDR triages them before they use AE time.
Round-robin lead assignment in Salesforce
Assignment rules don’t include round-robin. The common workaround uses two custom fields and one entry per rep:
- Add an auto-number field to Lead.
- Add a formula field that returns the remainder of that number divided by the number of reps, for example
MOD(VALUE(Lead_Number__c), 3)for three reps. - Add one rule entry per value (0, 1, 2), each assigning to a different rep, inside the territory that needs rotation.
It works, and it ignores everything a sales manager cares about: who is on vacation, who already has 40 open leads, and who just left the team. Every change in team size means rewriting entries. Teams that need weighting or availability move rotation into Flow, Apex, an AppExchange router, or a workflow layer outside Salesforce.
Salesforce lead assignment rule limits
| Limit | Value |
|---|---|
| Active assignment rules per object | 1 |
| Rule entries per assignment rule | 3,000, of which up to 300 can be formula-based (Salesforce rules limits) |
| Filter criteria per rule entry | 25 |
| Evaluation | Top to bottom, first match wins |
What the rule doesn’t do at all:
- Capacity and availability. No built-in workload balancing, PTO handling, or round-robin (Salesforce: Guidelines for Assignment Rules).
- SLAs and escalation for leads. Cases have escalation rules. Leads have nothing comparable.
- Re-routing when data changes later. Existing leads aren’t re-evaluated unless someone edits them with the checkbox selected.
- Data from outside Salesforce. Enrichment, intent, and product usage only count if they are written to the Lead before the rule runs.
Case assignment rules in Salesforce
Case assignment rules use the same engine for Cases. You find them in Setup by searching for Case Assignment Rules, and only one case rule can be active at a time. Entries are checked in order and assign the case to an agent or a support queue. They run on cases from Web-to-Case, Email-to-Case, and manual creation when the assignment checkbox is selected. Cases also get escalation rules, which reassign or notify when a case sits open past a time limit.
Why your lead assignment rule is not firing
When a rule is configured and leads still land in the wrong place, work through this list in order:
- The rule is inactive. Activating a different rule deactivated it.
- An earlier entry is too broad. It catches leads meant for a more specific entry below it.
- The checkbox isn’t selected. Manual leads skip the rule when Assign using active assignment rule is hidden or unchecked on the layout.
- The lead came in through an API path that skips the rule. SOAP calls without the AssignmentRuleHeader, Bulk API jobs without an assignmentRuleId, or REST calls that set Sforce-Auto-Assign to false. Check the table above.
- The field the entry needs was empty. Enrichment or scoring wrote the value after the rule ran.
- The Default Lead Owner is wrong. It points to an inactive user or a placeholder admin, so unmatched leads disappear from view.
- Something reassigned the lead afterward. A Flow, Apex trigger, or connector changed the owner right after the rule set it.
- The criteria use the wrong value. A picklist value or country spelling doesn’t match what the form sends (“UK” versus “United Kingdom”).
The first three explain most cases.
Why native assignment rules strain as you grow
Most guides end at the limits table. The bigger problem is the assumption underneath the rule: everything it needs is on the Lead at the moment it runs. That holds for geography, source, and basic firmographics. It stops holding once your stack grows:
- Enrichment from tools like Apollo or ZoomInfo lands seconds or minutes after the lead is created.
- Scoring runs on its own schedule, so a lead’s score can change hours later. (Predictive models work this way too; see how predictive lead scoring works.)
- Reassignment for vacations, quota, and aging leads has no home in the rule.
- The rep never sees the assignment unless someone builds the notification.
Each gap can be patched with custom fields, Flow, Apex, or an AppExchange app. After a few patches the routing logic lives in five places and nobody can explain why a given lead went where it did. This is true of every CRM with a single-pass criteria engine, HubSpot and Dynamics included, because the rule only sees its own database at the moment it runs.
The work that remains sits between systems: the enrichment service, the CRM, the channel your reps work in, and the manager who decides the unclear cases. An orchestration layer is the category built for that work. It sits above the systems of record, listens for what they emit, gathers the context the rule didn’t have, and brings a person in where a judgment call is needed. FlowRunner is built for that layer.
Extending assignment rules with a workflow layer
Keep the native rule for the first assignment. Add a workflow around it for the rest:
- Enrich after create, then correct the owner if the answer changes. For example, a flow can enrich a new lead through Apollo and Salesforce, then reassign it if the company turns out to be an existing account.
- Tell the rep where they work. Post the new lead to the owner in Slack with the source, key fields, and a link to the record. The Salesforce and Slack lead handoff guide shows the build.
- Ask a person when ownership is unclear. FlowRunner uses human-in-the-loop, an execution pattern where AI agents pause autonomously, assemble the relevant context and the decision choices available, route to a human via their preferred channel, and resume the moment the human responds. When a lead matches two territories or lands in the catch-all, the SDR manager gets the question in Slack, email, WhatsApp, or by phone, and the flow assigns the lead once they answer.
- Run an SLA check. Flag leads that sit unworked past your window and escalate to the manager with the context attached.
- Catch duplicates before they are assigned twice. See Salesforce data hygiene for the pattern.
FlowRunner connects to Salesforce and to HubSpot, so the same routing pattern works if part of your funnel runs there (HubSpot leads into Slack). If you want to size the manual effort first, this guide to what’s worth automating treats it as a cost calculation.
Checklist before you ship a routing change
- Write the routing logic down in plain language. If it doesn’t fit in two paragraphs, it won’t be debuggable in six months.
- Confirm every path that creates Leads runs the rule: manual entry, Web-to-Lead, imports, and each integration.
- Set the Default Lead Owner to a real person or a monitored queue.
- Decide what triggers a reassignment and who owns that decision.
- Decide how reps hear about new leads and how SLAs are tracked.
- Test with sample leads for every entry and the catch-all.
Native assignment rules handle the first owner decision well. Build the rest around them so leads from APIs and late enrichment still reach the right rep, and so the routing logic stays in one place you can still explain a year from now. If you would rather have that routing built for you, our implementation team can set it up in your FlowRunner workspace.
Frequently asked questions
How do I create a lead assignment rule in Salesforce?
In Setup, search for Lead Assignment Rules, click New, name the rule, and save it. Open the rule, add rule entries with a sort order, criteria, and the user or queue to assign, then activate the rule. Finish by setting a Default Lead Owner for leads that match no entry.
Can you have more than one active lead assignment rule in Salesforce?
No. You can create several lead assignment rules, but only one can be active at a time. Put all your routing logic into rule entries inside that one active rule, up to 3,000 entries per rule.
Do lead assignment rules run on leads created through the API?
It depends on the API. The REST API applies the active rule by default unless the Sforce-Auto-Assign header turns it off. The SOAP API skips the rule unless the call sets the AssignmentRuleHeader, and Bulk API 2.0 skips it unless the job sets an assignmentRuleId.
What is the difference between lead and case assignment rules?
They use the same engine: one active rule per object, entries checked in order, first match wins. Lead rules assign Leads to sales users or queues; case rules assign Cases to support agents or queues and run on Web-to-Case, Email-to-Case, and manually created cases.