What counts as an autodialer under TCPA after Facebook v. Duguid

Last updated 2026-07-10

What did Facebook v. Duguid actually decide?

In April 2021, the Supreme Court decided Facebook, Inc. v. Duguid 9-0 and ended a decade-long circuit split over what makes a dialing system an "automatic telephone dialing system" (ATDS) under the TCPA. ^[1]

Noah Duguid sued Facebook. He said the company sent him repeated automated login-alert texts to a phone number he had never given Facebook. The fight was over how to read the statute's definition at 47 U.S.C. § 227(a)(1), which defines an ATDS as equipment with "the capacity to store or produce telephone numbers to be called, using a random or sequential number generator, and to dial such numbers." ^[2]

Facebook argued the phrase "using a random or sequential number generator" modifies both "store" and "produce." Duguid argued it only modifies "produce," which would mean any system that could store and automatically dial numbers qualified as an ATDS. The Ninth Circuit had adopted Duguid's broader reading.

The Court sided with Facebook. Justice Sotomayor, writing for the Court, held that the generator clause modifies both the storage and production functions. As she put it, "To qualify as an 'automatic telephone dialing system,' a device must have the capacity either to store a telephone number using a random or sequential generator or to produce a telephone number using a random or sequential number generator." ^[1]

Here is the practical consequence. If your dialing system works from a pre-set list of real, specific phone numbers, it almost certainly does not meet this definition, no matter how automated it is.

What is the exact TCPA autodialer definition after Duguid?

The statutory text at 47 U.S.C. § 227(a)(1) never changed. What changed is the authoritative reading of it. ^[2]

An ATDS now requires two things:

1. The equipment must have the capacity to store or produce telephone numbers using a random or sequential number generator. 2. The equipment must dial those numbers.

Both elements have to be present. A system that pulls numbers from your CRM and dials them is not generating random or sequential numbers. It is working from a human-curated list. Under Duguid, that is not an ATDS.

This reshapes the risk math for outbound sales. Most modern predictive dialers, power dialers, and auto-dialers used by real businesses do not use random or sequential number generators. They dial from contact lists a human assembled. That alone used to trigger ATDS liability in the Ninth Circuit. It no longer does.

The definition still covers a few things:

• Old-school war-dialers that generate random 10-digit numbers and dial them in sequence
• Any system that produces numbers algorithmically rather than picking from a fixed list
• Whatever the FCC interprets more broadly in future rulemaking (more on that below)

One caution. The TCPA still bans artificial or prerecorded voice calls whether or not an ATDS is involved, so Duguid gives nobody a free pass on robocalls. ^[2]

How does the Duguid ruling affect predictive dialers and modern sales software?

Most sales managers only care about one question: is my dialer safe now? Short answer, Duguid cut the ATDS litigation risk sharply for teams using standard predictive dialers or power dialers that pull from a contact list.

Before 2021, plaintiff attorneys in the Ninth Circuit argued that any system with the technical capacity to auto-dial, even from a list, counted as an ATDS. That theory powered class actions against companies running off-the-shelf sales dialers. Duguid knocked the legs out from under it.

Dialing Method	ATDS After Duguid?	TCPA Still Applies?
Random number generator dialer	Yes	Yes
Sequential number generator dialer	Yes	Yes
Predictive dialer (from contact list)	Likely No	For prerecorded/artificial voice, Yes
Power dialer (click-to-call, agent-initiated)	Very likely No	For prerecorded/artificial voice, Yes
Ringless voicemail drops	Contested	FCC treating as prerecorded voice
SMS blast platform (from list)	Likely No for ATDS; contested	Yes, other TCPA provisions may apply

Look at the last two rows. Ringless voicemail and SMS blasting are still contested. The FCC has not given either a clean pass, and some courts apply TCPA provisions beyond the ATDS definition to them. ^[3]

For cold calling teams running a CRM-integrated dialer, the ATDS risk dropped a lot. But lower risk is not no risk. Plaintiff firms have pivoted. Some now argue that a specific dialer does use an algorithmic number-generation feature. Others pursue claims under state laws with their own definitions. More on that below.

What did the circuit courts disagree on before Duguid, and is there still disagreement after?

