Lead routing

Salesforce lead assignment round robin: three ways to build it

How to set up round robin lead assignment in Salesforce: three ways to build it, the gaps that skip leads, and how to check the split.

Abstract tokens travelling along a curved track and settling one at a time into a ring of evenly spaced cups.

Salesforce lead assignment rules route each new lead to a user or queue by its field values, and nothing in them takes turns between people. To get round robin lead assignment in Salesforce, you add the rotation yourself in one of three ways: a numbered formula that a lead assignment rule reads, a record-triggered Flow that tracks who received a lead last, or an app from AppExchange. For a small inside team that shares one pool of leads evenly, the formula is often enough. Once you need to skip people who are away, weight the split, or keep leads from existing customers with their account owner, Flow or an app is worth the extra effort.

Whichever you choose, the rotation only touches leads that actually pass through it. In our experience, that gap causes more complaints about unfair routing than the build method does, so it gets its own section below.

Write down what a fair split means first

“Round robin” means one thing to a sales leader and another to the reps keeping score. Before anyone opens Setup, write the rule as one sentence a rep could check against their own lead list. For example: new inbound leads from the website and trade shows go to the next active rep on the inside team, and a lead from a company we already sell to goes to that account’s owner.

The second half of that sentence is where simple builds break, because matching a lead to an existing account is a separate job from rotating. Settle a few smaller questions at the same time. Does a junk lead count as a turn? Does a lead that a rep passes back go to the next person, or back into the pool? Does someone on leave keep their place in the order? Each answer narrows the choice of method.

Formula, Flow or app: building round robin lead assignment in Salesforce

MethodHow the rotation worksFitsWhere it breaks
Formula plus assignment ruleAn auto number field numbers each lead, a formula turns the number into a slot, and the rule has one entry per slotA fixed team splitting leads evenly, with no extra licensesAnyone joins, leaves or goes on leave; earlier rule entries take some leads
Record-triggered FlowA small team list records each rep’s active flag and when they last received a lead; the Flow picks the active rep who has waited longestTeams that change often, or need people skipped without an admin editing logicNobody owns the Flow after the person who built it moves on; bulk imports go untested
AppExchange appThe app manages the queue, with availability, weighting and caps built inWeighted splits, working hours, many teams or objectsLicense cost, and another vendor with access to your lead data

The formula method uses three pieces. An auto number field on the lead gives each new record a sequence number. A formula field such as MOD(VALUE(Lead_Number__c), 4) + 1 turns that number into a slot from 1 to 4 for a team of four. The auto number format needs no prefix, such as {0}, so the formula can read it as a number. The lead assignment rule then has one entry per slot, each sending the lead to one rep. Salesforce evaluates rule entries in order and stops at the first match, so exceptions such as partner leads or named accounts belong above the rotation entries. Salesforce also recommends a final entry with no criteria, so nothing falls through.

The weakness is the counter. Every lead takes a number, including leads an earlier entry already sent elsewhere and leads deleted later, so leads stop arriving strictly in turn, and over a month of modest volume the counts can end up noticeably uneven. When the team changes size, the formula and the entries have to change on the same day, or one slot points to nobody.

The Flow method replaces the counter with a list of team members, usually a small custom object with an Active checkbox and a Last Assigned date and time. Marking someone inactive takes them out of the rotation without anyone touching the logic, which is the usual reason teams move off the formula. Whichever method you use, decide who covers the leads already in an absent rep’s name, because skipping them only protects new leads. Test the Flow with an import of fifty leads, not one lead at a time. A rotation that looks up the last person assigned once per batch can hand the whole batch to the same rep.

An app makes sense when the rules outgrow what your admin wants to maintain. During a trial, ask how it handles a rep marked out of office, what happens to leads that arrive outside working hours, and how a lead’s owner can be traced back to the rule that set it.

The leads that never reach your rotation

Web-to-Lead submissions go through the active lead assignment rule automatically. Imports through the Data Import Wizard do only when the person importing picks the rule during the import. Other routes need more care.

A lead entered by hand is only routed when the user ticks “Assign using active assignment rule” on the form. If the box is hidden or left unticked, the lead stays with whoever typed it. The opposite also happens: Salesforce notes that saving an existing record can run the rules again and reassign it, and it publishes a workaround that limits the checkbox to new records.

Leads created through the API, which covers most marketing automation, form and enrichment tools, only go through the active rule when the integration sends Salesforce’s assignment rule header. Ask whoever manages each integration whether it does. If it does not, those leads stay with the integration user or with whatever owner the tool sets.

If you trigger the rules from a Flow with the Apply Lead Assignment Rules action, Salesforce documents a quiet failure: in the Run Immediately path, the action does nothing when the lead was saved from the screen without the checkbox. Salesforce’s advice is to call it from the asynchronous path.

Leads that match no entry go to the default Web-to-Lead owner or to the administrator running the import. If your current rotation was built in Process Builder years ago, it still runs but no longer gets fixes, as our article on Workflow Rules end of support explains, so rebuild it in Flow rather than patching it.

None of this reaches back into your existing backlog unless someone edits a lead with the box ticked. Treat old, unworked leads as a one time cleanup: export them, agree owners with the sales manager, and update them in one load.

Check the split after the first month

Build one report of leads created in the last 30 days, grouped by owner and then by lead source. Even counts are the first test. The second is the rows that should not be there: leads owned by the default owner, by an integration user, or by a queue nobody watches. Those show you which route into Salesforce skips the rotation. Then filter for leads still in their first status after two business days, because an even split does not help if the leads sit untouched. If your team has not yet agreed what each lead status means, settle that first, as covered in how to track sales leads for a small business.