What Prior Consent Actually Means (and Why the Definition Just Shifted)

Prior consent is no longer a static legal concept. It has become a moving target that shifts depending on where your call center operates.

The Telephone Consumer Protection Act (TCPA) requires specific permission before you dial a consumer. For years, the Federal Communications Commission (FCC) demanded written consent for automated marketing calls. That standard just cracked in the Fifth Circuit.

In Bradford v. Sovereign Pest Control, decided in February 2026, the court rejected the FCC’s written-consent rule. The judges held that the statute only requires "prior express consent." This can be oral or written. They relied on Black's Law Dictionary, which defines express consent as "positive, direct, unequivocal consent." The court noted that Congress permits either form for auto-dialed calls.

This ruling changes the rules for Texas, Louisiana, and Mississippi. In these states, oral consent now satisfies the legal requirement. You no longer need a signed form for every automated call.

However, this shift is strictly regional. Forty-seven other states still follow the FCC’s written-consent framework. If you operate nationally, you cannot relax your documentation standards. A consent record that works in Dallas may fail in New York.

Here is what prior consent actually looks like in practice:

• Prior Express Consent (PEC) applies to informational calls. Think appointment reminders or delivery alerts. Providing a number in a transaction often satisfies this.
• Prior Express Written Consent (PEWC) governs marketing calls. This requires a signed, standalone disclosure naming the business and phone number.
• AI voices trigger full consent obligations. The FCC classifies them as "artificial voices." There are no exemptions for AI-assisted agents.

The distinction matters because penalties are severe. A single violation can cost $500, rising to $1,500 for willful breaches. There is no cap on total damages. Class action filings increased by 95% in the first half of 2025.

Documentation is your only defense. Even in the Fifth Circuit, you must prove consent was "clear, direct and unequivocal." Oral consent needs careful documentation and independent verification. Call logs and recorded conversations help, but they are not automatic proof.

My AI Call Center treats this ambiguity as a reason for stricter standards, not looser ones. We review list sources and consent records before any campaign launches. If a list lacks clear permission records, we flag it. In most cases, we decline the list entirely. We do not gamble on ambiguous consent.

You need to know exactly what you are dialing. We report what actually happens. We verify that your contacts have approved the specific type of call you are making. This protects your brand from liability and ensures your outreach is compliant.

Run more useful calls without building a bigger call center. Start with a free campaign review to see if your lists meet the strictest consent standards.

The Two Consent Tiers: PEC for Reminders, PEWC for Marketing

Not every outbound call carries the same legal weight. The TCPA splits outbound calling into two consent tiers, and the difference between them can mean the difference between a compliant reminder campaign and a class-action exposure.

The lighter tier, Prior Express Consent (PEC), covers informational and transactional calls. Appointment reminders, delivery notifications, account alerts, fraud warnings, prescription pickups, and shipping updates all fall here. Voluntarily giving a phone number during a transaction-related interaction satisfies PEC for related follow-ups, but it does not extend to unrelated marketing later. The consent has to match the purpose.

The heavier tier, Prior Express Written Consent (PEWC), governs AI-driven marketing calls to wireless numbers and prerecorded calls to residential landlines. PEWC requires an affirmative signature (electronic signatures under the E-SIGN Act qualify) on a disclosure that meets four conditions:

• Names the specific business making the calls
• Identifies the phone number authorized
• States that consent is not a condition of purchase
• Stands alone, not bundled into a broader terms-of-service agreement

PEWC is the standard most campaigns must clear, and it is the standard courts examine most closely when a class action lands.

AI-generated voices complicate both tiers in a way that catches many callers off guard. The FCC's February 2024 declaratory ruling classifies AI voices as "artificial voices" under the TCPA, triggering the same consent mandates as traditional autodialed calls with no AI-specific exemptions. The agency stated plainly that the statute "does not allow for any carve out of technologies that purport to provide the equivalent of a live agent," according to a compliance playbook for voice AI outbound.

The Established Business Relationship (EBR) exemption is the next misconception worth flagging. EBR only loosens DNC Registry restrictions for manual live calls. It does not extend to AI-driven dialing. A live sales rep can call a 16-month-old customer whose number sits on the DNC list under EBR. An AI agent dialing the same person still needs separate, documented consent. The voice is what the law cares about, not the relationship history.

