TCPA – Page 3 – Bring To Market

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.

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.

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.

TCPA “Revoke-All” Rule Pushed to 2027: A Year to Get Your Consent Plumbing Right

Marketing-ops teams just got a gift, even if the FCC did not frame it that way. On January 6, 2026, the Commission extended the effective date of the TCPA “revoke-all” consent rule to January 31, 2027 — giving every business that runs cross-channel customer messaging another year to fix the plumbing.

The rule, in plain English

Today, when a customer texts STOP to your billing reminders, that revocation applies to billing reminders. Under the “revoke-all” rule, the same STOP would have to silence your marketing campaigns, customer-service follow-ups, transactional alerts, and every other channel you operate — even ones the customer never explicitly opted out of. One revocation, full stop, across the entire enterprise.

For a martech stack stitched together from five vendors and three customer databases, that is genuinely hard. Hence the delay.

Why this matters for your stack

The compliance question is really a data question: when a revocation lands in any one channel, can it propagate — quickly and verifiably — to every other? Most teams find the answer is “kind of, eventually, with manual cleanup.” That is not going to be acceptable when the rule lands in 2027.

The teams who treat the next year as engineering runway will save themselves a hectic Q4 2026. Map your outbound channels. Identify the system of record for consent. Build (or buy) a real-time revocation pipeline. Test it with synthetic STOP events.

Three things to do this quarter

First, run a consent-state audit: pick 50 random customers, trace their consent and revocation status across every channel you use, and find the inconsistencies. Second, document your STOP propagation latency end-to-end — most teams are shocked by how long it takes. Third, get legal and growth in the same room to align on the unified “this customer has revoked” signal that will eventually need to gate every send.

Don’t waste the runway

Regulators only delay rules they intend to keep in some form. The “revoke-all” requirement, or something close to it, is coming. The companies that emerge with the cleanest consent operations will be the ones who treated the extension as engineering time, not vacation time.

What the Fifth Circuit’s TCPA Ruling Means for Your Go-to-Market Motion

If your growth motion includes outbound voice or SMS — and for most B2C operators, it does — a March 2026 Fifth Circuit ruling just changed the calculus. The court rejected the FCC’s “prior express written consent” rule for prerecorded marketing calls. For marketers, this is one of those decisions that sounds technical and is actually load-bearing.

The short version, for marketers

Since 2012, anyone running prerecorded marketing calls in the U.S. has had to capture a signed written consent before the call could legally land. The Fifth Circuit said the FCC overstepped when it added that “written” requirement, because the TCPA itself only says “prior express consent.” After Loper Bright stripped courts of their old habit of deferring to agencies, the rule became vulnerable, and the Fifth Circuit pulled the trigger.

In plain English: in the Fifth Circuit (Texas, Louisiana, Mississippi), the law is now closer to the plain text of the statute. Outside it, the FCC’s old rule still applies — for now.

Where this hits your funnel

Most growth teams use written consent as the universal default because (a) it is simpler than running region-specific consent flows and (b) it is the most defensible. That should not change overnight. What does change is risk allocation. If you are sued in a Fifth Circuit court, you have a meaningfully stronger argument that an opt-in checkbox you forgot to capture isn’t fatal. If you are sued anywhere else, the old rule still rules.

Practically, this means three things: keep your written-consent capture in production; expect plaintiff firms to forum-shop into pre-ruling circuits more aggressively; and assume the FCC will respond, probably within the next 12 months, with a new rule or new enforcement priorities.

Reviewing your stack this quarter

This is a good moment to audit consent capture in your tag manager, your email service provider, and your CRM. The questions to answer: Are timestamps captured? Is the disclosure language at the point of opt-in current? Are your DNC scrubs running on every list, every send? Is your suppression file actually being honored across channels?

The takeaway

One court has cracked the door on consent. Plaintiffs’ firms have not slowed down — if anything, the volume of TCPA suits is climbing. Treat the Fifth Circuit decision as a defensive tool, not a green light. Your outbound program is only as compliant as the weakest link in your consent and scrub stack.