Litigator Scrub: How to Screen Call Lists for TCPA Plaintiffs

A litigator scrub checks your call and text lists against databases of known TCPA plaintiffs, serial filers and their attorneys, and removes the matches before anyone dials. It is not a legal requirement. It is a risk filter that sits next to your Do Not Call scrub, and it catches the numbers the registry never will.

This guide covers what a litigator scrub does, where it fits in an outbound workflow, how to judge a provider, and what to do when a number matches. It is written for owners and ops managers at insurance agencies, brokerages, legal intake teams, healthcare practices and lead gen shops.

TL;DR

• A litigator scrub flags numbers tied to known TCPA plaintiffs, serial filers and their attorneys. A DNC scrub does not.
• Run both. The DNC scrub meets federal rules. The litigator scrub protects you from professional plaintiffs who keep their numbers off the registry.
• Freshness and name matching decide quality. Stale lists and number-only checks leave gaps.
• Treat a match as high risk, not as proof of anything. Suppress it or send it to human review.
• Scrub before the dial, inside the dialer, and keep a record of every check.

Table of Contents

• What a litigator scrub is
• Litigator scrub vs. DNC scrub
• Why the scrub matters more in 2026
• How a good litigator scrub works
• Where to put the scrub in your workflow
• What to do when a number matches
• Industry notes
• Our perspective
• Putting it into practice with RevRing
• A 30-day rollout plan
• FAQ
• Sources

What a litigator scrub is

Litigator scrubbing is the process of identifying and flagging phone numbers associated with known TCPA litigators, serial plaintiffs and their attorneys. Providers build their databases from court filings, complaint records and demand letters. You send your list, they compare it, and you get back the clean records and the flagged ones.

The reason the category exists is the size of the downside. Under the TCPA, statutory damages start at $500 per call, and courts can raise that to $1,500 per call for willful or knowing violations. Legal fees come on top. Multiply by a few hundred calls in a class action and one bad dial list becomes a balance sheet event.

That math is why some compliance vendors describe the plaintiff side as a “cottage industry” of repeat filers who look for chances to sue marketers. A litigator scrub is how you stay out of their path.

What it is not

• Not a consent record. A clean scrub does not prove you had permission to call. Consent still has to be documented. See our express written consent playbook.
• Not a legal shield. Nothing in the TCPA says a scrub protects you. It lowers the odds. It does not change your obligations.
• Not a verdict. A match is a record match, not a finding about a person.

Litigator scrub vs. DNC scrub

Most teams assume a National DNC scrub covers them. It does not cover this. Many serial plaintiffs deliberately keep their numbers off the DNC registry, so a registry check will pass them straight through.

The two scrubs do different jobs:

Compliance professionals call this stacking: DNC and litigator scrubs catch different high-risk groups, so using both is standard. Add your own internal do-not-call list and any state registries that apply to you, and you have the full stack.

Why the scrub matters more in 2026

Two changes make sloppy list hygiene more expensive.

First, consent revocation is easier. The FCC’s rules on revoking consent for robocalls and robotexts took effect April 11, 2025. A consumer can now opt out in reasonable ways, and you have to honor it quickly. A team without a tight suppression process will slip.

Second, courts have more room to read the statute for themselves. In June 2025 the Supreme Court held in McLaughlin Chiropractic v. McKesson that district courts are not bound by an agency’s interpretation of a statute in civil enforcement proceedings. For callers, that means FCC readings no longer settle every case. Outcomes depend more on the facts and the court in front of you, which is a reason to reduce exposure at the source.

The dialer definition also matters. In Facebook v. Duguid, the Court held that an autodialer must be able to store or produce numbers using a random or sequential number generator. That narrowed one theory of liability. It did not remove TCPA risk, and plaintiffs still bring claims on consent, DNC and timing grounds. Talk to your counsel about how your own setup fits.

How a good litigator scrub works

Not every list is equal. Four things separate a useful scrub from a checkbox.

1. Freshness

Serial plaintiffs change numbers and often use new ones to attract calls. A list that is a few weeks old can miss active baiting. Ask any provider how often the data updates and how new filings reach the database.

2. Name matching, not only number matching

Litigators use several lines: personal, work, family, secondary phones. A number-only scrub misses the other lines. Matching against plaintiff and attorney names gives a much stronger defense. Ask whether the provider matches on name and address, and how it handles false positives.

3. Real-time access

Batch uploads work for purchased lead files. They do not work for live web leads that you want to call in seconds. Integrating via API enables real-time pre-dial checks, so a flagged number is blocked before a connection is attempted.

4. Coverage of text as well as calls

Texts carry TCPA risk too. Make sure the scrub runs on SMS lists and not only on voice campaigns.

Provider checklist

Use these questions in vendor calls:

1. How is the database built, and how often does it update?
2. Is matching by number only, or by name and attorney as well?
3. Is there an API for per-lead checks, and what is the response time?
4. What do you return: a flag, a category, a case reference?
5. Can you export a log of every check with a timestamp?
6. What is the pricing model: per record, per batch, per seat?

Several established services run batch scrubs of call and text lists. Compare them on the criteria above, not on database size claims alone.

Where to put the scrub in your workflow

A scrub works only if it sits at the right points. Here is a simple sequence for an outbound operation.

1. At lead intake. Check each new lead as it arrives, by API where you can. Flagged leads never enter the dial queue.
2. Before every upload. Any purchased or imported list gets a batch scrub before it touches your dialer.
3. On a schedule. Rescrub your active database on a fixed cadence. A number clean in January may not be clean in March.
4. At the dial. Dialing software should block or escalate flagged records automatically. Agents should never have to remember.
5. After the call. Honor opt-outs immediately and add them to your internal suppression list.
6. In the record. Log what you checked, when and with what result.

