7 Recent TCPA Cases in 2026 That Could Affect Business Calls and Texts 

Calls and texts still help businesses generate leads, follow up with prospects, and close sales. They also still create legal risk.

What changed is how that risk is showing up in court.

Recent TCPA cases are forcing businesses to take a harder look at consent, text campaigns, vendor oversight, ringless voicemail, wrong-number outreach, and opt-out handling.

At the same time, the FCC is still moving businesses toward broader and faster handling of revocations, even though one part of that framework has been delayed until January 31, 2027.

That makes this a bad time to rely on old TCPA assumptions.

Many outbound teams do not get into TCPA trouble because they never heard of the law. The issue is usually operational. Consent records, lead source details, opt-out requests, and phone data often live in different systems. When that happens, it becomes harder to prove what happened, when it happened, and whether the outreach should have happened at all.

Recent TCPA cases do not mean all calls and texts are unsafe. They show where businesses keep running into the same problems: weak consent proof, stale phone data, poor suppression handling, outsourced outreach, and tools treated like shortcuts instead of regulated workflows.

This is what those cases mean for businesses using calls and texts right now.

Why recent TCPA cases matter more than older advice

A lot of TCPA guidance still circulating online was written for a different legal environment. That matters because some courts are no longer willing to automatically follow older agency interpretations when the statute itself says something narrower. In the TCPA space, that change is showing up most clearly in consent cases.

For businesses, that creates a messy reality. One court may narrow part of the rule. Another may not. A legal headline may sound business-friendly, but the operational risk may still be high.

That is why older checklists are not enough on their own. Businesses need to look at how courts are reading the law now, and then compare that to how their own call and text workflows actually work.The companies that end up in lawsuits are not always the most aggressive. Sometimes, they are simply the ones with the weakest records.

Recent trend #1: Written consent is getting challenged in court 

One of the biggest TCPA developments this year came from the Fifth Circuit.

In Bradford v. Sovereign Pest Control of TX, Inc., decided on February 25, 2026, the Fifth Circuit held that the TCPA itself requires prior express consent, not prior express written consent, for the calls at issue. The ruling focused on the text of the statute and rejected the idea that the TCPA itself imposed a written-consent requirement there. Legal analysis of the case has described it as a major shift away from years of reliance on FCC interpretations in this area.

That issue did not stop there.

In Bradley v. DentalPlans.com, a Maryland federal court followed the same direction in March 2026 and held that oral consent was enough under the TCPA in that case. Commentary on the ruling described it as another example of a court rejecting the FCC’s written-consent approach when the statute itself did not clearly require it.

Businesses should be careful with this trend. These rulings do not mean sloppy consent is now safe. They also do not create a nationwide rule. The practical takeaway is narrower. Some courts are moving toward a narrower reading of the TCPA, but that makes clean documentation even more important.If your team collects consent through forms, vendors, inbound calls, transfers, or lead funnels, this is the time to make sure you can prove what the customer agreed to, when it happened, and which number it covered.

Recent trend #2: Text messages are still a moving target  

Many businesses assume text campaigns are safer than calls as long as they include opt-out language. That is too simplistic.

Courts are still split on how text messages fit into some TCPA theories, especially around Do-Not-Call claims. Legal commentary in 2026 continues to describe the area as unsettled, not resolved.

That matters because a business may treat SMS like a lighter-touch channel when courts may still treat it as a regulated one. A texting workflow built on the narrowest possible reading of the law is not much of a safety strategy.The better approach is to treat text outreach with the same discipline you would expect for call campaigns. Store consent clearly. Capture opt-outs reliably. Sync suppression across systems. Review old numbers before reuse. A text may feel more casual to the sender, but courts do not treat it as casual when a dispute starts.

Recent trend #3: Using a vendor does not erase your risk  

Many businesses do not place every call or send every text themselves. They use lead generators, affiliates, agencies, or outside outreach vendors.

That setup can still create exposure for the business.

In Katz v. Allied First Bank, the court granted summary judgment for the bank on direct liability, but denied the motion in other respects, which meant the bank was not fully out of the case. That kind of outcome matters because it shows a company can still spend time and money fighting TCPA claims even when it argues that third parties made the calls.

That is the real lesson here. “We did not make the calls ourselves” is not a full compliance plan. It is just one defense argument.If your brand benefits from the campaign, if your product is being marketed, or if your leads come through a chain you do not fully control, the question becomes whether you can show valid consent and real oversight. Vendor contracts matter. So does actual monitoring. A clause in an agreement will not help much if the records behind the outreach are weak.

Recent trend #4: Ringless voicemail is still risky  

Ringless voicemail keeps getting pitched as an easier or softer way to reach leads. The legal risk is still real.

In Garvey v. Brittney Gaitan, a Nevada federal court certified a TCPA class action in March 2026 involving ringless voicemail messages sent to expired listings. Reporting on the case says the court treated the prerecorded outreach seriously and did not require recipients to actually listen to the message for the claim to matter.

That should get the attention of any business using prerecorded outreach tools, voicemail drop platforms, or similar systems. A channel that feels one step removed from a live call does not automatically avoid TCPA exposure.This is especially relevant in real estate, lead generation, and outbound sales environments where teams are constantly pitched new ways to revive older leads. A newer format does not cancel the need for valid consent.

