Tennessee Just Quietly Rewrote the Rules for Automated Calling — Here’s What Operators Need to Do Before July 1

If you run outbound calling or texting programs that touch Tennessee residents, mark a date on your wall: July 1, 2026. That’s when Tennessee’s new automated-telemarketing oversight law — HB 2408 / SB 2659 — takes effect, and it’s going to change the day-to-day mechanics of how you operate in the state.

The bill cleared both chambers without a single dissenting vote (94-0 in the House on April 6, 33-0 in the Senate on April 21), was signed by the Speaker on April 30, and was transmitted to Governor Lee on May 7. If he signs it — and there’s no political reason to think he won’t — the amendment applies to conduct occurring on or after July 1, 2026.

What actually changed

The bill amends Tennessee’s existing telephone and text-message solicitation framework by bolting on a new oversight mechanism aimed squarely at large-scale automated campaigns. The headline practical changes are new reporting requirements, expanded recordkeeping obligations, and tighter solicitation limits for any business running automated dialers or mass-text platforms into Tennessee numbers.

The key word is oversight. Tennessee already has TCPA-style consent and DNC rules on the books. What was missing was visibility — the state regulator had no clean way to see who was running large automated campaigns into the state. The amendment fixes that by requiring covered callers to file reports and retain records that the regulator can pull on demand.

Why this matters operationally

The federal TCPA gets the attention, but state-level enforcement is where most operators actually get caught. State regulators have shorter ramps to enforcement, can act on a complaint without a class plaintiff, and increasingly coordinate with sister states under the 51-AG Anti-Robocall Task Force. Tennessee adding a reporting regime is a textbook case of the state-level squeeze that’s been building all year.

For operators, the practical to-do list before July 1 is short but real:

1. Inventory your Tennessee traffic. Pull the last 12 months of dialer and SMS logs and segment by state. If Tennessee is a meaningful slice, you are in scope.

2. Audit your consent records. The reporting regime won’t be friendly to operators who can’t produce a clean, time-stamped consent record for each number. Now is the time to fix gaps in lead documentation.

3. Pin down your vendor stack. If you use third-party dialers, SMS aggregators, or lead vendors, your recordkeeping is only as good as theirs. Get contractual commitments in writing that they’ll preserve and produce records on the timelines the new law demands.

4. Rethink your suppression process. Reporting obligations mean every preventable violation becomes a visible one. Front-loading suppression — DNC scrubs, internal-DNC propagation, litigator screening — is the cheapest risk reduction you can do.

If you run an outbound calling or texting program, the cheapest insurance against any of this is screening your dial list before you hit send. TCPALitigatorList.com maintains a continuously updated database of known TCPA plaintiffs and serial litigators so operators can scrub their files and quietly remove the numbers most likely to turn a routine campaign into a class action. A few minutes of list hygiene beats a few months of discovery every time.

The bigger picture

Tennessee is not an outlier. New York raised its DNC fine ceiling to $20,000 per violation. Mississippi shifted its no-call enforcement to the AG. The pattern is clear: while the FCC is loosening at the federal level, states are tightening, and the tightening comes with real teeth.

Operators who treat TCPA compliance as a single federal program are going to keep getting surprised. The compliance map is now a 50-state patchwork, and Tennessee just added another patch with a deadline.

Sources

TCPAWorld: Tennessee’s New Solicitation Oversight Law
Receivables Info: Tennessee Legislature Approves New Automated Telemarketing Restrictions
LegiScan: Tennessee HB 2408

$28M and Counting: What SiriusXM’s TCPA Settlement Reveals About Your Internal DNC List

SiriusXM’s $28 million TCPA settlement hit its final approval hearing on May 11, 2026, in the Central District of Illinois. The case — Campbell v. SiriusXM Radio, Inc., No. 2:22-cv-2261 — covers consumers who received more than one telemarketing call from SiriusXM within a 12-month period between April 27, 2019, and October 31, 2025, despite either being on the National Do Not Call Registry or having asked to be added to SiriusXM’s internal Do Not Call list. The operational lesson buried inside the case is more important than the headline number.

