TCPA Exceptions Explained: What Contact Centers Need to Know

Written by: Matt Beucler, CEO, Plura AI

Key Takeaways

TCPA exceptions are narrow, category-specific exemptions from consent requirements for robocalls and robotexts. Categories include emergency purposes, informational and transactional calls, certain healthcare messages, nonprofit and political calls, manual dialing, and government debt collection.
Each exception has strict conditions and does not automatically exempt callers from Do-Not-Call requirements. The distinction between DNC and robocall frameworks is critical for avoiding violations.
Recent regulatory changes, including the vacated one-to-one consent rule, the Bradford decision, and expanding state mini-TCPA laws, have increased compliance complexity for high-volume communicators.
Practical compliance at scale depends on real-time DNC scrubbing, consent logging, and automated enforcement of quiet-hours and frequency limits across every outbound contact.
Plura AI builds TCPA compliance support into its platform, helping teams scale outreach while maintaining zero violations.

Why TCPA Exceptions Matter in 2026

The Telephone Consumer Protection Act (47 U.S.C. § 227) restricts autodialed and prerecorded calls and texts to wireless numbers and residential lines without prior consent.² Violations carry statutory damages of $500 to $1,500 per call or text, with no cap on aggregate liability. A single non-compliant campaign to 100,000 numbers can generate $150 million in exposure.³

The stakes have risen in recent years. Between January and November 2025 alone, 2,588 TCPA lawsuits were filed in the U.S.³ That wave of litigation coincided with major regulatory shifts. The FCC’s one-to-one consent rule was vacated by the Eleventh Circuit in January 2025 and formally eliminated in September 2025. The Fifth Circuit’s February 2026 Bradford decision created new uncertainty around written-consent requirements. At the same time, state mini-TCPA laws in Texas, Oregon, Florida, and others expanded restrictions beyond the federal floor.

This guide explains each TCPA exception, its conditions, and the distinction between DNC exceptions and robocall consent exceptions. That distinction confuses even experienced operators. Nothing here constitutes legal advice. Consult qualified counsel for guidance specific to your situation.

Book a live demo with Plura AI to see how compliance infrastructure works in practice.

How TCPA Exceptions Work

TCPA exceptions are specific categories of calls and texts that the statute or FCC regulations exempt from the general consent requirements. They fall into two distinct frameworks that teams often conflate.

Robocall consent exceptions: Exemptions from the requirement to obtain prior express consent (or prior express written consent) before placing autodialed or prerecorded calls and texts under 47 U.S.C. § 227(b).
Do-Not-Call (DNC) exceptions: Exemptions from the prohibition on telemarketing calls to numbers on the National DNC Registry under 47 U.S.C. § 227(c).

A call can be exempt from one framework but not the other. A call may fall outside the DNC rules via an established business relationship but still require prior express written consent under the robocall rules if it uses an autodialer to reach a cell phone. Teams first identify which framework applies, then determine whether an exception covers a specific communication.

Emergency Purposes Exception

Calls made for genuine emergency purposes are exempt from TCPA consent requirements. The FCC defines “emergency purposes” at 47 C.F.R. § 64.1200(f)(4) as calls “made necessary in any situation affecting the health and safety of consumers.”

Examples the FCC has recognized include:

Severe weather alerts
Public safety warnings
Health and safety emergencies requiring immediate action

The FCC interprets this exception strictly. The exception does not cover marketing messages that reference an emergency and does not extend to non-urgent communications. When in doubt, teams often assume the emergency exception does not apply and seek consent instead.

Informational and Transactional Calls

Informational and transactional calls, including appointment reminders, package delivery notifications, service outage alerts, and fraud warnings, are exempt from the prior express written consent requirement for robocalls when they contain no advertising or telemarketing content.

The scope of this exception varies by destination.

To cell phones: Non-marketing informational calls made with an autodialer or prerecorded voice require prior express consent, which the FCC has said can be satisfied when a consumer voluntarily provides their number in a context reasonably related to the call. Written consent is not required for purely informational calls.
To residential landlines: The TCPA does not restrict non-advertising prerecorded or autodialed calls to landlines, but prerecorded advertising calls to residential landlines are generally prohibited without prior express written consent.
DNC rules still apply: Informational calls are not “telephone solicitations,” so they fall outside National DNC Registry restrictions. Adding any marketing content converts the message into a solicitation and triggers both DNC and written-consent requirements.

The FCC’s 2012 Order eliminated the established business relationship (EBR) exemption for prerecorded telemarketing calls to cell phones. A purchase within the prior 18 months no longer permits calls without fresh consent.

Healthcare Messages Under HIPAA

The FCC created a specific exemption for certain healthcare messages sent by or on behalf of HIPAA-covered entities or their business associates.² Under 47 C.F.R. § 64.1200(a)(9)(iv), this exemption applies to autodialed or prerecorded calls to wireless numbers provided by the patient. Covered messages include several common clinical touchpoints.

