The smarter way to route leads in Salesforce.

Test it for free for 30 days or get in touch if you’d prefer to chat.

Talk to us
Free trial

Fancy giving Distribution Engine a try?

Have a play around for free, or get in touch if you’d prefer to chat.

Install in Production
Free trial

How to Set Up Lead Assignment Rules in Salesforce (Step-by-Step)

Toms Krauklis
RevOps & Customer Success
October 29, 2026

Key takeaways:

🧱

A lead assignment rule is a container; rule entries do the work. Each entry pairs criteria with an assignee, and Salesforce checks entries in sort order until one matches.

🔢

Order is everything. Put the most specific entries first and a catch-all last. First match wins, and nothing below it is checked.

‍

☝️

Only one lead assignment rule can be active. All of your routing logic, for every source, lives inside one rule's entries.

‍

🔌

Rules don't fire on their own. Web-to-Lead triggers them automatically. Manual entry, imports and API integrations each need to be told to use them.

‍

🧪

Test before you trust it. Create a test lead for every entry, check the owner, and repeat after every change.

‍

Lead assignment rules are the first routing tool most Salesforce admins build, and for good reason. They're native, they're free and they're quick to set up. Configured well, they get every new lead to a sensible owner the moment it's created. Configured carelessly, they send leads to the wrong queue without any error message.

This guide walks through building a lead assignment rule from scratch: planning the logic, creating the rule, adding entries in the right order, making sure the rule actually fires, and testing it. At the end, we cover where assignment rules stop being enough and what teams usually do next.

‍

What are lead assignment rules in Salesforce?

Lead assignment rules are a native Salesforce feature that automatically sets the owner of a new Lead record. A rule contains numbered rule entries, each with filter criteria and an assignee (a user or a queue). Salesforce evaluates the entries in sort order and assigns the lead using the first entry whose criteria match.

A few rules of the road before you start:

  • One active lead assignment rule per org. You can save several, but only one runs.
  • Up to 3,000 entries per rule, and each entry can hold up to 25 filter criteria (or one formula).
  • Assignees are a single user or a queue. There's no rotation, weighting or capacity logic.
  • Rules run on creation, and on edit only if someone ticks Assign using active assignment rule. They don't re-run on field updates by themselves.

‍

Before you build: map your routing logic.

Ten minutes with a spreadsheet will save you hours of debugging. List every way leads enter Salesforce and the owner each one should end up with. For example:

{{map-routing-logic="/utility/matrix"}}

Two things to notice. First, the specific scenarios (partners, enterprise) sit above the geographic ones. Otherwise an enterprise lead from the UK would match entry 3 and never reach entry 2. Second, the last entry has no criteria. That's your catch-all, and every rule needs one.

Tip: Assign to queues rather than individual users wherever you can. When someone leaves or goes on holiday, you change the queue membership instead of editing the rule.

‍

Step-by-step: creating a lead assignment rule.

Step 1: Create your queues.

In Setup, search Queues and click New. Name the queue, add Lead as a supported object, add members (users, roles or public groups) and save. Repeat for each destination in your routing map, including a Lead Review queue for the catch-all.

Step 2: Create the rule.

In Setup, search Lead Assignment Rules and click New. Give it a clear, dated name (for example, Inbound Routing – Oct 2026). Tick Active if you want it live straight away; this deactivates whichever rule is currently active. Save.

Tip: Build and test a new rule while it's inactive, then switch it on. That way you can roll back to the previous rule by reactivating it.

Step 3: Add rule entries.

Open the rule and click New under Rule Entries. For each entry:

  1. Sort Order: the evaluation position. Start with 1 for your most specific scenario.
  2. Criteria: choose criteria are met and add field/operator/value rows (for example Lead: Country equals United Kingdom, Ireland; commas act as OR within a field). Or choose formula evaluates to true for logic that filter rows can't express.
  3. Filter logic: if you have several rows, add custom logic such as (1 OR 2) AND 3.
  4. Assignee: select a user or queue.
  5. Email template (optional): notifies the new owner.
  6. Do Not Reassign Owner (optional): leaves the current owner unchanged when the entry matches. This is useful for excluding certain leads from routing.

Save and repeat for every scenario in your map.

Step 4: Add the catch-all.

Create a final entry with the highest sort order and no criteria (or criteria every lead will meet). Assign it to your Lead Review queue. This is how you spot gaps in your logic, because unmatched leads become visible instead of falling to a default owner.

Step 5: Set your Default Lead Owner.

In Setup → Lead Settings, set the Default Lead Owner. This is the safety net if no entry matches, but with a catch-all in place it should rarely be used. If leads regularly end up here, your catch-all is missing or misconfigured.

‍

Step 6: Make sure the rule actually fires.

This is where most "my assignment rule isn't working" tickets come from. The rule is fine; it just never ran.

Assignment rules run What to configure
Web-to-Lead Yes, automatically Nothing, as long as a rule is active
Manual creation in Salesforce Only if the box is ticked Edit the Lead page layout → Layout Properties → show and/or default the Assign using active assignment rule checkbox
Data Import Wizard Only if selected Choose the assignment rule during the import
Data Loader / API Only if requested Set the assignment rule ID in Data Loader settings, or the AssignmentRuleHeader in API calls
Marketing automation / integrations Depends on the connector Turn on the "use Salesforce assignment rules" option (or equivalent) in the connector
Flow / Apex No, by default Needs Apex using Database.DMLOptions (can be wrapped as an invocable action for Flow)
Lead updated / status changed No Re-run via the edit checkbox, Apex, or a routing tool that re-routes on field changes