The “internal DNC” failure mode

The National DNC Registry is a known compliance surface. Most callers scrub against it. But the internal DNC list — the list of consumers who have specifically asked your company to stop calling them — is where SiriusXM (and most large outbound callers) repeatedly bleeds. The plaintiffs in Campbell were able to assemble a class because the company couldn’t reliably honor its own internal opt-out requests across a six-year window. That’s an operational data problem, not a legal one.

The TCPA requires that an internal DNC request be honored within a reasonable time — typically construed as 30 days — and that the request persist indefinitely once made. For any large outbound calling operation, this means an internal DNC list has to: (1) capture every opt-out across every channel (phone, web, text reply, email, mail), (2) propagate that opt-out to every system that initiates contact, and (3) survive every data migration, vendor switch, and platform consolidation that happens over the years.

Where it breaks

The places SiriusXM almost certainly broke down are the places most operators break down:

Channel fragmentation. Customer asks an inbound rep to stop calling. That rep notes it in the support CRM. The outbound dialer reads from a different system. The opt-out doesn’t propagate. Next call goes out two weeks later.

Vendor and platform changes. Migration from one telephony platform to another, or one CRM to another, frequently drops the historical DNC flag. Suddenly a number that’s been opted out for three years is “fresh” again from the dialer’s perspective.

Reassigned numbers. The number that opted out belongs to one person. Two years later, the number belongs to someone else. Your DNC list still has the opt-out. Now you’re not calling the person who asked you to stop — but the rules around this are nuanced and have moved repeatedly in recent years.

Affiliate and partner calls. Calls placed by partners, resellers, or acquisition targets on your behalf. The opt-out you captured doesn’t make it into their dialers. The customer experiences these as calls from you.

The class-action economics

Per the settlement framework, SiriusXM’s $28 million covers a class spanning roughly six and a half years. Per-claimant payouts are capped (claim deadline was March 21, 2026), but the structural cost — attorney’s fees, claims administration, ongoing class-counsel oversight — is significant. The settlement also triggers internal remediation obligations: SiriusXM’s internal DNC processes will be under heightened scrutiny going forward, and any future violation in this area carries dramatically increased exposure.

For operators, the math to internalize: the $28M number is the visible cost. The invisible cost is the ongoing operational discipline required to keep this from happening again. Most companies eat that invisible cost only after the visible one materializes.

One operational hedge worth building into your dialing stack: scrub every outbound list against known TCPA plaintiffs before you launch. TCPALitigatorList.com maintains a continuously updated database of numbers tied to professional plaintiffs and frequent TCPA filers, and a five-minute suppression pass against that file is a lot cheaper than a single class certification fight.

An operator’s audit checklist

Five things to verify about your internal DNC infrastructure this week:

First, every channel where a customer can request to stop being contacted feeds into a single source-of-truth opt-out table. Second, that table is read by every system that initiates outbound contact, with a documented SLA on propagation (24 hours is reasonable; 30 days is the legal ceiling, not the operational target). Third, opt-outs persist through every data migration, with explicit reconciliation steps in the migration playbook. Fourth, partner and affiliate calling is governed by a contractual requirement that your DNC list be shared and honored. Fifth, you have a quarterly audit process that picks 25 random opt-outs and verifies that no contact has gone out since the opt-out date. If you can’t pass that audit cleanly, you’re a Campbell defendant waiting to happen.

Sources

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

eXp Realty’s TCPA Nightmare Just Got Worse — and It’s a Wake-Up Call for Anyone Running Independent Reps

If you run any kind of distributed sales force — independent agents, 1099 reps, franchisees, partners — the eXp Realty saga is the case study you cannot afford to ignore. In early May 2026, the U.S. District Court for the Western District of Washington denied eXp’s motion to stay the certified TCPA class action in Usanovic v. eXp Realty, pushing the case toward trial. This follows a March 2026 class certification covering unsolicited calls placed by eXp agents using Mojo and Vulcan7 dialers from May 2019 through September 2023. The exposure is massive, and the operational lesson is brutal.