Before Duguid, the split was stark. The Ninth Circuit, which covers California and the busiest TCPA venue in the country, used the broad reading: any system that could store and dial numbers was an ATDS. The Seventh and Eleventh Circuits used the narrow reading that required a random or sequential number generator. ^[4]

Duguid resolved the split in favor of the narrow reading. But the courts are not done fighting about ATDS questions. The disagreement moved downstream to harder edge cases.

What if the system has the capacity to generate random numbers but never uses it? The statute says "capacity," not "current use." Courts split here. Some hold a system must actually use random or sequential generation in the calls at issue. Others say capacity alone is enough.

What about systems that generate numbers algorithmically from a database but not truly at random? A system might pull numbers by a rule (every third number in a ZIP code, say) without being purely random. Is that a sequential number generator? No appellate court has fully answered that.

Do TCPA claims require showing the specific call used ATDS features, or just that the system could? The Eleventh Circuit in Borden v. eFinancial (2022) held that a plaintiff must show the system used a random or sequential number generator for the specific calls at issue, more than that it theoretically could. ^[5]

So yes, real uncertainty survives Duguid. It just moved to narrow, technical questions about specific system architectures instead of the big definitional brawl.

Does the FCC's ATDS definition match what the Supreme Court said?

Not exactly, and the gap matters.

The FCC issued ATDS guidance several times over the years, most notably in its 2015 Declaratory Ruling and Order, which used a very broad interpretation close to the Ninth Circuit's. The D.C. Circuit struck down parts of that 2015 ruling in ACA International v. FCC (2018) as arbitrary, but the agency's rulemaking authority stayed intact. ^[4]

After Duguid, the FCC opened a new proceeding in 2021 to revisit its ATDS rules in light of the decision. That rulemaking is still open as of mid-2026. The FCC has not issued a new definitive ATDS rule, which leaves a gap. The Supreme Court set the floor of the statutory definition. The FCC has not yet aligned its guidance with that reading or tried to expand TCPA protections through other tools.

What does that mean in practice? The FCC could try a broader rule on other TCPA provisions, like defining what counts as an artificial voice, that sweeps in more technology even though it cannot override Duguid's reading of the ATDS definition. Watch for new orders as this rulemaking closes.

The FCC also runs its own Do Not Call and telemarketing rules under the TCPA framework. Those are separate from the ATDS fight and stay in full force regardless of Duguid. ^[6]

Can you still face TCPA liability if your dialer isn't an ATDS?

Yes. This is the point people oversimplify most.

The TCPA has several liability hooks beyond the ATDS definition. Section 227(b)(1)(B) bans using an artificial or prerecorded voice to call residential lines without prior express consent, and that ban has nothing to do with whether you used an ATDS. ^[2] If your team drops prerecorded voicemails or uses AI-generated voice, that provision applies no matter how you dialed.

The TCPA's Do Not Call provisions at Section 227(c) also apply regardless of ATDS status. Call someone on the National Do Not Call Registry and you can face $500 to $1,500 per call in damages under 47 U.S.C. § 227(c)(5). Duguid does not touch that. Managing your do not call list compliance matters just as much as it did before 2021.

State mini-TCPA laws are the growing worry. Florida's Telephone Solicitation Act uses a broader ATDS-equivalent definition than the federal TCPA. Oklahoma and Maryland have passed similar laws. Some define an "automated system" in ways that could cover predictive dialers Duguid exempts from federal liability. ^[7]

The takeaway. Duguid narrowed one liability theory. It did not declaw the TCPA or make cold calls to cell phones consequence-free. You still need prior express written consent for most telemarketing to cell phones, and you still have to honor DNC requests.

For a sense of how expensive these cases get even under the old rules, the Cash App TCPA class action settlement and the Credit One TCPA settlement both involved autodialer allegations that ended in multi-million-dollar payouts.

What about text messages and SMS? Does Duguid change SMS liability?

Texts sent via an ATDS are covered by the TCPA the same way voice calls are. Duguid applies equally to SMS. ^[1]

If your SMS platform sends texts from a pre-loaded list of opt-in numbers and does not use a random or sequential number generator, it likely is not an ATDS under Duguid. Many mass text message marketing platforms work exactly this way.

