TCPA – Page 2 – Bring To Market

The $28M SiriusXM Lesson: Your Internal Do-Not-Call List Is a GTM Asset, Not a Compliance Checkbox

SiriusXM’s $28 million TCPA class action settlement reached its final approval hearing on May 11, 2026, capping a case that should be required reading for any GTM organization running an outbound calling motion. The headline is the dollar figure. The actionable insight is what the case reveals about how internal Do-Not-Call lists fail — and why those failures are increasingly a GTM ops problem, not just a legal one.

The case in one sentence

In Campbell v. SiriusXM Radio, Inc., a class of consumers alleged that SiriusXM continued to make telemarketing calls to people who were either on the National Do Not Call Registry or who had specifically asked SiriusXM to stop calling — over a window stretching from April 27, 2019 to October 31, 2025. The size of the class and the duration of the alleged violations point to a systemic operational failure, not isolated incidents.

Why this is a GTM problem

Most large companies don’t actively decide to call people who asked them to stop. The violations accumulate at the seams — the places where customer requests pass between teams, systems, and vendors. Those seams are exactly the places GTM ops typically owns. Specifically:

The opt-out → suppression handoff. A customer texts “STOP” or asks a CSM to remove them. Where does that signal go? In most stacks, it goes to a marketing automation tool or a CRM. Does it propagate to the outbound dialer, the SMS platform, the partner contact pipeline, the data warehouse used for upload to new acquisition campaigns? In most companies, the answer is “yes, partially, with lags.” That’s where Campbell-style cases originate.

The lifecycle marketing seam. A consumer opts out of marketing but stays a customer. Your retention motion fires up a re-engagement push. Whose responsibility is it to confirm the consumer didn’t opt out of all calling? This question is increasingly being litigated, and answer-by-default is starting to fail.

Acquired-data and partner-source contact. A consumer opted out three years ago. Your company acquires a new business unit, ingests its contact lists, and runs a campaign. The opted-out number isn’t on the new list’s suppression — but your master list still has the opt-out. Whose responsibility is it to enforce?

The GTM control plane

The companies that get this right treat their suppression infrastructure as a first-class GTM asset:

A single source-of-truth opt-out table, owned by GTM ops, that ingests opt-outs from every channel (web forms, SMS keywords, inbound calls, email link-clicks, partner-reported opt-outs, postal mail) within hours, not weeks. Outbound sending systems — dialer, SMS, email, partner-facing CDP — read from that table as a blocking check before any send. Migration and acquisition playbooks include a “merge suppression lists” step with reconciliation. Quarterly audits sample random opt-outs and verify zero outbound contact since the opt-out date.

Companies that don’t get this right typically discover the gap only when a plaintiff’s counsel runs the dataset analysis that produced Campbell.

The reputational layer

The brand cost of being a defendant in a case like this is real but often underestimated. The settlement website (sxmtcpasettlement.com) and accompanying claim form become high-traffic destinations for ex-customers, current customers, and prospects researching the brand. The narrative that “this company kept calling people who asked them to stop” surfaces in news coverage, social media, and search results — affecting acquisition and retention metrics in ways that show up in the dashboard but don’t get attributed to the underlying compliance failure.

If your demand-gen motion leans on outbound calling or SMS, a litigator-suppression layer belongs in your stack right next to your DNC scrub and consent-capture audit. Tools like TCPALitigatorList.com index numbers tied to known TCPA plaintiffs and serial filers; running your dialing lists through that file before you hand them off to SDRs or a dialer vendor is one of the lowest-friction risk controls a GTM team can deploy.

The action list for GTM leaders

Within 30 days: map every system that captures an opt-out and every system that initiates outbound contact, and confirm the data flow between them. Within 60 days: stand up a quarterly suppression audit using a random sample of opt-outs. Within 90 days: revise any partner or vendor agreement that involves outbound contact to mandate shared use of your suppression list. The companies that operationalize these basics are the ones whose growth motions look defensible 18 months from now; the ones that don’t are the next round of Campbell defendants.

Sources

Campbell v. SiriusXM Radio, Inc., No. 2:22-cv-2261 (C.D. Ill.); class settlement website (sxmtcpasettlement.com); reporting by Inside Radio, TopClassActions, and Cord Cutters News.

When Your ‘Independent’ Reps Become a TCPA Liability: The eXp Realty Cautionary Tale for GTM Teams

