compliance – 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

One STOP No Longer Kills Every Message: How the FCC’s November 25 Rules Change Lifecycle Marketing

Growth teams have spent two years worrying that one reply would wipe out an entire customer relationship. Under the “revoke all” approach the FCC kept delaying, a customer who texted STOP to a shipping update could have cut off every robotext and robocall from the brand. On November 25, 2026, revised FCC rules take effect that settle much of that question, and the answer is better for lifecycle programs than many expected. It is not a free pass for promotional channels.

The timeline

The FCC adopted the order, together with a Further Notice of Proposed Rulemaking, on September 30, 2026. Federal Register publication on October 26 set the effective date at November 25, which replaces the January 31, 2027 date that had applied to parts of the earlier revocation requirements. FNPRM comments are due November 25, and reply comments December 28.

What it means for your channel mix

The rules separate informational messages from telemarketing, so your go-to-market plan should do the same.

Informational and transactional streams such as order updates, payment reminders, appointment confirmations and fraud alerts now follow a category-specific approach. An opt-out from one category does not automatically end the others. A customer can turn off payment reminders and still get appointment reminders. For subscription businesses, that protects the servicing messages that keep churn and failed payments down.

Marketing and promotional streams keep the broad rule. A revocation made in response to a telemarketing or advertising call or text still covers all future marketing robocalls and robotexts from you. If a customer opts out of a flash-sale text, every SMS promo and prerecorded marketing call to that number has to stop.

That split matters for how you build programs. Teams that mix promotions into “informational” flows, such as an upsell slipped into a delivery notice, risk having the whole message treated as marketing, and then the global opt-out rule applies.

Owning the opt-out experience

The order also lets brands designate exclusive opt-out methods: an in-call voice or key-press option, a reply text using any of seven keywords (stop, quit, end, revoke, opt out, cancel, unsubscribe), or a designated website or phone number. The method must be clearly and conspicuously disclosed. If you do this right, you no longer have to process opt-outs that arrive through random channels, such as a comment on a social post or a note to a sales rep.

From a growth view, this is a chance to bring opt-out design into the product. A clear, consistent opt-out path is easier to measure and audit, and it gives you a defensible record if a dispute ever happens.

Plan for what’s coming

The FNPRM is a preview of what might come next. The FCC is asking whether to:

Cut the time to honor a revocation from ten business days to seven.
Require two-way texting so consumers can always reply with an opt-out.
Make category-specific treatment depend on also offering a one-step “revoke all” option.
Clarify how separately branded affiliates and divisions are treated.

Any team still running one-way, no-reply short codes for customer messaging should treat the second item as a warning. Multi-brand companies should watch the affiliate question closely, because it will decide whether an opt-out from one brand carries over to its sister brands.

Growth without the lawsuit tax

Every outbound campaign has a lawsuit tax built in, and much of it comes from a small number of people who sue for a living. TCPALitigatorList.com gives growth and RevOps teams a way to screen contact lists against known TCPA litigators before launch, which pairs well with tighter opt-out handling. One protects you from the people who opt out; the other protects you from the people who never meant to opt in.

The takeaway

The November 25 rules reward segmentation. Brands that clearly separate informational from promotional traffic, and that build a clean opt-out path, get to keep more of their customer conversations. Brands that blur the line get the strictest rule applied by default.

Sources

When a TCPA Lawsuit Is the Product: What the Human v. Fisher Sanctions Mean for Growth Teams

Growth teams like to think of TCPA risk as a compliance problem: consent language, opt-out handling, calling windows. A ruling out of Missouri is a reminder that part of the risk is something else entirely. Some of the people entering your funnel are not prospects. They are building a lawsuit.

On September 30, 2026, Judge Matthew T. Schelp of the U.S. District Court for the Eastern District of Missouri found that Daniel Human’s TCPA suit against Fisher Investments was brought “in complete bad faith.” The court held Human, his attorney Edwin Butler and Butler Law Group LLC jointly and severally liable for all of the reasonable attorney’s fees Fisher incurred defending the TCPA claims, from the beginning of the litigation (Human v. Fisher Investments, Inc., No. 4:24-cv-01177-MTS).

The setup, as the court described it

The court found that Human provided his number under a fake name to request solicitations, then sued once Fisher called. It called this his “practice” and noted that dozens of earlier defendants had settled similar claims. It also found that Human destroyed his desktop computer two days before a court-ordered inspection and arrived with a decoy laptop, and that his lawyer knew the claims were illegitimate when he took the case.

Fisher must file its fee records by October 22, 2026. Fees for Fisher’s separate fraud counterclaim are excluded from the blanket award.

