Most people read a litigator flag the way they'd read a DNC flag: as a "do not contact" stamp. That's not quite what it is, and treating the two the same way either costs you contacts you could have safely reached, or — worse — makes you overconfident about the ones you keep.
A DNC hit tells you someone doesn't want marketing calls. A litigator hit tells you this specific person has a documented history of suing companies over unwanted texts or calls. Those are different facts, and they call for different decisions.
Full disclosure: I work for Ready. We sell a standalone litigator/DNC scrub at $0.005 per contact, so I have a stake in you caring about this. But the reason I'm writing it is that I keep seeing senders make the wrong call on flagged numbers — usually because nobody explained what the flag actually means.
What a litigator hit represents
A litigator (or "serial plaintiff") flag comes from databases that track people who have filed TCPA complaints or lawsuits — often repeatedly. Some of these individuals have filed dozens of suits. A subset of them actively cultivate contact: they'll keep a phone specifically to collect violations, respond in ways designed to prolong a conversation, and document everything.
The flag is a probabilistic warning, not a legal designation. It's saying: this number belongs to someone who has demonstrated they'll take a texting violation to court. It doesn't mean texting them is illegal. It means that if your text to them turns out to be non-compliant — no consent, sent during quiet hours, a marketing message on a transactional consent basis — you've handed a violation to the one category of person most likely to act on it.
TCPA statutory damages run $500 to $1,500 per text. A litigator hit tells you which contacts turn a sloppy campaign into an actual check.
Litigator vs. DNC: not the same list, not the same decision
These get conflated constantly, and they answer different questions.
| DNC hit | Litigator hit | |
|---|---|---|
| What it tells you | This person opted out of / registered against marketing contact | This person has sued over unwanted texts/calls before |
| Legal weight | Contacting can itself be the violation (for marketing, without consent) | Contacting is not inherently a violation — it's a risk multiplier |
| The right default | Suppress for marketing | Depends on your consent basis |
| False-positive cost | Lose a contact who didn't want you anyway | Lose a contact who might convert |
A number can pass a DNC scrub clean and still belong to a known litigator — that's the whole reason both lists exist. We wrote about that distinction in A Number Can Pass DNC and Still Sue You, and if you're building a compliance stack it's worth understanding they're separate layers, not one check.
The decision tree: suppress, downgrade, or drop
When a scrub flags a litigator, you have three real options. Which one is right depends almost entirely on your consent basis for that contact.
1. Suppress entirely (drop them). Right call when you have no documented consent. Cold lists, skip-traced numbers, purchased data — if a flagged number has no opt-in behind it, there is no upside that justifies texting a person who sues for a living. Drop it. This is the default for wholesalers and anyone working skip-traced numbers without consent.
2. Downgrade to a different channel. Right call when you have some relationship but not airtight SMS consent. Maybe this is an existing customer whose consent to marketing texts is murky. Instead of texting, route them to an email or a manual call your rep places by hand — a channel where the compliance surface is different and you're not firing an automated message into a documented plaintiff's phone.
3. Keep them — but only with clean consent. Right call when you have real, documented opt-in. If someone gave you explicit SMS consent through a verified opt-in and you're sending exactly what they consented to, a litigator flag alone isn't a reason to suppress. They opted in. You have the audit trail. The flag becomes a reason to be extra precise about quiet hours, use-case matching, and honoring STOP — not a reason to drop a legitimate lead.
The mistake I see most: treating every litigator hit as an automatic drop. On a clean opt-in list, aggressive suppression just deletes convertible contacts to soothe anxiety. The flag should tighten your discipline, not replace your judgment.
False positives are real — size them before you over-suppress
Scrub databases aren't perfect. Numbers get reassigned. A litigator's old number can pass to an ordinary person. Name-matching can catch the wrong record. The false-positive rate on litigator lists is low but non-zero.
That matters most for opt-in lists, where a flagged contact is more likely to be a real customer than a real plaintiff. Two practical guardrails:
- On cold/purchased lists, err toward suppression. The base rate of actual litigators is higher there, and you have nothing to lose by dropping a stranger. Purchased lists flag several times more litigators than opt-in lists — the suppression math is easy.
- On opt-in lists, treat a lone litigator flag as a reason to review, not auto-drop — especially if the contact has real engagement history (a prior purchase, replies, a click). A person who bought from you twice and gave explicit consent is probably not a serial plaintiff waiting to pounce.
You're balancing two costs: the ~$500–$1,500 exposure of texting a real litigator without solid consent, versus the lifetime value of a real customer you suppressed by mistake. On a cold list that math is lopsided toward suppression. On a warm list it's much closer.
Scrub once and the flag goes stale
A litigator flag is a snapshot. The databases update as new suits get filed, and phone numbers churn constantly — roughly a third of a year-old list is reassigned or disconnected. A scrub you ran eight months ago describes a list that no longer exists.
This is why a one-time cleanse doesn't hold. A list you scrubbed clean in January accumulates new litigator flags as those people file new suits, and picks up reassigned numbers you've never checked. We dug into how fast that happens in A List You Bought 8 Months Ago Now Has 3x the Litigators — the growth is real and it compounds.
A workable cadence:
- Cold/purchased lists: re-scrub before every send, or at minimum monthly. These decay fastest and carry the highest base rate.
- Opt-in lists: re-scrub quarterly, plus before any large blast.
- After any list purchase or import: scrub before the first send, never after. One text to a flagged number is already the violation — scrubbing after import is too late.
At $0.005 per contact, re-scrubbing a 20,000-contact list costs $100. Set against a single $500–$1,500 statutory-damages text — from the one category of person most likely to file — that's not a budget line worth agonizing over.
Where scrubbing sits in the bigger picture
Scrubbing is one layer, not the whole thing. It reduces the odds you hand a violation to someone who'll act on it. It does not create consent you don't have, and it doesn't fix a message sent during quiet hours or a marketing text riding on a transactional consent basis. Those are separate failures a scrub can't catch.
Ready runs litigator and DNC screening alongside automatic STOP handling, quiet-hours enforcement, and consent attestation capture — because scrubbing only earns its keep when the layers around it are in place too. The standalone scrub at $0.005/contact works whether or not you send through us, so you can screen a list before it ever touches a campaign. If you want the full picture of how these fit together, The Three Layers of TCPA Risk Reduction lays out where scrubbing stops and consent and quiet hours take over.
The takeaway
A litigator flag isn't a "don't call" order — it's information about who is behind the number and what they've done before. Read against your consent basis, it tells you whether to drop the contact, move them to a safer channel, or keep them with extra care. The flag sharpens the decision; it doesn't make it for you.
If you're running high-risk verticals — real estate, cold outreach, purchased data — scrub before you send, re-scrub on a cadence that matches how fast your list decays, and reserve suppression for the contacts where you can't defend the consent. You can screen a list against litigator and DNC data at $0.005 per contact without committing to sending through us at all. Run it before your next campaign and see what your list actually looks like.