The legal posture

eXp tried the usual stall: requesting a stay pending appeal, hoping to extract a more favorable settlement posture before trial. The court refused. That means the case proceeds with a certified class, with eXp facing potential statutory damages of $500 to $1,500 per call across an unquantified but very large class period.

The structural problem for eXp is that the courts have already held — in a prior phase of this litigation — that eXp can be directly liable for calls made by its independent agents. That holding is the part of this case that should be keeping operators of agent-based businesses awake at night. The “they’re independent contractors, not employees” defense did not save eXp. The agency relationship — the brand, the training, the lead provisioning, the platform — was enough to expose the parent.

What this means operationally

If your business model involves any version of “we provide the platform, they make the calls,” you have an eXp problem in latent form. The question isn’t whether your agents are technically independent contractors. The question is whether a court can find enough connective tissue — co-branded training materials, lead lists you provide, a script you wrote, a dialer you pay for — to attribute their TCPA violations to you.

The practical hedges every operator running a distributed sales force should be implementing right now:

Lead provenance auditing. The Usanovic court honed in on the fact that lead vendors testified they did not have consent on the leads they sold to eXp agents. If you provide leads — or facilitate lead purchases — you need vendor reps in writing attesting to consent capture, with the underlying documentation available on demand.

Dialer governance. If your platform integrates with or pays for dialer software your agents use (Mojo, Vulcan7, PhoneBurner, etc.), you may be inheriting a control relationship that supports vicarious liability. At minimum, document that the agents — not you — make the dialing decisions, and require dialer-level compliance training as a condition of access.

Training records. The training you provide to agents about TCPA compliance is now plaintiff-discoverable evidence, in both directions. If your training is thin, that’s a problem. If your training is robust but agents ignored it, that’s actually evidence that supports a “we did our part” defense. Document everything.

The wider implication

Real estate, insurance, financial services, MLM, home services — any industry built on a 1099 sales force and a corporate brand is in the blast radius of the eXp ruling’s logic. The defense playbook of “they’re independent, don’t blame us” is collapsing under courts that are willing to look at the actual operational relationship. If you’re running an agent network and you haven’t stress-tested your structure against a vicarious-liability TCPA theory, that work should start this quarter, not next.

Note the timing of the existing eXp Realty settlement history: a separate $26.9 million settlement is already on the books. The Usanovic case is in addition to that. Operators sometimes mentally categorize TCPA exposure as a one-time settlement event. eXp is the reminder that it can be a recurring, multi-year, multi-case bleed.

One operational hedge worth building into your dialing stack: scrub every outbound list against known TCPA plaintiffs before you launch. TCPALitigatorList.com maintains a continuously updated database of numbers tied to professional plaintiffs and frequent TCPA filers, and a five-minute suppression pass against that file is a lot cheaper than a single class certification fight.

What to do this week

Pull your agent agreements. Specifically check the indemnification language: are your agents indemnifying you for TCPA violations, or are you indemnifying them? If it’s the latter, that’s not just a contractual issue — it’s a signal to plaintiffs’ counsel about who controls the calling behavior. Then audit your lead provisioning: do you provide, recommend, or facilitate access to the leads your agents call? Each of those words carries different exposure. Document accordingly.

Sources

Usanovic v. eXp Realty, 2026 WL 864633 (W.D. Wash. March 30, 2026); stay denial reporting from TCPAWorld (May 1, 2026); National Law Review coverage of direct-liability holding.

Operators, This Tennessee TCPA Ruling Is Your New Lead-Consent Playbook

A federal judge in the Eastern District of Tennessee just handed TCPA defendants a rare procedural win — and it should reframe how operators think about lead documentation. On May 11, 2026, U.S. District Judge Katherine A. Crytzer denied the plaintiff’s Rule 56(d) request in Brockington v. Hume Health, LLC, refusing to defer summary judgment so the plaintiff could fish for more discovery on her consent claim. The decision (2026 WL 1284850) is the kind of small, technical ruling that quietly changes the math on whether a TCPA class action is worth bringing in the first place.

