How to scrub for known TCPA litigant numbers before dialing

Last updated 2026-07-09

Who are TCPA serial litigants and why do they matter for your dial list?

A TCPA serial litigant is someone who has filed, or been named in, multiple TCPA lawsuits against different companies. Some file dozens of cases per year. A few well-documented individuals have been involved in hundreds. They are not random consumers who got annoyed. They actively solicit calls by publishing their numbers, then sue.

The Telephone Consumer Protection Act, 47 U.S.C. § 227, allows a private right of action with statutory damages of $500 per violation and up to $1,500 for willful violations ^[1]. There is no cap per plaintiff. One litigant, one number called once with an autodialer or prerecorded voice without consent, is a $500 to $1,500 exposure. A small campaign can generate six-figure liability from a single serial filer.

Here is the practical problem. Serial litigants look identical to legitimate prospects in your CRM. The number is real. The person may even have submitted a web form (some do this on purpose to manufacture a paper trail they can later dispute). You can not tell them apart from a warm lead by staring at the digits. That gap is exactly why a dedicated scrub step exists.

For context on what these suits cost when they escalate, look at the cash app tcpa class action settlement and the credit one tcpa settlement. Both started as individual complaints before they grew.

What lists actually exist for known TCPA litigant numbers?

There is no government-maintained TCPA litigant list. The FCC does not publish one. The FTC does not publish one. What exists are private commercial products built from public court records.

Here are the main categories.

Court-record aggregators. PACER (the federal court filing system at pacer.uscourts.gov) is public. Several companies scrape it to pull plaintiff names, attorney names, and phone numbers out of TCPA complaints. They package the result into a suppression file you match against your dial list.

Commercial litigant databases. Vendors like Litigation Firewall, TCPA Litigator List, and similar services maintain rolling databases of numbers tied to TCPA plaintiffs. They charge per-record or monthly subscription fees. Pricing runs wide. Most batch scrubs land in the range of $0.001 to $0.01 per record, with monthly minimums that can run from roughly $200 to $2,000 depending on volume. These prices move, so get current quotes straight from vendors.

Attorney-linked suppression. A handful of the most active TCPA plaintiff attorneys represent the same small pool of repeat filers. A few data services flag numbers tied to those frequent attorneys as a secondary signal.

Peer-shared internal lists. Some compliance networks and industry groups swap suppression files among members. These are informal, and their coverage is uneven.

None of these lists are complete or officially sanctioned. A number that has never surfaced in a lawsuit could still belong to someone who files their first suit against you tomorrow. The scrub reduces risk. It does not erase it.

How does a litigant scrub actually work step by step?

The mechanics look a lot like a standard do not call list scrub. Here is a clean flow.

Step 1: Normalize your phone numbers. Get every number into a consistent format (ten digits, country code, no dashes or parentheses). A mismatch on a single digit means a litigant number slips right through.

Step 2: Export your dial list. Pull the numbers you plan to call in the next campaign cycle. Do this as close to the actual dial date as you can. Fresh data matters, because litigant lists update as new cases hit the docket.

Step 3: Submit to your litigant database vendor. Most accept batch uploads as CSV or run through an API. The vendor returns a flag for each number: match or no match.

Step 4: Remove flagged numbers. Do more than tag them. Pull them out of the active campaign. Some teams route them to a manual-review queue to decide whether a documented business relationship or clear consent might justify a call anyway. That is a call for your legal counsel, not your sales manager.

Step 5: Log the scrub. Record the date, the vendor, the version of the list you used, and how many numbers you removed. If you ever get sued, this log is evidence of a reasonable compliance process.

Step 6: Repeat before each campaign. A scrub from six months ago is stale. New litigants show up constantly.

Once set up, this whole thing takes under an hour for a campaign of fewer than 100,000 numbers. The expensive part is the first setup and vendor integration, not the ongoing scrubs.

Does scrubbing litigant numbers actually protect you legally?

It is a mitigation tool, not a legal shield. No court has ruled that scrubbing a commercial litigant list creates an affirmative defense to a TCPA claim. The statute does not mention litigant lists at all.

What it does is cut the odds of calling a known bad actor, and it supports a broader argument about good-faith compliance. Courts have looked at whether defendants had reasonable processes in place when they weigh damages and class certification. A documented, systematic scrub is a reasonable process.

The FCC's 2023 rulemaking on TCPA consent and lead generation (the one-to-one consent rules) ^[2] pushed attention toward consent chain integrity, but it did not touch the private right of action that serial litigants exploit. Scrubbing litigant lists is a complement to valid consent, never a swap for it.

The honest answer is simple. The biggest legal protection you have is rock-solid, documented consent for every number you dial. Litigant scrubbing is the second line. Skip either one and you are exposed.

How much does a TCPA litigant scrub cost compared to the liability it prevents?