Why this is a funnel problem

Think about how the lead arrived: a person filled in a request, and the company followed up. From a dashboard, that looks like a healthy inbound conversion. The difference between a buyer and a plaintiff is invisible at the top of the funnel unless you look for it.

That has a few implications for teams that live on lead volume:

Lead quality metrics should include legal risk. A source that delivers high contact rates but also delivers repeat litigants is not a good source.
Purchased and partner leads deserve the most scrutiny. The further you are from the original form fill, the harder it is to prove consent later.
Speed-to-lead has a cost. Calling within seconds is great for conversion. It also means nobody looks at the number before the dialer does.

The settlement math growth teams should know

The detail worth sharing with finance is that dozens of companies settled with the same plaintiff before Fisher fought. That is the rational choice in most cases. Statutory damages under the TCPA run $500 per violation and up to $1,500 if willful or knowing, so a handful of calls can produce a demand that is cheaper to pay than to litigate. Serial filing works because the math works.

Fisher’s result shows what it takes to break that math: litigation running since 2024, a fight over a forensic inspection and a sanctions motion. Most growth-stage companies will never be in a position to do that. They need to avoid the exposure instead.

Build the screen into the stack

The practical answer is to put a check between lead capture and the first touch. TCPALitigatorList.com gives outbound and growth teams a way to scrub numbers against known TCPA litigators and serial filers before they reach the dialer or the SMS platform, so the riskiest contacts never become part of a campaign. It works alongside consent and DNC compliance rather than replacing them.

Pair that with consent capture you can actually prove: the form, the disclosure, the timestamp and the source. If a dispute does come, those records are what let you push back rather than pay.

Takeaway

Human v. Fisher is a rare win against a manufactured TCPA claim. For growth teams, the lesson is not to wait for a court to sort out who is a real prospect. Sort it out at intake, before the first call or text goes out.

Sources

Your Sender ID Is Now a Compliance Surface: The TCPA Claim Marketing Ops Missed

Ask a marketing-ops team to list their TCPA risks and you will hear consent, opt-outs, quiet hours, list scrubbing. You will almost never hear “caller ID.” That gap is now a problem, because a fast-growing 2026 litigation theory targets exactly the thing your team configures and then forgets: the name and number that appear when your call or text lands.

The theory in plain terms

FCC rule 47 C.F.R. 64.1601(e) requires telemarketers to transmit caller identification — identifying information plus a number a consumer can use to make a do-not-call request. Plaintiffs’ firms have reframed this dusty technical requirement as a private cause of action, and courts in 2026 are largely agreeing. More than one federal court has now held that consumers can sue over caller ID failures, including on marketing text messages — meaning your SMS sender configuration is a litigation surface, not just a deliverability setting.

The state of play

It is unsettled in a way that should worry any growth team. On the defense-friendly side, the District of New Jersey held in Zelma v. Ram (May 19, 2026) that showing the brand name “RE/MAX” alongside the number satisfied the rule — recognizable identification was enough. On the other side, a Massachusetts court in Novia v. Mobiz let a caller ID claim on marketing texts proceed past the motion to dismiss, and courts have recognized a private right of action for SMS caller ID defects. The boundary between “compliant” and “class action” is being drawn right now, case by case.

Why GTM teams own this

The caller ID claim is dangerous to a marketing org for one structural reason: it does not depend on consent. Your entire compliance posture might be built around proving opt-in — clean consent records, documented sources, airtight disclosures — and none of it answers a caller ID claim. A perfectly consented audience that receives a text from an unidentifiable alphanumeric sender, or a voice call with no resolvable callback identity, is still a class. At $500 to $1,500 per message across a campaign list, the math is brutal and the defense is narrow.

Building the fix into your stack

Add caller identity to your campaign QA checklist as a first-class item. For SMS, confirm every sending number or short code presents a clear, recognizable business identity and a monitored opt-out and callback path; retire “no-reply” sender configurations for marketing traffic. For voice, verify the CNAM and ANI you transmit resolve to your business name and a working callback line. Document these settings the way you document consent, so you can show a court a deliberate, compliant choice. And track the states — Florida’s 2026 session is considering caller identification mandates stricter than the federal baseline, and a multi-state program needs to plan for the tightest rule, not the loosest.

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

For years, marketing ops treated sender ID as plumbing. In 2026 it became a compliance surface with its own class-action theory attached. Audit what your campaigns actually display, fix the gaps before a plaintiff documents them, and make caller identity a permanent line in your launch process.

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 Post-Dobronski and McKesson”; Klein Moynihan Turco — “Caller ID and Text Messages”; 47 C.F.R. 64.1601(e).

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