Penalties reinforce why the distinction matters. TCPA violations run $500 per call as a base, $1,500 for knowing or willful violations, with no aggregate cap, and the statute of limitations stretches four years. Class-action filings rose 95% year-over-year in the first half of 2025, with over 80% of TCPA cases proceeding as class actions, per SecurePrivacy's 2025 TCPA compliance guide. A campaign that blurs the line between PEC and PEWC, or assumes EBR covers AI dialing, can scale into seven-figure exposure fast.

For organizations running outbound campaigns, the practical rule is simple: confirm the call's purpose first, match the consent tier to that purpose, and document the consent record before launch. Informational reminders can rely on PEC when the content stays informational. Anything that encourages a purchase, rental, or investment, including an account check-in that pivots to an upsell, requires PEWC.

That's the framework My AI Call Center applies during its list-and-consent review: list source and consent records are checked before any campaign launches, and bought lists without clear permission records are flagged, and in most cases declined. The team tells clients plainly if a list will not support the campaign before any spend happens.

What Consent Costs You When It's Missing

Missing prior consent turns a single outbound call into a balance-sheet event. The TCPA's statutory damages start at $500 per violation and triple to $1,500 for knowing or willful infractions, with no aggregate cap on total exposure (SecurePrivacy's TCPA compliance guide). A campaign that dials a few thousand numbers without verified permission can therefore generate six- or seven-figure liability before a single settlement dollar is paid.

