robocalls – Bring To Market

Your AI Voice Pilot Could Cost $1.1 Million: The GTM Lessons in This Month’s TCPA Settlements

AI voice agents are showing up in more go-to-market stacks: outbound qualification, appointment setting, renewal reminders. A settlement reported this week shows how quickly a short experiment can become a seven-figure line item. And it was not the only automated-voice settlement in the news.

A nine-day pilot, a $1.1 million settlement

On November 9, 2026, TCPAWorld reported that Finley v. Altrua settled for $1.1 million. The class, as the post describes it, is people that Crown Administrators sent messages to using AiRudder on Altrua’s behalf over nine days, roughly 900 AI call recipients in total. TCPAWorld called the outreach essentially a test run by a vendor.

The structure matters too. The calls were placed by one company, using another company’s AI platform, on behalf of a third. That layered setup is common in modern GTM stacks, where lead buyers, BPOs and software vendors all touch the same campaign. It did not keep the brand out of the lawsuit.

For a GTM leader, the takeaway is that a pilot is not a sandbox. The statute does not care that the volume was small or the campaign was experimental. It cares whether artificial-voice calls went to people without the required consent.

The rest of the week’s settlements

Three more settlements reported in the same window all involve prerecorded or artificial voice:

Connect America, up to $4 million, for prerecorded messages to cell phones of people who did not provide their numbers, from April 1, 2021 through preliminary approval. The National Law Review reported 14,534 class members, payments up to $275 each, and fees up to $1.3 million.
Bond v. Folsom Insurance Agency, $850,000 (N.D. Tex., No. 3:24-cv-02551-BN), covering 41,719 numbers that received artificial or prerecorded calls and voicemails between February 2020 and September 2026. Claims are due November 16, with a final approval hearing December 29. The defendants deny wrongdoing.
Seals v. Concora Credit, $9.375 million (D. Or., No. 3:25-cv-00728-AN), for prerecorded or artificial voice calls to non-accountholders, an estimated 147,000 people according to class counsel. The deal includes at least $1 million in compliance spending over three years, and the final fairness hearing is November 24. Concora denies the allegations.

Five GTM moves to make now

Put AI voice behind the same consent gate as prerecorded calls. Before any agent speaks to a prospect, confirm the consent on file supports an artificial-voice call.
Write vendor pilots into your compliance process. Require vendors to run tests on your approved, consented lists only, and get that in the contract.
Clean data before you scale. Concora’s class is wrong-number calls. Bought lists, stale CRMs and reassigned numbers are where that risk lives.
Count voicemail drops. Folsom’s class covers voicemails, so ringless or prerecorded drops need the same review.
Model the downside. Divide $1.1 million by 900 recipients and compare it to the expected pipeline from the pilot. That is the real cost of skipping consent.

List hygiene is a GTM job as much as a legal one. TCPALitigatorList.com helps sales and marketing teams scrub contact lists against known TCPA litigators and serial plaintiffs before campaigns launch, removing the people most likely to turn an outreach test into a lawsuit.

The takeaway

AI voice can scale outreach. It can also scale liability at the same speed. The teams that win with it will be the ones that treat consent and list quality as part of the launch plan, not an afterthought.

Sources

Free Offers, Opt-Outs and Class Actions: What Two New TCPA Rulings Mean for Your Growth Playbook

Growth teams usually hear about TCPA cases after the settlement number lands. Two rulings from the past ten days are worth catching earlier, because they speak directly to how campaigns are written and how legal exposure gets sized.

On October 30, 2026, the U.S. District Court for the Central District of California held that texts offering free, insurance-covered products were not “telephone solicitations.” On November 2, the Western District of Washington held that a consumer who opted out of a class settlement cannot lead a new class over the same kind of calls. One is about message content; the other is about how big a lawsuit can get.

Message content: Bravo v. Hygeia Health

In Bravo v. Hygeia Health, Inc., No. 2:26-cv-08900 (C.D. Cal. Oct. 30, 2026), the plaintiff sought a default judgment of $1,000 in statutory damages and $565 in costs for two early-morning texts in April 2026. Hygeia had not appeared. The court denied the motion anyway.

