What Counts as an Autodialer? The TCPA ATDS Rule
The Telephone Consumer Protection Act's central restriction turns on a single defined term: the automatic telephone dialing system, or ATDS. Under 47 U.S.C. 227(b), calling or texting a cell phone using an ATDS without the recipient's prior express consent is unlawful. For three decades, what counted as an ATDS was among the most litigated questions in American consumer law, until the Supreme Court answered it in Facebook v. Duguid in 2021.
This guide states the statutory definition, explains the Duguid holding in plain English, and then delivers the caution every organization needs: a narrow autodialer definition did not make consent optional.
The Statutory Definition
The TCPA defines an ATDS at 47 U.S.C. 227(a)(1) as equipment which has the capacity:
- to store or produce telephone numbers to be called, using a random or sequential number generator; and
- to dial such numbers.
Every word of that definition was fought over in court. Does "using a random or sequential number generator" modify both "store" and "produce," or only "produce"? If it modifies both, an ATDS is a narrow category: machines that generate numbers randomly or in sequence. If it modifies only "produce," then any system that merely stores numbers and dials them automatically, which describes essentially every modern texting platform and smartphone, could be an ATDS.
Facebook v. Duguid: What the Supreme Court Held
In Facebook v. Duguid, 592 U.S. 395 (2021), a unanimous Supreme Court adopted the narrow reading. Noah Duguid had received login-alert texts from Facebook for an account he never had, and argued Facebook's system was an ATDS because it stored numbers and texted them automatically. The Court disagreed.
The holding, stated plainly: to qualify as an ATDS, a device must have the capacity either to store a telephone number using a random or sequential number generator, or to produce a telephone number using a random or sequential number generator. Equipment that simply dials or texts from a stored list of specific numbers, numbers collected from customers, for example, is not an ATDS under the federal definition.
The Court's reasoning rested on grammar (the series-qualifier canon: the modifying phrase applies to the whole list) and on statutory purpose: Congress in 1991 targeted machines that dialed blocks of random or sequential numbers, tying up emergency lines and cell networks, not every device capable of automated dialing.
What Duguid Means for Texting Programs
| System behavior | ATDS under Duguid? |
|---|---|
| Generates random phone numbers and dials them | Yes |
| Dials sequential number blocks (555-0100, 555-0101...) | Yes |
| Sends broadcasts to an opt-in subscriber list | Not on that basis alone |
| Sends automated replies to numbers that texted in | Not on that basis alone |
| Stores customer numbers and texts them on a schedule | Not on that basis alone |
Modern organizational texting, sending to a list of people who provided their numbers, falls outside the federal ATDS definition as the Supreme Court read it. That is the good news. It is also where careless readers stop, and the next section is why they should not.
Why Consent Still Rules After Duguid
Four independent legal layers keep consent mandatory even for non-ATDS texting:
- Prerecorded and artificial voice rules. The TCPA's consent requirements for artificial or prerecorded voice calls do not depend on ATDS status at all, and the FCC has applied related reasoning to AI-generated voice content.
- The FCC's telemarketing framework. The written-consent requirement for marketing messages at 47 CFR 64.1200(a)(2) and the do-not-call rules operate independently of the autodialer question. Our guide to express vs. written consent covers those tiers.
- State mini-TCPA statutes. After Duguid, several states enacted statutes with broader definitions. Florida's FTSA and Oklahoma's OTSA reach "automated system[s] for the selection or dialing of telephone numbers," language written specifically to cover list-based platforms the federal definition now excludes. A national texting program is subject to the strictest state law its recipients live under.
- Carrier and industry rules. The CTIA Messaging Principles and carrier registration frameworks require consent for A2P messaging regardless of any statute. Carriers filter and block programs without proper opt-in evidence, no lawsuit required.
The operational conclusion: Duguid changed litigation leverage, not program design. Documented opt-in consent, honored opt-outs, and disclosure remain the architecture of every defensible texting program.
How the ATDS Question Fits the Larger Statute
The autodialer definition is one gear in a larger machine, and reading it in isolation misleads. The TCPA's structure, mapped fully in our plain-language TCPA guide, restricts several distinct behaviors:
- 47 U.S.C. 227(b): autodialed and artificial or prerecorded voice calls to cell phones and certain other lines, the provision the ATDS definition gates.
- 47 U.S.C. 227(c): the do-not-call framework for telephone solicitations, no autodialer required.
- 47 CFR 64.1200(a)(2) and (f): the FCC's written-consent requirement for telemarketing and its definitions.
- The 2024 revocation order: opt-out rights that attach to consent-based messaging generally.
A texting program can be untouched by 227(b) after Duguid and still violate 227(c), the FCC's consent rules, or a state statute on the same day with the same message. That layered structure is why the ATDS holding changed less in practice than the headlines suggested.
Litigation After Duguid
Plaintiffs did not disappear after 2021; they changed theories. Post-Duguid TCPA suits emphasize prerecorded-voice claims, do-not-call violations, revocation failures under the FCC's 2024 rules, and state statutes with broader autodialer definitions. Courts also continue to work through what "capacity" to use a number generator means for modern systems. The lesson from the case law, explored in our review of TCPA class action lessons, is that the plaintiffs' bar follows whichever door is open, and consent records close most of them.
Why the Definition Was Worth a Supreme Court Case
The stakes in Duguid explain the intensity around nine words of statutory text. Under the broad reading, every smartphone and every customer database with a texting feature was potentially an ATDS, which made every unconsented text a candidate for 500 to 1,500 dollars in statutory damages, multiplied across class actions covering millions of messages. Businesses faced annihilating exposure for routine communication; plaintiffs' firms had built practices on that exposure; and the circuits had split, meaning identical conduct was lawful in one part of the country and actionable in another.
The unanimous decision resolved the split in favor of the narrow reading, and the aftermath reshaped the field: federal ATDS filings fell, state legislatures wrote broader definitions into their own statutes, and the FCC shifted energy toward revocation rights and robocall infrastructure rules. For organizations, the lasting lesson is about legal architecture rather than any single holding: liability theories move, definitions get relitigated, and the only program design that survives every shift is the one that never depends on winning a definitional argument, documented consent, honored opt-outs, and complete records.
Frequently Asked Questions
Is a mass texting platform an autodialer?
Not by reason of sending broadcasts to a stored subscriber list. Under Facebook v. Duguid, a system is an ATDS only if it stores or produces numbers using a random or sequential number generator. But state statutes and FCC telemarketing rules impose consent requirements on list-based platforms anyway.
Is my smartphone an ATDS?
The Duguid Court noted that the broad reading would have captured every smartphone, and rejected it partly for that reason. An ordinary phone dialing stored contacts is not an ATDS.
Did Duguid make it legal to text people without consent?
No. It narrowed one liability theory under one federal provision. Marketing texts still require prior express written consent under FCC rules, state mini-TCPAs cover list-based automated texting, revocations must be honored, and carriers require opt-in evidence for A2P traffic.
What does "capacity" mean in the definition?
The statute covers equipment that has the capacity to store or produce numbers with a random or sequential generator, and courts continue to address whether present configuration or theoretical capability controls. Programs built on documented consent do not need to win that argument.
Do AI-assisted texting tools change the ATDS analysis?
The ATDS question turns on number generation, not message intelligence, so AI-drafted or AI-routed replies to consented contacts do not create ATDS status. Separately, the FCC has addressed AI-generated voice calls under the artificial voice rules, and disclosure best practices apply to automated conversations.
Built for the Rules as They Actually Are
FRANSiS sends only to documented opt-in contacts, honors revocations instantly, and keeps the consent records that make autodialer arguments irrelevant, with an AI Powered Helper managing replies transparently. Contact us to run texting that holds up under every definition.