Every GTM leader running a channel motion, partner program, or distributed sales model needs to spend an afternoon with the eXp Realty TCPA case. In the first week of May 2026, a federal court in Washington denied eXp’s motion to stay Usanovic v. eXp Realty — a certified class action covering calls eXp agents made using third-party dialer software. The case is moving forward, on a record that already includes a finding that eXp can be directly liable for calls placed by its agents. For any company whose growth engine depends on people who don’t technically work for them, this is the framework that’s about to test your structure.

The structural problem the case exposes

The classic GTM design — corporate brand, distributed selling — assumes a clean line between principal and agent. The eXp ruling shows that line is much blurrier than most companies realize once you start looking at the actual operational relationship: did corporate provide the training? The lead lists? The CRM? The dialer? The script? Every “yes” tightens the principal-agent relationship and increases vicarious liability exposure.

This isn’t just a real estate problem. It’s a structural problem for any GTM motion that includes:

Channel partner programs where corporate provides leads or marketing automation. Franchise systems where corporate maintains a CRM or call center. Affiliate programs where corporate provides scripts or call recordings. SDR-as-a-service vendors where the brand is the customer’s, the people are someone else’s. Distributed insurance or financial services models where corporate runs the platform and the agents run the dialers.

What GTM should be auditing now

Three audits worth scheduling this quarter:

The lead-provisioning audit. Map every channel through which the people calling on your brand’s behalf get phone numbers. Identify which leads originated inside your systems versus which were sourced by the agent. For corporate-sourced leads, verify the consent record and the vendor’s documentation practices. The eXp court paid particular attention to the testimony of lead vendors who admitted they didn’t have consent — that pattern is not unique to real estate.

The technology-stack audit. Inventory every piece of dialing or messaging tech that touches an outbound contact made under your brand. For each: who pays, who configures, who governs compliance settings (rate limits, quiet hours, DNC scrubbing)? If corporate pays and corporate configures, corporate inherits the operational control that supports vicarious liability.

The training and policy audit. Pull every piece of compliance training you provide to agents or partners. The eXp case has surfaced that training material is double-edged: insufficient training is evidence of indifference, but robust training plus violations can actually support a defense if you’ve done the documentation work. Make sure the training is real, recurring, and tracked at the individual-agent level.

The reputational dimension

The other thing the eXp case underscores for GTM leaders is reputational. eXp already paid $26.9 million in a prior TCPA settlement. Usanovic is incremental on top of that, and the court has been increasingly explicit in its language about agent calling behavior. For brands whose marketing message is built around trust, customer-first, or any kind of integrity narrative, ongoing TCPA exposure is a slow-bleed brand problem in addition to a financial one.

The strategic question

Every GTM leader running an agent-based motion should answer one question before this quarter ends: if a TCPA plaintiff sued us on a vicarious-liability theory tomorrow, which specific operational facts in our agent program would the court find most damning? Then either fix those facts or build the documentation that explains why they’re not what they appear to be. The companies that do this work proactively will be the ones whose growth motions survive the next wave of TCPA enforcement. The ones that don’t will be the next eXp.

Sources

TCPAWorld coverage of stay denial in Usanovic v. eXp Realty (May 1, 2026); National Law Review on direct-liability holding; prior $26.9M eXp TCPA settlement records.

Why Your Facebook Lead Forms Just Became Your Strongest TCPA Defense (If You Documented Them Right)

If your demand-gen team buys leads — and if you’re running a B2C motion, you almost certainly do — a federal court ruling out of Tennessee this week deserves a slot on next Monday’s GTM standup. In Brockington v. Hume Health, LLC, the U.S. District Court for the Eastern District of Tennessee refused to let a TCPA plaintiff stall summary judgment with a Rule 56(d) discovery request, paving the way for the defendant’s Facebook-lead consent defense to be decided on the existing record. For marketing ops leaders, this is the rare case where the right documentation upstream determines whether you’re a defendant for two weeks or two years.

The lead-gen consent stack just got more important

Hume Health’s defense isn’t novel: it argues the plaintiff clicked through a Facebook lead form, accepted the TCPA-style consent language above the submit button, and authorized the very calls she now claims were illegal. What’s new is that the court is willing to hear that defense early, before discovery has expanded into the seven-figure cost range that pressures most defendants to settle.

