How to Assign Leads in Salesforce: Auto, Bulk, and Queue Assignment

To assign leads in Salesforce, you have four options: set an owner manually on the record, let the active lead assignment rule assign automatically when a lead is created, set the OwnerId with a record-triggered Flow, or bulk reassign existing leads with Change Owner, Mass Transfer Records, or Data Loader. Assignment rules are the default automatic path, and they only fire when the "Assign using active assignment rule" box is checked or when the lead comes in through Web-to-Lead. Below is how each method actually behaves, when to use which, and where they run out of road.

The four ways to assign a lead

Most confusion about Salesforce lead assignment comes from not knowing which mechanism is in play on a given record. Here is the whole map in one table.

How to auto assign leads in Salesforce

Automatic assignment runs on lead assignment rules. In Setup, search for Lead Assignment Rules, create a rule, and add rule entries. Each entry has an order number, criteria, and an assigned user or queue. When a lead is evaluated, Salesforce walks the entries from the top and stops at the first one whose criteria the lead matches, then hands the record to that entry owner. If nothing matches, the lead falls to the Default Lead Owner set in Lead Settings.

Two details trip people up more than anything else in the rule builder:

• Only one assignment rule can be active per object at a time. You can have many rules saved, but exactly one is active for Leads. All of your routing logic therefore lives inside that one rule as ordered entries, which is why mature orgs end up with fifty-entry rules that nobody wants to touch.
• The rule does not always fire. On a manual create or edit, the user has to tick "Assign using active assignment rule" on the record. Web-to-Lead submissions run the rule automatically. Records created through the API, an integration, or Data Loader only run it if the caller sets the assignment rule header, which most integrations do not do by default. If leads from your marketing platform are all landing on one owner, this is usually why.

Rule entries also carry a "Do not reassign owner" option, which tells Salesforce to leave the existing owner alone when a matching lead is updated. Use it when you want a rule to catch new leads without yanking records away from reps mid-conversation.

How to assign a lead to a queue

A queue is a shared holding area that leads sit in until a rep takes ownership. Create it in Setup under Queues, add Lead as a supported object, and add the members who should see it. From then on a queue can be the owner on an assignment rule entry, the value you set in a Flow, or the target of a manual owner change.

Queues suit work that a group should self-serve from, such as an overflow pool or a region with several reps sharing coverage. Their trade-off is the claim step: a lead in a queue belongs to nobody until somebody clicks Accept, and unclaimed leads age quietly. If your response time targets matter, assign to a person and use a queue only as a fallback.

How to change lead owner in Salesforce

On a single record, open the lead, click Change Owner on the Lead Owner field, pick a user or queue, and choose whether to notify them. On a list view, select the leads you want and use Change Owner to move them together. For larger reassignments, Setup has Mass Transfer Records, which moves leads from one user to another with optional criteria, and Data Loader handles anything bigger or more selective by updating the OwnerId field from a CSV.

One caution on bulk moves: unless you deliberately re-run assignment rules, a mass transfer just changes the owner field. It does not re-evaluate your routing logic, so the leads land wherever your CSV said, not wherever the rules would have put them. If you want the rules applied instead, update the records with the assignment rule header set, which admins usually do through Data Loader settings or a small piece of Apex. If you are not fluent in Apex, this is the kind of short, well-scoped snippet an AI coding assistant that plans and writes the code handles quickly, though you should still test it in a sandbox before pointing it at production.

How to bulk assign leads in Salesforce

Bulk assignment usually comes up in four situations, and each has a different right answer.

1. A rep leaves. Use Mass Transfer Records to move that user open leads to a named replacement or a queue, then let normal routing take over from there.
2. Territories change. Update the rules first, then re-run assignment on the affected leads so the new logic decides, rather than moving records by hand and having the rules disagree with reality next week.
3. A backlog of unworked leads. Filter a list view on last activity date and redistribute, ideally spread across the team rather than dumped on one person.
4. A bad import landed on one owner. The usual cause is an integration that did not set the assignment rule header. Fix the integration, then reassign the affected batch.