That last step matters in a dispute. We cover the timing side in our post on the 31-day scrub rule and court-ready evidence and the logging side in our compliance audit trail guide.

The same logic applies to call recording. State rules differ, and a mistake there creates its own liability. This overview of U.S. call recording laws by state is a useful companion when you set up contact center rules.

What to do when a number matches

A match is not a guilty verdict. It is a record match against a database, and a person with the same name may be unrelated. Still, for outbound the safe default is simple:

• Suppress it. Do not dial. This is the standard approach for most teams.
• Or escalate. Send it to a compliance owner who can look up the actual case record if the lead is valuable.
• Never let an agent decide on the fly. Rules beat judgment at 4:45 p.m. on a Friday.
• Never contact the person to ask about it. Contact is the risk.

If your team takes inbound calls from people who then ask odd questions about recordings, consent or your dialer, train agents to stay calm, stick to the script and escalate. Odd, leading questions on a call are a known pattern, and agents should know it.

Industry notes

Insurance. Medicare and final expense calling is heavily scrutinized. Lead sources vary in quality, and a scrub on every purchased lead is a basic hygiene step. Our post on TCPA compliance for insurance agents goes deeper.

Real estate. Multi-line dialing speeds up speed-to-lead, which raises the number of calls per hour and the cost of a bad list. Scrub first, then dial in volume.

Legal intake. Firms handling inbound and outbound follow-up should scrub web form leads before callbacks.

Healthcare. Outreach has HIPAA considerations on top of TCPA. Keep scrub logs free of unnecessary patient data and work with your compliance officer.

Lead generation. If you sell leads, buyers will ask whether you scrub. Doing it at capture, before delivery, is a selling point.

Our perspective

We see the same pattern at agencies that grow fast. The compliance process that worked for 12 agents breaks at 60. Lists get uploaded from three places, someone skips a step, and the dialer happily calls whatever it is given.

Our view is blunt: a scrub should not be a task. It should be infrastructure. That means checks sit inside the workflow, rules block records automatically, and every action leaves a trail. When compliance depends on people remembering, it fails at scale.

Three principles guide how we think about it:

• Stack the defenses. DNC, internal suppression, consent records and a litigator scrub each cover a different gap. No single layer is enough.
• Automate the block. A flagged number should never reach an agent’s screen.
• Keep the evidence. If you cannot show what you checked and when, it did not happen.

We built our platform around compliance infrastructure for regulated teams, connecting calling, CRM and automation so that rules apply to every record the same way. If you run a scrub vendor today, keep it. The point is to wire its results into the dial path.

— Marc

Putting it into practice with RevRing

RevRing is a cloud platform that brings predictive dialing, blended inbound and outbound calling, CRM connectivity, lead routing and compliance infrastructure (TCPA, DNC, HIPAA BAA) into one place. It works with your existing CRM rather than replacing it.

If you are mapping where scrubs, suppression and consent checks belong in your dial flow, see how RevRing works or review plans and per-seat pricing. Plans start at 39.99 USD per month per seat on Starter. To talk through your own compliance setup, start from revring.com and schedule a live demo.

A 30-day rollout plan

If you have no litigator scrub today, here is a realistic month.

Week 1: Audit. List every source of numbers: purchased leads, web forms, referrals, old databases. Note who uploads them and where.

Week 2: Choose and test. Run a sample file of a few thousand records through two or three providers. Compare hit counts, how matches are explained and turnaround time. Ask your counsel to review the contract.

Week 3: Wire it in. Connect the scrub at intake and before imports. Set the rule for matches: suppress or escalate. Document it.

Week 4: Train and log. Brief agents and managers on what a flag means and who owns escalations. Start the log. Schedule your recurring rescrub.

After that, review quarterly: hit rates, escalations, and any complaints or demand letters. If you get a demand letter, treat it as urgent and call your attorney the same day.

FAQ

Is a litigator scrub required by law?

No. The TCPA does not require it, and the DNC registry check is the federal baseline. A litigator scrub is a voluntary risk control that most outbound compliance teams add on top. Ask your attorney whether your state or industry adds any rules.

Does a DNC scrub already cover litigators?

No. Many serial plaintiffs keep their numbers off the registry, so a DNC scrub passes them. The two checks cover different risks, which is why teams run both.

How often should I scrub my lists?

Scrub every new lead at intake and every imported list before dialing. Rescrub active databases on a fixed schedule, since plaintiffs change numbers often. A list that is only weeks old can miss recent activity.

What should I do if a number matches?

Do not dial it. Suppress the record or send it to a compliance owner for review. A match is a record match, not proof about the person, so verify the case record if the lead is worth the effort.

How much can a TCPA violation cost?

Statutory damages start at $500 per call and can reach $1,500 per call for willful or knowing violations, plus legal fees. Class actions multiply that. Speak with a TCPA attorney about your specific exposure.

Sources

• Litigator Scrubbing Service, The DNC Project
• TCPA Litigator List
• TCPA Litigator List, PossibleNOW
• TCPA Litigator Name Search
• Litigator Insights
• Campbell-Ewald Co. v. Gomez, Legal Information Institute
• McLaughlin Chiropractic Associates v. McKesson, Legal Information Institute
• Facebook v. Duguid, Legal Information Institute
• FTC Q&A for Telemarketers and Sellers About DNC Provisions
• FCC: TCPA Rules on Revoking Consent