Round-robin lead assignment in Salesforce: four ways to do it
The short answer: Salesforce has no round-robin switch. You can build the rotation with an auto-number field, a MOD formula and assignment rule entries; with a record-triggered Flow that gives the next lead to whoever was assigned longest ago; with Omni-Channel, which routes by capacity rather than strict turns; or with a routing app. Choose by how often your team changes and whether anyone has to explain a result.
A rep stops you at the coffee machine. “I swear the round robin skips me.” You open the routing and find an assignment rule, a formula nobody has touched since the last hire, and a spreadsheet of who’s on vacation. You can’t prove she’s wrong. You can’t prove she’s right either, because nothing wrote down why each lead went where it did.
That’s the real problem with most round robins. Building one is an afternoon. Defending it is the part that takes months.
Does Salesforce have round-robin lead assignment built in?
Not as a setting. Salesforce Ben reports that Salesforce doesn’t offer a direct built-in round robin feature, and that the usual builds are a formula-based rotation and a Flow. Omni-Channel is the nearest native feature, though it’s built for a different job, as covered below.
So “round robin in Salesforce” really means a pattern you assemble. Each pattern has a different failure mode, and the failure mode is what you’re choosing between.
How do assignment rules do round robin?
Add an Auto Number field and a formula that turns it into a rotation, then write one assignment rule entry per rep. The formula uses MOD to cycle the number through 1, 2, 3 and back. Each entry matches one value and names one owner. Salesforce Help documents this method under “Create a Round Robin Lead Assignment Rule”.
It needs no new objects and no installation, which is why it’s everywhere. The trouble is upkeep. Salesforce Ben’s walkthrough points out that when you add or remove a rep, you edit the formula and the rule entries by hand, and that the method doesn’t handle someone going on leave. A rep on a two-week holiday keeps getting leads, or you edit the rule twice.
Use it when the team is small, stable and all in the office. For anything else it ages badly.
Can a Flow do round robin?
Yes, and it’s the more flexible option. A record-triggered Flow looks up the eligible reps, picks the one assigned longest ago, sets them as owner and stamps their “last assigned” time. Salesforce Ben describes a version with a Team object, a Team Member object, an Active checkbox and a Last Assignment timestamp.
An unavailable rep gets unticked and drops out. That fixes the vacation problem, as long as someone remembers the checkbox. The same article is frank about the drawbacks: you maintain custom objects, a deleted or half-filled member record quietly removes someone from the rotation, and repeated Get Records and Update Records steps can run into Flow limits at volume.
One thing to test before you trust it, and I’m not citing anyone for this: load 200 leads at once and count the owners. A rotation that reads “who was assigned last” can behave differently when many leads arrive in one transaction. Better to find out on a sandbox load than from the rep who got 40.
Is Omni-Channel round robin?
Not strictly. Omni-Channel can route leads, but it routes by capacity: Salesforce’s Omni-Channel for Administrators guide (Winter ’27) lists leads among the objects it supports, and describes two routing options, Least Active and Most Available, which look at each agent’s used or available capacity. When two agents tie, the work goes to whoever has waited longest without receiving any.
That’s close to fair turns for evenly loaded people, but it isn’t a turn counter. It also assumes an agent model: service channels, presence statuses, queues and routing configurations, set up under Setup, Omni-Channel. Routing a lead means invoking an Omni-Channel flow from a parent flow, per the same guide.
The guide recommends Enhanced Omni-Channel over Standard. One third-party blog claims Standard has been retired, which we couldn’t confirm from Salesforce, so check your org. Also check which licenses your sales users would need. This is a sound choice if your reps already work Omni-Channel’s way, and a lot of setup if they don’t.
When is a dedicated routing app worth it?
When the questions you get are about time away, caps, weights and “why not me?”, and you’re tired of answering them from memory. A routing app, by which I mean an app that holds pools, rules and a log of every decision, is a way to stop maintaining the Flow yourself. It doesn’t make the rules simpler. It makes them visible.
Here’s how the four compare.
| Assignment rules and formula | Flow | Omni-Channel | Routing app | |
|---|---|---|---|---|
| Effort to start | Low | Medium | High if new to it | Install and configure |
| Fair turns | Strict turns, until the team changes | Longest-ago-first | By capacity, ties to longest wait | Round robin, weight or fewest open |
| Time off and caps | Manual edits | An Active checkbox you maintain | Presence and capacity | Usually built in |
| Explaining a result | Read the formula | Read the Flow, debug logs | Omni-Channel reports | A log, if the app keeps one |
One routing question sits outside the table: a new lead from an existing customer usually belongs with that account’s owner, not in the rotation. We cover that in lead-to-account matching. And if the data feeding your router is the doubt, a Data Health Check looks at it first.
What does “fair” mean, and how do you prove it?
Fair means every eligible rep gets their share over a stated period, and the people who weren’t eligible have a recorded reason. Equal turns aren’t the same as equal opportunity. A rep with a full plate, or a week off, shouldn’t get a turn just because the counter says so.
Write the definition down before you build. Then test it with a report you can run today:
- Create a Leads report, filter Created Date to the last 30 days, group by Lead Owner, and show the record count.
- Put next to it the list of reps who were eligible and how many working days each had.
- Look for the gaps. Someone with half the leads and no explanation is your coffee-machine complaint.
One caveat: the report shows the current owner, not the first one. If reps pass leads on, the counts drift from what the router did. Field history on Lead Owner, if you track it, helps you separate the two. Whatever method you pick, “which rule matched and who was skipped” is the thing to capture. It’s the part native builds rarely keep.
What to do Monday:
1. Run the 30-day leads-by-owner report and write down what “fair” means for your team in one sentence.
2. List who is on the rotation today, who’s on leave this month and who has a cap. If that list lives in someone’s head or a spreadsheet, that’s your risk.
3. Open the assignment rule or Flow and note who last edited it. If nobody knows, schedule an hour to read it.
Where we come in
Bosun, by GTM Cloud, is pre-release: it’s built, install-tested and in pilot, but not publicly listed. It routes records through ordered rules and round robin pools with caps and time away, lets you test a run first, and logs why each record went where it did. Version 1 sets the owner only. If that sounds like your coffee-machine problem, see Bosun.
Questions people ask
Can assignment rules assign leads in a rotation?
Not by themselves. An assignment rule matches criteria to an owner. To rotate, you pair it with a number that cycles, usually an Auto Number field and a MOD formula, so each rule entry catches one value. Adding or removing a rep means editing both the formula and the entries.
How do you skip reps who are on vacation?
Assignment rules don’t take out-of-office status into account, per Salesforce Ben. In a Flow you can use an Active checkbox on team members, maintained by hand. Omni-Channel uses presence and capacity. Some routing apps, Bosun included, let people record their own time away so the skip happens without an edit.
Should leads go to a queue instead?
If your team prefers to pick up work, yes. A queue lets members take ownership of any record in it, and Omni-Channel can push queue work to agents. The trade-off is speed: a queue works when someone watches it. Round robin gives the lead an owner in the same moment.
Sources
- Round Robin Assignment in Salesforce (Salesforce Ben): the formula and Flow methods, their stated downsides, and the absence of a built-in round robin. Published June 2025.
- Create a Round Robin Lead Assignment Rule (Salesforce Help): Salesforce’s own article on the formula method. Its text did not load for us, so the steps here follow Salesforce Ben’s account.
- Omni-Channel for Administrators, Winter ’27 (Salesforce PDF): leads as a routable object, Least Active and Most Available, Omni-Channel flows for non-real-time objects, queue behavior, Enhanced Omni-Channel recommendation.
- A Short But Mighty Guide to Salesforce Lead Routing (Salesforce Ben): assignment rules do not support round robin or weighting and ignore out-of-office status. Updated June 2025.