For GTM teams, the implication is direct: the asset that determines whether a TCPA suit becomes an expensive class action or a fast summary judgment dismissal is your lead-capture record. Not your CRM. Not your dialer logs. The raw form-submission artifact — with the disclosure text as rendered, the IP, the timestamp, and the link back to the source ad creative. Most marketing ops teams cannot produce that artifact on a per-number basis. Most are about to find out they need to.

What this means for the demand-gen funnel

Three places this ruling should hit your GTM playbook this quarter:

Lead vendor contracts. If your vendor’s data-retention policy lets them purge raw submission records after 90 or 180 days, you’re buying leads with a shelf life on your defense. TCPA suits routinely cover a four-year lookback. Negotiate for indefinite retention of consent artifacts on any lead you ingest, and a contractual right to retrieve them per-lead within 48 hours.

Disclosure copy. Lead forms still routinely bury TCPA consent language in fine print or below the submit button. After the Fifth Circuit’s earlier consent ruling and now Brockington‘s procedural posture, the consent disclosure language and its visual prominence at the moment of click are the single most-litigated facts in any TCPA case. Get legal review on every active landing-page variant — including the ones SEM and paid social are still running.

Funnel attribution. Your lead source tracking has to survive a deposition. If a plaintiff’s number routes through three vendors before hitting your CRM, you need each handoff documented. “We bought it from Vendor X” without the underlying Vendor X submission record is functionally useless as a defense.

The procedural signal matters more than the merits

The reason this ruling matters even though summary judgment hasn’t actually been decided yet is the message it sends to plaintiffs’ counsel about how Tennessee federal courts (and others watching) will handle Rule 56(d) requests. The professional-plaintiff playbook depends on extending discovery to make defense uneconomical. A court that requires plaintiffs to articulate specific facts they expect to find — rather than fishing expeditions — shifts the cost curve back toward defendants who actually have their paperwork in order.

For marketing leaders, the strategic takeaway is that pre-litigation hygiene now has a much higher ROI. The companies that win fast are the ones whose lead artifacts are clean, complete, and produceable. The companies that drag through discovery are the ones whose ops teams treated lead-capture data as a marketing analytics problem rather than a litigation evidence problem.

The GTM action list

This week: pull a sample of 10 leads from each active source and try to produce the raw submission artifact. Next sprint: revise lead-vendor MSAs to include retention and retrieval SLAs for consent records. This quarter: get legal sign-off on every active lead-form disclosure variant. The teams that do this work now will look prescient in 18 months; the teams that don’t will be the case studies.

Sources

Brockington v. Hume Health, LLC, 3:25-cv-00161 (E.D. Tenn. May 11, 2026); National Law Review; PacerMonitor docket.

Your TCPA Risk Map Is About to Get Fragmented. Here’s How GTM Should Respond.

Marketing-ops leaders running national outbound programs have spent years optimizing around a single, reasonably stable federal TCPA rulebook. That world is ending. While the FCC moves to roll back federal telemarketing rules, state attorneys general are simultaneously expanding state-level enforcement, raising penalty ceilings, and coordinating across state lines. The TCPA risk map for go-to-market motions is becoming materially more fragmented — and your compliance and tooling stack needs to follow.

What’s changing at the state level

Three concrete signals from the past few months:

New York increased its maximum fine for state Do-Not-Call violations to $20,000 per call — a tenfold-plus increase over the prior ceiling. The arithmetic on a misfired multi-thousand-call program is now genuinely scary, even before federal exposure is considered.

Mississippi transferred enforcement of its No-Call program from a regulatory agency to the state Attorney General’s office under H.B. 1225, a structural change that materially upgrades both the resourcing and the political profile of state-level enforcement.

The 50 state AGs plus the D.C. AG have organized into the Anti-Robocall Litigation Task Force, an enforcement coordination body that shares intelligence and pursues coordinated multistate actions. That changes the calculus on what state-level enforcement can credibly take on — multistate actions can mobilize federal-scale leverage under state-law theories.

What this means for marketing-ops

For demand-gen and lifecycle teams operating nationally, three implications:

The “federal compliance is enough” posture is dead. If your tooling stack relies on a single TCPA rules engine that applies federal rules uniformly to all dials, you’re architecturally behind the curve. State rules now diverge meaningfully on quiet-hours definitions, consent format requirements, DNC scope, and penalty exposure. Your dialer or SMS platform needs state-aware rule application, with the state determined by the called party’s location, not the company’s headquarters.