The texts offered breast pump accessories covered by the plaintiff’s insurance, at no cost. Under Section 227(c)(5), the do-not-call private claim requires a “telephone solicitation,” which means encouraging a purchase. The court found these texts did not encourage the recipient to buy anything. It leaned on Hulce v. Zipongo Inc., a 2025 Seventh Circuit decision, and gave the plaintiff 14 days to show why the case should survive.

For growth teams, the lesson is about copy discipline. A truly free, no-strings message tied to an existing benefit sits on different legal ground than a promo. The moment the message drives toward a paid product, a discount or an upgrade, that protection likely disappears.

Exposure sizing: Brown v. Citibank

In Brown v. Citibank, N.A., No. 3:25-cv-5119-TL (W.D. Wash. Nov. 2, 2026), the plaintiff alleged at least 46 prerecorded robocalls. She had opted out of a prior class settlement, Head v. Citigroup, then sought to add class claims. The court denied that request, finding the proposed class failed Rule 23 requirements including typicality. She can still pursue her own claims and was allowed to add individual factual allegations.

TCPAWorld summed up the principle: someone who opts out gets the right to go it alone, not to start a rival class. For a business, that matters when budgeting for litigation. A settled class should stay settled, and the residual risk from opt-outs is individual-sized, not class-sized.

How to apply this to your go-to-market motion

Separate informational and promotional templates. Keep a clear library of service messages that offer value without a sales ask, and review them whenever marketing wants to add a CTA.
Tag message intent in your send platform. If you ever need to show a court a message was informational, the tag and the template history help make the case.
Suppress settlement opt-outs permanently. When a class settles, the opt-out list is a ready-made list of people willing to sue you individually. Put them on a do-not-contact list across every channel.
Don’t assume a default wins for the plaintiff. Hygeia shows judges still test the merits, but responding to every complaint is cheaper than relying on that.

Pre-send screening closes the remaining gap. TCPALitigatorList.com gives marketing and sales teams a way to scrub contact lists against known TCPA litigators and serial plaintiffs before launch, so a growth campaign does not become the next filing in a plaintiff’s portfolio.

The takeaway for growth leaders

Courts are reading TCPA claims closely: what the message actually said, and whether the plaintiff is entitled to represent anyone else. Teams that write clean copy and keep clean suppression lists get the benefit of both.

Sources

Q1 2026 Set a TCPA Filing Record. Here’s What the Latest Settlements Tell GTM Teams.

The data point that should reframe how every go-to-market team thinks about outbound: more TCPA class actions were filed in the first quarter of 2026 than in any quarter on record. That is the backdrop for a run of settlements finalized this spring — Zales at $7.54 million, Truist Bank at $4.1 million, Everything Breaks at roughly $995,000 — and each one maps to a specific, fixable breakdown in a marketing operation.

Reading the settlements as GTM diagnostics

Zales, $7.54M — a list-sourcing failure. The class covers numbers on the National Do Not Call Registry that received marketing texts anyway. For a GTM team, this is a question of where audiences come from and how they are filtered. If your SMS audiences are built from purchased data, old CRM segments, or event lists that were never scrubbed against the DNC registry, you are assembling a Zales class one campaign at a time.

Truist, $4.1M — a data-quality failure. The bank settled over prerecorded calls that reached the wrong people — numbers that had been reassigned or simply did not belong to the intended customer. For lifecycle and retention programs, this is the reassigned-number problem: phone numbers change hands constantly, and a CRM that never re-verifies them will keep dialing strangers.

Everything Breaks, ~$995K — the same DNC failure, smaller company. The lesson is that none of this scales with brand size. A mid-market outbound program with a stale list carries the same per-message exposure as a national retailer.

Why the filing record changes the calculus

When TCPA filings hit an all-time high, the plaintiffs’ bar is signaling that intake and class-building have become a repeatable, low-friction pipeline. The implication for marketing leaders is that compliance can no longer sit downstream as a legal review after a campaign ships. It has to be designed into the audience-build and campaign-QA stages, where the actual risk is created.

