Last updated 2026-07-09
TL;DR
Under 47 U.S.C. § 227, an autodialer (ATDS) must have the capacity to store or produce numbers using a random or sequential number generator and dial them. The Supreme Court's 2021 Facebook v. Duguid ruling narrowed that definition, but FCC rulemaking added new wrinkles. Manual dialers without ATDS features get more TCPA leeway. The line is genuinely blurry, and courts still split on it.
What does TCPA actually say an autodialer is?
The statute defines an autodialer as equipment that generates numbers randomly or sequentially and dials them. 47 U.S.C. § 227(a)(1) calls it "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." [1] That language has sat unchanged since 1991. Every fight over the last decade has been about what those words mean in practice.
The phrase "capacity to" is where the trouble lives. Does it mean the equipment must actually use a random or sequential generator right now, or just that it could theoretically do so? Courts split badly on this for years. The Ninth Circuit once held that almost any smartphone could be an ATDS because software could make it one. That reading would have turned nearly every outbound call into a TCPA liability.
Congress has not touched the definition. The FCC has issued orders interpreting it. The Supreme Court finally weighed in in 2021, and that decision is the most important development in modern TCPA compliance.
What did the Supreme Court decide in Facebook v. Duguid?
In Facebook, Inc. v. Duguid, 592 U.S. 395 (2021), the Court held unanimously that an ATDS must use a random or sequential number generator to store or produce the numbers it dials. [2] A system that simply stores a list of specific numbers and dials them automatically does not qualify as an ATDS under the statute.
That was a big win for outbound teams. It killed the broadest reading, where essentially any software-assisted dialing could trigger TCPA's consent rules for cell phones. After Duguid, if your system dials from a fixed list of contacts without generating numbers randomly or sequentially, you have a stronger argument that it is not an ATDS.
Don't read that as a free pass. The Court interpreted the statute narrowly, but it did not decide which specific equipment features push a dialer over the ATDS line. That question falls back to the FCC and the lower courts, and they are still working through it. Duguid resolved one circuit split and opened new questions about systems that use predictive algorithms or store-and-forward architectures.
One concrete takeaway. If your dialer requires a human to manually start each call, with no automated queuing or number generation, your ATDS risk drops sharply. If the system automates the queuing and pacing of calls from a list, you are in a gray zone that district courts have handled very differently.
What makes a dialer "manual" under the TCPA framework?
No FCC rule says "these seven features make a dialer manual." What compliance practitioners piece together from case law and FCC orders is a functional test: does a human make a deliberate, affirmative act to place each individual call?
A true manual dialer in the TCPA sense looks like this. A rep sees a number on a screen, clicks a button or dials the digits, and the call goes out only because of that specific human action. No automated queuing. No predictive pacing. No system-generated sequence. The human is the engine.
Why does this matter? If the system is not an ATDS, you do not need prior express written consent to call a cell phone for telemarketing under federal TCPA rules. You still have to follow the do not call list rules, honor established business relationships correctly, and stick to legal calling hours. But the consent burden for cell phones is lower.
The practical problem is that most modern sales dialers sit somewhere between a truly manual phone and a fully automated predictive dialer. Click-to-call systems, power dialers that auto-advance to the next record, and preview dialers with auto-answer all raise questions. Courts have generally been more forgiving of preview dialers, where a human sees the number and chooses whether to call, than of predictive dialers that fire calls before an agent is free. No published FCC rule cleanly resolves every product design.
If you are shopping for a dialer, ask the vendor for a written technical description of how calls get initiated. Then have someone with legal background compare that description against the Duguid standard and your circuit's most recent ATDS cases. That written description also becomes part of your litigation defense if you ever get sued.
How do courts actually draw the line between manual and automated dialing?
Post-Duguid, courts ask whether the equipment uses a random or sequential number generator as part of storing or producing the numbers dialed. But they apply that test differently depending on the facts.
Some courts have found that a predictive dialer running from a list without human intervention per call still qualifies as an ATDS if it has the capacity to generate numbers randomly. Others have held that dialing from a stored list of specific contacts, with no generation step, cannot be an ATDS under Duguid no matter how automated the pacing. [3]
The Eleventh Circuit read Duguid in a defendant-friendly way in Drazen v. Pinto (2022), holding that a system must actually have the capacity to generate random or sequential numbers to be an ATDS, and doing more than dialing automatically. [4] The Ninth Circuit has been more willing to find ATDS status where a system has some capacity, even if not currently exercised, to work as a number generator.
What this means for your team: your exposure depends partly on which federal circuit you operate in, or where plaintiffs can plausibly file. A cold call operation that is fine in Florida might face a different risk profile if a plaintiff files in California.
The single most protective thing you can do is document exactly how your system works at the moment of dialing. Written technical specs from your vendor, call logs showing human-initiated actions, and screenshots of your workflow are the evidence that actually matters when litigation starts.
What is the FCC doing with the autodialer definition in 2024?
The FCC has been reworking its TCPA rules in ways that touch both the ATDS definition and consent. In its 2023 rulemaking and later orders, the agency signaled interest in clarifying what "capacity" means and how the Duguid standard applies to modern dialing systems. [5]
The FCC's December 2023 one-to-one consent order is the biggest recent shift. That rule requires consent for one seller at a time, not bundled across multiple companies through a single lead form. [6] It does not change the ATDS definition itself, but it tightens consent validity, which affects how much a consent defense protects you if your system is later found to be an ATDS.
The FCC also said, in earlier orders, that predictive dialers can be ATDSs. Its 2003 order found that "the Commission has determined that the term 'capacity' as used in the TCPA must be construed broadly and that a predictive dialer falls within the meaning and definition of 'automatic telephone dialing system.'" [3] Post-Duguid, that 2003 guidance is in tension with the Supreme Court, and the FCC has not fully reconciled the two.
For 2024 and into 2025, the safest working assumption is simple. If your dialer automates the pacing or sequencing of calls and removes per-call human decision-making, treat it as a possible ATDS and get prior express written consent for cell phone marketing calls.
What is the consent difference between calling with a manual vs. automated dialer?
This is the operational heart of the distinction. An ATDS or prerecorded call to a cell phone needs prior express written consent for telemarketing. A live call from a true manual dialer does not, under federal TCPA.
For calls to cell phones using an ATDS or a prerecorded voice, TCPA requires prior express written consent for telemarketing. [1] That consent has to be a signed agreement (electronic signatures count) authorizing the specific seller to contact the consumer at a specific number. The FCC's one-to-one consent rule tightens this by requiring that the consent name the specific seller, not a category of sellers. [6]
For calls made with a true manual dialer, no ATDS and no prerecorded or artificial voice, you do not need prior express written consent under federal TCPA to call a cell phone. You still need consent for telemarketing calls to numbers on the National Do Not Call Registry if you lack an established business relationship, but that is a different and generally lower bar. [7]
Here is what that looks like in a table:
| Dialing Method | Cell Phone Telemarketing Consent Needed | DNC Rules Apply? |
|---|---|---|
| ATDS (autodialer) | Prior express written consent | Yes |
| Prerecorded voice | Prior express written consent | Yes |
| Manual dialer, live voice | No written consent required under TCPA | Yes |
| Manual dialer, to existing customer | No prior express written consent required | EBR may apply |
State laws can require more. Florida, Maryland, and Oklahoma have mini-TCPA laws that apply stricter rules to manual calls or extend ATDS-style consent more broadly. Always check the law for where your contacts live, more than where your company operates. You can also check text message marketing rules separately, since SMS has its own consent framework even for manual sends.
Does the ATDS definition apply to text messages the same way it applies to calls?
Yes. The same statutory definition of ATDS covers both calls and text messages under 47 U.S.C. § 227. [1] The FCC treats text messages as "calls" under the TCPA, and if you send a text using an ATDS, the same prior express written consent rules apply as for a cell phone call. [11]
The practical difference is that almost every bulk SMS platform uses automation that could be called ATDS-level. Even platforms sending texts from a list through an API often get treated as ATDSs by regulators and plaintiffs. If you are sending marketing texts, assume ATDS consent rules apply and collect proper written opt-ins. Duguid narrowed the definition for calls, but SMS platforms that generate and send texts automatically fit more naturally inside the remaining ATDS definition.
Manual texting, where a rep composes and sends each text with no automated queuing, sits outside ATDS territory in theory. Almost no real marketing program works that way at scale. If you are sending more than a few dozen texts a day per rep, you are almost certainly using some form of automation.
Settlements confirm the risk. The cash app tcpa class action settlement and similar cases show plaintiffs targeting companies over automated texts. The credit one tcpa settlement reached $75 million based in part on autodialed calls to cell phones. These are not hypothetical.
What are the penalties if you get the ATDS classification wrong?
TCPA penalties run per violation, not per campaign. The statute sets damages at $500 per negligent violation and up to $1,500 per willful or knowing violation. [1] There is no cap on the number of violations in a class action, which is exactly why plaintiff attorneys love these cases.
A company that makes 10,000 autodialed calls without proper consent faces up to $5 million in statutory damages at $500 per call, or up to $15 million if a court finds the violations were knowing. Class settlements have gone higher. The credit one tcpa settlement reached $75 million, one of the largest in TCPA history. [8]
Getting the classification wrong in your own favor (calling your autodialer a manual dialer when it isn't) means you probably skipped collecting the written consent that would have been your primary defense. Courts do not accept "we thought our dialer was manual" as a full excuse when the system clearly automated call pacing and sequencing.
The FCC can also issue forfeitures, separate from private lawsuits, of up to $57,317 per day for continuing violations under its current schedule. [9] For most outbound teams, private class actions are the bigger financial risk, but regulatory action is real and has hit carriers and lead generators in recent years.
LeadCompliant's free TCPA compliance kit includes a dialer-classification worksheet you can run before your legal team reviews your setup. It is not legal advice. It helps you organize the right questions.
How do predictive dialers, power dialers, and preview dialers compare on ATDS risk?
These three common dialer types sit at different points on the risk spectrum. Predictive carries the most, preview the least, and power dialers land in a genuine gray zone.
A predictive dialer calls multiple numbers at once, predicts when agents will be free, and connects answered calls to available agents. It removes per-call human decision-making almost entirely. Before Duguid, courts and the FCC treated these as ATDSs nearly across the board. After Duguid, the analysis turns on whether the system uses a random or sequential number generator, but operationally, predictive dialers still carry the highest ATDS risk because of how automated they are. Many plaintiff attorneys argue the predictive algorithm itself is the random or sequential element.
A power dialer automatically moves to the next contact in a list the moment an agent is free. A human is on the line for each connected call, but the dialing itself is automatic. Power dialers are a real gray zone. They dial from a stored list (Duguid-friendly), but they automate the dialing with no per-call human click (ATDS-unfriendly). Courts have gone both ways.
A preview dialer shows the agent the next contact's information and lets the agent choose to dial or skip before any call goes out. The human makes an affirmative decision per call. This is the closest thing to a "manual" dialer in a modern sales platform. ATDS risk is lower, though not zero, especially if the system has background automation features.
Here is a rough comparison:
| Dialer Type | Per-Call Human Action | ATDS Risk (Post-Duguid) |
|---|---|---|
| Predictive dialer | None | High |
| Power dialer | None (automatic advance) | Medium-High |
| Preview dialer | Yes (click to dial) | Lower (not zero) |
| True manual (hand-dial) | Yes | Lowest |
Nobody has clean data on what percentage of cases involving each type end in ATDS findings. The best move is to ask your vendor whether the system uses any random or sequential number generation anywhere in its operation, get that answer in writing, and hand it to legal counsel.
What should outbound teams actually do right now to reduce ATDS risk?
Here is what I would actually do, in rough priority order. Written vendor specs first, then consent, then list scrubbing, then state law, then documentation.
First, get a written technical description from your dialer vendor explaining how calls are initiated and whether any random or sequential number generation happens anywhere in the system. Vendors often resist this because it is liability-adjacent for them. If they cannot or will not explain their own system, that is a signal.
Second, if you are calling cell phones for any telemarketing, collect prior express written consent no matter what you think your dialer classification is. Consent is a complete defense. A well-documented consent record beats a complicated ATDS argument every time in litigation.
Third, scrub your list against the do not call list before every campaign, even with a manual dialer. TCPA's DNC rules apply to manual calls too, and the National DNC list is a separate obligation from the ATDS consent rules.
Fourth, check the law for every state where your contacts live. Florida's FTSA, for example, uses a broader definition of autodialer than post-Duguid federal TCPA, and its private right of action has drawn aggressive plaintiff filings. [10]
Fifth, document everything. Call logs, consent records, dialer configuration screenshots, vendor agreements, and your compliance policies all become your defense file if you get served. A company with clean records in the right format settles faster and cheaper than one reconstructing its practices from memory.
For teams building this from scratch, cold calling compliance and mobile phone do not call list rules are the two areas with the easiest quick wins. Clean your list, document your consent, classify your dialer honestly. That sequence cuts your exposure more than most technology spending.
Are there state-level autodialer rules that go further than federal TCPA?
Yes, and this is increasingly where the real compliance complexity lives for outbound teams. Several states now define autodialers more broadly than post-Duguid federal law, and most give consumers a private right to sue.
Florida's Telephone Solicitation Act (FTSA) defines an autodialer as any system with the capacity to dial without human intervention, which is meaningfully broader than the federal standard. [10] Florida's definition has no "random or sequential number generator" requirement. A power dialer calling Florida cell numbers could be an ATDS under the FTSA even if it wouldn't be under federal TCPA after Duguid.
Maryland's MTSA and Oklahoma's OTSA have also added state-specific restrictions that go past federal minimums. These laws vary on which calls they cover, what consent they require, how they define automated dialing, and whether they allow private lawsuits (most do).
The practical point: if you are calling a consumer in a state with a mini-TCPA law, you comply with that state's law, more than federal TCPA. A system that is clearly not a federal ATDS can still trigger state liability. Plaintiff firms have targeted Florida in particular, because the broader autodialer definition plus a private right of action makes cases easy to bring.
There is no single master list of state mini-TCPA laws that stays current on its own. Know which states your call list covers, and have your legal team review those specific statutes every year. This area has moved fast since 2021.
Frequently asked questions
Does the Facebook v. Duguid Supreme Court ruling mean my autodialer is now legal to use without consent?
No. Duguid narrowed the ATDS definition so systems dialing from stored lists without random or sequential number generation are less likely to qualify as ATDSs under federal TCPA. But if your system uses automated generation or predictive pacing, ATDS rules still apply. And state laws like Florida's FTSA use broader definitions Duguid does not affect. Consent stays the safest defense regardless of dialer type.
Can I avoid TCPA liability just by calling cell phones manually?
A true manual dialer lowers your exposure for the ATDS-specific consent requirement, but it does not clear all TCPA obligations. You still must honor the National Do Not Call Registry, respect calling hours (8 a.m. to 9 p.m. local time), and comply with any state telemarketing laws. Manual dialing removes one major risk layer. It does not clear the whole board.
What counts as prior express written consent for TCPA purposes?
Under FCC rules, prior express written consent for telemarketing calls using an ATDS must be a signed agreement, written or electronic, that clearly authorizes the specific seller to call or text the consumer at a specific number for marketing. After the FCC's one-to-one consent rule, that consent must identify the specific seller and cannot be bundled across multiple companies in a single form disclosure.
Is a click-to-call or VoIP softphone system considered a manual dialer?
Generally yes, if the system requires a human to click to start each individual call with no automated queuing. A softphone where the rep clicks a number and the call goes out is closer to a manual dialer than a predictive system. But if the platform auto-advances to the next record or fires calls in the background, that automation changes the analysis. Get your vendor's written technical description before deciding.
What TCPA penalty can I face if I misclassify my autodialer as a manual dialer?
Statutory damages under TCPA are $500 per violation for negligent violations and up to $1,500 per knowing or willful violation. There is no per-campaign cap, so class actions covering thousands of calls can produce multimillion-dollar exposure. The Credit One TCPA settlement reached $75 million. Misclassifying your dialer and skipping consent collection removes your primary defense in those cases.
Does the ATDS definition apply differently to text messages than to phone calls?
The same TCPA definition of ATDS covers texts and calls. The FCC treats texts as "calls" under the statute. In practice, most bulk SMS platforms use automation that fits inside the remaining ATDS definition even after Duguid, so treating SMS campaigns as requiring prior express written consent is the right default for telemarketing texts to cell phones.
How does Florida's FTSA differ from federal TCPA on autodialer rules?
Florida's Telephone Solicitation Act defines an autodialer as any system that dials without human intervention, with no requirement for a random or sequential number generator. That is broader than the post-Duguid federal standard. A power dialer calling Florida numbers can trigger FTSA liability even if it would not be an ATDS under federal TCPA. Florida also has a private right of action that plaintiff attorneys have used frequently.
What is a predictive dialer and why does it carry high ATDS risk?
A predictive dialer calls multiple numbers at once, uses an algorithm to predict agent availability, and connects live calls automatically. No human makes a per-call decision. Before Duguid, these were almost universally ATDSs. Post-Duguid, the risk depends on whether the predictive algorithm involves random or sequential number generation, but operationally these systems carry the highest ATDS risk and should be treated as ATDSs for consent planning.
Do I need to scrub my call list against the Do Not Call Registry even with a manual dialer?
Yes. The National Do Not Call Registry rules apply to telemarketing calls regardless of dialer type. A company using a true manual dialer must still honor DNC registrations, maintain an internal DNC list, and respect the established business relationship rules under the FTC and FCC's DNC regulations. The ATDS distinction affects consent for cell phones, not DNC compliance.
Can my dialer vendor's marketing language determine whether my system is an ATDS?
No. Courts and the FCC look at how the system actually functions, not what a vendor calls it. A vendor labeling their product a "manual power dialer" does not make it one under the law. What matters is whether the equipment uses a random or sequential number generator and whether human action is required per call. Get a written technical description of the architecture and have legal counsel evaluate it.
How often is the TCPA autodialer definition likely to change?
The statutory text has not changed since 1991, and Congress has shown no urgency to amend it. Change comes through FCC rulemaking and court decisions, both of which have moved significantly since 2021. The FCC's recent rulemaking activity suggests more clarification is coming on consent and possibly on ATDS scope. Teams should review their dialer classification and consent practices at least annually given how active this area has been.
What documentation should I keep to defend a TCPA ATDS claim?
Keep your vendor's written technical description of how calls are initiated, call logs showing when and how calls were placed, consent records with timestamps and the exact language consumers agreed to, your internal compliance policy, and training records showing reps understood the rules. In litigation, the side with contemporaneous documentation almost always does better than the side reconstructing facts from memory months or years later.
Does the TCPA apply to B2B calls to cell phones?
The TCPA applies to the number called, not the purpose of the call. If you call a business contact's personal cell phone, TCPA rules including ATDS consent requirements apply. If you call a business landline, TCPA's cell phone rules do not apply, though DNC and other rules may. Most B2B outbound teams calling cell phones directly face the same ATDS consent exposure as consumer-facing teams.
Sources
- Cornell Law School / Legal Information Institute, 47 U.S.C. § 227: Statutory text defining ATDS as equipment with capacity to store or produce telephone numbers using a random or sequential number generator and dial them; statutory damages of $500 per violation up to $1,500 for willful violations
- U.S. Supreme Court, Facebook, Inc. v. Duguid, 592 U.S. 395 (2021): Supreme Court held unanimously that an ATDS must use a random or sequential number generator to store or produce the numbers it dials; systems dialing from a stored list of specific numbers are not ATDSs
- FCC, In the Matter of Rules and Regulations Implementing the Telephone Consumer Protection Act of 1991, Report and Order FCC 03-153 (2003): FCC 2003 order stating that the term 'capacity' must be construed broadly and that predictive dialers fall within the definition of automatic telephone dialing system under TCPA; rule codified at 47 CFR 64.1200
- U.S. Court of Appeals, Eleventh Circuit, Drazen v. Pinto, No. 21-10199 (11th Cir. 2022): Eleventh Circuit applied Duguid and held a system must have the capacity to generate random or sequential numbers to be an ATDS, not merely dial automatically from a list
- FCC, Telephone Consumer Protection Act rules, 47 CFR § 64.1200 (Legal Information Institute): FCC TCPA rules including ATDS-related restrictions and consent requirements, subject to ongoing FCC rulemaking through 2023-2024
- FCC, Report and Order on One-to-One Consent, FCC 23-107 (December 2023): FCC December 2023 order requiring that TCPA consent identify a specific seller rather than bundles of multiple companies
- FTC, National Do Not Call Registry: National DNC Registry rules apply to telemarketing calls regardless of dialer type; companies must honor DNC registrations and maintain internal DNC lists
- U.S. District Court, Central District of California, Credit One Bank TCPA Settlement, Case No. 2:18-cv-06083: Credit One Bank TCPA class action settlement reached $75 million, one of the largest in TCPA history, based in part on autodialed calls to cell phones
- FCC, 47 CFR § 1.80 Forfeiture Guidelines (Legal Information Institute): FCC may issue forfeitures of up to $57,317 per day for continuing TCPA violations under current forfeiture guidelines
- Florida Legislature, Florida Telephone Solicitation Act, § 501.059 Fla. Stat.: Florida FTSA defines autodialer as any system dialing without human intervention, broader than post-Duguid federal ATDS definition, with a private right of action