TCPA 1991: A Section-by-Section Walkthrough
The Telephone Consumer Protection Act of 1991, codified at 47 USC 227, restricts the use of automated calling, texting, and fax equipment to protect consumers from unwanted communications, and and its operative rules sit in subsections (a) through (g), each covering a distinct piece of the framework: definitions, restrictions on automated equipment, do-not-call protections, technical standards, caller ID rules, the relationship to state law, and state enforcement authority. Later amendments added further subsections covering annual reporting to Congress, information sharing, and robocall blocking services. Congress passed the Act in response to a rising volume of automated telemarketing calls that consumers had no practical way to stop, and it built in a private right of action so individual consumers, not just regulators, could enforce the restrictions. Decades later, the statute is still the foundation for almost every text messaging compliance question, because SMS is treated as a "call" for TCPA purposes when it is sent using qualifying automated equipment.
Subsection (a): Definitions
Subsection (a) defines the terms that do the heavy lifting throughout the rest of the statute, including automatic telephone dialing system, established business relationship, telephone facsimile machine, telephone solicitation, and unsolicited advertisement. How narrowly or broadly these terms are read determines which communications the Act reaches at all. The definition of automatic telephone dialing system has generated the most litigation of any term in the statute; the Supreme Court resolved a long-running circuit split over its meaning in Facebook, Inc. v. Duguid, decided in April 2021, holding that a device only qualifies if it has the capacity to store or produce telephone numbers using a random or sequential number generator. That reading narrowed the statute's reach considerably and is discussed further in what counts as an autodialer under the TCPA.
Subsection (b): Restrictions on automated equipment
Subsection (b) is the core operative provision for text messaging compliance. It prohibits calls, including texts, made using an automatic telephone dialing system or an artificial or prerecorded voice to emergency lines, hospital patient rooms, paging services, and cellular telephones, subject to specific exceptions such as calls made for emergency purposes or with the prior express consent of the called party. It separately restricts prerecorded voice calls to residential lines and unsolicited fax advertisements. This subsection also creates the private right of action that makes the TCPA so consequential: a person may sue to enjoin a violation, recover actual monetary loss or $500 for each violation, whichever is greater, and a court may treble that amount up to $1,500 per violation if it finds the defendant acted willfully or knowingly. Because damages accrue per message rather than per lawsuit, subsection (b) is the source of the large aggregate exposure discussed in TCPA violations and penalties explained.
Subsection (c): Protection of subscriber privacy rights
Subsection (c) directed the FCC to establish, and gave legal force to, the national do-not-call registry framework that protects residential subscribers from unwanted telephone solicitations. It authorizes the database mechanism consumers use to register their numbers and requires telemarketers to check the registry before making solicitation calls. Like subsection (b), it includes a private right of action for consumers whose registered numbers are called in violation of the do-not-call rules, separate from the automated-equipment violations addressed above.
Subsection (d): Technical and procedural standards
Subsection (d) requires that equipment used for calls, faxes, and prerecorded messages meet certain technical and procedural standards, including that a fax transmission carry a mark identifying the sender along with the date and time of transmission, and that a prerecorded message state clearly at the outset the identity of the business responsible for the call. This subsection is where the statute's more mechanical, equipment-level requirements live, as distinct from the consent-focused restrictions in subsection (b).
Subsection (e): Prohibition on caller ID spoofing
Subsection (e) prohibits knowingly transmitting misleading or inaccurate caller identification information, commonly called caller ID spoofing, with the intent to defraud, cause harm, or wrongfully obtain anything of value, and it extends this prohibition to text messages as well as voice calls. The statute sets a forfeiture penalty of up to $10,000 per violation through FCC enforcement, an amount the FCC adjusts for inflation, in addition to any private right of action available under other subsections. This is a narrower, intent-based provision compared to the strict-liability structure of subsection (b), since it requires a showing of intent to defraud or cause harm rather than simply the absence of consent.
Subsection (f): Effect on state law
Subsection (f) preserves the authority of individual states to impose their own, potentially stricter, requirements on intrastate faxes, autodialed calls, prerecorded messages, and telephone solicitations, while coordinating those state rules with the federal do-not-call database. The TCPA sets a federal floor, not a ceiling, and a number of states maintain their own telemarketing and consumer protection statutes that layer additional obligations on top of the federal requirements.
Subsection (g): Actions by states
Subsection (g) authorizes state attorneys general to bring civil enforcement actions in federal court on behalf of their state's residents when a pattern or practice of violations occurs, allowing states to recover actual damages or the same $500 per-violation statutory amount available to private plaintiffs, again subject to trebling for willful or knowing violations. This gives the TCPA an enforcement layer beyond individual lawsuits and FCC action.
The statute and its implementing rules side by side
| Subsection | Core subject | Key implementing rule |
|---|---|---|
| (a) | Definitions, including automatic telephone dialing system | 47 CFR 64.1200(f) |
| (b) | Restrictions on automated calls and texts; private right of action and statutory damages | 47 CFR 64.1200(a) |
| (c) | Do-not-call registry and residential subscriber protections | 47 CFR 64.1200(c) and (d) |
| (d) | Technical and procedural standards for calling and messaging equipment | 47 CFR 64.1200(b); fax identification marking at 47 CFR 68.318(d) |
| (e) | Caller ID spoofing prohibition | 47 CFR 64.1604 |
| (f) | Effect on and coordination with state law | Not separately codified in Part 64; state statutes govern |
| (g) | State attorney general enforcement actions | Applied directly from the statute in federal court proceedings |
Where the FCC's rules fit in
The statute at 47 USC 227 sets the framework Congress enacted; the FCC then fills in operational detail through rules at 47 CFR 64.1200, which is where most of the day-to-day compliance requirements a texting program actually has to follow are spelled out, including the specific mechanics of prior express written consent, revocation of consent, and opt-out notice content. Those implementing rules change more frequently than the statute itself, since the FCC can amend Part 64 through its own rulemaking process without needing new legislation, which is why current guidance on consent and revocation should always be checked against the FCC's most recent orders rather than the statutory text alone. A current summary of those requirements is maintained in the TCPA compliance guide for SMS.
Why the autodialer definition in subsection (a) matters so much
Of the seven operative subsections, (a) has driven the most litigation, because subsection (b)'s core prohibitions only apply to calls and texts made using an "automatic telephone dialing system" or an artificial or prerecorded voice. Get the definition of automatic telephone dialing system wrong, in either direction, and you either sweep in ordinary business texting platforms that never should have been covered or exempt genuinely automated blast systems the statute was written to reach. The Supreme Court's 2021 resolution of that question in Facebook v. Duguid is the reason so much current TCPA compliance guidance, including the practical penalty exposure discussed in TCPA violations and penalties explained, reads differently than guidance written before that decision.
This article is general information, not legal advice. Requirements vary by jurisdiction and change over time, so confirm your own obligations with qualified counsel or the relevant regulator.
Frequently Asked Questions
What does 47 USC 227 cover?
It is the codified text of the Telephone Consumer Protection Act of 1991, covering definitions, restrictions on autodialed and prerecorded calls and texts, the national do-not-call registry, technical equipment standards, caller ID spoofing, and the relationship between federal and state telemarketing law, across its seven main subsections.
How many main subsections does the TCPA have?
Seven subsections carry the operative rules: subsection (a) covers definitions, (b) covers restrictions on automated equipment along with the private right of action, (c) covers the do-not-call registry, (d) covers technical and procedural standards, (e) covers caller ID spoofing, (f) covers the statute's effect on state law, and (g) authorizes state attorney general enforcement actions. Later amendments added further subsections covering annual reporting to Congress, information sharing, and robocall blocking services.
What are the statutory damages under the TCPA?
A private plaintiff can recover actual monetary loss or $500 for each violation, whichever is greater, under subsection (b)(3). A court may treble that amount up to $1,500 per violation if it finds the violation was committed willfully or knowingly. These amounts are written directly into the statute rather than set by regulation.
Where are the TCPA's implementing rules found?
The FCC's implementing regulations sit at 47 CFR 64.1200, which is where most operational requirements for consent, revocation, do-not-call compliance, and technical standards are actually spelled out. The statute at 47 USC 227 establishes the framework; the FCC's Part 64 rules fill in the day-to-day detail and are updated more frequently than the statute.
Does the TCPA apply to text messages?
Yes. Courts and the FCC treat text messages sent using qualifying automated equipment as "calls" for purposes of subsection (b), so the same restrictions, consent requirements, and statutory damages that apply to automated voice calls apply to automated text messages as well.
What is an automatic telephone dialing system under the statute?
Subsection (a) defines the term, and the Supreme Court clarified its meaning in Facebook v. Duguid in 2021, holding that a device qualifies only if it has the capacity to store or produce telephone numbers using a random or sequential number generator. Equipment that simply dials from a fixed, pre-existing contact list does not meet that definition.
Can state governments enforce the TCPA?
Yes, under subsection (g), state attorneys general can bring civil actions in federal court against patterns of violations affecting their state's residents, recovering the same statutory damages available to private plaintiffs, subject to the same trebling standard for willful or knowing conduct.
Does the TCPA preempt state telemarketing laws?
No. Subsection (f) preserves state authority to impose their own, potentially stricter, requirements on intrastate calls, texts, and faxes. The TCPA functions as a federal floor rather than a ceiling, so a communication that satisfies federal requirements can still violate a stricter state statute.
A texting platform built around the statute
FRANSiS is an AI powered SMS platform built to support consent capture, opt-out handling, and message records against the framework Congress set out in 47 USC 227 and the FCC's rules under it. Its AI Powered Helper drafts replies for staff review rather than answering on its own. To talk through how this would work for your organization, contact us.