What actually happened

Sheri Butler Brockington sued Hume Health alleging it called and texted her in violation of the TCPA and the National Do Not Call Registry rules. Hume Health moved for summary judgment, attaching its evidence of consent: a Facebook lead form Brockington had filled out, complete with the “SIGN UP” click that allegedly authorized the contact. Instead of opposing the motion on its merits, the plaintiff asked the court to delay summary judgment under Rule 56(d), claiming she needed more discovery to challenge the lead’s authenticity.

Judge Crytzer wasn’t having it. She held that Brockington failed to identify specific facts she expected to find or explain how additional discovery would actually defeat the consent defense. Bare assertions that “more discovery might reveal something” don’t clear the Rule 56(d) bar. The court will now decide the summary judgment motion on the existing record — a record that includes Hume Health’s lead documentation.

Why this matters for operators

For anyone running outbound calling or texting off paid lead sources, the practical lesson is brutal and useful: the quality of your consent record at the moment of capture determines whether a TCPA case lives or dies. Hume Health is in this position because it has a screenshot, a timestamp, an IP address, and a clean audit trail tying Brockington’s number to the form submission. That documentation is what flipped a class action from “discovery nightmare” to “summary judgment in 90 days.”

If your lead capture pipeline can’t produce that artifact on demand for any phone number on any list, you’re a Rule 56(d) request away from being on the wrong side of this ruling. Operators should be auditing three things this week: (1) whether their lead vendors retain raw form-submission data with full metadata, (2) whether that data is retrievable per-number on a one-day SLA, and (3) whether the disclosure language above the submit button actually clears Reyes v. Lincoln Automotive Financial Services and the broader “clear and conspicuous” standard.

The Rule 56(d) angle is the real signal

What’s notable about Brockington isn’t the consent fight itself — that’s still pending. It’s that the court refused to let a TCPA plaintiff use discovery as leverage to extract a settlement. Rule 56(d) fishing expeditions have been one of the most reliable tools in the professional plaintiff playbook: file a thin complaint, survive the motion to dismiss, demand discovery, and let the defense costs do the rest. A court willing to deny that move on a clear record changes the calculus for both sides.

Expect more defendants to push for early summary judgment on consent when they have the receipts. And expect plaintiffs’ counsel to scrutinize lead provenance harder before filing — because the cases where lead data is clean and dated are now the cases that end fastest.

What to do Monday morning

Three concrete actions for operators reading this: First, pull a random sample of 25 phone numbers off your most recent dialer list and try to produce the underlying consent artifact (form, source URL, timestamp, IP, disclosure text shown at submit). If you can’t, escalate to the lead vendor today. Second, get your lead-storage retention policy in writing — many vendors quietly delete raw submission data after 90 days, which is exactly when you need it most. Third, make sure your dialer’s “do not contact” logic is wired to the same source-of-truth that holds consent records, so a revocation request actually propagates.

One operational hedge worth building into your dialing stack: scrub every outbound list against known TCPA plaintiffs before you launch. TCPALitigatorList.com maintains a continuously updated database of numbers tied to professional plaintiffs and frequent TCPA filers, and a five-minute suppression pass against that file is a lot cheaper than a single class certification fight.

Sources

Brockington v. Hume Health, LLC, 2026 WL 1284850 (E.D. Tenn. May 11, 2026); coverage at National Law Review and LitNews.ai.

Operators, Breathe: A Federal Judge Just Gutted the Quiet-Hours Lawsuit Playbook

If you’ve been bracing for the next quiet-hours TCPA demand letter, a Delaware federal judge just handed outbound operators a real win. In King v. Bon Charge, decided April 30, 2026, the U.S. District Court for the District of Delaware held that a plaintiff who voluntarily gives a business their phone number can’t turn around and sue under the TCPA’s quiet-hours rule when that business texts them outside the 8 a.m.–9 p.m. window.