Recent trend #5: Wrong numbers and reassigned numbers remain a major risk  

One of the clearest business warnings from recent TCPA litigation is the continued danger of bad phone data.

In Saggio v. Medicredit, a federal court in Missouri certified a TCPA class action in January 2026 involving around 300,000 calls that the company’s own records indicated might have gone to wrong numbers. That detail is what made the case stand out. The alleged warning signs were not hidden. They were reportedly already in the records.

That matters to any business working from older contact lists, recycled leads, aged customer records, or numbers collected months or years ago. A number that once belonged to the right person may not belong to that person now. Once ownership changes, old consent becomes harder to rely on.

This is also where small workflow failures become expensive. One rep marks a number wrong. Another system keeps texting it. A list gets reused without checking freshness. A campaign launches from a file that looked fine but had not been reviewed in months.Wrong-number issues are not just data cleanup problems. Courts keep treating them like evidence.

Recent trend #6: Some technical TCPA claims still fail when the facts are weak 

Not every new TCPA case ends badly for the business.

In Robertson v. TrueAccord, a Texas federal court dismissed TCPA ATDS claims in February 2026. Commentary on the ruling said the allegations did not plausibly show use of an automatic telephone dialing system, and the nature of the messages mattered to the court’s analysis.

That is useful because it shows courts are still paying attention to actual facts and message flows, not just assuming every text states a valid TCPA claim.Still, that is not a reason to relax. A strong dismissal usually depends on strong facts, good records, and a campaign setup that does not fit the legal theory being alleged. A weak workflow should not expect a technical escape later.

Recent trend #7: Revocation and opt-out handling still need work  

There is also a timing issue businesses should not ignore.

The FCC’s 2024 revocation framework made clear that consumers can revoke consent in any reasonable way and that callers must honor that request within a reasonable time, not to exceed 10 business days.

Then, in January 2026, the FCC extended the waiver for part of the broader “revoke all” framework until January 31, 2027. The delay changed timing, not direction. Businesses are still expected to handle opt-outs faster and more consistently.

That means suppression handling cannot stay siloed. A stop request captured in one system but missed in another is still a problem. Teams using multiple platforms, multiple vendors, or separate call and SMS tools should pay attention here.The operational lesson is clear. Opt-out handling should be treated like a core compliance workflow, not a side setting buried in a platform dashboard.

What these cases have in common 

The case names are different. The business lesson is not.

Recent TCPA cases keep circling back to the same operational failures: unclear proof of consent, weak list hygiene, third-party outreach tied back to the brand, outdated assumptions about texts, and poor handling of opt-outs or wrong-number warnings.

That is why businesses should be careful about reacting only to legal headlines.A headline may say written consent is under pressure in court. Another may say a technical TCPA claim was dismissed. Those updates matter. But the real exposure still shows up when a business cannot show a clean process behind the outreach.

What businesses using calls and texts should do now

Businesses using calls and texts should review four areas:

• Consent records: Tie consent to the exact person, phone number, date, source, and campaign. If proof sits in screenshots, email threads, or scattered vendor portals, it may be weaker than your team thinks.
• Lead and vendor chain: Know who is placing calls, who is sending texts, which systems they use, and how opt-outs or suppression updates are shared back.
• Phone data quality: Review line status, line type, and number freshness before launch. Watch for wrong-number notes, aged lists, and numbers tied to older consent.
• Opt-out workflow: Make sure revocation requests move across systems, vendors, call platforms, and SMS tools. Do not rely on one keyword, one platform, or one rep to catch everything.

Note: This article is for general information only and is not legal advice. Businesses should consult legal counsel when reviewing TCPA compliance policies.

How Searchbug Supports TCPA Compliance for Calls and Texts  

This is where support tools make sense.

• Phone Validator with DNC Check API can help teams review phone records before outreach starts. That can help with line type, phone status, and DNC-related screening points that make a number riskier to call or text.
• Reassigned Numbers Database API checks can help address one of the biggest takeaways from recent wrong-number cases. A number that once belonged to the right person may not belong to them now.
• Bulk Phone Validation can help teams working from spreadsheets or larger lists review records before launch instead of checking numbers one at a time.

These tools do not replace legal advice or internal policy. They support a cleaner workflow. And that matters because many TCPA problems start before the first call or text ever goes out.

TL;DR  

Recent TCPA cases are a warning for businesses using calls and texts.

Some courts are narrowing how they read written consent. Text-message treatment is still unsettled in some TCPA contexts. Vendor and contractor activity can still create exposure.

Ringless voicemail is still risky. Wrong-number and reassigned-number issues are still dangerous. The FCC is still pushing businesses toward faster and broader handling of revocations and opt-outs.

The practical answer is not panic.

It is process.

Tighten consent records. Review vendors. Clean the phone data. Treat texts like a regulated channel. Make sure opt-outs move across your systems. That is what recent TCPA cases mean in real business terms.

Recent TCPA cases show how weak phone data and weak process can create real risk.  

Register for a FREE Searchbug API Test Account and get $10 in free credits to test tools that help review phone records, screen for DNC-related risk, and check reassigned numbers before your next call or text campaign starts.Not using an API? Bulk Data Processing can help you clean and review larger outreach lists before launch.