Here is where SMS gets messy. Some platforms use short codes that the FCC and courts have looked at under separate theories. Application-to-person (A2P) messaging through a short code can be analyzed differently depending on how the platform queues and sends messages. A few courts have found that certain SMS gateway architectures do behave like sequential number generators, even after Duguid.

More practically: even if your SMS platform is not an ATDS, the FCC's consent rules for marketing texts still apply. Section 227(b)(1)(A)(iii) covers ATDS calls and texts to a cell phone. If your system is not an ATDS, that specific hook does not fire, but you can still face consent requirements for commercial texts under other authority.

The safest position for SMS marketing is simple. Get written consent regardless of what the ATDS analysis says. A clean consent record is more defensible than an argument that your platform is not an ATDS.

How do courts determine if a specific system is an ATDS after Duguid?

This is where litigation gets expensive and fact-heavy. After Duguid, both sides fight over the technical architecture of the exact dialing system used.

Plaintiff attorneys typically use discovery to request:

• Technical documentation and source code for the dialing platform
• Vendor contracts and feature descriptions
• Logs of how numbers were generated or selected for the calls in question
• Expert witnesses who can testify about whether the system uses any random or sequential number generation

Courts ask whether a human picked the numbers from a known list or whether the system produced them through some algorithmic process. The core factual question is blunt: did a human decide to call this specific number, or did the system generate it?

So your documentation matters enormously. If you can show, with logs and vendor affidavits, that your system only dials numbers a human agent entered or imported from a consent-verified list, you have a far stronger defense than if you cannot explain how numbers got selected.

Platforms that use number-scoring, sequential progression through a numeric range, or area-code-based prospecting should think hard about whether that architecture could be cast as sequential number generation. "We picked numbers from a bought list sorted by area code" is technically sequential, though most courts have not held that qualifies. Nobody has litigated all these edge cases to a clean answer yet.

LeadCompliant's compliance kit includes a dialer architecture documentation template that helps teams build this paper trail before a lawsuit forces the issue.

What do state laws say about autodialers that goes beyond Duguid?

This is the frontier for outbound sales compliance, and it blindsides a lot of teams.

Several states have passed telemarketing laws that define "automated" dialing systems differently from the federal TCPA. Duguid is a federal statutory interpretation case, so it has no binding effect on how states define prohibited technology under their own laws. ^[7]

Florida's Telephone Solicitation Act (FTSA), amended in 2021 and revised again in 2023, originally banned calls and texts made with "an automated system for the selection or dialing of telephone numbers." That language pulled in systems Duguid would exclude from the federal ATDS definition. Florida amended the law in May 2023 to add a human intervention requirement back in, which narrowed it somewhat, but Florida stays a high-litigation state for these claims. ^[8]

Oklahoma's Telephone Solicitation Act covers automated communication systems too. Maryland, Washington, and a handful of other states have either passed or are weighing laws that create state-level liability for calls made with auto-dialing features, whether or not they use random or sequential number generators.

If your team calls into California, Florida, Texas, or other big-population states, you need the state-specific rules, more than the federal ones. The mobile phone do not call list rules also vary by state in ways that tangle with these autodialer definitions.

What practical steps should outbound teams take after Duguid?

Duguid was a win for legitimate outbound sales. Treating it as a compliance holiday is a mistake. Here is what actually makes sense given where the law sits.

Document your dialing platform's architecture. Get a written statement from your vendor confirming the system does not use a random or sequential number generator to produce call targets. Keep it on file. If you get sued, this is your first line of defense.

Do not abandon consent practices. Prior express written consent for telemarketing to cell phones is still required under the TCPA, ATDS or not. The requirement lives in Section 227(b)(1)(A)(iii) and FCC rules at 47 C.F.R. § 64.1200. Build and keep a real consent record for every number you market to. ^[11]

Scrub your lists against the DNC registry. National Do Not Call Registry obligations survived Duguid completely. Scrub before calling, keep an internal DNC list, and honor opt-outs fast. The do not call telemarketer list rules apply even if your system is not an ATDS.

Know the state laws for your calling geography. Calling Florida? Get Florida FTSA counsel. Same for any state with its own telemarketing act.