The time horizon makes that risk worse. A four-year statute of limitations means a single bad campaign keeps accruing exposure long after the dialer is shut off (SecurePrivacy's TCPA compliance guide). And plaintiffs' lawyers have noticed: 1,052 TCPA class actions were filed in the first half of 2025 alone, a 95% jump year-over-year, with more than 80% of TCPA filings proceeding as class actions (SecurePrivacy's TCPA compliance guide).

Recent settlements show what those class actions cost when they land. Voice-AI and outbound-calling defendants have resolved matters in the $5M–$20M range over the past two years, including a $9.95M Gen Digital settlement in January 2026 and a $19M QuoteWizard resolution (Retell AI's TCPA compliance playbook). One outlier jury verdict, $925 million for 1.8 million ATDS violations, is a reminder of what happens when a case goes to trial instead of settling (SecurePrivacy's TCPA compliance guide).

The liability map also matters for who pays. The entity on whose behalf the calls are made bears responsibility, regardless of which downstream vendor or lead generator pressed dial. A proposed class in Lamb v. Mortgage One Funding (February 2026) covers calls made "or from any of the company's vendors, lead generators, or agents," so outsourcing the dialing does not outsource the risk (Retell AI's TCPA compliance playbook).

A few practical points that fall out of that liability picture:

• Statutory damages stack per call, so volume without verified consent compounds exposure fast.
• The four-year limitations window means a 2026 violation is still actionable in 2030.
• Class certification is the norm, not the exception, in TCPA litigation.
• Vendor relationships do not insulate the brand that benefits from the calls.
• Settlement ranges in the millions are now routine for AI-voice and outbound campaigns.

That is why consent verification has to happen before launch, not after a demand letter arrives. At My AI Call Center, every campaign starts with a list-and-consent review: source, permission records, and calling windows are checked, and bought lists without clear permission records are flagged and, in most cases, declined. The first campaign review is free, and the team tells you plainly if the list will not support the campaign before you spend anything.

Plan your next campaign with a list-and-consent review before dialing begins.

How to Verify Consent Before Any Campaign Launches

Consent you can't prove is consent you don't have. Even after the Fifth Circuit's February 2026 ruling in Bradford v. Sovereign Pest Control opened the door to oral consent, the court still required callers to show "clear, direct and unequivocal" consent that is "carefully documented and independently verifiable." If your records can't back up a claim of permission, a plaintiff's attorney will treat it as no permission at all.

That's why verification, not collection, is the real work. Here's the process we'd walk any campaign through before a single dial.

Document consent so it stands on its own. The form of consent matters less than the proof behind it. Oral or implied consent now carries a viable defense in Texas, Louisiana, and Mississippi, but legal analysis of the ruling stresses that relying on it demands robust record-keeping: call logs, recorded conversations, and contractual provisions that show exactly what the person agreed to. Written consent should be stored for at least five years, and many defense counsel recommend seven. Whatever the form, capture the timestamp, the disclosure shown, and the specific number authorized.

Default to the stricter standard nationally. The Fifth Circuit's oral-consent holding applies only in three states. The other 47 still apply the FCC's written-consent rule, and state telemarketing statutes may add their own requirements. For marketing calls, that means building to the prior express written consent standard everywhere: a signed, standalone disclosure naming your business, identifying the phone number, and stating that consent is not a condition of purchase. Electronic signatures qualify under the E-SIGN Act. Building to the stricter bar once is simpler than tracking which standard applies in which jurisdiction.

Re-consent the gray areas. Co-registration consents that name "and our partners" face skepticism in court, and "warm cold list" has no legal meaning at all. The practical answer is to re-consent every co-reg lead before dialing. The same logic applies to purchased lists generally: if you can't trace the permission record back to a specific disclosure, the list can't support the campaign. This is a line we hold at My AI Call Center. Bought lists without clear permission records get flagged, and in most cases declined, before you spend anything.

• Screen for reassigned numbers. Many TCPA violations happen when a number has been reassigned to a new consumer who never consented. The FCC-authorized Reassigned Numbers Database exists for this, and the safe harbor requires querying before every call.
• Honor revocations fast, on every channel. Since April 2025, consumers can revoke by any reasonable method, including text, email, voicemail, or a verbal request, and opt-outs must be honored within 10 business days, down from 30.
• Carry opt-outs across campaigns. A STOP or REVOKE in one campaign should suppress that number everywhere, including in your client DNC records.

One more trap worth naming: established business relationships don't exempt AI calls. The FCC's February 2024 ruling treats AI-generated voices as artificial voices requiring full prior express consent, so your live agent's EBR exemption does not transfer to an AI campaign. With penalties running $500 to $1,500 per call and no aggregate cap, verification before launch is the cheapest compliance you'll ever buy.

Running AI Calling Campaigns on Consent You Can Prove

Knowing what prior consent means is one thing. Proving it for every number on your list is where campaigns actually get safe.

That's why consent verification belongs at the start of a campaign, not the end of a dispute. Before any calls go out, the list source and consent records should be reviewed, because the legal standard isn't just "they said yes." Courts require consent that is clear, direct and unequivocal, and oral consent must be carefully documented and independently verifiable to hold up, per Holland & Knight's analysis of the Fifth Circuit's Bradford ruling.

Bought lists deserve special scrutiny. Co-registration consents naming "and our partners" face skepticism in court, and "warm cold list" has no legal meaning at all, so compliance guidance recommends re-consenting those leads before any AI dialing. My AI Call Center's practice reflects this: bought lists without clear permission records get flagged, and in most cases declined, before a campaign ever launches. The stakes justify the discipline. TCPA violations run $500 to $1,500 per call with no cap on total damages, and TCPA class actions jumped 95% year-over-year, with 1,052 filings in the first half of 2025 alone.

A consent-verified campaign workflow should cover four things:

• Pre-launch list and consent review, confirm where each number came from and what permission exists, before spending anything.
• AI disclosure on every call, recipients can ask whether the call is AI-assisted, request a human, or opt out on the spot.
• Immediate opt-out handling, STOP and REVOKE keyword requests are logged and honored the moment they happen.
• Cross-campaign DNC carryover, a do-not-call request from one campaign is respected in every future campaign and carried into your DNC records.

The timing rules matter too. Since April 2025, consumers can revoke consent by "any reasonable method," including text, email, voicemail, or verbally, and opt-out requests must be honored within 10 business days. Waiting weeks to scrub a list is no longer defensible.

One more caution: an established business relationship won't save an AI campaign. EBR only exempts manual dials from DNC Registry rules. As one voice AI compliance analysis puts it, your live rep can call a 16-month-old customer on the DNC list, but your AI agent cannot dial the same person without separate consent. The voice is what the law cares about.

Consent you can prove, disclosed on every call, with opt-outs honored instantly. That's the difference between a campaign that scales and one that ends up in a class action.