The Best TCPA Litigator Scrub List Services: Who Can Screen Your Calls and Texts Against Known Litigators

Most TCPA lawsuits don’t come from random consumers. A large share come from a small, identifiable group of repeat plaintiffs and the attorneys who file for them. Contact Center Compliance, one of the oldest vendors in this space, says about one-third of TCPA suits come from serial plaintiffs and litigators. Whatever the exact number, the takeaway for anyone running outbound calls or texts is the same: if you can identify those numbers before you dial, you avoid a large part of your exposure.

That is what a TCPA litigator scrub does. Below is a practical look at the companies that offer it, what each one actually provides, and how to choose.

Litigator scrubbing vs. Do Not Call scrubbing

A DNC scrub checks your list against the National Do Not Call Registry, state DNC lists, and your own internal suppression list. That is legally required for telemarketing. A litigator scrub is different. It checks your numbers against a database of people who have filed TCPA lawsuits, sent demand letters, or filed repeated complaints, plus the attorneys behind them. It isn’t required by law. It’s a risk filter that removes the contacts most likely to turn a single call into a federal case.

Most serious outbound programs run both. Several of the vendors below bundle them.

Companies that screen outbound lists against TCPA litigators

1. TCPALitigatorList.com
TCPA Litigator List has been operating since 2017 and focuses on litigator suppression. The company says its database holds over 600,000 names, including individual plaintiffs, professional and multi-case litigators, demand-letter “trolls,” plaintiff attorneys, and frequent DNC complainers, and that its researchers update it every weekday. You can upload a CSV or Excel file with multiple phone columns and download a clean list, or connect through a real-time API that checks each number before the call and blocks it on a match. A Name Recognition Algorithm flags serial litigators by name, which helps catch plaintiffs who switch to new prepaid numbers. The service also scrubs against federal and state DNC lists. Pricing is published: a Basic plan at $199 a month, and API plans starting at $299 a month that scale to enterprise tiers.

2. Contact Center Compliance (DNC.com) – Litigator Scrub
DNC.com has been in call center compliance for more than 20 years. Its Litigator Scrub runs alongside its wireless, VoIP and DNC scrubs, and the company says its litigator data is updated in real time from original court documents. It offers a REST API and lists about 20 integrations, including Five9, Genesys, Salesforce, Convoso, RingCentral, Vicidial and PhoneBurner. Pricing isn’t published; you book a meeting.

3. The Blacklist Alliance – TCPA Litigation Firewall
Blacklist Alliance’s firewall scrubs against its own high-risk data plus your internal DNC list, the National DNC Registry and state registries, for both inbound and outbound campaigns. It’s widely used in lead generation, partly because it is available as a LeadConduit (ActiveProspect) add-on. Subscribers also get access to online TCPA compliance training.

4. PossibleNOW – DNCSolution
PossibleNOW is aimed at enterprises. DNCSolution checks calls in real time against federal, state, internal, wireless, reassigned-number and known-litigator lists. It’s a fit for large financial, insurance and healthcare operations that want litigator suppression as one layer of a wider consent and preference program.

5. Gryphon
Gryphon puts litigator screening inside a broader real-time compliance platform that also enforces DNC rules, consent and calling-hour restrictions at the dialer level. It’s worth a look if you want one control point across many agents and dialers, but you’re buying a platform, not just a list.

6. Trestle – Real Contact
Trestle is mainly a phone validation and data quality API: line type, carrier, whether the number is active. It also includes a litigator-risk flag. It works well as an add-on at the lead-intake stage, though it isn’t a dedicated litigator database.

How to choose

  • Coverage beyond plaintiffs. Ask whether the database includes demand-letter senders and plaintiff attorneys, not just people named in filed cases. Many TCPA claims settle before anyone files.
  • Update frequency. Serial plaintiffs register new numbers constantly. Daily or weekday updates should be the minimum.
  • Name matching. Matching by phone number alone misses a litigator’s new number. Name-based matching closes that gap.
  • Real-time vs. batch. Batch scrubs suit campaign lists. Real-time API checks suit inbound leads, dialers and SMS platforms where numbers arrive constantly.
  • Integration. Confirm the vendor connects to your dialer, CRM or texting platform before you sign.
  • Transparent pricing. Published pricing makes it easy to compare cost per scrub at your volume.

What a scrub won’t do

Removing litigators lowers your exposure. It doesn’t fix a consent problem. You still need documented prior express consent where the law requires it, a working opt-out process, and calling-hour controls. The FCC’s revised opt-out rules take effect November 25, 2026, so this is a good time to check your revocation handling too. Treat litigator scrubbing as one layer of a compliance program, not a replacement for one.

If you’re deciding where to start, run a sample of your current list through TCPALitigatorList.com and count how many known litigators and plaintiff attorneys are already on it. That number usually makes the case on its own.

This article is general information, not legal advice. Talk to TCPA counsel about your specific program. Disclosure: this publication has a business relationship with TCPALitigatorList.com. Vendor details are drawn from each company’s public materials as of November 2026.

Pennsylvania Just Moved Your Calling Window. Three Weeks In, Is Your Dialer Caught Up?

Pennsylvania’s rewrite of its telemarketing law has been in force since October 18, 2026, and it is the kind of change that sits quietly in a dialer config until it causes a problem. If your campaigns still treat Pennsylvania like it did in September, you are now calling outside the legal window, texting under rules that did not apply before, and possibly relying on a consent standard the state no longer accepts.

Pennsylvania’s governor signed Senate Bill 992 on July 20, 2026. The law had a 90-day compliance runway, which put the effective date at October 18. Here is what changed on the floor, based on law firm summaries of the statute.

Texts and ringless voicemail now count

The definition of a telephone solicitation now expressly covers text messages and ringless voicemail, not just live calls. If your SMS or RVM programs ran on the assumption that Pennsylvania’s telemarketing law was a voice-only problem, that assumption ended on October 18.

The calling window got shorter

The old window was 8 a.m. to 9 p.m. The new one is 9 a.m. to 7 p.m., and solicitations on Sundays are banned entirely. Holidays were already off limits. That is three hours a day cut from your schedule, plus every Sunday, for any number tied to Pennsylvania. Check your time-zone logic too: the rule follows the person you are contacting, not your call center’s location.

Robocalls need written consent

According to Kelley Drye and Mac Murray & Shuster, the law replaces the old “express request” carve-out with a prior express written consent standard that largely tracks the federal TCPA definition. Robocalls using prerecorded or artificial voice need that written consent for residential, business and wireless lines, subject to statutory exceptions. Electronic signatures count. The established-business-relationship exception survives.

The law also prohibits unfair or deceptive practices to obtain consent and bans using synthetic or computer-generated messaging to defraud, deceive or mislead. Operators running AI voice agents should have their scripts reviewed with that language in mind.

No spoofing, and the brand is on the hook

Telemarketers may not falsify their caller ID name or number. The prohibitions reach anyone who “initiates or causes to be initiated” a solicitation, which TCPAWorld reads as extending liability to the company that hired the telemarketer. If you buy outbound from a vendor, their mistakes in Pennsylvania are now more clearly yours.

Penalties remain up to $1,000 per violation, or $3,000 when the person contacted is 60 or older. The Attorney General and district attorneys can enforce. Commentators disagree on how easily consumers can sue on their own under the state’s consumer protection law, so do not plan around a quiet plaintiffs’ bar.

The state is paying attention

This is not a sleepy statute. Attorney General Dave Sunday co-led a bipartisan coalition that in July urged the FCC to toughen “Know Your Customer” obligations for voice providers, citing an estimated one billion robocalls to Pennsylvanians the year before. A state AG that engaged on carrier policy is not likely to ignore a fresh telemarketing law.

Your three-week audit

  • Pull Pennsylvania numbers into their own calling-window rule: 9 to 7, no Sundays, no holidays.
  • Apply the same window to SMS and RVM, not just voice.
  • Audit consent records for robocall and prerecorded campaigns against a written-consent standard.
  • Confirm all seven opt-out words (stop, quit, end, revoke, opt out, cancel, unsubscribe) are honored.
  • Get written assurances from vendors, since liability flows back to you.

State mini-TCPAs like Pennsylvania’s tend to draw the same repeat plaintiffs who work the federal statute. Scrubbing your lists through TCPALitigatorList.com before you dial flags known TCPA litigators so a Sunday text to the wrong person does not turn into a demand letter.

Pennsylvania just joined the growing list of states with their own calling rules. The operators who handle that best treat state rules as data in the dialer, not a memo in a shared drive.

Sources

The FCC’s New Opt-Out Rules Hit on November 25. Here’s the Operator’s Checklist.

If you run calls or texts at volume, put November 25, 2026 on the wall. That is the day the FCC’s revised TCPA consent-revocation rules take effect, the day before Thanksgiving. The rules change how “stop” works for informational messages, let callers name the channels they will accept opt-outs through, and widen an exemption banks rely on for fraud alerts. They do not loosen anything for telemarketing.

The Commission adopted the Report and Order and a Further Notice of Proposed Rulemaking on September 30, 2026. Both were published in the Federal Register on October 26, which started the clock. Comments on the new proposals are due the same day the rules take effect, November 25, and reply comments are due December 28.

Why this matters on the floor

For two years, operators have been planning around a broad “revoke all” requirement: a consumer who opts out of one kind of robocall or robotext from you would be treated as opting out of everything. That requirement kept getting delayed, most recently to January 31, 2027. The new order replaces that approach for informational traffic with a narrower, category-specific framework.

In practice, a customer who texts STOP to your payment reminders can still get fraud alerts, appointment reminders and similar informational messages from you. That is a big deal for servicing, collections and healthcare scheduling teams, who were bracing for a single opt-out to shut down every non-marketing message.

What did not change

Telemarketing is where operators should be careful not to over-read the headlines. The narrower framework does not apply to advertising or telemarketing. If someone revokes consent in response to a marketing call or text, that revocation still covers all of your future marketing robocalls and robotexts. Your sales and promotional lists should treat an opt-out as global, just as before.

The deadline to honor a revocation also stays put: a reasonable time, not more than ten business days after you receive it.

The new tool: exclusive opt-out methods

Starting November 25, a caller can designate exclusive methods for revoking consent. The order lists three:

  • An automated, interactive voice or key-press opt-out during the call.
  • A reply text using any of seven words: stop, quit, end, revoke, opt out, cancel or unsubscribe.
  • A website or phone number the caller designates for opt-outs.

The method has to be clearly and conspicuously disclosed. If you tell texters to reply STOP, you still have to honor all seven words. Callers that designate an exclusive method do not have to process revocations sent some other way. Callers that do not designate one must keep honoring any reasonable method. Counsel at CommLaw Group also caution not to switch this on before the 25th, and note that separate mandated opt-outs for certain prerecorded telemarketing calls still apply.

The operator’s checklist

  • Tag every message stream as informational or telemarketing. The rules now treat them differently, so your suppression logic must too.
  • Map opt-outs to categories for informational traffic, and keep marketing opt-outs global.
  • Decide on exclusive methods, then update scripts, IVR prompts and text templates with the disclosure language before the 25th.
  • Parse all seven keywords on every inbound text channel, not just STOP.
  • Measure time-to-suppress. Ten business days is the ceiling, and the FCC is asking whether to cut it to seven.

What’s next

The FNPRM asks whether to shorten the ten-business-day window to seven, require two-way texting so consumers can always reply, make category-specific treatment depend on also offering a one-step “revoke all” option, and clarify how affiliates and separate business divisions are treated. None of that is final, but each would land on the same systems you are touching now. Build with headroom.

Clean opt-out handling is half the battle; the other half is knowing who you are dialing. Many TCPA suits come from a small group of repeat plaintiffs who know these rules better than most compliance teams. TCPALitigatorList.com lets outbound teams screen their lists against known TCPA litigators before a campaign goes out, so a rule change does not become someone’s next demand letter.

The bottom line for operators: November 25 gives informational programs some room, keeps marketing just as strict, and rewards teams whose opt-out plumbing is already tidy.

Sources

Two Texting Settlements, Two Different Mistakes: What Teleflora and Coast Dental Should Teach Every SMS Program

October brought two TCPA texting settlements worth studying side by side. One company allegedly texted people on the National Do Not Call Registry who never gave it their number. The other allegedly kept texting people after they replied STOP. Different failures, same result: a class action and a settlement fund in the millions.

Teleflora: $6 million over promotional texts to DNC numbers

In Carter v. Teleflora LLC, Case No. 2026-012979-CA-01, in the Circuit Court of Miami-Dade County, Florida, Teleflora agreed to pay $6 million to settle claims that it sent telemarketing texts without consent and without checking the National Do Not Call Registry. The plaintiff says she received multiple texts even though she never gave Teleflora her number. Teleflora denies wrongdoing.

The class covers people who never gave Teleflora their phone number, received more than one promotional text within a 12-month period starting May 9, 2021, and whose number had been on the National DNC Registry for at least 30 days. The estimated payment is about $251 per class member. The settlement received preliminary approval on August 26, 2026; claims, opt-outs and objections are due November 17, and the final approval hearing is set for November 25.

Coast Dental: up to $3.84 million over texts after STOP

In Chaviano v. Coast Dental Services, LLC, filed in Florida on July 6, 2026, Coast Dental agreed to pay up to $3,840,664. The suit alleged that the company sent appointment-related marketing texts and calls after consumers asked it to stop, in violation of the TCPA and the Florida Telephone Solicitation Act.

The class, roughly 24,308 people, covers individuals who received more than one appointment reminder or scheduling text within a 12-month period after replying “stop” or a similar opt-out. Class members can choose a pro rata cash payment of up to $59 or a voucher of up to $99 toward an electronic toothbrush. Preliminary approval came August 31, the final approval hearing is December 9, and claims are due December 24, 2026.

The operator’s read

These are not exotic legal theories. They are basic process failures, and they are the kind that scale. One missing suppression step touches every message in a campaign, which is exactly what makes a case certifiable as a class.

Here is what to check on your own program this week:

  • DNC scrubbing for SMS. If you send promotional texts to numbers you did not collect directly with consent, run them against the National DNC Registry first. Teleflora’s class is defined by registry status.
  • STOP handling end to end. Test it. Reply STOP to your own short code and confirm every platform that can send to that number stops, including reminder and scheduling flows that marketing may not think of as marketing.
  • Know where every number came from. “Never gave us their number” is a hard fact pattern to defend.
  • Watch your Florida exposure. Both cases were filed in Florida, and Coast Dental’s included a state-law claim on top of the TCPA.

Add a litigator screen

Consent and suppression are the foundation. A litigator screen is the next layer. TCPALitigatorList.com lets outbound and SMS teams check numbers against known TCPA litigators before a send, pulling the contacts most likely to file out of a campaign before they ever receive a message. It works alongside DNC scrubbing and opt-out handling, not in place of them.

Don’t forget the paper trail

If one of these claims ever lands on your desk, the first questions will be simple: where did this number come from, what did the person agree to, and when did they opt out? Make sure your team can answer all three from records, not memory. Pull a random sample of numbers each month and try it. If you cannot reconstruct the history in a few minutes, a plaintiff’s lawyer will happily do it for you.

Bottom line

A texting program does not need a dramatic mistake to end up in a settlement. It needs one gap repeated across every message. Close the gaps before the volume does the damage.

Sources

A Judge Just Made a Serial TCPA Plaintiff Pay for His Own Setup. Here’s What Outbound Operators Should Take From It.

If you run an outbound floor long enough, you meet him eventually: the consumer who seems to want your call, picks up, plays along, and then shows up as the named plaintiff in a TCPA complaint. Most operators treat that as a cost of doing business. On September 30, 2026, a federal judge in Missouri treated it as fraud.

In Human v. Fisher Investments, Inc., No. 4:24-cv-01177-MTS (E.D. Mo.), Judge Matthew T. Schelp found that the lawsuit was brought “in complete bad faith” and that “the genesis of this entire action was Human’s fraud.” The court ordered that Fisher Investments can recover all of its reasonable attorney’s fees for defending against the TCPA claims, from the start of the case. The plaintiff, his attorney Edwin Butler, and Butler Law Group LLC are jointly and severally liable for the full award.

What the court found

According to reporting on the order, the court found that Daniel Human gave his phone number under a fake name to request solicitations, so that he could sue under the TCPA once Fisher called. The court described this as his “practice,” and noted that dozens of prior defendants had settled similar claims.

The discovery record made it worse. The court found that Human destroyed his desktop computer two days before a court-ordered inspection and brought a decoy laptop instead. The court had previously struck Human’s pleadings. It also found that his lawyer knew the claims were not legitimate when he entered the case, and it did not credit the lawyer’s testimony.

The fee award covers the defense of Human’s claims. Fees tied to Fisher’s own fraud counterclaim are carved out of the blanket award, though Fisher can seek separate sanctions for specific misconduct. Fisher’s fee records are due October 22, 2026, with oppositions and replies to follow.

Why operators should not relax

It is tempting to read this as the system finally catching up with professional plaintiffs. Be careful with that conclusion. Look at what it took. The case was filed in 2024. Fisher had to push for a forensic inspection, fight through discovery, prove the setup, and then win sanctions. That is a defense budget most outbound businesses do not have for a single plaintiff.

The other detail that matters is the one that sounds most ordinary: dozens of prior defendants settled. Each of those companies made a rational decision. Paying a settlement was cheaper than finding out what Fisher found out. That is the business model a serial filer depends on, and one sanctions order does not end it.

What to change on the floor

The practical lesson is to stop meeting these plaintiffs in the first place. A few habits help:

  • Treat consent records as evidence. Capture the form, the timestamp, the IP and the exact language the person agreed to. Fisher’s case turned on proving how the number entered its system.
  • Watch for mismatches. A name that does not match the number’s history, or a lead that converts suspiciously well and then goes quiet, deserves a second look before the second call.
  • Keep your own data. Call logs, dispositions and recordings are what let you show a court what actually happened.
  • Screen before you dial. The cheapest dispute is the call that never went out.

That last point is where a litigator screen earns its keep. TCPALitigatorList.com helps outbound teams check numbers against known TCPA litigators and serial filers before a campaign goes live, so the contacts most likely to turn into a complaint are pulled out of the list upstream rather than discovered in a demand letter.

The bottom line

Courts will occasionally punish a manufactured TCPA claim, and Human v. Fisher shows they can do it forcefully. But a fee award at the end of a long case is a remedy, not a strategy. For an outbound operator, the strategy is clean consent, good records and a list that has already been scrubbed of the people who sue for a living.

Sources

Florida’s AG Wants STOP to Mean Stop, Faster. Outbound Teams Should Get Ready Now.

Florida already has one of the toughest telemarketing laws in the country. Its Attorney General wants to make it tougher. On September 17, 2026, Attorney General James Uthmeier proposed the Florida Anti-Spam Communications Act, a package that would hand his office independent authority to go after spam calls and texts, put new duties on phone carriers and, most relevant to legitimate outbound teams, shorten the time businesses have to honor a STOP request.

No bill text or bill number had surfaced as of late September, so the details could change a lot. But the direction is clear, and if you call or text Florida numbers, it is worth planning for.

What’s in the proposal

Based on the announcement as reported by Spectrum News, WCTV and TCPAWorld, the proposal would:

  • Give the Department of Legal Affairs independent authority to investigate spam calls and texts and seek injunctions, restitution and civil penalties.
  • Target impersonation of officials, caller ID spoofing, undisclosed AI voices used to get money, and fake warrants sent by text or email.
  • Make high-volume or high-loss schemes heightened felonies with mandatory prison time.
  • Make it a felony to possess or import phone farms or SIM farms, and treat that equipment as contraband.
  • Require communications providers to authenticate caller ID, answer traceback requests and stop carrying a named unlawful campaign after written notice.
  • Make selling stolen lists used to target Florida numbers a separate civil violation.
  • Tighten Florida’s telemarketing consent law and require STOP requests to be honored “within days instead of weeks.”

Uthmeier did not soften the message. “You need to go to jail for four or five years if you’re engaging in this kind of sophisticated fraud,” he said, according to WCTV.

Why legit operators should care

Most of this package is aimed squarely at scammers: fake deputies, spoofed toll agencies, SIM farms. You are not running a SIM farm. But two pieces land on everyone.

First, the opt-out clock. Under the current Florida Telephone Solicitation Act, a text-message damages claim generally depends on the consumer replying STOP and the sender continuing to text 15 days after that notice, as TCPAWorld points out, citing Fla. Stat. 501.059(10)(c). Federally, the TCPA requires revocations to be honored within a reasonable time, not to exceed ten business days. “Within days instead of weeks” suggests Florida wants something shorter. TCPAWorld also notes that a faster opt-out duty would not automatically change when a plaintiff can sue. That depends on the final text.

Second, carrier cutoffs. If providers must kill a “named unlawful campaign” after written notice from the state, your traffic’s fate could depend on how carriers identify covered messages. TCPAWorld flags that the response deadline and any process for challenging a mistaken notice are still unknown. A legitimate campaign caught in a sweep is a real business risk.

What to do this quarter

  • Audit your opt-out latency. Measure the time from STOP to suppression across every tool. If it is measured in days, fix it now. Aim for near real time.
  • Clean up caller ID. Make sure your numbers are properly registered and authenticated with your carriers.
  • Know your data sources. The stolen-list provision is a reminder to document where every lead came from.
  • Watch Tallahassee. The actual bill language will decide everything.

Cut the riskiest numbers before you dial

Florida’s FTSA already gives consumers a private right of action, and tighter state rules tend to give plaintiffs new theories to plead. One fast way to cut exposure is to remove the people who sue for a living from your lists before a campaign launches. TCPALitigatorList.com lets teams screen numbers against known TCPA litigators, so a tighter STOP window does not become an expensive surprise.

Bottom line

This is a proposal, not a law. But state AGs set the tone for enforcement, and Florida’s is telling the market that speed on opt-outs and clean caller ID are table stakes. Build for that now and the final bill will be an update, not an emergency.

Sources

A Florida Judge Just Said Consumers Can’t Sue Over the National Do-Not-Call List. Don’t Celebrate Yet.

If you run an outbound floor, you have probably treated the National Do-Not-Call Registry as the one rule you never mess with. On September 24, 2026, a federal court in the Middle District of Florida said something that would have sounded impossible a few years ago: a consumer cannot privately sue under the TCPA for calls to a number on the national registry. The case is Internicola v. MortgagePros, LLC, No. 6:25-CV-01613, and it is the sharpest swing yet in a fall full of rulings that are hollowing out the TCPA’s do-not-call claims.

Before anyone rips the DNC scrub out of their dialer, read on. This is a single district court, the plaintiff has already asked the judge to reconsider, and plenty of exposure remains.

What happened

According to TCPAWorld’s write-up of the decision, plaintiff Daniel Internicola put his number on the National DNC Registry in 2008. In April 2025 he talked to MortgagePros about refinancing his mortgage. On July 1, 2025, he withdrew his consent to be contacted. Over the next ten days, MortgagePros allegedly called or texted him just over a dozen times.

MortgagePros moved to dismiss, arguing that Section 227(c)(5), the TCPA’s do-not-call private right of action, does not reach national registry claims at all. The court agreed.

The reasoning, in plain terms

Section 227(c)(5) lets people sue over violations of “regulations prescribed under this subsection.” The court tied that phrase to Section 227(c)(2), which ordered the FCC to finish its do-not-call rulemaking “[n]ot later than 9 months after December 20, 1991.” By that reading, the private right of action only covers rules prescribed by September 20, 1992.

The problem for plaintiffs: the 1992 rules did not create a national registry. They required telemarketers to keep their own internal do-not-call lists. The National DNC Registry came in 2003, after Congress passed the Do-Not-Call Implementation Act. So, the court concluded, there is no private right of action for national DNC claims. The court also agreed that texts are not “calls” under Section 227(c)(5), which TCPAWorld notes is a well-established position in Florida by now.

It is not just Florida

Six days later, on September 30, the Eastern District of Missouri dismissed DNC claims in Koeller v. Ox AppSec Security, Inc. on a different theory: cellphones are not “residential” telephones. Relying on Loper Bright and McLaughlin, the court declined to follow the FCC’s 2003 interpretation that swept cellphones into the residential subscriber category, writing that “updating the statute to extend coverage to cellphones is Congress’s job, not the courts.”

Stack those with the growing pile of “texts are not calls” decisions and you get a picture of DNC litigation that looks very different depending on which courthouse you are standing in.

What operators should actually do

  • Keep scrubbing. These are district court rulings. They bind nobody outside their own cases, and TCPAWorld reported on October 5 that California federal courts are still holding SMS counts as calls for DNC purposes. Your dialer does not know which district a lawsuit will be filed in.
  • Your internal DNC list matters more, not less. If the Internicola logic spreads, the 1992-era internal do-not-call obligations are exactly what it leaves standing. Honor opt-outs fast and log them.
  • Look at the facts. This case started with a consumer who withdrew consent and then allegedly got a dozen-plus contacts in ten days. Revocation handling is where the trouble began, and revocation rules are not going anywhere.
  • Remember the other statutes. Robocall and autodialer claims under Section 227(b) were not touched here, and state mini-TCPAs have their own private rights of action.

Screen the people who sue for a living

Rulings like these will change how plaintiffs plead, not whether they file. Serial filers adapt fast, and they will reach for state statutes, revocation theories and autodialer counts when DNC claims dry up. One of the simplest defenses is knowing who is on the other end of the line before you dial. TCPALitigatorList.com lets teams screen their call and text lists against known TCPA litigators, so the numbers most likely to turn into a demand letter never make it into the campaign.

The bottom line

Internicola is a big swing, and a motion for reconsideration is already pending. Treat it as a sign of where some courts are heading, not as a hall pass. The operators who stay out of court will be the ones who keep their consent records clean, honor stop requests quickly, and know their risk before the first ring.

Sources

Checks Are Going Out in the Zales TCPA Settlement — Here’s the Operator Lesson Behind the Headlines

This month, settlement checks started landing in mailboxes for the Zales TCPA class action — up to $100 each, across roughly 75,000 phone numbers, out of a $7.54 million fund. It is a useful moment to look past the headline number, because the three biggest TCPA settlements making news right now each fail in a different, very preventable way. For operators, they read less like legal news and more like a punch list.

Three settlements, three distinct mistakes

Zales — $7.54M. The jeweler was sued for sending marketing texts to numbers on the National Do Not Call Registry. The class definition is the lesson: numbers registered on the DNC list for at least 30 days that then received at least two texts within a 12-month period. That is a pure list-hygiene failure — texting people who had told the government, in writing, to leave them alone.

Truist Bank — $4.1M. The bank settled claims it placed prerecorded calls about accounts to the wrong people — roughly 6,000 numbers that were not the account holders and had not consented to anything. The plaintiff alleged he got two dozen robocalls meant for someone else. That is a wrong-number and data-quality failure: calling reassigned or mistyped numbers without a process to catch them.

Everything Breaks — about $995K. The warranty company settled claims of repeated telemarketing robocalls to consumers on the National Do Not Call Registry. Same root cause as Zales, smaller company, smaller fund — proof the exposure is not just a big-brand problem.

The volume behind the settlements

None of this is happening in a vacuum. More TCPA class actions were filed in the first quarter of 2026 than in any quarter in recorded history. The plaintiffs’ bar has industrialized the work: intake, list analysis, demand letters, and class definitions are now a repeatable pipeline. When filing volume is at an all-time high, the question for an outbound operation is not whether your practices will be tested but when.

The operator punch list

Scrub every outbound list against the National Do Not Call Registry on a fresh cycle — not a download from last quarter — and keep your internal do-not-call suppression synchronized across every system and brand. Build reassigned-number checking into your dialing so you stop calling numbers that changed hands; the FCC’s Reassigned Numbers Database exists for exactly this. Treat a wrong-number complaint as a stop signal, not a data-entry note. And keep consent and suppression records you can actually produce, because in every one of these cases the company’s inability to prove a clean practice is what turned a complaint into a fund.

For operators, the cheapest line of defense is also the most overlooked: scrub your call and text lists before you dial. TCPALitigatorList.com maintains the most widely used database of known TCPA plaintiffs and serial filers. Running an outbound list through it takes minutes and keeps professional litigants off your campaigns before they ever pick up the phone — which, given how fast statutory damages add up, is one of the highest-return compliance steps an operator can build into a launch checklist.

The takeaway

Zales, Truist, and Everything Breaks did not lose to exotic legal theories. They lost to stale lists, wrong numbers, and opt-outs that did not propagate. Those are operational problems with operational fixes — and in a record-setting filing environment, fixing them is cheaper than funding the next settlement.

Sources

Top Class Actions — “$7.54M Zales TCPA class action settlement”; Class Action.org — “$4.1M Truist Bank Settlement”; CompliancePoint — “Truist Bank Settles $4.1M TCPA Lawsuit”; Top Class Actions — “Everything Breaks $995,000 TCPA settlement”; CompliancePoint / Shipkevich PLLC — 2026 TCPA litigation trend reporting.

There’s a New TCPA Lawsuit Going Around — and It’s About What Shows Up on the Screen

Operators have spent two years bracing for the obvious TCPA traps: consent, quiet hours, do-not-call scrubbing. Here is the one most teams have not even put on the board. Plaintiffs’ lawyers have found a new claim, and it has nothing to do with whether the recipient consented. It is about what your call or text actually displayed on the recipient’s phone — the caller ID — and a string of 2026 rulings just confirmed consumers can sue over it.

The rule nobody was watching

Buried in the FCC’s telemarketing regulations, 47 C.F.R. 64.1601(e) requires telemarketers to transmit caller identification information — a name and a number a consumer can call back to make a do-not-call request. For years this was treated as a technical rule enforced, if at all, by regulators. In 2026 that changed. Multiple federal courts have now held that consumers have a private right of action to sue over caller ID failures, and that the requirement applies not just to voice calls but to marketing text messages.

What the recent cases show

The picture is genuinely mixed, which is exactly why it is dangerous. In Zelma v. Ram, decided in the District of New Jersey on May 19, 2026, the court gave defendants something to like: displaying the recognizable brand name “RE/MAX” next to the number was enough to satisfy the caller ID requirement. But in Novia v. Mobiz, a Massachusetts federal court let a caller ID claim over marketing texts survive the pleading stage, and a second court has now recognized a private right of action for SMS caller ID failures. Translation: a defective sender ID on a text blast is now a viable class claim, and the safe-harbor line — what counts as adequate identification — is still being drawn case by case.

Why this hits operators hard

Most outbound text programs were never built with this rule in mind. Short codes, rotating 10DLC numbers, alphanumeric sender IDs, and “no-reply” configurations are everywhere — and several of those setups arguably fail to give the consumer a name plus a callable number for do-not-call requests. Because TCPA damages run $500 to $1,500 per message, a single campaign sent from a non-compliant sender ID to a large list is a ready-made class action, even if every recipient opted in. Consent does not cure a caller ID defect.

What to do this week

Pull up your last five outbound campaigns on an actual phone and look at what displays. Does the recipient see an identifiable business name? Is there a number they can call back — one that is monitored — to ask not to be contacted? For voice, confirm your transmitted CNAM and ANI resolve to your business, not a blank or a spoofed-looking string. For texts, make sure the sender identity and the opt-out path are unambiguous. And watch the states: Florida’s 2026 legislature is weighing strict caller identification mandates that would go further than the federal rule.

For operators, the cheapest line of defense is also the most overlooked: scrub your call and text lists before you dial. TCPALitigatorList.com maintains the most widely used database of known TCPA plaintiffs and serial filers. Running an outbound list through it takes minutes and keeps professional litigants off your campaigns before they ever pick up the phone — which, given how fast statutory damages add up, is one of the highest-return compliance steps an operator can build into a launch checklist.

The takeaway

The caller ID claim is attractive to plaintiffs precisely because it sidesteps the hardest part of a TCPA case — proving lack of consent — and turns instead on a technical display detail the defendant either got right or did not. Get it right before a plaintiff checks it for you.

Sources

Zelma v. Ram, 2026 WL 1398784 (D.N.J. May 19, 2026); National Law Review — “MAX TCPA Clarity”; Buchanan Ingersoll & Rooney — “Calling for Clarity: Navigating New Caller ID TCPA Claims”; Bubeck Law — “A New TCPA Risk: Caller ID Requirements for Marketing Texts?”; 47 C.F.R. 64.1601(e).

A Federal Court Just Drew a Cleaner Line Between You and Your Lead Vendors

If you run outbound calling or texting and you buy leads, hire a dialing vendor, or work through affiliates, here is a ruling worth pinning to the wall. On May 15, 2026, a federal judge in the Western District of Washington threw out TCPA claims against two insurance companies in Sundstrom v. Ocean Reef Media LLC, finding the plaintiff never plausibly explained why those insurers should answer for calls a different company allegedly placed. For operators, that is a rare piece of good news — and a clear roadmap for how to keep yourself out of the same complaint.

What happened

The plaintiff received marketing calls and sued not just the entity that dialed, but the insurers whose products were ultimately being pitched. The theory was vicarious liability: hold the brand at the end of the funnel responsible for the conduct of the lead generator at the front of it. The court was not persuaded. It dismissed the claims against the insurers because the complaint offered conclusions — “they were agents,” “they authorized this” — without the concrete facts a court needs to make that link plausible. Speculative inferences, the judge held, are not enough.

Why operators should care

TCPA liability has never stopped at the company that physically pressed “send.” Under the FCC’s long-standing agency framework, a brand can be on the hook for a vendor’s or affiliate’s calls if it controlled the manner and means of those calls, ratified them, or cloaked the caller in apparent authority. That is exactly how a plaintiff’s lawyer tries to reach the deeper pockets. Sundstrom does not erase that exposure. What it does is confirm that a plaintiff has to actually plead the relationship — who directed whom, what the contract said, who set the script, who controlled the lists — and cannot simply name every company in the chain and hope discovery fills the gap.

That cuts both ways. It is a defense win if your paperwork and your day-to-day practice genuinely keep you at arm’s length from a vendor. It is a loaded gun pointed at you if they do not, because the same facts that defeat a vague complaint will sink a well-pleaded one.

The operator checklist

Treat Sundstrom as a prompt to audit how much control you exert over the people dialing on your behalf. Read your vendor contracts: do they assign TCPA compliance, consent capture, and list scrubbing to the vendor in writing, with indemnification? Look at practice, not just paper — if your team writes the scripts, approves the call windows, hands over the lists, and monitors the dialer, a court will see an agency relationship no matter what the contract title says. Keep consent records that travel with the lead, so you can show where a phone number came from and what the consumer actually agreed to. And require proof, not promises, that your partners are scrubbing against do-not-call data and known litigants before any campaign goes out.

For operators, the cheapest line of defense is also the most overlooked: scrub your call and text lists before you dial. TCPALitigatorList.com maintains the most widely used database of known TCPA plaintiffs and serial filers. Running an outbound list through it takes minutes and keeps professional litigants off your campaigns before they ever pick up the phone — which, given how fast statutory damages add up, is one of the highest-return compliance steps an operator can build into a launch checklist.

The takeaway

The win in Sundstrom went to defendants who could not be plausibly tied to the calls. The lesson for everyone else is that the tie is built — or avoided — long before a complaint is filed. Tighten your vendor governance now, and a future plaintiff will have nothing concrete to plead. Leave it loose, and the next court may have plenty.

Sources

Faegre Drinker — “Washington Federal Court Dismisses TCPA Claims, Finding Insufficient Allegations of Vicarious Liability”; Sundstrom v. Ocean Reef Media LLC, No. 26-5036, 2026 WL 1361646 (W.D. Wash. May 15, 2026).