Watch the FCC docket. The FCC's open ATDS rulemaking could shift the ground again. Watch especially for rules on AI-generated voices, which could widen prerecorded-voice liability for teams using voice-drop tools.

Train your reps. Legal theory does not help if a rep is manually calling numbers they Googled. Even without ATDS liability, one-off DNC or consent violations spawn real lawsuits. The TCPA framework has teeth well beyond the autodialer question.

If you want a structured way to size up your exposure, LeadCompliant has a free compliance kit with consent documentation, DNC scrubbing checklists, and a dialer classification worksheet you can run with your vendor.

Could the autodialer definition change again? What's the FCC doing?

Yes, it could change, and the FCC is the body most likely to do it.

The Supreme Court interpreted the existing statutory text in Duguid. Congress could amend 47 U.S.C. § 227 to broaden the definition again, and lawmakers have floated TCPA reforms in both directions. As of mid-2026, no amendment has passed.

The FCC's open ATDS rulemaking (CG Docket No. 02-278, consolidated with related dockets) is the nearer risk. The agency could try to define ATDS more broadly through its rulemaking power, test the limits of Duguid, or use other authority to regulate AI-calling and autodialers through different hooks. ^[9]

Some advocacy groups have pushed the FCC to treat any system that dials without contemporaneous human decision-making as functionally equivalent to an ATDS, even if it does not technically use a random or sequential number generator. The FCC has not gone there. It is not off the table either.

The practical move is to run a compliance system that would hold up even under a broader rule. If your consent, DNC scrubbing, and opt-out processes are solid, a shift in the ATDS definition creates no new exposure for you. The teams that banked entirely on the Duguid defense, with no underlying consent practices, are the ones who will scramble if the FCC acts.

Frequently asked questions

Does Facebook v. Duguid mean I can auto-dial cell phones without consent?

No. Duguid narrowed what equipment counts as an ATDS, but it did not remove the consent requirement for telemarketing to cell phones. The TCPA still requires prior express written consent for marketing calls or texts to cell phones regardless of whether your dialer is technically an ATDS. DNC rules also still apply in full.

What exactly is a random or sequential number generator under the TCPA?

A random number generator produces phone numbers by chance rather than picking from a known list. A sequential number generator produces numbers in order, like dialing every number from 555-0000 to 555-9999. Both were the technology the TCPA targeted in 1991, when spammers used them to blanket entire area codes. Systems working from a curated list of real contacts use neither method.

Is a predictive dialer an ATDS after Duguid?

Probably not, if it dials from a list of specific phone numbers a human assembled. Most predictive dialers used by sales teams select from pre-loaded contact records, not randomly or sequentially generated numbers. After Duguid, that architecture likely falls outside the ATDS definition. Check your platform's technical documentation and know your state laws, which may define things differently.

Does the Duguid decision apply to text messages?

Yes. The ATDS definition in 47 U.S.C. § 227(a)(1) applies equally to SMS and voice calls. If your texting platform does not use a random or sequential number generator to produce the numbers it texts, it likely is not an ATDS under Duguid. Separate FCC rules and state laws may still require consent for commercial texts independent of the ATDS analysis.

What is the statutory language the Supreme Court interpreted in Duguid?

The Court interpreted 47 U.S.C. § 227(a)(1), which defines an ATDS as equipment with the capacity to store or produce telephone numbers to be called, using a random or sequential number generator, and to dial such numbers. The Court held that "using a random or sequential number generator" modifies both "store" and "produce," not "produce" alone.

Can plaintiffs still sue over autodialer violations after Duguid?

Yes, but the theory is narrower. Plaintiffs must now plausibly allege the defendant used equipment with random or sequential number generation capacity. Courts have dismissed ATDS claims where plaintiffs offered only conclusory allegations that a system was automated without specifying how it generated numbers. Many plaintiffs shifted to prerecorded voice claims and state law claims, which survived Duguid intact.

Does Duguid affect ringless voicemail drops?

Duguid affects only the ATDS prong of TCPA liability. Ringless voicemail drops face separate liability under the prerecorded or artificial voice prohibition in 47 U.S.C. § 227(b)(1)(B). The FCC has treated ringless voicemails as covered under TCPA prerecorded voice rules, and that analysis does not depend on the ATDS definition Duguid addressed.