Appointment and exam confirmations and reminders
Wellness checkups
Hospital pre-registration instructions
Pre-operative instructions
Lab results
Post-discharge follow-up to prevent readmission
Prescription notifications
Home healthcare instructions

Strict conditions apply under 47 C.F.R. § 64.1200(a)(9)(iv)(D)-(H).

No telemarketing, solicitation, or advertising content
No billing, debt-collection, or financial content
Maximum one message per day per patient and three per week combined
Voice calls one minute or less and texts 160 characters or less
Must include an easy opt-out mechanism, such as a “STOP” reply for texts
Must comply with HIPAA privacy rules

The FCC never extended the healthcare exemption to SMS text messages. Appointment reminder texts to cell phones require at least prior express consent, and any marketing language pushes them to prior express written consent.

Nonprofit and Political Calls

Tax-exempt nonprofit organizations and political campaigns have partial exemptions from TCPA rules, but the scope is narrower than many teams assume.

DNC rules: Calls from tax-exempt nonprofits and political organizations are exempt from National DNC Registry restrictions because they are not “telephone solicitations” under 47 U.S.C. § 227(a)(4).
Robocall rules: For autodialed messages to mobile phones, callers must have prior consent, and all prerecorded calls must identify the caller.

A nonprofit or political campaign can call a DNC-registered number, yet it cannot autodial a cell phone without consent.

Manual Dialing Exception

The TCPA’s autodialer restrictions apply only to calls made using an automatic telephone dialing system (ATDS). Following the Supreme Court’s 2021 decision in Facebook v. Duguid, 592 U.S. 395, a device qualifies as an ATDS only if it can generate or store phone numbers using a random or sequential number generator.

Calls placed entirely by human effort, with no autodialer and no automated system, fall outside the ATDS restrictions.

Prerecorded voice calls are separately regulated under 47 U.S.C. § 227(b)(1)(B), regardless of whether an autodialer is used.
DNC rules still apply to manually dialed telemarketing calls.
State mini-TCPA laws, such as Florida’s Telephone Solicitation Act, define “automated systems” more broadly and may capture technology the federal definition misses.

How DNC and Robocall Exceptions Interact

This distinction is the most common source of compliance errors in high-volume calling programs.

The DNC framework (47 U.S.C. § 227(c)) restricts telemarketing calls to numbers on the National DNC Registry. Exceptions include prior express written consent, established business relationship (18 months after purchase and 3 months after inquiry), calls from tax-exempt nonprofits, political calls, survey calls with no sales component, and most B2B calls to business-only lines.

The robocall framework (47 U.S.C. § 227(b)) restricts autodialed or prerecorded calls to cell phones and residential lines. Exceptions include emergency purposes, prior express consent for informational calls, prior express written consent for telemarketing calls, certain healthcare messages, and calls to collect U.S. government-backed debt.

A call can violate one framework while being exempt from the other. A telemarketing call to a DNC-registered number with an EBR may be DNC-exempt. However, if it uses an autodialer to reach a cell phone without prior express written consent, it implicates the robocall rules. An informational call with prior express consent may satisfy robocall rules but can become a “telephone solicitation” if it nudges toward a purchase, which triggers DNC obligations.

Book a live demo with Plura AI to see how real-time DNC scrubbing and consent logging work across every outbound contact.

Recent Regulatory Changes and Operational Impact

2023 FCC Declaratory Ruling (Called Party Standard): The FCC confirmed that consent is tied to the current subscriber or called party, not the person who previously held the number. Consent does not travel with a reassigned number. The Reassigned Numbers Database (RND) provides a safe harbor for callers who query it properly, and approximately 35 million U.S. phone numbers are reassigned every year.³

Plura Security & Compliance dashboard highlighting SOC 2, ISO, and GDPR standards with secure trust verification management. — *Plura Security & Compliance supports SOC 2, ISO, and GDPR standards with trust registration, verification management, and secure AI communications.*

One-to-One Consent Rule (Adopted 2023, Vacated 2025): The FCC’s one-to-one consent rule was vacated by the Eleventh Circuit in January 2025 and formally eliminated in September 2025. Multi-seller consent is again permissible at the federal level. States like Florida and Oklahoma have written one-to-one-style requirements into their own statutes. National campaigns now navigate a patchwork of state-level consent rules.

Fifth Circuit’s Bradford Decision (February 2026): In Bradford v. Sovereign Pest Control of TX, Inc., the Fifth Circuit held that the TCPA does not require prior express written consent for automated or prerecorded telemarketing calls to cell phones within its jurisdiction (Texas, Louisiana, and Mississippi), finding that oral or written prior express consent suffices under 47 U.S.C. § 227(b)(1). This creates a circuit split. For nationwide programs, many operators treat prior express written consent as the operational standard.

