List hygiene is the least discussed and most load-bearing function on an outbound floor. It is also the one that fails invisibly: nothing breaks, no alarm goes off, the dialer keeps dialing. Contact rates just drift down over a few weeks until someone concludes the reps have gone soft.
This is the routine that prevents that — what to run, in what order, and how often.
The order matters
Hygiene steps are not interchangeable, because each one changes the input to the next. Running them in the wrong sequence wastes money on records you were about to discard.
- Standardise. Normalise addresses and names before anything else. Two records for the same house written differently are two records until you fix the formatting.
- Deduplicate. At household level, not row level. The same property arriving from two sources with two spellings is the commonest form of waste.
- Suppress. Apply your own lists — customers, prior complaints, internal do-not-call, litigators, anything you have decided is off limits — before you spend money enriching records you will never dial.
- Enrich. Now append phones, because you are only paying for records that survived the first three steps.
- Scrub. Registry scrub last, immediately before load, so the scrub is as fresh as possible when dialing starts.
Teams that enrich before suppressing routinely pay to skip-trace thousands of records they then throw away. It is the single most common expensive mistake in this process.
Household-level deduplication
Row-level dedupe catches identical strings and almost nothing else. Real duplicates look like 124 N Maple St and 124 North Maple Street, or the same parcel appearing once with the owner’s name and once with a trust. Deduplicating on a normalised property identifier rather than on the text of the address is what actually collapses them.
The cost of getting this wrong is not just wasted dials. It is the homeowner who gets called twice in a week by two different reps from the same company, which is how a nuisance complaint starts.
Suppression is a permanent asset
Most floors treat suppression as a per-campaign checkbox. It should be a permanent, growing file that outlives every list you buy — because the cost of a suppression failure is asymmetric. A missed dial costs you a possible sale; a call to someone who has already asked you twice to stop costs you a complaint, and complaints are what regulators and carriers act on.
What belongs in it:
- Anyone who has asked not to be called, permanently and immediately
- Current and prior customers, unless a campaign deliberately targets them
- Known litigators and serial complainants
- Numbers that generated a complaint, regardless of outcome
- Households you have already sold, so a second rep does not re-pitch them
Store it independently of any vendor. A suppression file that lives inside a dialer you might replace is a suppression file you will lose.
Dead numbers and the decay curve
Phone data ages. Numbers get disconnected, reassigned, ported, abandoned in favour of a mobile. A list that produced strong connects in January will not in June, and no amount of coaching changes that.
The two defences are replacement and rotation. Replacement means going back for a new number when one goes dead rather than marking the record unreachable and losing the household. Rotation means retiring worked segments on a schedule and loading fresh ones, so the floor is never living on residue. Both need to be routine; neither survives as an occasional cleanup project.
It is worth being precise about what you measure here, because vendors report match rate and match rate is not the number that matters — the distinction between a match and a right-party connect is where most list disappointment actually lives.
A working cadence
| When | What runs |
|---|---|
| Every load | Standardise, dedupe against everything already in the system, apply suppression, registry scrub |
| Daily | Push new do-not-call requests and complaints into suppression — same day, no batching |
| Weekly | Review contact rate by segment age; retire segments that have fallen below your floor and queue replacements |
| Monthly | Re-scrub anything held longer than a campaign; audit a sample for wrong-party and stale-ownership rates |
What good looks like
The honest test is whether you can answer three questions in under a minute: when was this segment last scrubbed, how many times has this household been dialed, and what is the contact rate by segment age. A floor that can answer those is a floor where a falling connect rate leads to the right diagnosis instead of a coaching session.
For the buying side of the same problem — how to evaluate a provider before their records ever reach your dialer — see best skip tracing software and bulk skip tracing. For what the cleaned list should cost you per booked opportunity, see the cost calculator.
Frequently asked questions
How often should a call center scrub against the DNC registry?
Before every load, and again on a standing schedule for anything held longer than a campaign. Registrations are added continuously, so a scrub performed once at purchase decays from the day it ran. Treat the scrub as a property of the load, not of the file. Operational detail is in DNC compliance for outbound solar; none of this is legal advice.
What is the difference between a duplicate and a suppression?
A duplicate is the same household appearing twice in the data you are about to load. A suppression is a household you have decided never to call again — a prior customer, a complaint, an internal do-not-call request, a competitor. Duplicates waste dials; failing to suppress creates the calls that generate complaints. They need separate lists and separate handling.
Why does contact rate fall over the life of a list?
Because the reachable records get reached first. Every pass removes connects, leaving a residue enriched in dead numbers, wrong parties and people who never answer. The decline is a property of the file, not of the floor — which is exactly why managers so often misread it as a rep performance problem and go looking for a coaching fix.