Scrubbing is one of the cheapest insurance policies in outbound. A litigator and DNC scrub runs $0.005 per contact: half a cent to find out whether a number belongs to someone who sues people for a living. Most of the content out there (including some of ours) pushes you to scrub harder and more often, and that advice is correct more often than it's wrong.
But there's a failure mode nobody talks about: a scrub that's too aggressive quietly deletes good buyers. A contact gets flagged, your ops person sees red, and the lead goes to the suppression bucket without a second look. If that contact was a legitimate buyer who happened to share a data signal with a known complainer, you just threw away pipeline to avoid a risk that may not have been real.
Full disclosure: I work for Ready, and we sell standalone litigator scrubbing at $0.005/contact. So you'd think I'd want you scrubbing everything into oblivion. I don't. A scrub that nukes good leads is a scrub that costs you money, and over time it trains your team to distrust the tool, which is worse. The point of this post is how to read a scrub result instead of treating every hit as a death sentence.
What a scrub result actually tells you
A scrub hit is not one thing. It's a bucket of very different signals that get lumped under one scary word. Before you suppress anything, you need to know which bucket the hit fell into, because the right action is different for each.
Broadly, a scrub result sorts into three tiers:
| Tier | What it means | Suppress or verify? |
|---|---|---|
| Known litigator | This specific number is tied to a person who has filed TCPA suits or demand letters before | Suppress. This is the whole point |
| DNC / DNC-complainer | On the federal/state DNC or has filed a do-not-call complaint | Suppress for cold outreach; context-dependent if you have consent |
| High-complaint / predictive flag | No lawsuit history, but statistically resembles risky numbers (list source, carrier complaints, pattern) | Verify before deleting. The highest false-positive rate lives here |
The first tier is where scrubbing earns its keep. A litigator flag doesn't mean "don't call" in general. It means this person has sued over a text before. With documented TCPA exposure sitting at $500 to $1,500 per message, suppressing a known litigator is an easy call. You're not losing a buyer; you're avoiding someone whose business model is your lawsuit.
The third tier is where good leads die. Keep reading.
The false-positive problem lives in the predictive layer
Known-litigator databases are relatively tight. A number is on there because there's a paper trail: a filed case, a demand letter, a documented complaint. False positives at that tier are rare.
The predictive and high-complaint signals are different. These lists infer risk from patterns: the list source, how many complaints a number has generated, whether it looks like a professional complainer's phone. That inference is useful at scale, but it's probabilistic, and probability produces false positives.
Here's a concrete version of the problem. Say you buy a 20,000-record list and scrub it. Your litigator hits come back at, say, 2%, or 400 numbers. Of those, maybe 250 are hard litigator/DNC matches you should absolutely suppress. The remaining 150 are predictive or high-complaint flags. If even a third of those 150 are legitimate buyers caught in a wide net, you've suppressed ~50 people who would have answered the phone. On a list where you expected a 5% close rate on connects, that's real revenue walking out the door, and you'll never see it, because suppressed contacts don't show up in your "what went wrong" reporting.
That's the asymmetry: hard litigator hits are rare and worth suppressing; predictive flags are more common and worth a second look.
When to suppress on sight
Suppress immediately, no verification needed, when:
- The hit is a known litigator match. Documented suit or demand-letter history. There is no upside to calling or texting this person.
- It's a cold list and the number is on the DNC. No prior business relationship, no consent, DNC flag: don't call it. This is also why scrub order matters: scrub before import so these never load into your dialer screen in the first place.
- The flag matches an entry on your internal do-not-call list. If someone already told you to stop, that's the list regulators check first, and no amount of "but they're a good buyer" overrides it.
In all three cases, the cost of being wrong (a lawsuit at $500 to $1,500 per text, a regulator complaint) dwarfs the value of one more connect. Delete and move on.
When to verify before you delete
Pause and look closer when:
- The hit is a predictive/high-complaint flag with no documented litigator or DNC match. This is the murkiest signal and the one most likely to catch a real buyer.
- The contact has an existing relationship or prior consent with you. A flag on a number you have a written opt-in for is a different situation than a flag on a cold purchased record. Consent doesn't make a litigator safe, but it changes the risk math on a soft predictive flag.
- The flag is on a high-value named account, such as a contact your sales team already recognizes, a company you're mid-deal with. A broad list sometimes catches a legitimate business number because of carrier-level complaint noise, not because the human behind it sues people.
Verifying doesn't mean "call them anyway and hope." It means: check whether you have consent on file, confirm whether the hit is a hard match or a soft one, and if you're genuinely unsure on a high-value contact, route it to the channel with the lower regulatory surface. Which brings up the practical workaround.
Route the gray-area contacts, don't just delete them
A contact caught on a soft flag doesn't have to be a choice between suppress and blast. There's a middle path.
Cold texting a flagged number is the highest-risk move you can make, because cold SMS has essentially no compliant path under 10DLC and a litigator-adjacent flag amplifies that. But a dial carries different exposure than a text in many contexts. If you've got a gray-area contact you don't want to lose, a manual, one-at-a-time dial (not an auto-dial blast) lets a human make the judgment call on a single number rather than a machine suppressing or spraying 50 of them.
Ready's Power Dialer supports exactly that kind of deliberate dialing (manual dialing, plus call recording for your own audit trail), and the standalone scrub runs independently of whether you ever send a text. You can scrub a list, suppress the hard hits, and manually work the handful of high-value soft flags through voice instead of torching them. That's not a loophole. It's matching the channel to the risk.
Build the scrub into a cadence, not a one-time purge
The reason teams over-suppress is usually that they treat scrubbing as a single, high-stakes event: scrub once, delete everything flagged, never think about it again. That makes every hit feel permanent and raises the cost of a false positive.
Treat it as maintenance instead. Lists rot. a list you scrubbed in January is dirty again by March, and purchased lists accumulate litigators over time faster than lists you grew yourself. When you re-scrub on a cadence, a soft flag that shows up once and disappears next cycle was probably noise. A number that keeps hitting as a hard litigator match is a real suppression. Repeat scrubbing turns a single scary snapshot into a trend you can actually read.
At $0.005/contact, re-scrubbing 20,000 records costs $100. Losing even two or three legitimate deals to over-aggressive suppression costs a lot more than that.
The practical takeaway
Scrubbing is risk reduction, not a verdict machine. The discipline isn't "scrub harder"; it's "read the hit before you act on it":
- Hard litigator and DNC matches: suppress on sight. This is what you paid half a cent to find.
- Predictive/high-complaint flags with no documented history: verify, especially on high-value or consented contacts. This tier produces most of your false positives.
- Gray-area, high-value contacts: route to a manual dial rather than deleting or cold-texting. Let a human make the call on one number.
- Run it on a cadence so a one-time snapshot becomes a trend you can trust.
Compliance is still your responsibility. A scrub reduces exposure; it doesn't make you lawsuit-proof. But the goal is to suppress the people who sue for a living without throwing away the people who'd buy from you. Those are not the same list.
If you want to scrub a list before you dial or blast (standalone, no SMS required), you can start free with 2,500 credits and see how your real list sorts across these tiers before you suppress a single contact. The product and pricing details are here.