Lead management in Salesforce: routing, scoring, SLAs

Lead Management in Salesforce: Routing, Scoring, SLAs (Best Practices)

Strong lead management in Salesforce comes down to three things: route leads to the right owner fast, prioritize the best leads, and enforce follow-up SLAs so leads don’t go cold. Start by standardizing lead sources and required fields, then implement routing rules (territory/segment/round-robin), a simple scoring model (fit + intent), and SLA automation (tasks, alerts, escalations). Finally, track performance with dashboards for response time, contact rate, conversion rate, and lead aging. If your team can’t answer “who owns this lead and when will they follow up?” Salesforce won’t fix pipeline quality.

Why lead management fails (even with Salesforce)

Most teams struggle because:

  • leads arrive with missing or inconsistent data,

  • ownership is unclear,

  • reps cherry-pick easy leads,

  • follow-up isn’t measured,

  • marketing and sales disagree on what a “good lead” is.

Reasoning layer

  • If your routing is wrong → speed-to-lead doesn’t matter; leads go to the wrong person.

  • If your scoring is vague → reps ignore the best leads and work the loudest ones.

  • If your SLAs aren’t enforced → your best leads go cold.

Step 1: Standardize the inputs (so routing can work)

Create a minimum required lead dataset

You don’t need 40 fields. You need the few that determine ownership and priority.

Recommended “minimum viable” lead fields

  • Lead source (standardized picklist)

  • Country/region (or territory)

  • Company name + website (if B2B)

  • Email + phone (at least one workable contact method)

  • Product interest / topic (high-level)

  • Segment / employee size / revenue band (if used)

  • Consent/opt-in fields (where required)

Data quality rules

  • Use picklists for source and product interest (avoid free text)

  • Validate email format; normalize phone

  • Dedupe rules for email + company (as appropriate)

  • Capture UTM fields if you rely on attribution (optional)

Step 2: Build routing that matches how you sell

Choose your routing model

Model A: Territory-based routing

Best when ownership is defined by geography or named accounts.

  • Route by country/state/region

  • Support exception rules (named accounts, strategic segments)

Model B: Segment-based routing

Best when teams are split by company size or product line.

  • Route by employee band, revenue band, or product interest

  • Add tie-breakers (region + segment)

Model C: Round-robin routing

Best when speed matters and reps can handle any lead.

  • Round-robin within a queue/team

  • Add rules for exclusions (PTO, capacity, performance)

Model D: Hybrid routing (most common)

  • Named accounts override everything

  • Then segment/team

  • Then territory

  • Then round-robin

Reasoning layer

  • If you have named accounts → route by account ownership first.

  • If you sell multiple products → route by product interest next.

  • If speed is critical → round-robin within the right team.

Routing best practices in Salesforce

  • Use queues as the “front door” (so nothing is unowned)

  • Create assignment rules that are readable and documented

  • Add a fallback rule (if data is missing, route to a triage queue)

  • Track first-touch timestamps (so response time is measurable)

  • Build exception workflows (reassignment rules and dispute handling)

Step 3: Add lead scoring that reps will trust

Lead scoring fails when it’s overly complex. Start simple, prove it works, then expand.

A simple scoring model (Fit + Intent)

Fit signals (who they are)

  • Company size matches ICP

  • Industry matches ICP

  • Role/title matches buyer persona

  • Region is serviceable

Intent signals (what they did)

  • Requested demo / contact sales

  • Viewed pricing page

  • Returned multiple times

  • Downloaded high-intent content

  • Opened/clicked key emails (if reliable)

Recommended approach

  • Score Fit (0–50) and Intent (0–50)

  • Combine into a single score (0–100)

  • Create 3 buckets:

    • Hot (70–100): immediate follow-up

    • Warm (40–69): follow-up within SLA window

    • Nurture (<40): marketing nurture or lower-priority outreach

Reasoning layer

  • If you can’t explain the score in one sentence → reps won’t trust it.

  • If scoring doesn’t change behavior → it’s not useful.

Step 4: Define SLAs and enforce them with automation

An SLA is a promise: “how fast we respond” and “how many attempts we make.”

Example lead SLAs (edit to match your motion)

  • Hot leads: first response within 15–60 minutes (business hours)

  • Warm leads: first response within 4–24 hours

  • Inbound demo requests: same day

  • Outbound lists: first touch within 24–48 hours

Enforcement automation (what to build)

  • Auto-create a task on lead assignment

  • Send an alert if the task isn’t completed within the SLA window

  • Escalate (reassign to queue/manager) if SLA is breached

  • Track attempt count (calls/emails) with a simple field or report logic

  • Use business hours logic (don’t penalize nights/weekends unfairly)

Reasoning layer

  • If SLAs aren’t measured → they aren’t real.

  • If there’s no escalation → reps learn they can ignore the SLA.

Step 5: Track performance with dashboards (the “truth layer”)

Your lead management system is only as good as what you can measure.

Salesforce lead management dashboard metrics

Speed and coverage

  • Lead response time (time-to-first-touch)

  • SLA compliance rate

  • % of leads with an owner within X minutes

  • Lead aging (leads not touched in 1/3/7 days)

Quality and conversion

  • Contact rate (touched → connected)

  • Lead-to-opportunity conversion rate

  • MQL → SQL conversion rate (if used)

  • Conversion by source, segment, and rep/team

Routing health

  • Leads routed to fallback/triage queue (data quality issues)

  • Reassignment rate (routing accuracy signal)

  • Capacity by rep/team (volume per rep)

Common pitfalls (and fixes)

Pitfall: missing fields prevent routing
Fix: minimum required fields + triage queue fallback.

Pitfall: scoring is opaque
Fix: Fit + Intent model with 3 buckets.

Pitfall: reps ignore leads
Fix: SLAs + task automation + escalation.

Pitfall: “first touch” isn’t tracked
Fix: define and capture first-touch timestamp consistently.

Pitfall: too many lead statuses
Fix: keep lead status simple and tied to outcomes.

Quick checklist (copy/paste)

  • Standardize lead sources and required fields

  • Create queues and assignment rules with a fallback queue

  • Define routing hierarchy (named account → segment → territory → round-robin)

  • Implement Fit + Intent scoring with 3 buckets

  • Define SLAs by lead bucket and business hours

  • Automate tasks, alerts, and escalation for SLA breaches

  • Build dashboards for response time, SLA compliance, lead aging, conversion

  • Review routing and scoring monthly and adjust based on outcomes

Frequently Asked Questions

What’s the best way to route leads in Salesforce?

Use a hybrid model: route named accounts first, then segment/product, then territory, then round-robin within the right team. Always use queues as the front door and a fallback queue for missing data.

How do I set up lead scoring in Salesforce?

Start simple with Fit + Intent scoring and three buckets (Hot/Warm/Nurture). Make the score explainable, tie it to SLAs, and validate it by comparing score buckets to conversion rates.

What lead SLA should we use?

Use SLAs based on lead type and intent. High-intent inbound leads should get the fastest response; lower-intent leads can have longer windows. The key is to measure SLA compliance and escalate breaches.

How do we track lead response time in Salesforce?

Define “first touch” (first call/email/task completion) and capture a timestamp when it happens. Then report on time-to-first-touch and SLA compliance by rep, team, source, and segment.

Book a Sales Cloud roadmap session

If your leads are getting lost or follow-up is inconsistent, book a Sales Cloud roadmap session. We’ll map your routing rules, build an SLA and scoring model your reps will use, and set up dashboards that make performance measurable.