The cost math here is lopsided in your favor.

Item	Approximate cost
Commercial litigant database (monthly, small team)	$200 to $500/month
Per-record batch scrub (high volume)	$0.001 to $0.01 per record
PACER record access (DIY research)	$0.10 per page [3]
Average TCPA individual settlement	$500 to $5,000 per plaintiff
Willful violation statutory damages	$1,500 per call [1]
Class action settlement (mid-size)	$5 million to $75 million+

The settlement range is wide because it turns entirely on call volume and how many class members can be identified. Even a modest individual lawsuit, once you add attorney fees and internal distraction, costs more than a full year of litigant scrubbing.

One caveat on the per-record numbers above. I have seen vendors quote these ranges in public pricing pages and industry chatter, but the costs are genuinely variable and some vendors do not publish rates at all. Get three quotes before you commit.

For teams running high-volume cold calling, a $300/month litigant scrub against even one avoided lawsuit pays for itself many times over. The question is not whether to do it. The question is which vendor has the freshest data.

What is the difference between a litigant scrub and a DNC scrub?

These are two separate processes for two separate legal risks. Plenty of teams confuse them or assume one covers the other. It does not.

A do not call telemarketer list scrub (the national DNC registry at donotcall.gov) tells you which numbers have registered a preference against telemarketing calls. Calling a registered number without an established business relationship or prior written consent violates the FTC's Telemarketing Sales Rule and can also trigger TCPA liability under the FCC's implementation rules ^[4].

A litigant scrub tells you which numbers belong to people who have actually filed TCPA lawsuits in the past. These two sets barely touch in practice. A serial litigant's number may not sit on the national DNC registry at all, because DNC status is not how they build cases. They build cases by receiving autodialed or prerecorded calls and then suing under 47 U.S.C. § 227(b), which does not require DNC registration.

You need both. Run your list against the national DNC registry (required by law), then run it against a litigant database (risk management). Treat them as two distinct steps in your pre-campaign checklist.

If you want to understand how to pull the national DNC list for your organization, the how do i get the do not call list article walks through that access process. For mobile phone do not call list questions, cell numbers have been registerable on the national DNC since 2003, so that scrub applies to mobile too.

Are there public court records you can use to build your own litigant list?

Yes, technically. PACER (pacer.uscourts.gov) is the federal court filing system. TCPA cases filed in federal district courts are public records. You can search by statute citation (47 U.S.C. 227) and pull plaintiff names, and sometimes phone numbers, out of complaints ^[3].

In practice, building your own list from PACER is painful for most small teams. The data is unstructured. Parsing thousands of complaints to extract phone numbers takes real engineering work. Coverage is incomplete on top of that, because plenty of TCPA cases are filed in state court, and state court records are far harder to aggregate.

State court systems like California's or the Tyler Technologies platforms used across Texas are not centrally searchable the way PACER is. A litigant who files in California state court never shows up in PACER at all.

For a team without a dedicated data engineer, the practical answer is to pay a vendor that already did this work. The DIY route makes sense only if you have the technical capacity and want to cross-check a vendor's list against your own.

How often should you update your litigant scrub list?

New TCPA cases hit federal courts every week. The most active serial litigants file multiple cases a month. A list that is 90 days old has real gaps.

The standard advice from compliance consultants is to scrub before each new campaign, not on a calendar. Run campaigns weekly, scrub weekly. Batch campaigns monthly, scrub monthly at the minimum.

There is one other trigger for an off-cycle refresh. Any time you buy or rent a new lead list from a third party, scrub it. Purchased and rented lists carry higher risk because you have no insight into how the leads were collected. Run a fresh litigant scrub the day the list arrives, before it touches your dialing queue.

Most commercial litigant database vendors refresh their records somewhere between daily and weekly. Ask your vendor point blank how often their data updates. That cadence sets the ceiling on how fresh your protection can be.

What should you do if a known TCPA litigant calls you or contacts your business?

This happens more than people expect. Some litigants submit web forms or inbound inquiries precisely to build a paper trail they can later dispute as insufficient consent.

If someone identifies as a TCPA plaintiff or attorney, or your scrub flags an inbound number as a known litigant, do this: add the number to your internal do-not-contact list right away and document why. Do not call them back, even if they filled out a form.

The broader lesson is that consent documentation has to be airtight. If a litigant submits a form on your site and you call them, your defense rests entirely on that form. The timestamp, the IP address, the exact disclosure language, and whether the form truly captured prior express written consent as required by the FCC's rules under 47 C.F.R. § 64.1200 ^[5]. If any piece of that record is weak, the fact that they submitted the form will not save you.

For outbound teams that also run text message marketing or SMS campaigns, the same logic holds. A litigant who texts you first does not thereby hand you valid TCPA consent to text back, unless the opt-in language specifically covers it.

What does a complete pre-dial compliance checklist look like?

