Must-read
How Round Robin lead Assignment works in Salesforce, HubSpot and pipedrive (opens in a new tab)
You will learn how each of the three platforms rotates leads between reps, including the Salesforce formula and assignment rule setup and the common reasons assignment rules fail to fire.
Why read this
You will also see how availability, weighting and rule order differ between them.
Salesforce
- No round robin switch built in
- Autonumber, formula and rule entries
- Edit formula when team changes
HubSpot
- Rotate record to owner action
- Load balanced, round robin, random
- Assign to available users only
Round robin lead assignment hands each new lead to the next rep in a fixed order, which suits teams where reps sell the same thing and leads are broadly alike. The article sets it against weighted, load-balanced and rules-based approaches, and notes that real setups usually combine rules to pick a team with a rotation inside it. It lists four common cases where a plain rotation breaks down: leads from existing accounts, uneven lead quality, reps who are away, and reps who own territories.
In Salesforce there is no round robin switch. The article walks through the build: an Autonumber field, a Round Robin ID formula using MOD over the number of reps, and one Assignment Rule entry per rep, with a catch-all entry at the bottom. Each time a rep joins or leaves, the formula and entries must be changed by hand. The article then lists why rules often appear not to fire, such as API calls missing the AssignmentRuleHeader, Data Loader imports without the rule ID, the Lightning checkbox setting, and Flows using the Run Immediately path.
HubSpot uses the Rotate record to owner workflow action, available on Sales Hub and Service Hub Professional and Enterprise, with options for round robin, load balanced and random, and an option to skip users who are set to Away. Its first assignment is random, counts are kept per action, and changing owners resets the counts. Pipedrive offers automatic assignment on Professional and higher plans, where each rule keeps its own rotation, there are no caps or weights, and a rep on leave must be removed from rules by hand.
A comparison table sets the three platforms side by side, covering built-in support, plan requirements, handling of absent reps, and how imports and API traffic are treated. The article then describes Operelio, a tool that applies routing before a lead reaches the CRM, and its routing rules, round robin and CRM checks.
Read the original at dev.to (opens in a new tab)