What to operationalize

Make DNC scrubbing a non-negotiable, automated step in every audience build, refreshed on a current cycle rather than from a stale file. Synchronize internal opt-out and do-not-call data across every platform — CRM, ESP, SMS tool, dialer — so a “STOP” in one system suppresses the contact everywhere. Add reassigned-number and phone-validation checks to recurring programs so lifecycle automation is not quietly dialing numbers that changed owners. And keep consent and suppression evidence that your team can produce on demand, because the absence of that proof is what converts an allegation into a settlement fund.

From a go-to-market standpoint, list hygiene belongs in your campaign QA, not in a legal post-mortem. Marketing-ops teams increasingly screen outbound audiences against TCPALitigatorList.com, the most widely used registry of known TCPA litigators and serial plaintiffs, so a single suppression step upstream stops a known filer from turning a routine nurture flow into a class action. Wiring that check into your audience-build process is a small operational change with an outsized risk reduction.

The bottom line

Zales, Truist, and Everything Breaks are not cautionary tales about bad actors. They are cautionary tales about ordinary outbound programs with ungoverned lists. In a record-setting litigation environment, the GTM teams that move compliance upstream — into how audiences are sourced, filtered, and refreshed — are the ones that stay out of the next settlement roundup.

Sources

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

Your Lead-Gen Stack Is a TCPA Liability Map. A New Ruling Shows Where the Lines Are.

Modern go-to-market motions are rarely a single company calling a single list. They are layered: a lead generator captures interest, a data broker enriches it, an affiliate or BPO places the call, and a brand sits at the end collecting the conversions. Every one of those handoffs is also a potential TCPA liability transfer — and a May 15, 2026 federal ruling just clarified how plaintiffs can, and cannot, walk that chain back to your brand.

The decision

In Sundstrom v. Ocean Reef Media LLC, the Western District of Washington dismissed TCPA claims against two insurance companies. The plaintiff wanted the insurers held vicariously liable for marketing calls placed by another party in the funnel. The court said the complaint had not done the work: it asserted an agency relationship but never alleged the specific facts — direction, control, authorization, ratification — that make such a relationship plausible. Naming the brand at the top of the funnel is not the same as explaining how the brand controlled the call.

Why this is a GTM problem, not just a legal one

Vicarious liability is the mechanism that turns a vendor’s sloppy dialing into your nine-figure class action. The TCPA reaches a brand when it controls how calls are made, authorizes them, ratifies them after the fact, or lets a caller appear to act with its authority. The uncomfortable truth for marketing-ops teams is that the things you do to run a tight, on-brand program — supplying approved scripts, dictating call cadence and hours, handing over targeting lists, monitoring performance dashboards — are the exact facts a plaintiff cites to prove control.

Sundstrom is a reminder that the plaintiff still has to plead those facts specifically. But it is cold comfort if your operational reality hands them the facts on a plate. The ruling rewards companies whose vendor relationships are genuinely arm’s-length, and punishes those whose “vendor” is functionally an extension of the in-house team.

How to map and harden your funnel

Build a liability map of your outbound stack. For every partner that touches a phone number, document who controls the script, the call window, the list, the dialer configuration, and the consent record. Where you can, push genuine control to the vendor and memorialize it: contracts that assign TCPA compliance and consent collection, with indemnification and audit rights. Insist that consent provenance — source URL, timestamp, the exact disclosure language — flows downstream with every lead, because a brand that can prove clean consent rarely needs the vicarious-liability argument at all. And make list scrubbing a contractual deliverable your partners must evidence, not a box they say they checked.

The bottom line

Sundstrom did not narrow the TCPA. It narrowed sloppy pleading. The brands that benefit are the ones whose go-to-market architecture genuinely separates them from the dialing — clean contracts, real arm’s-length practice, portable consent records. Treat your lead-gen stack as a risk surface you actively manage, and the next plaintiff who tries to walk the chain to your door will run out of facts before they reach it.

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