The last case matters more than it looks. If a lead is recycled, re-scored to MQL or has its territory field corrected, the assignment rule won't route it again without help.

‍

Step 7: Test every entry.

Create one test lead per entry, ticking Assign using active assignment rule, with field values designed to hit that entry and no other. Then:

  • Confirm the owner on each test lead.
  • Create an "edge case" lead that should fall through to the catch-all.
  • Create a lead that matches two entries and confirm the higher-priority one wins.
  • Delete your test leads (or exclude them with a naming convention) so they don't distort reports.

Repeat after every change. Adding a single entry in the wrong position can reroute a whole segment without anyone noticing.

‍

Best practices for assignment rules that last.

Keep entries single-purpose. One entry, one scenario. If you can't describe an entry in a sentence, split it.

Use picklists, not free text. Criteria on free-text fields like Country fail on "UK" vs "United Kingdom" vs "U.K.". Use State and Country picklists, or normalise the values before the rule runs.

Prefer queues over users. Changes in staff then become a membership edit, not a rule rebuild.

Document the sort order. Keep your routing map outside Salesforce and update it whenever the rule changes.

Report on the catch-all queue weekly. Every lead that lands there points to a gap in your logic.

Audit quarterly. Territories, teams and products change, and your rule needs to keep up. Our guide to auditing your Salesforce lead routing logic gives you a checklist.

For the most common ways rules go wrong, see Salesforce assignment rule mistakes.

‍

When lead assignment rules aren't enough.

Assignment rules decide which bucket a lead goes into. They can't decide which person in that bucket should get it, or what happens if that person doesn't respond. Most teams reach that point once they need:

  • Round robin across a team, rather than dropping leads in a queue for reps to claim
  • Workload balancing, so the rep with the fewest open leads gets the next one
  • Availability awareness, so nobody is assigned leads while on holiday or off shift
  • SLA reassignment, so untouched leads move on automatically
  • Account-based routing, so a lead from an existing customer goes to that account's owner
  • Re-routing on updates, such as MQL status changes, recycled leads or territory corrections
  • Visibility, meaning a record of why each lead went where it did

The usual next step is Salesforce Flow, which can handle most of these with enough custom fields, counters and scheduled paths. The trade-off is maintenance.

Distribution Engine is the alternative to building it yourself. It's a Salesforce-native routing app that keeps the criteria-based logic admins are familiar with, adds round robin, load balancing, availability, caps and SLA reassignment as configuration, and works across Leads, Contacts, Cases, Opportunities and custom objects. Many teams keep a simple assignment rule to decide the destination team and let Distribution Engine decide which person in that team gets each lead.

‍

The bottom line: build it in the right order, then make sure it fires.

A good lead assignment rule is a routing map turned into numbered entries: specific scenarios first, broad ones next, a catch-all last, and queues rather than people as assignees. Most "broken" rules aren't broken at all. They never ran, because an import, integration or Flow didn't ask them to. Check how each lead source triggers the rule, test every entry, and review the catch-all queue every week.

‍

Fancy giving Distribution Engine a try?

You can trial Distribution Engine for free, or get in touch if you'd prefer to chat.

Related articles

‍

Frequently asked questions.

How do I create a lead assignment rule in Salesforce?

In Setup, search Lead Assignment Rules, click New, name the rule and tick Active. Open the rule, add rule entries with a sort order, criteria and an assignee (user or queue), and finish with a catch-all entry that has no criteria. Test each entry with a test lead before relying on it.

How many lead assignment rules can be active in Salesforce?

Only one lead assignment rule can be active at a time. You can save several rules, but activating one deactivates the others. All of your routing scenarios must be built as entries inside that single active rule, which can hold up to 3,000 entries.

In what order are Salesforce assignment rule entries evaluated?

Entries are evaluated in ascending sort order, and Salesforce stops at the first entry whose criteria match. Put the most specific entries (named partners, enterprise segments) first and broad entries (whole regions) later, with a criteria-free catch-all last.

Why is my Salesforce lead assignment rule not working?

Usually the rule never ran. Assignment rules fire automatically only for Web-to-Lead and Web-to-Case. Manual creation needs the Assign using active assignment rule checkbox, imports need the rule selected, and API or marketing automation integrations must request it. If the rule did run, check the entry order and whether field values (such as Country) match your criteria exactly.

Do assignment rules run when a lead is updated?

No. Lead assignment rules run when a record is created, or when someone edits a lead and ticks Assign using active assignment rule. Changing a field such as Status or Lead Score doesn't re-trigger them. Re-routing on updates requires Apex, or a routing tool that responds to field changes.

Can Salesforce assignment rules do round robin?

No. Each rule entry assigns to one user or one queue. Round robin needs Flow with a counter field, Apex, or a Salesforce-native routing app such as Distribution Engine, which also supports weighting, capacity caps and skipping unavailable reps.

‍

Fancy giving Distribution Engine a try?

Have a play around for free, or get in touch if you’d prefer to chat.

Install in Production
Free trial

Take us for a spin with a 30 day Free Trial

Have a play around for free, or get in touch if you’d prefer to chat.