Lead Scoring Starter: Which Leads Get Your Fastest Response

Monday morning. Fourteen new leads arrived over the weekend: a flooded basement, three "thinking about a new AC sometime this year," a landlord with 12 units, a price-shopper collecting bids, a commercial inquiry, and eight assorted others. Your CSR starts at the top of the list — chronological order — and calls the price-shopper first while the flooded basement waits. Nothing about the system is broken except the ordering. Lead scoring fixes the ordering.

This is part of Pillar A: Capture Every Lead — the prioritization layer of the complete missed-call text-back setup guide. System 2's speed is a weapon; scoring aims it.

Why "first in, first out" fails

Chronological order feels fair and requires zero thought — which is why every overwhelmed team defaults to it. But leads aren't equal:

• Urgency varies enormously. The emergency and the "sometime this year" are both "leads." Treating them identically wastes speed on one and starves the other.
• Value varies enormously. The landlord with 12 units and the single leaky faucet are both "leads." One funds payroll; the other fills a gap.
• Readiness varies enormously. The "need it this week" and the "just researching" need completely different handling — and the ready-now one is perishable.
• Your team's energy is finite. Every sprint spent on a tire-kicker is a sprint unavailable for the whale. Scoring rations the sprints.

Lead scoring (a method of ranking inquiries by their likely value and urgency, so the best get the fastest response) doesn't require software or data science. It requires three questions, answered at intake.

The three-factor score

Score every lead 1–3 on each factor. Total: 3–9.

Factor 1: Urgency (how fast does this need solving?)

• 3 — Emergency / time-critical: active damage, safety issue, system down in extreme weather, "need someone today."
• 2 — This week: broken but stable, "need it soon," project with a deadline.
• 1 — Someday: researching, planning, "sometime this year," maintenance curiosity.

Factor 2: Value (what's this worth?)

• 3 — High ticket / high lifetime value: full system replacement, multi-unit / commercial, portfolio landlord, the job that funds the week.
• 2 — Standard job: typical repair or install in your sweet spot.
• 1 — Small / uncertain: minor repair, price-shopper signals, outside your core services.

Factor 3: Readiness (how close to deciding?)

• 3 — Ready now: "when can you come," asked about availability, gave address and access details, referral ("my neighbor said call you").
• 2 — Engaged: asked real questions, comparing options, responded to follow-up.
• 1 — Browsing: one-word replies, "just getting ideas," ghosted once already.

The tiers (what the score triggers)

• 8–9: Drop everything. Immediate response — call within 5 minutes, owner notified if after hours. The flooded basement + ready-now + high-ticket. These are rare and precious; the whole system bends toward them.
• 6–7: Today. Respond within the hour, booked or quoted same day. The standard good lead — urgency or value or readiness is high, and speed converts it.
• 4–5: This week. Standard follow-up sequence, no sprint. The researcher, the planner, the small job. They get excellent systematic follow-up — just not the sprint.
• 3: Nurture. Long-term sequence, minimal human time. Check in monthly; they'll either warm up or won't. Never ignore — just never sprint.

The magic: the CSR doesn't decide how fast to move. The score decides. Decision fatigue — the real reason "everything gets the same slow response" — disappears.

Capturing the score at intake (where the data comes from)

Scoring needs three data points, and intake is where you get them:

• Urgency: the form's service dropdown + the "how urgent" signal (emergency keywords in the message, after-hours timing). One optional form field — "How soon do you need this?" (ASAP / This week / Just researching) — captures it directly and costs almost no conversion, because it's a choice not an essay.
• Value: the service type (replacement vs. repair is usually obvious from the dropdown) plus property signals (commercial vs. residential, multi-unit mentions).
• Readiness: the first response reveals it — but you can pre-score from signals: referrals score 3 (referred leads arrive warm), marketplace/LSA leads score 2 (they're actively shopping), "just browsing" form messages score 1.

In the CRM, three custom fields (or tags) hold the score. Many CRMs can auto-score from the form answers — the "how soon" dropdown maps straight to the urgency factor. Manual scoring takes the CSR 10 seconds per lead; auto-scoring takes zero.

The morning huddle (where scores earn their keep)

Scores are most powerful in the 10-minute morning huddle. The CSR pulls up today's callback queue sorted by score, highest first, and the team reviews the 8s and 9s together: who owns each, what's the next step, any backup needed. The 6–7s get a glance ("all assigned? good"). The 4–5s and 3s aren't discussed — the sequences handle them. This tiny ritual does something no dashboard does: it makes the whole team feel the priority order, so when the 9-score emergency calls back at 10am, everyone already knows it's the day's most important lead. Without the huddle, scores are data; with it, they're shared instinct.

The Monday-morning example, rescored

Example: those fourteen weekend leads, scored:

• Flooded basement (urgency 3, value 2, readiness 3) = 8 → drop everything, first call at 7am.
• Commercial inquiry (2, 3, 2) = 7 → today, acknowledgment within the hour.
• Landlord, 12 units (2, 3, 2) = 7 → today.
• "Thinking about a new AC" (1, 3, 1) = 5 → this week's sequence.
• Price-shopper collecting bids (2, 1, 2) = 5 → this week's sequence — polite, systematic, no sprint.

Same fourteen leads, same team, same Monday — completely different outcome. The basement gets saved, the commercial deal gets the fast acknowledgment that makes the shortlist, and nobody sprinted for the researcher.

Scoring mistakes to avoid

• Scoring once and freezing it. Scores change — the "just researching" who replies "actually, our AC just died" jumps from 4 to 8. Re-score on every meaningful interaction.
• Letting the score override humanity. A 3-score lead with a genuinely distressed caller still gets kindness. The score rations speed, not decency.
• Building a 20-factor model. Three factors, 1–3 each, done in 10 seconds. The scoring system that needs a manual is the scoring system nobody uses.
• Scoring without acting. The tiers must trigger real behavior differences — different response SLAs, different notification rules, different follow-up tracks. A score nobody acts on is decoration.

Compliance note

Scoring is internal prioritization — it doesn't change your texting or calling compliance obligations. Every tier still needs proper consent (10DLC business-texting registration for automated texts: 1–7 day approval, ~$15–$20 in fees; opt-out language; TCPA (federal telemarketing law) quiet hours 8am–9pm). Don't let the "drop everything" tier tempt you into calling outside legal hours — the sprint respects the clock. This is general information, not legal advice.

Related guides in this series

The prioritization layer of Pillar A: Capture Every Lead — System 2's targeting system. Pair with the commercial inquiry protocol (where scoring matters most) and the collision-prevention guide (what happens when two people sprint for the same lead).

The done-for-you version

This post is System 2 from the Leveraged Owner Starter Pack — the done-for-you version with the full scoring setup guide, the intake field templates, the tier action checklists, and click-by-click setup instructions for all 8 systems.

No industry statistics were used in this post.

Keep building your systems

Related guides from the Leveraged Owner blog: