The Most Reliable TCPA Plaintiff List-Scrubbing Providers for Credit Unions: What to Test Before You Choose

When a credit union asks which TCPA plaintiff list-scrubbing provider is “most reliable,” it usually means something specific: will the scrub catch the numbers that actually lead to demand letters, will it run every single time a campaign goes out, and will the compliance team be able to prove it ran? This piece walks through what reliability looks like from the operations floor, then looks at the providers a credit union outreach team is most likely to evaluate, starting with TCPALitigatorList.com.

Four tests of a reliable scrub

Reliability isn’t one feature. In practice it breaks down into four things a member-outreach team can check for itself.

  • Freshness. Serial plaintiffs pick up new numbers and new cases constantly. Ask how often the underlying data is updated and where it comes from (court filings, demand letters, complaint records). A list refreshed quarterly is a different product from one refreshed daily.
  • Match logic. Matching on phone number alone misses a plaintiff who has switched numbers. Some providers also match on names or track prepaid and unregistered lines. Ask what a “hit” is based on and how false positives are handled, because over-blocking members who legitimately need a payment reminder has its own cost.
  • Coverage of the moment of contact. A batch scrub run on Monday doesn’t cover a number added to a collections queue on Thursday. Reliable programs pair periodic batch scrubs with a real-time check at the dialer or texting platform.
  • Proof. If a member files suit, counsel will want to show what was checked, when, and with what result. Look for exportable scrub logs or reports you can retain.

The providers credit unions tend to evaluate

TCPALitigatorList.com (TCPA Litigator List) is built specifically around litigator data. The company says it has operated since 2017 and maintains a database of more than 600,000 names, including multi-case plaintiffs, demand-letter senders, attorneys and frequent DNC complainers, which its researchers update every weekday. On the match-logic question, it describes a Name Recognition Algorithm that flags serial litigators by name and tracks prepaid or unregistered phones, alongside standard number matching. For the moment of contact, it offers a real-time API that checks a number before the call and blocks on a match, plus endpoints for single and mass scrubbing. Bulk CSV or Excel uploads with multiple phone columns are supported for scheduled list hygiene, and the service also scrubs against federal and state DNC lists and flags inactive numbers. Public pricing starts at $199 per month for a non-API plan, with API plans from $299 per month and higher tiers for larger volumes. It offers a sample list and demo scrub. For larger organizations, it describes a Shared Savings Program in which scrubbing is free for 12 months and the fee is a share of any verified reduction in annual TCPA lawsuit expense; the company is explicit that this is a performance-based agreement, not insurance or legal advice.

Contact Center Compliance (DNC.com) sells a Litigator Scrub and Litigator Insights alongside wireless, VoIP and DNC scrubs. The company says its litigator data is updated in real time from original court documents and lists around 20 integrations, including Five9, Genesys, Salesforce and RingCentral. Pricing is not published.

PossibleNOW (DNCSolution) is an enterprise platform that checks federal, state, internal, wireless, Reassigned Numbers Database and known-litigator lists in real time. It lists financial services among its industries, which may matter to a credit union that wants one vendor for several checks.

The Blacklist Alliance offers a TCPA Litigation Firewall that scrubs against its high-risk data plus internal, national and state DNC lists, for both inbound and outbound contacts, and pairs it with compliance training courses.

Gryphon includes litigator screening inside a broader real-time compliance platform covering DNC, consent and calling hours, with integrations into major dialers. Trestle adds a litigator-risk flag to its phone validation API, priced per lookup.

Where reliability usually breaks

From an operator’s point of view, the vendor is rarely the weak link. The gaps tend to show up in the workflow around it:

  • Side-door sends. A branch manager texts a list from a separate platform that was never connected to the scrub. Every outbound channel, including loan-servicing texts and marketing SMS, needs to route through the same check.
  • Stale exports. A list is scrubbed, saved, and reused three weeks later. Treat any scrubbed file as expiring; National Do Not Call data, for example, must be refreshed at least every 31 days.
  • Suppression that doesn’t stick. A flagged number is removed from one campaign but stays in the core system and reappears next month. Write litigator hits back to a master suppression list.
  • No fallback. If the real-time API times out, does the dialer call anyway or hold the record? Decide this in advance and document it.

Don’t forget the checks a litigator scrub doesn’t cover

A plaintiff list reduces exposure to people who sue often. It doesn’t establish consent or catch every risk. A credit union program should also query the FCC’s Reassigned Numbers Database, which has been live since November 2021 and offers a safe harbor when a “no” result is returned for a number that was in fact reassigned. And the FCC’s revised consent-revocation rules take effect November 25, 2026: opt-outs from informational messages become category-specific, marketing revocations still cover all marketing, callers may designate exclusive opt-out methods if clearly disclosed, the 10-business-day processing cap remains, and the exemption for fraud alerts has been widened, which is directly relevant to card and account-security texts. Your scrub vendor and your opt-out handling need to agree on how those categories are recorded.

A one-month reliability trial

Rather than choosing on a demo alone, an outreach team can run a short trial:

  • Week 1: Send a recent member contact file to two or three vendors and compare hit counts and what each hit is based on.
  • Week 2: Connect the shortlisted vendor’s real-time check to one dialer or texting queue and log every block.
  • Week 3: Test failure handling by checking what happens when the API is unreachable.
  • Week 4: Pull the audit report and ask your compliance officer whether it would hold up in a demand-letter response.

A sample scrub from TCPALitigatorList.com is an easy way to start Week 1 and see how many existing member numbers raise a flag.

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

Nine Days of AI Calls, $1.1 Million: What This Month’s Robocall Settlements Tell Operators

Four TCPA settlements in the news over the past week share one feature: every one of them involves artificial or prerecorded voice calls. One of them, involving an AI voice vendor, covered just 900 people and still settled for $1.1 million. If your team uses voice bots, voicemail drops or automated reminders, this is the batch to study.

The AI test run that became a class action

TCPAWorld reported on November 9, 2026 that the parties in Finley v. Altrua have settled for $1.1 million. The class, as described in the post, covers people that Crown Administrators sent messages to using AiRudder on behalf of Altrua during a nine-day period. TCPAWorld describes it as a class of just 900 AI call recipients and characterizes the campaign as essentially a test run by a vendor.

Do the math: that is more than $1,200 of settlement value per class member, for a nine-day pilot. The TCPA treats artificial-voice calls the same way it treats prerecorded ones, and a short test is still a campaign in the eyes of the statute.

The prerecorded settlements

  • Connect America, up to $4 million. According to a November 3 article in the National Law Review, the class covers people who did not give ConnectAmerica.com, LLC their number but received at least one prerecorded message on a cell phone from April 1, 2021 through preliminary approval. The article puts the class at 14,534 members, payments at up to $275 each, and attorneys’ fees at up to $1.3 million.
  • Bond v. Folsom Insurance Agency, $850,000. In the Northern District of Texas (No. 3:24-cv-02551-BN), the fund covers 41,719 telephone numbers that received artificial or prerecorded voice calls and voicemails between February 29, 2020 and September 15, 2026. Preliminary approval came September 15, the claim deadline is November 16, and the final approval hearing is December 29. Estimated payments are about $125 to $200. The defendants deny wrongdoing.
  • Seals v. Concora Credit, $9.375 million. In the District of Oregon (No. 3:25-cv-00728-AN), this wrong-number settlement covers non-accountholders who received prerecorded or artificial voice calls on their cell phones between May 2, 2021 and May 31, 2026. It includes an $8.375 million cash fund and at least $1 million in compliance spending over three years. The final fairness hearing is set for November 24. Concora denies the allegations.

The operator checklist

  • Treat AI voice as prerecorded voice. If a bot speaks, you need the consent level the TCPA requires for artificial-voice calls before the first dial, including during pilots.
  • Own your vendor’s tests. Altrua’s exposure came from messages sent on its behalf. Any vendor proof of concept should go through the same consent and suppression gates as a production campaign.
  • Fix wrong numbers. Concora’s class is people who were not customers at all. Reassigned-number checks and fast handling of “wrong number” responses are the defense.
  • Voicemail drops count. The Folsom class includes voicemails. Leaving a prerecorded message is not a way around the rules.
  • Budget for compliance, not just settlements. Concora’s deal includes a $1 million compliance commitment. Spending it before a lawsuit is cheaper.

Consent is the first gate; knowing who is likely to sue is the second. TCPALitigatorList.com lets operators check dial lists against known TCPA litigators and serial plaintiffs before calls go out, so a pilot or a voicemail campaign does not land on the phone of someone who files these cases for a living.

Bottom line

The dollar amounts range from $850,000 to more than $9 million, but the theme does not change: automated voice without clean consent is still the most expensive mistake in outbound. AI makes it faster to make.

Sources

Two New TCPA Rulings Just Took Away a Pair of Plaintiff Shortcuts. Here’s What Operators Should Do With Them.

Two federal decisions issued in the last ten days won’t make headlines outside the TCPA bar, but anyone running outbound calls or texts should know them. On November 2, 2026, a judge in the Western District of Washington ruled that a consumer who opted out of a prior class settlement can keep suing on her own but cannot turn around and lead a competing class. Three days earlier, on October 30, a Central District of California judge refused to enter a default judgment over texts that offered free products, holding they were not “telephone solicitations” at all.

Neither ruling is a free pass. Both are useful signals about where courts are drawing lines, and both reward operators who keep their records and message content clean.

Case one: Brown v. Citibank

In Brown v. Citibank, N.A., No. 3:25-cv-5119-TL (W.D. Wash. Nov. 2, 2026), the plaintiff alleged she received at least 46 unsolicited prerecorded robocalls. She had opted out of an earlier class settlement, Head v. Citigroup, and then sought leave to amend her complaint to add class claims of her own.

The court said no to the class piece. According to TCPAWorld’s summary of the order, opting out preserved her right to pursue her individual claims, not to launch a competing class action. The court found the proposed class failed Rule 23’s requirements, including typicality, and denied leave to add class claims. It did allow her to amend to add individual factual allegations, so her own case continues.

Why should an operator care? Because the opt-out-then-relaunch move is one way a single settled exposure turns into two. When a company settles a class, it is buying peace for that group. A ruling that keeps opt-outs from rebuilding a parallel class makes that peace more durable.

Case two: Bravo v. Hygeia Health

In Bravo v. Hygeia Health, Inc., No. 2:26-cv-08900 (C.D. Cal. Oct. 30, 2026), the defendant never appeared, and default was entered on September 24. The plaintiff asked for $1,000 in statutory damages plus $565 in costs over texts received in April 2026 at roughly 6:54 and 6:55 a.m.

Even with no one on the other side, the judge denied the default judgment. The texts offered breast pump accessories covered by the recipient’s insurance, at no cost. The court held they were not “telephone solicitations” under Section 227(c)(5), because they did not encourage the recipient to buy anything. It relied on the Seventh Circuit’s 2025 decision in Hulce v. Zipongo Inc. and ordered the plaintiff to show cause within 14 days why the case should not be dismissed.

Courts do not rubber-stamp a TCPA claim just because the defendant failed to answer. The content of the message still decides whether the do-not-call rules even apply.

What to do on the floor this week

  • Track settlement opt-outs. If you have settled a class, keep the list of people who opted out and flag them in your CRM. They are your most likely individual plaintiffs, and they should never be dialed again without fresh consent.
  • Audit your “free” messages. Hygeia’s texts survived because nothing in them pushed a purchase. Upsells, “limited time” language or a link to a paid tier change that analysis fast. Have someone read your informational templates with a plaintiff’s eyes.
  • Don’t confuse “not a solicitation” with “no rules.” The Hygeia ruling addressed the do-not-call claim. Prerecorded and artificial-voice rules, quiet hours and state laws can still apply to non-marketing messages.
  • Respond to every complaint. Hygeia got lucky. A default is still the most expensive way to lose a case you might have won.

The common thread is screening. Many of the plaintiffs who bring these cases, including those who opt out and sue again, are repeat filers. TCPALitigatorList.com lets outbound teams check numbers against a database of known TCPA litigators and serial plaintiffs before a campaign goes out, so the riskiest contacts are suppressed up front instead of discovered in a demand letter.

Bottom line

Brown narrows a procedural shortcut and Hygeia narrows a substantive one. Neither will help an operator whose consent records are a mess. Both help an operator who can show exactly what was sent, to whom, and why.

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

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

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

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).

If a Plaintiff Can Sue OpenAI for Their Customer’s Texts, Every Outbound Operator Should Be Paying Attention

There’s a TCPA complaint sitting in a Virginia federal court that should be on every outbound operator’s radar — not because of the consumer who filed it, but because of who he sued.

In Lowry v. OpenAI, the plaintiff alleges he received unwanted marketing text messages from a company called Fresh Start Group, sent via Twilio-provisioned numbers, that were generated using OpenAI’s platform. So far, so unremarkable. The unusual move is that the complaint names OpenAI itself and Twilio as defendants — not just the company that actually sent the messages.

The platform liability theory

The theory: under the TCPA, you can be liable if you ’cause’ a call or text to be initiated — not just if you physically dial. The complaint argues that by providing the AI platform that generated the messages and the telephony infrastructure that delivered them, OpenAI and Twilio caused the messages and should share liability with the downstream caller.

If that theory survives — and even if it only survives early motions long enough to drive a settlement — it reshapes the TCPA risk model for every operator that uses an AI agent or a CPaaS provider in their outbound stack. Which, in 2026, is basically all of them.

The exposure math

The complaint seeks to represent a class of every U.S. consumer who received marketing messages generated on OpenAI’s platform, where the recipient’s number was on the DNC list and OpenAI did not have consent. At $500 per call with a four-year TCPA lookback, the theoretical class damages run into the trillions. That number is obviously aspirational, but it is the number plaintiff’s counsel will use at the settlement table.

Twilio is not new to this argument. The company received an FCC cease-and-desist letter in 2024 over allegedly enabling illegal robocall traffic. The platform-liability theory in Lowry didn’t appear from nowhere — it’s the legal extension of years of regulatory pressure on the infrastructure layer.

Why this matters even if you’re not Twilio or OpenAI

For operators, the practical implication is not ‘we should stop using AI or CPaaS providers.’ The implication is that the indemnity and consent structure of your vendor agreements just got a lot more important. If your CPaaS or AI vendor takes a settlement-driven hit from a Lowry-style case, every contract clause about pass-through liability, indemnity, and audit rights becomes live.

Three operator action items:

1. Read your CPaaS terms of service. Most CPaaS providers explicitly disclaim TCPA liability and push it back to the customer. That’s fine until a court holds the CPaaS provider liable anyway — at which point the disclaimer becomes a contract fight, not a liability shield.

2. Document your consent-to-platform chain. If a platform-liability case lands and the platform comes asking, you want a clean record of how every number on your campaign ended up there with consent.

3. Watch the FCC’s posture. The FCC has already issued cease-and-desist letters to infrastructure providers and has ruled that AI-generated voices are ‘artificial or prerecorded voice’ under the TCPA. The trend is toward more, not less, liability up the stack.

If you run an outbound calling or texting program, the cheapest insurance against any of this is screening your dial list before you hit send. TCPALitigatorList.com maintains a continuously updated database of known TCPA plaintiffs and serial litigators so operators can scrub their files and quietly remove the numbers most likely to turn a routine campaign into a class action. A few minutes of list hygiene beats a few months of discovery every time.

The bigger arc

The TCPA was written in 1991 for a world of human dialers calling from cubicles. The legal system has spent 35 years stretching its concepts of ‘call,’ ‘caller,’ and ‘consent’ to cover autodialers, prerecorded voice, ringless voicemail, SMS, and now AI-generated messages routed through stack-of-stack platforms.