Litigant scrubbing is one step in a bigger process. Here is a full pre-dial checklist that compliance-minded teams actually run.

1. Consent verification. Confirm prior express written consent for each number, with documentation (timestamp, IP, disclosure text). For cold call campaigns to business lines, check whether a business exemption applies.

2. National DNC registry scrub. Access via donotcall.gov for your SIC code. Required at least every 31 days under FTC rules ^[4].

3. State DNC scrub. Several states (Indiana, Texas, and Wyoming among them) maintain their own DNC lists with separate access requirements.

4. Internal DNC/suppression list. Anyone who asked you not to call, filed a complaint, or triggered prior legal action goes here.

5. Litigant database scrub. Cross-reference against a commercial litigant list. Document the vendor name, list version, and date.

6. Reassigned numbers check. The FCC's Reassigned Numbers Database, run by USAC (usac.org), helps you spot numbers reassigned to a new subscriber since your last contact ^[6]. Calling a reassigned number can create TCPA liability against the new owner.

7. Time-of-day check. TCPA regulations permit calls between 8 a.m. and 9 p.m. local time at the called party's location ^[1]. Automate this check. Do not lean on agents to remember.

8. Record the scrub log. Date, every list used, counts removed at each step.

LeadCompliant offers a free pre-campaign checklist and TCPA compliance kit at leadcompliant.com if you want a templated version to hand your ops team.

Steps 1 through 8 take maybe two hours of setup the first time, then a fraction of that on each cycle once your integrations are wired in.

How do TCPA litigant databases stay current and how accurate are they?

The reputable vendors pull from PACER on a regular schedule, parse the complaints, and extract plaintiff contact information. Some also watch state court dockets where data feeds exist. The best ones cross-reference plaintiff names against known attorney relationships to catch cases that never listed a phone number in the complaint itself.

Accuracy is genuinely uneven. Nobody has published an independent audit of any commercial litigant database that I am aware of. Vendors claim coverage in the tens of thousands of unique numbers, but what share of active litigants that actually represents is unknown.

There is a false positive risk too. A number once tied to a litigant may have been reassigned since. If you suppress a number now owned by a legitimate prospect, you lose a sale but carry no legal risk. That trade is fine.

The false negative risk is the one that costs you money. A litigant whose number is not in the database. No commercial list is complete. Treat it as a serious risk reduction tool, not a guarantee.

If this worries you, stack two vendors' lists. Running your list against two separate litigant databases catches more than either one alone. The marginal cost is usually small.

What have courts said about TCPA serial litigants and good-faith compliance?

Courts have reacted to serial litigants in different ways. Some federal courts have noted that a plaintiff's status as a serial filer bears on whether they suffered actual harm, and a few decisions have questioned whether serial litigants even have standing under Article III after TransUnion LLC v. Ramirez (2021) ^[7], which held that a plaintiff must have a concrete injury to sue in federal court.

The 11th Circuit in Salcedo v. Hanna (2019) held that a single unsolicited text message was not a concrete enough injury for Article III standing ^[8]. That ruling does not apply everywhere, and the Ninth Circuit has landed differently, but it shows courts are not uniformly friendly to serial litigant claims.

None of this means you should skip compliance steps and bet on standing arguments to bail you out. Standing challenges take expensive litigation. Even a win on standing costs money.

The more useful practical point is this. The FCC's 2015 TCPA Omnibus Declaratory Ruling and Order stated that callers who take reasonable steps to avoid calling reassigned numbers and to honor consumer preferences can limit liability ^[9]. Courts have echoed similar reasoning in individual cases. A documented litigant scrub process is evidence of reasonable steps.

The statute text itself is worth knowing. 47 U.S.C. § 227(b)(3) says a person may bring an action "to recover for actual monetary loss from such a violation, or to receive $500 in damages for each such violation, whichever is greater" ^[1]. That $500 floor is per violation, per call or text. It adds up fast.

Frequently asked questions

Is there a free government list of TCPA serial litigants?

No. The FCC and FTC do not publish litigant lists. The only public source is PACER, the federal court system at pacer.uscourts.gov, where you can search TCPA cases by statute. Extracting phone numbers from individual complaints takes manual work or custom software. Every ready-to-use litigant suppression list is a commercial product built from PACER and state court data.

Can I build my own TCPA litigant suppression list from PACER?

You can, but it is not practical for most teams. PACER charges $0.10 per page and the data is unstructured text. You would search by statute citation, download complaints, and parse phone numbers by hand or with custom code. State court cases are mostly excluded because there is no central state filing system. Commercial vendors have already done this work, so paying them is usually faster and cheaper.

How many TCPA lawsuits do serial litigants file each year?