Revocation Rules (Delayed to 2027): In January 2026, the FCC issued an order further delaying the “revoke-all” requirement to January 31, 2027. Current rules under 47 C.F.R. § 64.1200(a)(10) require honoring opt-out requests within 10 business days.

AI-Generated Voice (February 2024 Declaratory Ruling): FCC Declaratory Ruling FCC-24-17 confirmed that AI-generated voices fall within the TCPA’s “artificial or prerecorded voice” restrictions. Outbound AI voice calls require the same consent as traditional robocalls.

Practical Decision Framework for Evaluating Exceptions

Given the complexity of the exceptions and recent regulatory shifts, a practical checklist helps teams apply these rules consistently. Use this framework to assess whether a specific call or text may qualify for a TCPA exception. This framework is a starting point, not legal advice. Consult qualified counsel for your specific situation.

Step 1: Is the communication an emergency?

If yes: Consent requirements may not apply. Verify the FCC’s narrow definition.
If no: Continue to Step 2.

Step 2: Does the communication use an autodialer or prerecorded/artificial voice?

If no (fully manual, live agent): ATDS rules do not apply. Check DNC rules separately.
If yes: Continue to Step 3.

Step 3: Is the communication telemarketing or advertising?

If no (informational or transactional): Prior express consent may be sufficient for cell phones. DNC rules generally do not apply.
If yes: Prior express written consent is the standard. DNC rules apply.

Step 4: Does a specific exemption apply?

Healthcare (HIPAA-covered entity, permitted purpose, all strict conditions met)?
Tax-exempt nonprofit or political organization?
U.S. government-backed debt collection?
If yes: Verify every condition is satisfied before proceeding.
If no: Full consent requirements apply.

Step 5: Have you verified the number?

Scrub against the National DNC Registry within 31 days of calling.
Query the Reassigned Numbers Database (RND) for wireless numbers.
Check your internal DNC list.

Real-world examples:

Appointment reminder (healthcare): Informational; prior express consent may be sufficient if no marketing content is present. The HIPAA exemption may apply if all conditions under 47 C.F.R. § 64.1200(a)(9)(iv) are met.
Debt collection: Not a “telephone solicitation” for DNC purposes, but autodialed calls to cell phones require prior express consent. FDCPA rules also apply.
Political outreach: DNC-exempt, but autodialed calls to cell phones require prior consent.
Abandoned cart text with promo code: Telemarketing; prior express written consent and DNC scrubbing are the applicable standards.

Quick-Reference Summary Table

Exception	Scope	Key Conditions
Emergency Purposes	Calls/texts for health and safety emergencies	Narrow FCC interpretation; no marketing content
Informational/Transactional	Non-marketing calls/texts (appointment reminders, alerts)	No advertising; prior express consent for cell phones
Healthcare (HIPAA)	Specific treatment-related messages from covered entities	No marketing/billing; 1/day, 3/week max; opt-out required; does not cover SMS to cell phones
Nonprofit/Political	Calls from tax-exempt nonprofits and political campaigns	DNC-exempt; consent still required for autodialed cell calls
Manual Dialing	Calls placed without an autodialer	No ATDS; DNC rules still apply; prerecorded voice separately regulated
U.S. Government Debt	Calls to collect federal government-backed debt	Statutory exception under 47 U.S.C. § 227(b)

Frequently Asked Questions

These answers address common questions leaders raise about TCPA exceptions and day-to-day compliance.

What does the TCPA not cover?

The TCPA does not restrict manually dialed calls from live agents where no autodialer or prerecorded voice is used. Most B2B calls to lines used exclusively for business purposes fall outside the National DNC Registry’s scope. Non-advertising prerecorded or autodialed calls to residential landlines are generally not restricted under the robocall framework, though prerecorded advertising calls to landlines require prior express written consent. The TCPA also does not cover over-the-top messaging services such as iMessage or WhatsApp. State mini-TCPA laws may reach further than the federal statute in some jurisdictions, and operators with a national footprint should review applicable state rules.

What are the key TCPA developments for 2026?

Several significant changes have shaped the 2025-2026 landscape. The FCC’s one-to-one consent rule was vacated by the Eleventh Circuit in January 2025 and formally eliminated in September 2025, making multi-seller consent permissible again at the federal level. The Fifth Circuit’s February 2026 decision in Bradford v. Sovereign Pest Control held that written consent is not required for telemarketing robocalls within that circuit’s jurisdiction, creating a circuit split with other federal courts. The FCC’s “revoke-all” requirement was further delayed to January 31, 2027. New state laws in Texas (effective September 2025) and Oregon (effective January 2026) expanded restrictions on text message solicitations. FCC Declaratory Ruling FCC-24-17 (February 2024) confirmed that AI-generated voices fall under the TCPA’s artificial or prerecorded voice restrictions.