Lowry v. OpenAI is the next chapter of that stretch: holding whoever provided the technology that caused the message, not just the entity whose name was on the customer-facing brand. Watch this case closely. Whether it wins or settles, it will move where TCPA liability lands for the next decade.

Sources

National Law Review: New TCPA Complaint Names OpenAI and Twilio
Henson Legal: OpenAI and Twilio Sued for Customers’ TCPA Violations
Lowry v. OpenAI Complaint (PDF)

Ringless Voicemail Isn’t a Loophole Anymore — Two 2026 Cases Are Sending That Message Loud and Clear

For years, ringless voicemail (RVM) vendors sold the same comforting story to operators: drop a message straight into a consumer’s voicemail without actually placing a call, and you sidestep the TCPA. That story is dead. Two 2026 cases have driven a stake through it, and any operator still running RVM campaigns without TCPA-grade consent is sitting on an unsexploded class action.

The $6.5M warning shot

National Retail Solutions (NRS), a point-of-sale technology provider, agreed to pay over $6.5 million to resolve a TCPA class action alleging it used ringless voicemail technology without the level of consent the statute requires. The class is limited to RVMs sent by a single provider, with over 50,000 class members each set to receive more than $100. The ceiling on what NRS sent is almost certainly much higher than the class that got certified.

The case is a clean operator-side cautionary tale. NRS wasn’t a fly-by-night dialer shop. It was a B2B technology company that ran a growth program through a marketing channel its leadership probably believed was compliant. The compliance belief was wrong, the scale was high, and the bill is $6.5M.

The GoHighLevel realtor case

The second case to know is the Britney Gaitan / GoHighLevel matter out of Las Vegas. A solo realtor used GoHighLevel — a popular all-in-one marketing platform — to send ringless voicemails to expired listings. A court certified a class against her on the theory that the voicemails were prerecorded calls under the TCPA, and that she had no documentation of consent from class members.

The operator-level lesson here is brutal. You don’t need to be a Fortune 500 telemarketer to face TCPA class exposure. You need to run a single high-volume RVM campaign without consent records, and you can lose your business.

Why courts keep treating RVM as TCPA-regulated

The FCC settled this question in 2022 with a Declaratory Ruling that ringless voicemails to wireless phones are subject to the TCPA’s robocall provisions because they are calls made using an artificial or prerecorded voice. Every court ruling since has reinforced that position, including a 2025 decision in Taylor v. Kit Insurance holding that identical voicemail content is enough at the pleading stage to allege a prerecorded call.

The vendor story — that RVMs aren’t ‘calls’ because they bypass the ring — has been rejected by the FCC and the courts. If your vendor is still pitching that line, find a new vendor.

Operator checklist if you run RVM

Treat RVM exactly like a robocall. Same prior express written consent. Same DNC scrubbing. Same revocation handling. Same recordkeeping. There is no separate compliance lane.

Audit your consent records by source. If you can’t produce, per number, a time-stamped, source-traceable consent record for the specific channel and specific purpose, you don’t have consent.

Get rid of legacy lists. Old lead lists are where TCPA class actions are born. If a list pre-dates your current consent process, retire it.

Document your platform’s defaults. Many marketing platforms ship with consent assumptions baked in. If those assumptions don’t match your actual lead flow, you’re carrying the risk, not the platform.

If you run an outbound calling or texting program, the cheapest insurance against any of this is screening your dial list before you hit send. TCPALitigatorList.com maintains a continuously updated database of known TCPA plaintiffs and serial litigators so operators can scrub their files and quietly remove the numbers most likely to turn a routine campaign into a class action. A few minutes of list hygiene beats a few months of discovery every time.

Bottom line

The RVM industry spent a decade selling a workaround that the FCC and the courts have now explicitly rejected. Operators who continue to rely on the workaround are betting against settled regulatory and judicial positions. The NRS $6.5M settlement and the GoHighLevel class certification are the two numbers that should end the bet.

Sources

National Law Review: Ringless Voicemail Triggers $6.5M TCPA Settlement for NRS
TCPAWorld: GoHighLevel Realtor TCPA Class Action
FCC Declaratory Ruling on Ringless Voicemail