What the court actually said

The TCPA bars telephone solicitations before 8 a.m. or after 9 p.m. in the called party’s local time zone. For the last year, that single sentence has spawned a cottage industry of “gotcha” lawsuits where a consumer drops their number into a brand’s webform, signs up for SMS, and then waits to receive a single text at 9:02 p.m. local time before filing a putative class action.

The Delaware court called the bluff. Quoting from the opinion, the judge held that quiet-hours claims “cannot be brought by a consumer who has provided their number voluntarily to the caller.” The reasoning: a consumer who has invited contact has, by that act, supplied prior express invitation or permission to be contacted — which is exactly what the TCPA’s quiet-hours provision was designed to backstop in the first place.

Why this matters operationally

If you’re running a 50-state outbound program, you’ve likely been quietly throttling your send windows down to a conservative 9 a.m.–8 p.m. local-time band, just to avoid the edge cases. King v. Bon Charge doesn’t repeal the rule — you still need to honor quiet hours for cold contacts — but it does carve out the segment of your audience that opted in via your own funnel. That’s the bulk of most lifecycle, abandoned-cart, and re-engagement sends.

Three operator takeaways:

1. Capture consent receipts in your CDP. If you can prove the recipient submitted their number through your form, with a timestamp and the page they were on, you have the factual record this opinion turns on. Make sure your event log retains it — not just in your ESP, but in cold storage you can produce in discovery.

2. Re-examine your send-window policies. If your team has been holding back on time-sensitive flows (delivery confirmations, appointment reminders, two-factor codes) because of quiet-hours anxiety, the calculus has shifted for opted-in audiences. You don’t necessarily need to send at 10 p.m. just because you can — but you don’t have to artificially clip your operational sends either.

3. The list you bought is still radioactive. This ruling protects sends to numbers the consumer gave you. Lists from data vendors, lead aggregators, or “co-reg” partners are not covered. Quiet-hours risk on cold lists is unchanged, and frankly the bigger threat is that those lists also tend to contain professional litigators.

The split is forming

This is a district court ruling, not binding outside Delaware, and other courts have gone the other way on similar facts. Expect the plaintiffs’ bar to forum-shop into more permissive districts — the Northern District of California and the Southern District of Florida have both been favorable jurisdictions for quiet-hours suits in 2026. But Bon Charge gives defendants real precedent to cite at the motion-to-dismiss stage, and a few more rulings like this could shift the settlement-leverage math meaningfully.

If you’re running an outbound calling or texting program, screening your lists against known TCPA litigators before you dial is one of the cheapest forms of insurance you can buy. TCPALitigatorList.com maintains a continuously updated database of plaintiffs who have already filed TCPA suits — feed it into your dialer’s suppression layer and skip the numbers that have a documented history of turning a single text into a five-figure demand letter.

Bottom line for operators

Quiet-hours suits aren’t dead, but the easiest version — “I gave them my number and they texted me at 9:01 p.m.” — just got a lot harder to bring in at least one federal district. Keep your consent records clean, keep cold lists scrubbed, and keep watching the docket.

Sources: TCPAWorld coverage of King v. Bon Charge; National Law Review analysis.

FCC Buys Callers Another Year on the TCPA “Revoke-All” Rule

On January 6, 2026, the FCC’s Consumer and Governmental Affairs Bureau quietly bought the call-center industry another year of breathing room. The Bureau extended the effective date of the TCPA “revoke-all” requirement to January 31, 2027, citing the operational difficulties of designing a compliant system across complex enterprises.

What the “revoke-all” rule actually does

Under the rule as written, when a consumer revokes consent in response to one type of call or text — say, a payment reminder — the caller must treat that revocation as applying to every call and text on every other unrelated subject from the same business. A revocation on a billing text would silence promotional emails, reminder calls, and customer-service follow-ups.

