Lead scoring for aged insurance leads: a dial-priority framework for who to call first

Same price, different value

An aged list prices every record the same way — one flat rate per lead, regardless of state, age, or anything else about the person on the other end of the number. That's a pricing decision, not a claim that every record is equally likely to answer, qualify, or convert. A 10,000-lead batch is 10,000 records worth exactly what you paid for them individually, but they are not 10,000 equally good uses of your first hour of dialing. Scoring the file before you start sorts that difference out instead of discovering it dial by dial.

The three signals you actually have

A data record doesn't carry a credit score or a buying-intent flag. What it does carry is enough to build a real priority order from, without guessing:

• Phone type. A validated file runs roughly 96% mobile, but that still leaves a landline slice mixed in. A mobile number can be called or texted; a landline can only be called, and texting one wastes a send and can itself be a compliance problem — see the landline scrub guide for why. Phone type is the single highest-value signal you can add to a file, because it changes which channel a record belongs in, not just its priority inside one.
• Age-band fit for the vertical you're selling. The file runs 18–64 across every record, but your pitch doesn't fit that whole range the same way. A term life or ACA opener lands better in the 25–45 slice; mortgage protection and final-expense-adjacent offers land better at 55–64 — see the 55–64 age-band post for why that end of the range behaves differently. A record outside your vertical's sweet spot isn't dead, it just scores lower than one inside it.
• Recency inside the file's own age window. "Aged 30–90 days" describes a range, not a single age — a batch delivered today can mix records captured six weeks apart. The newer end of that window has had less time to go stale: fewer numbers reassigned, fewer people who've since bought the policy they needed elsewhere. If your order or export carries a capture date column, it's worth keeping instead of discarding on import.

A simple point system

You don't need a model, just a spreadsheet column. Score each record on the three signals above and sum the points:

• Phone type: mobile = 2 points, landline = 0 points (and route to call-only, never text).
• Age-band fit: inside your vertical's target range = 2 points, adjacent = 1 point, outside = 0 points.
• Recency: in the newer half of the batch's date range = 1 point, older half = 0 points. Skip this one entirely if you don't have a capture date — don't invent one.

That's a 0–5 scale. Sort into three tiers: A (4–5 points) dial first, in the first 24–48 hours the data is freshest to you; B (2–3 points) dial on the normal cadence, days two through five; C (0–1 points) route to SMS or email only rather than a live dial, since the lowest-scoring slice is where a call is least likely to be worth an agent's time. A low score isn't a reason to delete a record — it's a reason to work it on the cheaper channel instead of the most expensive one.

Worked example: a 10,000-lead batch

Say you ordered 10,000 leads at the standard $0.012/lead rate ($120) with no state or age filter beyond the vertical you're working. A typical mobile-validation split and an even age spread across 18–64 might sort out something like this once scored:

• Tier A — roughly 2,500–3,000 records. Mobile, inside your vertical's age sweet spot, in the newer half of the file. Call these first; they're the highest-value fifth of what you paid $120 for.
• Tier B — roughly 4,000–4,500 records. Mobile with a partial match on age or recency. Normal cadence, normal script.
• Tier C — the remainder, commonly 2,000–3,000 records. Landline numbers and records well outside the age fit. Route to text or email instead of a dial — a landline can't take an SMS at all, and an off-fit age band is a worse use of a live agent's minute than it is of a templated send.

The exact split varies by state mix and vertical, but the shape holds: scoring doesn't shrink the file, it tells you which fifth to work with your best hour.

Score after the scrub, not before

Run this after your DNC scrub and phone-type check, not before — a record that scores a 5 but turns out to be DNC-listed never should have been in tier A to begin with. A bundled scrubber is the practical way to get the mobile/landline flag this whole system depends on in the same pass as the DNC check; the one we point buyers at is Landline Remover (disclosure: that's an affiliate link, and we may earn a commission if you sign up through it) — upload the CSV and it returns the phone-type flag and the DNC/litigator check together, so the score and the scrub come out of the same file pass instead of two.

What this doesn't replace

Scoring sorts a list you already own into a calling order — it doesn't make a bad-fit list good. A file with the wrong state mix or a vertical that doesn't match the age range you bought won't score its way into a better batch; that's a buying decision, not a dialing one. And a score built on three signals is a starting order, not a verdict — a tier-C record that answers and qualifies is worth more than a tier-A record that never picks up. Update the score with real outcomes as the batch gets worked, the same way disposition codes turn a dial into a decision about what happens to that record next.

Buy the file with the signals already in it

Order from a builder that lets you filter by state and age band up front, so the age-band-fit signal starts closer to a match before you ever score anything. Link Leads lists run $0.012 per lead with a 5,000-lead minimum ($60.00), SMS or email, any state or age band at link-leads.com — grab the free 100-row sample first to see the fields a score like this one actually runs on.