Round robin lead assignment in Salesforce, HubSpot and Pipedrive

Salesforce's own definition is the clearest: "Round robin assignment means that each new lead is assigned to a different user until everyone has been assigned the same amount and the cycle repeats." It works like dealing cards. With three reps, Ana, Ben and Chloe, lead 1 goes to Ana, lead 2 to Ben, lead 3 to Chloe, and lead 4 back to Ana.

People also call it round robin lead distribution or round robin lead routing. Strictly, routing is the wider job of deciding where a lead goes (which team, which territory, which owner), and round robin is one way of picking the person once you know the team. Most setups use both: rules first, then a rotation inside each team.

It sits alongside three other ways of handing out leads:

Round robin is fair and simple when every rep sells the same thing to the same kind of buyer, and the leads coming in are roughly alike. Nobody can claim the good leads went to someone else, and nobody needs to decide who gets what.

It breaks when the leads or the reps aren't alike. Four common cases, and the fix for each:

Salesforce assigns leads with lead assignment rules, under Setup > Lead Assignment Rules. A rule is a list of entries. Each entry has criteria (such as Lead Source equals Web, or Country equals Canada) and a user or queue to assign to. Salesforce's help describes how it reads them: "Salesforce evaluates each entry in order and tries to match the criteria for the entry. When a match is found, Salesforce assigns the item and stops evaluating the rule entries for that item. If no match is found, the item is reassigned to either the default Web-to-Lead owner, the administrator doing a lead import, or the default case owner."

"For each rule type, only one rule can be in effect at any time." So all your lead logic lives in one active rule, as entries in order. An entry can have up to 25 filter criteria of up to 255 characters each, and a rule up to 3,000 entries. Assignment rules run after validation rules and before auto-response rules, workflow and escalation, so a lead that fails validation is never assigned.

Salesforce says rules can assign leads "regardless of whether leads are created manually, are generated from Web-to-Lead forms, or are imported using the Data Import Wizard." Leads from the API, Data Loader and Flow are different, as the section on rules that don't fire explains.

Salesforce's own tip for the last entry: "Create an error-proof rule by always creating the last rule entry with no criteria." Point that entry at a queue someone watches, so a lead that matches nothing still lands with a person.

Facts here are from Salesforce's help, read October 20, 2026. Salesforce Help's setup pages show no update date.

Salesforce has no round robin switch. Its own help page says "You can set up round robin lead assignment with a few custom fields and a lead assignment rule." The idea: every lead gets a running number, a formula turns that number into 1, 2 or 3 in a repeating cycle, and the assignment rule sends 1 to the first rep, 2 to the second and 3 to the third.

Salesforce's own steps, for three reps (we haven't run them in an org of our own):

Most "my assignment rule isn't firing" problems come from how the lead was created, not from the rule's criteria. Salesforce runs the rule when it's asked to, and several ways in don't ask by default.

The quotes below are from Salesforce's knowledge base, read October 20, 2026: its articles on the API headers, on Data Loader and, from September 2026, on Flow. Check these in order:

A few habits keep one active rule readable as it grows:

HubSpot rotates owners with the Rotate record to owner workflow action, "available with" Sales Hub Professional and Enterprise and Service Hub Professional and Enterprise. You add the action to a workflow, choose the owner property, and choose to rotate between specific users or a team. HubSpot then assigns "records to users equally within a selected team or between specified users."

Leads (the Leads object, in beta for this action) and tickets get extra options: Load Balanced ("the user with the least amount of open, assigned tickets"), Round Robin ("assign records in a rotating, sequential order") and Random. They also get "Assign to available users only": "users that are set to Away will not be assigned records", and if everyone is away the record is left with no owner. To rotate leads, "you'll need to turn off the Sync lead owner with contact or company owner setting."

If HubSpot's owner property syncs to Salesforce, HubSpot warns that "the action may not work as expected", because Salesforce may write the old owner back. In that setup, assign in one system only.

Five things about how the rotation behaves, from HubSpot's help, updated October 9 and October 19, 2026:

Pipedrive's automatic assignment is "only available on Professional and higher plans". A rule fires when a lead or deal is added, or a deal moves pipeline or stage, checks its conditions, and assigns to one of four assignee types. Picking Team "uses a round-robin to distribute newly created data between its members". You can add up to 50 rules per entity type, and the first rule in the priority list that matches wins.

When a rule fails, the lead or deal shows in the Not assigned tab with a reason, such as "User not found" or "No user in the team". The assignment history keeps seven days of logs.

What Pipedrive's FAQ says about how the rotation behaves (updated September 4, 2026):

Side by side, from each vendor's help pages (Salesforce read October 20, HubSpot and Pipedrive October 21, 2026):

Every setup above runs inside the CRM, after the record exists. Operelio does it on the way in, so the owner is set when the lead is pushed. It works on a single lead sent to a folder's webhook (from Zapier, Make or your own code), straight from Typeform, or by email, and on a list, where it deals the rotation across the whole file. Typeform can send each response straight to a folder, and each response becomes one lead, so a test response from Typeform makes a real lead too.

On a trail, routing rules decide who owns each lead. They run in order, the first one a lead matches decides, and a required Otherwise catches the rest, up to 50 rules. A rule can test a column (is, is one of, contains, at least, at most), the lead's score, where it came from, or its location. A rule can send the lead to one person, to a team in turn, to the owner named in one of its columns, to the review queue, with no owner, or drop it. You can drag a rule by its grip, or move it with the arrow keys, to change the order.

A team in turn is a round robin. The turn carries on from where it stopped last time, not from the start of each file. A list's rows are dealt in file order. A rep who is no longer active in the CRM is passed over and the lead goes to the next one. If nobody on the team is active, the lead is held and the trail's people are told, rather than pushed with no owner.

On HubSpot and Salesforce, a list's rows and single leads are checked against the CRM before routing, which adds two choices. A rule can test the CRM check (already in the CRM, new person at an existing company, or new), and a rule can send the lead to the Company owner, the owner of its company in the CRM. A row the check couldn't reach, or a company with no owner or whose owner has left, goes on to the next rule. Pipedrive has no CRM check, so those two rules don't place its rows, and Pipedrive takes lists from a trail, not single leads yet.

To see what the rules would do before you rely on them, Test on a file runs them over one of your files and sends nothing. Each rule shows how many of the tested rows it took, and a table lists rows with their owner and why that owner.

What it doesn't do: the editor has no weights, so every rep on a team gets the same share, and it doesn't know when a rep is away in the CRM, only when they're no longer active.