Banks, insurers, hospitals, and pharmacy chains pushed back hard, arguing that their call platforms, CRMs, and consent databases simply do not share state cleanly enough to honor a single revocation across business units in real time.

Why the FCC pumped the brakes

The Bureau’s order points to “good cause” — implementation challenges raised by financial institutions and healthcare providers — and notes that the underlying Notice of Proposed Rulemaking from 2025 is still receiving comment. In short: the agency is reconsidering whether the “revoke-all” rule should be modified to give consumers more tailored control rather than an all-or-nothing global stop.

What still applies right now

The extension does not give callers a holiday from TCPA basics. Consumers can still revoke consent through any reasonable method, and callers must still honor those revocations promptly. Keyword-based opt-out mechanisms (STOP, QUIT, CANCEL) are still in force, and existing consent and scrubbing obligations are unchanged.

Before your sales or marketing team places its next outbound call or text, run the recipient list through TCPALitigatorList.com. It is the largest curated database of known TCPA litigators and serial-suers in the United States, and a single scrub against it can keep one mistaken contact from turning into a five- or six-figure demand letter. Most of the defendants in the cases above were dialing or texting numbers they could have flagged in seconds.

What to do with the extra runway

Use the year. Map every channel and every business unit that touches a consumer phone number. Inventory where consent is captured, where it is stored, and how revocations propagate. Most enterprises will discover the system is more fragmented than they thought — and the next 12 months are the cheapest time to fix it.

Fifth Circuit Just Rewrote the TCPA Playbook on Written Consent

In a decision that has compliance officers across the country tearing up their training decks, the U.S. Court of Appeals for the Fifth Circuit has rejected the FCC’s long-standing “prior express written consent” requirement for prerecorded telemarketing calls. The ruling, handed down in March 2026, reshapes one of the most settled-feeling corners of the Telephone Consumer Protection Act and sets up a fast-moving circuit split.

What the court actually held

For more than a decade, the FCC’s 2012 order required marketers placing prerecorded or autodialed calls to consumers to obtain a signed, written consent — typically through a checkbox or e-signature flow. The Fifth Circuit, applying the Supreme Court’s Loper Bright framework that scaled back agency deference, concluded that the statute itself never required written consent for prerecorded marketing calls and that the FCC exceeded its authority when it added that requirement by rule.

That does not mean consent has disappeared. The TCPA still requires “prior express consent” — but in the Fifth Circuit, oral consent and other reasonable methods may now suffice, where written consent was previously the only accepted form for marketing prerecorded calls.

Why it matters even if you are not in the Fifth Circuit

Three reasons. First, the ruling encourages defense counsel in other circuits to make the same argument, which means more motions, more conflicting decisions, and more uncertainty. Second, plaintiffs’ firms are already racing to file in friendlier circuits to lock in pre-Fifth-Circuit standards before other appeals courts weigh in. Third, the FCC is widely expected to respond — possibly by re-issuing the rule under different statutory hooks, possibly by tightening the substantive consent standard.

Action items for any business doing outbound

Do not abandon written consent. The patchwork is now genuinely circuit-by-circuit, and most plaintiffs’ lawyers will choose the venue that helps them. Your safest move is still a well-documented, opt-in workflow with timestamped records, IP capture, and the disclosure language laid out in the FCC’s existing rule. What changes is the legal theory of defense if you are sued: in some courts you now have a much stronger argument that less-than-written consent is sufficient.

Before your sales or marketing team places its next outbound call or text, run the recipient list through TCPALitigatorList.com. It is the largest curated database of known TCPA litigators and serial-suers in the United States, and a single scrub against it can keep one mistaken contact from turning into a five- or six-figure demand letter. Most of the defendants in the cases above were dialing or texting numbers they could have flagged in seconds.

Bottom line

The Fifth Circuit decision is the biggest TCPA development of 2026 so far, and the ground will keep moving. Watch the Eleventh and Ninth Circuits closely — both are sitting on similar challenges. Until they rule, treat your written-consent flows as load-bearing and assume any oral-consent argument will be tested in court.