The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

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
Salesforce and HubSpot round robin setups differ in what the platform provides

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)

Worth reading?

Routing every Salesforce Lead to the right rep with Assignment Rules (opens in a new tab)

You will know how Salesforce Lead Assignment Rules evaluate entries, why a catch-all Queue matters, and the main ways to get round-robin distribution.

Why read this

You will also have a short checklist for testing before activation.

  1. Lead is created with assignment flag set
  2. Entries checked top to bottom
  3. First matching entry sets the owner
  4. No match: lead goes to catch-all queue
How a new lead is routed through assignment rule entries

Lead Assignment Rules route each new Lead to an owner as soon as it is created, which removes the slow and inconsistent manual triage that many teams rely on. The rule is a list of entries evaluated top to bottom, each with criteria and an owner that is a User or a Queue. The first entry whose criteria match wins, so the most specific entries must sit above the broader ones or they will never fire.

The article points out a common trap: rules only run when the record is created with the “Assign using active assignment rule” flag. The web-to-lead form, the API and Data Loader set this by default, but a manual record created in the UI does not unless the user ticks the box. It recommends structuring entries by territory first, then Lead Source, then score or company size, rather than writing one large entry per rep.

Every rule should end with a catch-all entry that sends unmatched Leads to a Queue rather than a named person, since a Queue is visible to the whole team and keeps working when someone is away. A growing catch-all Queue is a sign that criteria are missing a segment. Standard Lead Assignment Rules do not provide round-robin, so the options are a Queue that team members pull from, an autolaunched Flow that stamps a rotating owner using a counter field, or a third-party tool. The author suggests a Queue for most small teams because it is easier to audit, and notes that a Flow assigning owners should run in system context so creating-user permissions do not block it.

Before activating, create a test Lead for each entry and one that matches nothing, confirm each lands with the right owner, and check the web-to-lead path specifically. The article advises trialling the rule in a Sandbox against a week of real traffic before changing production.

Read the original at dev.to (opens in a new tab)

Worth reading?

How Salesforce cut lead assignment to 20 seconds using Data 360 scoring (opens in a new tab)

You will learn how Salesforce built lead scoring and three-way routing on a unified Data 360 profile, and which design choices carried the gains.

Why read this

The piece also gives a practical checklist for applying the pattern at a smaller scale.

  1. Match to unified profile
  2. Classify job level and score
  3. Apply team thresholds
  4. Route to sales, nurture or agent
Each inbound response is matched, scored and sent to one of three routes

Salesforce’s sales team routed leads across three systems with heavily customized rules, and routing changes often went live weeks late. The team unified signals such as website activity, event attendance, email engagement, support history and product usage in Data 360, then built scoring and routing on that profile. Its in-house data science team built a lead score from 1 to 5 and a product interest score, and each inbound response is matched to a profile, classified by job level, scored, and sent to a sales team, marketing nurture or agent-first outreach.

The article reports that lead assignment fell from 20 minutes to 20 seconds, custom code dropped 90% from about 2 million lines, and routing changes now take days instead of four weeks. Thresholds sit in configurable tables rather than code, so a business user could raise the bar for Tableau leads without a release. The authors credit the whole implementation for these results, not Data 360 alone, and note that the same profile drives an email journey with a 233% higher click-through rate than their average Marketing Cloud journey.

The closing advice is to unify data before scoring, define what sales-ready means for each team, give every lead a destination, and keep rule changes out of code releases.

Read the original at Salesforce Blog (opens in a new tab)

Worth reading?