How did Florida change its autodialer law after Duguid?

Florida's Telephone Solicitation Act originally defined prohibited systems as any automated system for the selection or dialing of telephone numbers, broader than the federal ATDS definition after Duguid. Florida amended the FTSA in May 2023 to add a human intervention element, which narrowed it somewhat. Florida remains one of the most active states for telemarketing litigation, so any operation calling Florida residents needs current state-specific guidance.

What evidence do courts look at to decide if a system is an ATDS after Duguid?

Courts look at the technical architecture of the specific dialing system. Plaintiff attorneys use discovery to get source code, vendor documentation, and call logs. The key question is whether the system generated the numbers it called through a random or sequential process or selected them from a human-curated list. Expert witnesses on both sides often testify about platform architecture.

Are there still TCPA cases being filed after Duguid?

Yes, many. TCPA class action filings did not stop after Duguid. Plaintiff firms shifted toward prerecorded voice claims, DNC violations, consent disputes, and state law claims. Cases involving AI-generated voices are an emerging category. The FCC also still brings enforcement actions. TCPA litigation volume stayed high through 2024 and into 2025 despite the narrowing of the ATDS definition.

What is the penalty for an ATDS violation under TCPA?

The TCPA provides $500 per negligent violation and up to $1,500 per willful or knowing violation. Because these cases often run as class actions covering thousands or millions of calls, exposure can reach tens of millions of dollars even at the minimum statutory rate. There is no cap on aggregate damages in a class action.

Does the FCC's 2015 ATDS ruling still apply after Duguid?

The D.C. Circuit struck down key parts of the FCC's 2015 Declaratory Ruling in ACA International v. FCC in 2018, before Duguid. Duguid then set the binding statutory interpretation. The 2015 ruling's broad capacity-based ATDS definition does not control in court. The FCC has an open rulemaking to update its guidance but has not issued a new ATDS rule as of mid-2026.

Do I need to scrub my call list against the DNC registry even if my dialer is not an ATDS?

Yes. National Do Not Call Registry obligations under 47 U.S.C. § 227(c) and 16 C.F.R. Part 310 apply to telemarketing calls regardless of whether you use an ATDS. DNC violations carry their own per-call damages of $500 to $1,500 and are a separate TCPA liability track from the ATDS definition. Duguid did not touch DNC compliance requirements at all.

Sources

1. U.S. Supreme Court, Facebook, Inc. v. Duguid, 592 U.S. 395 (2021): Supreme Court held 9-0 that an ATDS must use a random or sequential number generator to store or produce numbers; systems dialing from a stored list of specific numbers do not qualify
2. U.S. House of Representatives, Office of the Law Revision Counsel, 47 U.S.C. § 227 (TCPA statutory text): Full text of TCPA including ATDS definition at subsection (a)(1), prohibition on prerecorded voice calls at (b)(1)(B), and DNC private right of action at (c)(5)
3. U.S. Court of Appeals, D.C. Circuit, ACA International v. FCC, 885 F.3d 687 (D.C. Cir. 2018): D.C. Circuit struck down key parts of FCC's 2015 ATDS guidance as arbitrary; established pre-Duguid circuit split context
4. U.S. Court of Appeals, Eleventh Circuit, Borden v. eFinancial LLC, 53 F.4th 1264 (11th Cir. 2022): Eleventh Circuit held that a plaintiff must show the system used random or sequential number generation for the specific calls at issue, not just that the system had theoretical capacity
5. National Conference of State Legislatures, State Telemarketing Laws: State telemarketing laws including Florida FTSA and Oklahoma provisions that define automated dialing systems differently from federal TCPA after Duguid
6. Florida Legislature, Florida Telephone Solicitation Act, Fla. Stat. § 501.059 (as amended 2023): Florida's 2023 amendment to FTSA adding human intervention element, partially narrowing automated dialing system definition
7. FTC, Telemarketing Sales Rule, 16 C.F.R. Part 310: FTC Telemarketing Sales Rule DNC provisions applying to outbound telemarketing calls regardless of ATDS status
8. FCC, 47 C.F.R. § 64.1200, Delivery restrictions: FCC rule requiring prior express written consent for telemarketing calls and texts, a requirement that applies regardless of ATDS classification after Duguid