Whatever the reason, decide the split before you start clicking. Dropping 800 leads on the two reps who happened to be in the list view is how a rebalance becomes a morale problem.

Where native lead assignment stops

Assignment rules do static criteria well and cost nothing. What they cannot do is anything that depends on the state of your team right now:

• No round-robin. There is no rotation option. Teams fake it with an auto-number field and a modulo formula that cycles owner IDs, or with a Flow that remembers who was last. Both work until someone joins, leaves, or goes on PTO.
• No workload awareness. A rule cannot see that a rep already has forty open leads. It matches criteria and assigns.
• No availability check. A rule will happily hand a hot inbound lead to someone on vacation, where it sits until they get back.
• Setup access to change anything. A sales manager who wants to shift coverage for a week files a request with an admin instead of doing it.

If your routing needs any of those, you either build them in Flow and Apex and then maintain that code, or you put a routing layer next to Salesforce. Assigner does the second: it distributes leads by round-robin, weighted round-robin, skill, current workload, priority, and availability, respects working hours and time zones, and names the rule behind every assignment so nobody has to guess. It sits beside Salesforce rather than replacing it, and it routes support tickets and ops tasks through the same engine. See Salesforce lead routing beside your CRM for how that works, or how native assignment rules compare feature by feature. For a plain-language look at the rotation itself, read round robin assignment beside Salesforce.

A working setup that holds up

The pattern that survives contact with a growing team looks like this. Keep assignment rules for the coarse decision: which segment, region, or product line a lead belongs to. Keep a queue as the catch-all for anything that matches nothing, and put an owner on that queue so it gets checked. Handle the fair split inside each segment with rotation that accounts for load and availability, whether you build that yourself or run a layer beside the CRM. And log the reason for every assignment, because the first question after any routing change is always "why did this one go there".

If you are writing the rules themselves for the first time, our guide on how to write lead routing rules covers the ordering and fallback decisions in detail.

Frequently asked questions

How do I auto assign leads in Salesforce?

Create a lead assignment rule in Setup, add ordered rule entries with criteria and an assigned user or queue, and activate it. Salesforce then assigns each evaluated lead to the first entry whose criteria it matches. The rule runs automatically for Web-to-Lead, and on manual creates or edits only when the "Assign using active assignment rule" checkbox is ticked. API and Data Loader inserts need the assignment rule header set.

Why are my Salesforce lead assignment rules not working?

The three usual causes are that the rule is saved but not active, that the record was created through an integration or Data Loader without the assignment rule header so the rule never ran, or that an earlier rule entry matched first and took the lead. Check active status, check the entry order, and check how the record was created before you rewrite any criteria.

How do I bulk assign leads in Salesforce?

Use Change Owner on a list view for a modest batch, Mass Transfer Records in Setup to move one user leads to another with optional criteria, or Data Loader to update OwnerId from a CSV for anything larger. Note that a plain bulk update changes the owner without re-running your assignment rules, so if you want the rules to decide, run the update with the assignment rule header set.

Can you assign leads to a queue in Salesforce?

Yes. Create a queue in Setup, add Lead as a supported object, and add members. You can then set that queue as the owner on an assignment rule entry, target it from a Flow, or move records to it manually. Leads in a queue belong to no individual until someone accepts them, which makes queues good for shared overflow and poor for anything with a response-time target.

Does Salesforce have round robin lead assignment?

Not natively. Assignment rules have no rotation option. Common workarounds are an auto-number formula field with a modulo calculation that cycles through owner IDs, a Flow that tracks the last assigned rep, or an AppExchange app. All of them rotate blindly, so they keep assigning to reps who are at capacity or out of office unless you add that logic yourself.

What is the difference between a lead assignment rule and a Flow?

An assignment rule is a declarative, ordered list of criteria-to-owner mappings, limited to one active rule per object and to field-level criteria. A record-triggered Flow can express far richer logic, look up related records, and set OwnerId directly, but it is something you build and maintain. Flow cannot re-run assignment rules on its own; that needs an invocable Apex action.