Are appointment reminders exempt from the TCPA?

Pure appointment reminders with no marketing content are informational calls. For cell phones, prior express consent is the applicable standard, not prior express written consent. Healthcare providers may qualify for the FCC’s HIPAA exemption under 47 C.F.R. § 64.1200(a)(9)(iv) if all conditions are satisfied, including frequency limits, no marketing content, and an opt-out mechanism. The HIPAA exemption does not cover text messages to cell phones. Adding any promotional language to an appointment reminder, such as a reference to a new service or special offer, converts the message into telemarketing and triggers stricter consent and DNC requirements. Consult qualified counsel to assess whether a specific message qualifies as informational.

What are the healthcare message exceptions under the TCPA?

The FCC’s healthcare exemption at 47 C.F.R. § 64.1200(a)(9)(iv) covers specific treatment-related messages from HIPAA-covered entities and their business associates, including appointment reminders, lab results, prescription notifications, and post-discharge follow-up. Strict conditions apply: no marketing or billing content, a maximum of one message per day and three per week per patient, voice calls of one minute or less, texts of 160 characters or less, and an opt-out mechanism on every message. The exemption applies to calls to wireless numbers provided by the patient. It does not extend to SMS text messages to cell phones, and it does not cover any message with a marketing or financial component. Operators should consult the full regulatory text and qualified counsel before relying on this exemption.

What are the TCPA exceptions for text messages?

The FCC classifies text messages as “calls” under the TCPA, so the same general framework applies. Emergency purposes, informational content with prior express consent, and manual sending without an autodialer are the primary categories that may reduce consent requirements. The HIPAA healthcare exemption does not cover SMS to cell phones. Marketing texts require prior express written consent and DNC scrubbing. As of April 2025, the National DNC Registry’s restrictions, previously applied primarily to voice calls, now cover text messages as well. State laws in Texas, Oregon, Florida, and others impose additional restrictions on text solicitations beyond the federal floor.

Compliance at Scale Requires Infrastructure

TCPA exceptions are narrow, condition-heavy, and evolving. The 2023-2026 regulatory landscape, including the vacated one-to-one rule, the Bradford decision, delayed revocation requirements, and expanding state mini-TCPA laws, has made compliance more complex. For high-volume communicators, understanding the exceptions is only half the battle; the infrastructure must enforce them on every call and text.

Plura AI is an FCC-licensed carrier that builds TCPA compliance support into the platform as a first-class layer. Every outbound contact is checked against federal and state DNC registries in real time before dial, and consent records are timestamped and immutable for audit readiness. Quiet-hours rules enforce automatically through time-zone detection, so teams do not have to manage them manually. The platform’s track record: DNC and TCPA compliant, 0 violations.³

Screenshot of Plura’s fully compliant AI communications platform showing business registration and phone number provisioning workflows for AI Voice, SMS, RCS, and Webchat communication automation. — *Plura’s FCC-licensed AI communications platform simplifies compliant business registration and phone number provisioning for AI Voice, SMS, RCS, and Webchat workflows.*

Plura’s AI Predictive Dialer, AI SMS, and AI voice agent all run on the same compliance engine. Teams can scale outreach without scaling risk. Customers are responsible for their own compliance obligations; Plura provides the infrastructure to support those obligations at scale.

Compare plans and rates side by side.

Run your numbers through Plura’s ROI calculator to check your cost savings in real time.

Book a live demo with Plura to see the compliance engine in action.

¹ Plura AI maintains SOC 2, HIPAA, ISO, and GDPR posture as part of its platform infrastructure. References to compliance frameworks in this article describe Plura’s platform capabilities and do not constitute a guarantee that any customer using Plura will themselves be compliant with applicable laws or standards. Customers remain solely responsible for their own regulatory obligations, certifications, consent management, recordkeeping, and the claims they make to their own end users. Consult qualified legal counsel for guidance specific to your use case.

² This article describes regulatory frameworks at a general level and does not constitute legal advice. Laws and regulations vary by jurisdiction, change over time, and apply differently depending on facts and circumstances. Readers should consult qualified legal counsel before making compliance decisions.

³ Performance figures, customer outcomes, and industry statistics referenced in this article are drawn from cited third-party sources or Plura customer case studies. Individual results vary based on implementation, use case, industry, audience, and execution. Past or aggregate performance is not a guarantee of future results.

This article is provided for informational purposes only and reflects Plura AI’s understanding at the time of publication. Product capabilities, integrations, and specifications are subject to change. For the most current information, visit plura.ai.

This article was produced with the assistance of AI tools and reviewed by Plura AI prior to publication.