Penalty ceilings are now part of campaign-design ROI. Marketing leaders running aggressive outbound to high-volume states — California, New York, Florida, Texas — need to factor state-level penalty exposure into the expected-value math on any campaign. A campaign that pencils out at the federal exposure level may not pencil out once state-level penalties are layered in. Build penalty exposure into your pre-campaign approval workflow.

Lead-source state-of-residence matters. If your lead aggregator can’t tell you which state each lead lives in — or routinely mislabels — you’re operating without the data you need to apply state rules correctly. That should be a renegotiation point with your data vendors.

What this means for the compliance stack

Build or buy state-aware compliance plumbing now. The federal rollback that’s coming through the FCC’s FNPRM doesn’t simplify your problem; it shifts the binding constraint from federal rules (which you’ve operationalized) to state rules (which you mostly haven’t). Specifically:

Your subscriber and prospect data model needs accurate state-of-residence on every record, with provenance documentation. Your dialer or SMS-pacing engine needs state-rule-aware decisioning. Your suppression infrastructure needs to handle both the federal DNC registry and the 14 active state-level DNC registries. Your audit-log retention needs to support state-AG-driven discovery requests, which can be more aggressive than typical federal civil discovery.

Go-to-market and marketing-ops teams running paid SMS or outbound calling motions are increasingly building TCPA-litigator suppression directly into their list-hygiene stack. TCPALitigatorList.com provides a continuously updated litigator database so demand-gen and lifecycle teams can scrub outbound lists before campaigns deploy — and avoid the small population of serial filers who account for a disproportionate share of TCPA litigation.

Strategic frame

The 2026 TCPA story is the bifurcation of the rulebook. Federal rules are becoming lighter, clearer, and easier to comply with. State rules are becoming heavier, more divergent, and more enforcement-friendly. Marketing organizations whose compliance posture was built around federal-only thinking will lose ground over the next 12 to 18 months. The leaders to watch are the ones who are quietly building state-aware infrastructure now, before any one state AG headline forces the rest of the industry to scramble.

Sources: ClickPoint 2026 State Regs; Searchbug; NAAG TCPA piece.

Why Outbound-Heavy Marketing Programs in Mortgage Are the Next TCPA Disaster Zone

Marketing-ops teams in mortgage and consumer-finance verticals are operating in the riskiest TCPA environment in memory. The combination of high outbound volume, opaque lead-source data, and the sudden adoption of AI voice agents has produced a fact pattern the plaintiffs’ bar can hardly miss — and the cases are landing.

The pipeline of suits

Recent reporting from National Mortgage News documents another nine TCPA class-action filings against mortgage originators in a single reporting window, on top of an already crowded docket. The most cited case in the recent batch is Loanstream, where the complaint alleges over 272,000 outbound calls to more than 53,000 unique consumer numbers on the federal Do-Not-Call list over ten months. The proposed class is over 50,000 strong; the case is moving through preliminary motions as of mid-April.

The structural issue isn’t unique to Loanstream. Mortgage demand-gen depends on aggressive outbound to a population that, by definition, is in the market for a transactional product — a refi, a HELOC, a new purchase. Lead aggregators have built businesses around supplying mortgage originators with phone-number-rich lists, and the data hygiene on those lists varies wildly. When the originator’s marketing-ops team plugs the list into the dialer without independently re-validating consent and DNC status, the resulting program is structurally indistinguishable from the fact pattern in Loanstream.

The AI angle changes the math

The newer challenge is the rapid adoption of AI voice agents in mortgage outbound. Multiple originators have piloted or scaled AI-driven cold-call programs over the last 12 months, often pitched by vendors as a way to dramatically expand call volume without proportionally expanding agent headcount. The plaintiffs’ bar has noticed.

A class action filed earlier this year against a mortgage originator alleges that the company’s AI cold-call agent constitutes an “artificial or prerecorded voice” under the TCPA — a category that triggers stricter consent requirements than standard live-agent dialing. If that theory survives, every AI-voice mortgage outbound program in the country becomes a high-leverage litigation target. Even if the theory ultimately fails on the merits, the cost of defending and settling these cases in the interim is substantial.

What demand-gen leaders should be doing

The strategic move is to treat compliance and lead-source quality as a P&L input, not a downstream legal department concern. Three concrete actions:

