A lead contacted within 5 minutes of submission converts at 9x the rate of a lead contacted after 30 minutes. That's not a RevKit stat — that's research from InsideSales.com replicated across dozens of studies. Speed to contact is the single most predictive factor in lead conversion.
And yet, in most Salesforce orgs we audit, the average time between lead creation and first rep contact is 4–6 hours. Some leads sit unassigned for days.
The cause is almost always the same: no assignment rules, or assignment rules so poorly configured that leads fall through the cracks.
The Problem with Manual Assignment
If your current process is "leads land in a queue and reps grab them" — you don't have a process. You have a race condition where the fastest clicker gets the lead and everyone else ignores the queue.
- Cherry-picking. Reps scan the queue and grab leads from big companies or with recognizable names.
- Uneven distribution. Your fastest clicker gets 60% of the leads.
- No accountability. When a lead goes stale, nobody's name is on it.
- No automation. No follow-up tasks are created. No notifications fire.
Round-Robin Assignment
Round-robin distributes leads equally. It's the right choice when all reps handle the same type of leads and you want equal distribution.
Setup → Queues → New. Create a queue called "Inbound Sales." Add all participating reps as members. Supported objects: Lead.
The limitation: Salesforce queues don't do true round-robin natively. They assign to the queue, then the first rep who grabs the lead gets it — which brings back the cherry-picking problem.
The real round-robin fix: Build a Flow that actually rotates assignment. Create a Custom Setting called "Round Robin Counter" with a single number field. Each time a new Lead is created, the Flow increments the counter, divides by the number of reps, and assigns based on the remainder. Rep 1 gets leads where counter mod 4 = 0, Rep 2 gets mod 4 = 1, and so on. This is true round-robin.
Territory-Based Assignment
Territory assignment routes leads to the rep who owns that geographic or industry territory. Setup → Lead Assignment Rules → New Rule Entry.
- Criteria: State/Province = "California" → Assign to: West Coast Rep
- Criteria: Industry = "Healthcare" → Assign to: Healthcare Specialist
- Criteria: Annual Revenue > $10M → Assign to: Enterprise Team Queue
- Default: → Assign to: General Inbound Queue
Priority matters. Rule entries are evaluated in order. Put your most specific rules first and your catch-all default last.
Automated Follow-Up Tasks
Assignment without follow-up is assignment without accountability. Build a Flow that creates a follow-up task every time a lead is assigned.
Flow type: Record-Triggered Flow. Object: Lead. Trigger: After save. Condition: Owner has changed (ISCHANGED(OwnerId) = true).
Action: Create Task.
- Subject: "Call new lead: {Lead.FirstName} {Lead.LastName} at {Lead.Company}"
- Due Date: TODAY (same day)
- Priority: High
- Assigned To: Lead Owner
This ensures every newly assigned lead has a task in the rep's task list. It's not in their inbox (where it might be ignored). It's in their Salesforce task queue where it shows as overdue if they don't complete it.
Speed-to-Contact Tracking
You can't improve what you don't measure. Create a formula field on Lead:
- Name: Speed_to_First_Contact
- Type: Number (days, with 2 decimal places)
- Formula:
IF(ISBLANK(First_Contact_Date__c), null, First_Contact_Date__c - CreatedDate)
Track Speed_to_First_Contact on a weekly report grouped by Owner. The data will show you which reps are fast and which are slow — and correlate it with conversion rates to prove that speed matters.