TCPA – Page 3 – Bring To Market

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.

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

How a Single Delaware Ruling Just Reshaped Your SMS Send-Time Strategy

If you run lifecycle marketing, demand-gen, or any SMS motion at scale, the most important TCPA development of the past week wasn’t a settlement or an FCC filing. It was a 28-page opinion out of a Delaware federal courtroom that just rewired the risk calculus on quiet-hours claims for opted-in audiences.

The case in one paragraph

In King v. Bon Charge (D. Del., April 30, 2026), the court dismissed a putative class action alleging that the defendant violated the TCPA’s quiet-hours provision by sending marketing texts before 8 a.m. or after 9 p.m. local time. The dispositive fact: the plaintiff had voluntarily provided their phone number to Bon Charge through the company’s own digital channels. The court held that a consumer who hands a business their number cannot then weaponize the quiet-hours rule against the business they invited to contact them.

Why your GTM team should care

Quiet-hours suits have been one of the fastest-growing categories of TCPA litigation in 2025 and 2026. They’re attractive to the plaintiffs’ bar because the trigger is mechanical: a single timestamp on a single text. Damages are statutory ($500 per violation, trebled to $1,500 for willful violations), so a dispatch to 100,000 phones at the wrong minute is a $50M-to-$150M exposure on paper. That math has driven brands to clip their send windows aggressively, even when the audience explicitly opted in.

That conservative posture comes with a real revenue cost. SMS open rates spike in the early morning and the post-dinner window. The Wednesday-night “last-call” email—long a workhorse of e-commerce and B2B lifecycle programs—has been quietly pushed earlier and earlier as legal teams hedge. Bon Charge creates the first meaningful judicial pushback on that trend for opt-in sends.

What this means for your stack

The legal frontier is moving toward a clean distinction: cold lists still carry full quiet-hours risk; self-supplied numbers have at least one persuasive ruling in their favor. Three implications for marketing-ops:

Consent provenance is now a marketing-ops problem. Your ESP probably knows that a number is subscribed. Does it know where the consent originated? The pop-up checkbox on your PDP, the lead-gen form your SDR sent, a partner co-registration deal? Bon Charge protects the first two; the third is murky. Build the source field into your subscriber schema and pipe it through to compliance review.

Send-time tests are back on the table. If your lifecycle team has been forbidden from running send-time experiments outside 9-to-8 windows for opt-in audiences, this ruling is a reasonable trigger to revisit that policy with legal. The upside on engagement metrics from broadening your send window can be material; the legal downside, at least in the Third Circuit, just got smaller.

Co-registration and lead-aggregator data is on the wrong side. If a measurable fraction of your subscriber base came in through bought lists or partner co-reg, that segment doesn’t enjoy the protection Bon Charge describes. Tag those subscribers in your CDP and consider routing them through a more conservative compliance posture.

What it doesn’t mean

This is a district court ruling and it isn’t binding outside Delaware. Plaintiffs will keep filing quiet-hours suits, and they’ll keep winning some of them — particularly in jurisdictions that have been more receptive to the consumer-protection framing. Treat Bon Charge as a meaningful new arrow in defense counsel’s quiver, not an all-clear signal.

The marketing-ops takeaway

Build consent provenance into your subscriber data model. Treat opted-in numbers and acquired numbers as distinct compliance segments. And re-examine the artificially narrow send windows your legal team imposed in the panic phase of the quiet-hours litigation wave — for the segment of your audience that gave you their number directly, the playing field just tilted back toward operators.

Sources: TCPAWorld; Blacklist Alliance.

Why TCPA Lawsuits Are Suddenly More Expensive (and How to Stay Out of Them)

For growth teams running SMS at scale, April 2026 brought a string of headlines that should rewrite your pre-flight checklist. New settlements, new theories, and a striking $3,787-per-claimant payout in one TCPA case have reset both the average cost of getting it wrong and the appetite of plaintiffs’ firms to find new targets.

The economic picture

Recent TCPA resolutions cluster in a now-familiar range: $1M to $10M total fund, with per-claimant payouts that have crept upward as settlements get smaller class definitions. Gen Digital settled prerecorded-message claims for $9.95M. Wilshire Law Firm: up to $5.975M. ASP Aesthetics: $1.32M for sending marketing texts after opt-outs. Nationwide: $1.4M on robocalls. And in one outlier case, claimants split the fund into $3,787-per-person checks.

Add up the legal fees, the cy pres, the operational disruption, and even a “small” TCPA case rarely lands under $500K all-in for the defendant.

The new frontier: quiet hours

The most interesting development is the rise of “quiet hours” class actions. The TCPA prohibits telemarketing calls and texts before 8 a.m. or after 9 p.m. local time. Plaintiffs’ firms have realized that SMS marketing platforms frequently fire on UTC or server time, not recipient local time — meaning a 7 p.m. Pacific send hits 10 p.m. on the East Coast and creates a class of millions instantly. A new suit against Ruggable targets exactly this pattern.

The growth-team playbook

If you run outbound SMS, four controls catch most of the failure modes plaintiffs are exploiting in 2026. Time-zone-aware scheduling that uses the recipient’s wireless area code to infer local time. STOP-keyword propagation that completes within seconds, not minutes, across channels. DNC scrubs run on every send, not on every list. And a screen against known TCPA litigator databases, performed at the list level before any campaign goes live.

Outbound is still one of the highest-ROI channels in B2C and B2B — but only if your dial list is clean. TCPALitigatorList.com is the de-facto industry list of known TCPA plaintiffs and professional-litigant phone numbers, updated continuously. Marketing and growth teams that scrub their cadences against it before a launch dramatically reduce the odds that a campaign turns into a class action. If you are running outreach at any scale, it belongs in your pre-flight checklist.

Why now

Plaintiffs’ firms have gotten more sophisticated, more aggressive on forum selection, and more creative on theories. The bar for filing has dropped. The smart move for any team running outbound at scale is to assume your campaigns will be audited by an adversary, and build accordingly.