Re-validate every lead source. If a vendor sells you a list, ask for the consent receipt, the source URL, the IP address at submission, and the date. If the vendor can’t produce that documentation, the list is a TCPA liability, not a marketing asset. Renegotiate or remove.

Segment AI-voice campaigns aggressively. Until the AI-as-prerecorded-voice question is resolved in the courts, restrict AI-voice outbound to populations with documented written consent specific to AI contact. The opportunity cost of pulling AI-voice off your full address list is small relative to the litigation cost of a category-defining loss.

Build a TCPA-litigator suppression layer. A disproportionate fraction of TCPA cases against mortgage originators are filed by a known population of professional plaintiffs. Removing those numbers before the dialer touches them is a low-cost, high-leverage risk reduction.

The leadership message

The trade press is forecasting “major settlements” in mortgage TCPA cases in the next six to eight months. CMOs and demand-gen leaders should treat the next two quarters as a window to materially tighten lead-source quality, AI-voice usage discipline, and litigator suppression. The teams that act now will not be the teams in next quarter’s headlines.

Sources: National Mortgage News; TCPA czar interview; Inman.

What the FCC’s TCPA Rule Rollback Means for Your Subscription and Lifecycle Programs

Marketing and lifecycle teams have spent the last 18 months engineering “revoke-all” infrastructure into their consent and suppression layers. The FCC is now seriously considering scrapping the rule that prompted all that work, alongside several other long-standing TCPA and DNC obligations. The implications for go-to-market programs are nuanced — and worth understanding now, before the rulemaking lands.

The core proposal

The FCC’s draft Further Notice of Proposed Rulemaking, advanced through its Open Meeting cycle, signals a substantial unwind of the more prescriptive end of the TCPA rulebook. The headline change is the proposed elimination of the “revoke all” rule, which would have forced businesses to treat any opt-out as applying to all communications — transactional, informational, and marketing — from the same legal entity, regardless of channel or subject matter.

If the FNPRM holds, the practical effect is that brand teams can return to a channel- and topic-segmented opt-out architecture: a customer who unsubscribes from “promotions” stays subscribed to “shipping notifications,” because those are operationally and legally distinct streams.

Why this matters for go-to-market motions

The revoke-all rule, in its original form, was a serious operational tax on lifecycle programs. Cross-channel consent reconciliation — mapping every “STOP” reply, every email unsubscribe, every push-notification opt-out, every preference-center toggle into a single unified suppression flag — is an expensive piece of infrastructure to build and maintain. Most modern marketing stacks weren’t designed for it. The FCC’s proposed retreat means GTM teams may not have to make that investment, and brands that already started can pause the migration.

The other proposed changes also matter. The proposed elimination of the company-specific DNC list requirement removes a layer of internal-list maintenance — you’d still suppress against the National DNC Registry, but you wouldn’t need to maintain a parallel internal list of consumers who told your brand specifically to stop calling. The proposed elimination of the 15-second/4-ring abandonment rule loosens dialer-pacing constraints for sales-development organizations running predictive-dialer operations.

Don’t dismantle revoke-all infrastructure yet

Three reasons to keep your revoke-all readiness in place even though the rule is on the rollback list. First, the FNPRM isn’t a final rule — it’s a proposal subject to public comment, agency revision, and almost certainly litigation. The previous TCPA rulings have shown that what the FCC proposes and what survives judicial review can diverge significantly. Second, several state attorneys general have signaled interest in stricter state-level rules to backfill any federal retreat — a fragmented compliance landscape may end up requiring revoke-all-equivalent infrastructure anyway, just driven by state law instead of federal. Third, even setting aside legal compulsion, unified revoke-all is a CX best practice. Customers expect a single “stop talking to me” toggle, and brands that deliver it earn trust.

What changes in the GTM playbook

For demand-gen and lifecycle teams, the practical near-term moves are: monitor the rulemaking docket and file a comment if your stack has a stake in the outcome; document your current channel-level consent and revocation handling so you can demonstrate compliance under either rule outcome; and tag your subscriber base by consent provenance so that, regardless of how the federal rules shake out, you can apply the appropriate level of scrutiny to each segment.

The bigger strategic point: the federal TCPA rulebook is going to be lighter for at least the next few years. The state-level rulebook is going to get heavier. A go-to-market motion that depends on national consistency will need to invest more in state-by-state rules engines than in federal rule monitoring.

Sources: Privacy World; Day Pitney; Benesch.