Precise counts are hard to verify because TCPA cases are filed in both federal and state courts, and not all are publicly indexed. Federal TCPA filings have numbered in the thousands annually for most years since 2015, with individual prolific filers sometimes appearing in dozens or hundreds of cases. No single government source publishes a clean annual count broken down by plaintiff.

Does scrubbing a litigant list give me an affirmative defense under the TCPA?

No court has recognized a litigant-scrub defense as a statutory safe harbor. The TCPA's defenses are narrow: prior express consent, established business relationship (for certain calls), and emergency purposes. A litigant scrub supports a broader good-faith compliance argument and may influence damages, but it is not a defense you can cite chapter and verse.

What is the minimum TCPA statutory damages amount per violation?

Under 47 U.S.C. § 227(b)(3), the minimum is $500 per violation for standard violations and $1,500 per violation for willful or knowing violations. Courts have discretion to treble damages in willful cases. There is no cap per plaintiff in individual suits, though class action settlements typically spread a negotiated total across many class members.

How is a TCPA litigant scrub different from checking the national DNC registry?

They address different legal risks. The national DNC registry (donotcall.gov) identifies numbers where consumers registered a preference against telemarketing calls. A litigant scrub identifies numbers tied to people who have previously sued under the TCPA. The two lists barely overlap. You need both: DNC scrubbing is legally required, and litigant scrubbing is risk management.

How much do commercial TCPA litigant database subscriptions cost?

Most vendors charge monthly subscriptions from roughly $200 to $2,000 depending on volume and features, or per-record fees in the range of $0.001 to $0.01 for batch scrubs. These are market estimates from publicly discussed pricing. Actual quotes vary by vendor and contract terms. Get multiple quotes and ask specifically how often the database updates.

Do TCPA litigant scrubs apply to text message campaigns too?

Yes. The TCPA covers both calls and text messages sent via autodialer or prerecorded content under 47 U.S.C. § 227(b). Serial litigants sue over both. Your litigant scrub should run before SMS campaigns exactly as it does before voice campaigns. Some litigants are more active in text cases, and the databases typically cover numbers regardless of how the litigant was first contacted.

What happens if a known TCPA litigant submits a web form on my site?

Document everything right away: timestamp, IP address, the exact consent language shown, and the submission record. Add the number to your internal do-not-contact list and consult legal counsel before calling. Some litigants submit forms specifically to dispute the quality of consent later. Strong documentation is your best protection, but calling a known litigant back is a high-risk move regardless of the form.

How often should I refresh my litigant scrub?

Scrub before each new campaign, not on a fixed calendar. Run campaigns weekly, scrub weekly. Always run a fresh scrub the day you acquire any purchased or rented lead list. Most commercial litigant databases update daily to weekly, so ask your vendor their refresh cadence. A 90-day-old scrub has real gaps given how often new cases are filed.

Can stacking two litigant database vendors improve coverage?

Yes, and it is worth doing if your call volume is high. No single commercial litigant database captures every case, especially state court filings. Running your list against two vendors catches numbers that appear in one dataset but not the other. The marginal cost per record is low, and the added risk reduction from a second source is real.

Does the FCC's reassigned numbers database help with litigant risk?

Indirectly. The FCC's Reassigned Numbers Database (run by USAC at usac.org) tells you if a number was reassigned to a new subscriber since your last contact. That stops you from accidentally calling a new subscriber under old consent. It does not flag litigants specifically, but combining it with a litigant scrub and a DNC scrub closes three distinct liability gaps in one pre-campaign workflow.

Sources

1. U.S. Code, 47 U.S.C. § 227, Telephone Consumer Protection Act: $500 per violation minimum statutory damages, $1,500 for willful violations; calls permitted 8am-9pm local time
2. PACER, Public Access to Court Electronic Records (U.S. Courts): Federal court filings including TCPA complaints are publicly accessible; PACER charges $0.10 per page
3. FTC, Telemarketing Sales Rule, 16 C.F.R. Part 310: National DNC registry scrub required at minimum every 31 days under FTC Telemarketing Sales Rule
4. FCC, 47 C.F.R. § 64.1200, Delivery Restrictions: FCC rules at 47 C.F.R. § 64.1200 define prior express written consent requirements for autodialed and prerecorded calls
5. USAC, FCC Reassigned Numbers Database: The FCC Reassigned Numbers Database, administered by USAC, allows callers to check whether a number has been reassigned to a new subscriber
6. TransUnion LLC v. Ramirez, 594 U.S. 413 (2021), Supreme Court: 2021 Supreme Court ruling held plaintiffs must have concrete injury for Article III standing, relevant to serial litigant standing challenges
7. Salcedo v. Hanna, 936 F.3d 1162 (11th Cir. 2019): 11th Circuit held a single unsolicited text message was not a sufficiently concrete injury for Article III standing under TCPA
8. FTC, National Do Not Call Registry, donotcall.gov: National DNC registry is maintained by FTC; cell numbers have been registerable since 2003