How to argue no autodialer was used as a TCPA defense

Last updated 2026-07-11

What does the TCPA actually say about autodialers?

The statute defines an automatic telephone dialing system in 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." ^[1] That sentence, written in 1991, is the whole definition Congress gave. Every ATDS fight in court comes back to parsing those exact words.

For almost thirty years, courts read the definition wide. Some circuits said any equipment that could dial automatically qualified, whether or not it actually used a random or sequential number generator. Plaintiffs loved that reading. Defendants hated it.

Then in April 2021, the Supreme Court settled the circuit split in Facebook, Inc. v. Duguid. The Court held that the phrase "using a random or sequential number generator" modifies both "store" and "produce." To qualify as an ATDS, the device has to use a random or sequential number generator to do one of those two things. Dialing from a fixed list of specific numbers does not meet that bar. ^[2]

That one ruling wiped out a huge category of exposure for outbound sales teams running predictive dialers loaded with their own contact lists. It did not end TCPA liability. Consent, the Do Not Call rules, and state mini-TCPAs all still apply. But the ATDS element became genuinely winnable.

What did Facebook v. Duguid actually decide, and why does it matter?

Noah Duguid sued Facebook over automated security-alert texts sent to a number he never gave the company. The Ninth Circuit found Facebook's notification system could qualify as an ATDS because it stored and dialed numbers automatically. The Supreme Court reversed, unanimously. ^[2]

Justice Sotomayor wrote the opinion. The equipment has to use a random or sequential number generator to store or produce the numbers dialed. Facebook's system stored specific user-account phone numbers, not numbers spit out by a randomizing function. That distinction killed the ATDS claim.

Here is the practical read. Predictive dialers, power dialers, and preview dialers that work from a CRM-exported list of real customer or prospect numbers almost certainly do not qualify as ATDS systems under the current federal standard. ^[3] Those numbers are specific. Nothing randomly or sequentially generated them.

The ruling binds all federal courts. Some state courts and state statutes use different tests, so this defense is not a total shield everywhere. Florida, Washington, and a few others have their own autodialer definitions that can reach further. For federal TCPA claims, Duguid controls.

How do you actually build the 'no ATDS' defense in practice?

Winning this argument is part legal, part technical. Judges and juries will not take your word for how your dialer works. You need documentation that predates the complaint.

Start with your dialing platform vendor. Get a written technical description of how the system selects and dials numbers. You want it to say, in plain terms, that the system dials from a list of specific telephone numbers supplied by the user and does not use a random or sequential number generator to produce or store those numbers. Many vendors (Five9, NICE inContact, Twilio, and similar platforms) can provide this. If yours cannot, that is a red flag worth fixing now.

Next, preserve your campaign configuration files. The actual list you imported. The dialing order you set. The timestamp of the upload. This shows the numbers were specific, human-selected contacts, not machine-generated targets.

Write down your calling workflow. A one-page internal memo describing how reps or campaign managers pull a list from your CRM, load it into the dialer, and launch campaigns is more useful than you might think. It creates a contemporaneous record of human involvement in number selection.

Using click-to-call or preview dialing where a human clicks to start each call? Document that too. Courts have consistently found that systems requiring human initiation for each call do not qualify as ATDS. ^[3]

For teams running cold calling campaigns, all of this should be standard practice anyway. Think of it as the technical side of your compliance stack.

LeadCompliant's free compliance kit includes a dialer documentation checklist you can hand straight to your vendor or IT contact to get the right language on file.

What is a random or sequential number generator, exactly?

This sounds technical, and it is. A random number generator (RNG) produces telephone numbers without reference to any pre-existing list. Old-school robocallers used these to blast every possible number in an area code. A sequential number generator does the same thing in order: 555-0001, 555-0002, and on down the line.

A CRM export is neither of those things. Pull a list of 5,000 leads from Salesforce and load them into a dialer, and those 5,000 numbers came from real people who submitted a form, bought something, or were sourced through a data provider. No algorithm generated them randomly or sequentially. They are specific, identified individuals.

This distinction is what defense counsel uses to defeat ATDS claims after Duguid. The argument runs like this: "Your Honor, plaintiff must show our client's equipment used a random or sequential number generator to store or produce these numbers. The record shows the opposite. Our system dialed a fixed list of known contacts. That is not an ATDS under 47 U.S.C. § 227(a)(1) as interpreted in Facebook v. Duguid."

Some plaintiffs try to argue that any software capable of generating numbers randomly, even if it was never used that way for the calls at issue, qualifies. Courts have largely rejected that after Duguid. The question is whether the system used a random or sequential number generator for the calls in dispute, not whether such a function sits unused somewhere in the codebase. ^[3]

Does this defense work for text messages, more than phone calls?

Yes. The TCPA's ATDS restriction covers calls and texts to cell phones equally under 47 U.S.C. § 227(b)(1)(A). ^[1] If your SMS platform sends messages from a fixed contact list without using a random or sequential number generator, the same Duguid framework applies.

The wrinkle for text message marketing is that many SMS platforms, especially those using short codes or 10DLC, have automation features that look more ATDS-like to some courts. The question stays the same: does the system use a random or sequential number generator to store or produce the numbers it texts?

Platforms like Klaviyo, Attentive, or Postscript that send SMS only to opt-in subscriber lists almost certainly do not qualify as ATDS systems. You still need documentation from those vendors confirming the architecture. A plaintiff's attorney will subpoena your vendor records. You want those records saying the right thing before the subpoena arrives.

One more thing. The DNC rules under 47 U.S.C. § 227(c) apply to text messages too, regardless of whether an ATDS was used. Winning the ATDS argument does not end the lawsuit if the person was on a do not call list. These defenses work together. They are not substitutes for each other.

What evidence do courts look for when evaluating an ATDS defense?

Courts weigh a mix of technical evidence and factual evidence about how the calls actually got made.

On the technical side, courts want to know how the software selects numbers. Does any component of the system generate numbers randomly or sequentially, or does it only dial numbers from a pre-loaded list? Vendor documentation, source code descriptions, and expert testimony all come into play in bigger cases.

On the factual side, courts look at whether a human being was involved in selecting and starting calls. Preview dialing systems where an agent clicks "call" are strong for defendants. Fully automated campaigns that run overnight without human involvement are weaker, even when the list was compiled by hand, because plaintiffs will argue the campaign "function" is automated.

The Eleventh Circuit in Glasser v. Hilton Grand Vacations (2020, decided before Duguid but consistent with it) held that a system requiring a human to initiate each call is not an ATDS. ^[3] That case is still good law and useful precedent for preview-dialer defendants.

Courts also look at call volume and campaign structure. Send 2 million texts in 48 hours and a judge may doubt the process was truly human-directed, even if the technical ATDS definition is not met. Scale matters for credibility even when it does not change the legal standard.

What are the limits of the no-ATDS defense?

Even when it works perfectly, this defense only defeats the ATDS-based claim under 47 U.S.C. § 227(b). The TCPA has other teeth.

The Do Not Call provisions at 47 U.S.C. § 227(c) apply to any telephone solicitation, whether or not an autodialer was used. ^[1] If you cold call someone whose number is on the National DNC Registry and you lack a prior business relationship or written consent, that is a separate violation. Winning the ATDS argument does not touch it.

Prerecorded messages carry their own ban under 47 U.S.C. § 227(b)(1)(B) that is not tied to the ATDS definition. Use a prerecorded or artificial voice on a call to a residential landline without consent and that is a separate violation, even if you dialed by hand.

State laws stack another layer on top. Florida's FTSA, Washington's CEMA, and California's statutes may define autodialers more broadly than the federal standard does after Duguid. A defendant who wins the federal ATDS argument can still face state-law exposure. ^[4]

And if the calls or texts involved prerecorded messages to cell phones, or if there were DNC violations, those claims survive the ATDS defense whole. The no-ATDS argument is powerful but narrow. Build it alongside a consent documentation program, never instead of one.

For a sense of what happens when these claims reach settlement, the cash app tcpa class action settlement and credit one tcpa settlement show what is at stake when defendants cannot win on the merits.

How does the FCC's interpretation affect this defense?

The FCC has issued guidance on ATDS definitions over the years, and its position has moved. In a 2015 Declaratory Ruling, the FCC took an expansive line, saying equipment with the capacity to function as an ATDS qualified, even if that capacity was not used for the calls at issue. ^[5] The D.C. Circuit largely vacated that reading in ACA International v. FCC (2018), calling the FCC's definition unworkably broad. ^[5]

After Duguid, the FCC has not issued a definitive new order restating the ATDS definition to match the Supreme Court's ruling. The Commission has ongoing TCPA proceedings, but as of mid-2025, no FCC order supersedes or meaningfully narrows Duguid for federal purposes.

What that means for defendants: the Supreme Court's statutory interpretation in Duguid controls. You do not need an FCC order to invoke it. Courts apply Duguid straight from the statute.

Watch for FCC rulemaking, though. The Commission keeps authority to clarify the ATDS definition, and future orders could shift the ground again. Subscribing to FCC consumer and enforcement updates (fcc.gov) is cheap insurance for compliance teams.

Also worth knowing: the FCC's one-to-one consent rule, adopted in December 2023 and set to take effect in January 2025 before it was paused pending litigation, targeted consent aggregation practices. It was not about ATDS definitions, but it signals the agency is tightening TCPA enforcement more broadly. ^[6]

What does this defense cost to run, and when should you settle instead?

Nobody has published a clean study of TCPA defense costs broken out by defense theory, so I will be honest about the range based on publicly reported case data.

A single-plaintiff TCPA case that goes through early motion practice (motion to dismiss, limited discovery, summary judgment on the ATDS issue) usually costs a defendant somewhere between $50,000 and $200,000 in legal fees before any settlement. Class actions run into the millions. The ATDS defense, if strong, belongs at the motion to dismiss or early summary judgment stage to cut those costs.

If your dialer documentation is clean and your vendor can give a credible declaration, a motion to dismiss or early summary judgment on the ATDS issue has a real shot after Duguid. That is the bet you want to make. If the documentation is weak, or you used a platform with any randomization feature in its codebase, the argument gets expensive and uncertain fast.

When to settle: if the ATDS argument has obvious holes and there are DNC violations or consent problems, settling early is usually cheaper. Defendants who fight on weak ATDS grounds while sitting on clear DNC violations tend to end up worse off than those who resolved claims quickly.

The statutory damages under 47 U.S.C. § 227(b)(3) are $500 per violation for negligent violations and $1,500 for willful ones. ^[1] In a class action, those numbers multiply by the size of the class. A modest class of 10,000 members at $500 per call is $5 million before trebling.

How should small outbound teams document their dialer setup before any lawsuit?

Most small teams never think about this until a demand letter arrives. By then, the scramble to reconstruct documentation looks exactly as bad as it is.

Here is what a reasonable pre-lawsuit documentation package looks like:

1. A letter or technical declaration from your dialing platform vendor stating that the system does not use a random or sequential number generator to produce or store telephone numbers, and that all numbers dialed come from a pre-existing list supplied by the customer.

2. Your standard operating procedure for campaign setup: who pulls the list, from what source, how it gets uploaded, and how the campaign launches. One page is enough.

3. Screenshots or export records of a representative campaign showing the list source (CRM, lead import, etc.) and the manual upload step.

4. If you use preview or click-to-dial, a description of how the agent starts each call (agent must click, system does not auto-advance without action, etc.).

5. Any consent records for the numbers called. Even if you win the ATDS argument, consent records are the backup defense.

Store all of this in a compliance folder outside counsel can reach if needed. Review it whenever you change dialers or platforms. The LeadCompliant compliance kit has a template for this documentation set that you can adapt to your vendor's specific platform.

For teams that need to check which numbers to call, tools like the mobile phone do not call list checker can layer DNC scrubbing into this same process, so your documentation covers both the ATDS defense and DNC compliance at once.

What are the strongest and weakest fact patterns for this defense?

Knowing where this defense wins and where it struggles helps you size up your own exposure honestly.

Fact pattern	Strength of ATDS defense	Why
Preview dialer, human clicks each call	Very strong	Courts have found human initiation defeats ATDS [3]
Predictive dialer, fixed CRM list, no RNG in system	Strong post-Duguid	No random/sequential generation; Duguid standard met [2]
Predictive dialer with "dial mode" that can generate test numbers	Moderate	Plaintiff may argue RNG capacity exists even if unused
Platform with marketing materials calling it an "autodialer"	Weak	Plaintiff's counsel will cite vendor's own language
Mass text blast to uploaded opt-in list, SMS API	Strong if vendor confirms no RNG	Same Duguid analysis applies to SMS [1]
Ringless voicemail drops	Uncertain	FCC and courts split on whether RVMs are "calls"; ATDS question is secondary
Offshore call center using VOIP softphone, manual dialing	Very strong	Pure manual dialing is not ATDS regardless of Duguid

The weakest cases are the ones where the vendor's own documentation or marketing calls the system an "autodialer" or "ATDS." Plaintiff's counsel will put that brochure in front of the judge and ask why you are claiming otherwise. If your vendor uses that language, get a clarifying technical statement from them now, or switch vendors and document the change.

The strongest cases are pure preview dialers with agent-initiated calls and zero randomization features anywhere in the platform. Those cases often get dismissed at the pleading stage after Duguid, especially in the Eleventh and Eighth circuits.

Frequently asked questions

Does Facebook v. Duguid apply to all federal TCPA cases?

Yes. Facebook, Inc. v. Duguid (2021) is a Supreme Court decision interpreting 47 U.S.C. § 227(a)(1), the federal TCPA statute. It applies in all federal courts nationwide. State courts applying state-law versions of the TCPA may use different standards, so you need to check the specific state statute if state claims are also in play.

Can I still be sued under the TCPA if I win the no-ATDS argument?

Yes. The ATDS element only governs one type of claim under 47 U.S.C. § 227(b). Separate claims under the Do Not Call provisions of 47 U.S.C. § 227(c) require no autodialer at all. Call someone on the National DNC Registry without a valid exemption and that violation survives the ATDS defense entirely.

What is the difference between a predictive dialer and an ATDS after Duguid?

A predictive dialer that works only from a pre-loaded list of specific phone numbers, without using any random or sequential number generator to produce or store those numbers, is not an ATDS under Duguid. The deciding question is the number-generation method, not the automation level of the dialing itself. Get your vendor to confirm this in writing.

Do state TCPA laws use the same autodialer definition as the federal statute?

Not always. Florida's FTSA, Washington's CEMA, and California's statutes each carry their own definitions that may reach further than the federal post-Duguid standard. Winning the federal ATDS argument does not automatically defeat a parallel state-law ATDS claim. Review the specific state statute wherever you make calls.

Does using a short code or 10DLC number make my texts more likely to be treated as ATDS?

Not inherently. The ATDS analysis under Duguid turns on whether a random or sequential number generator stored or produced the recipient numbers, not on the sending number format. Short codes and 10DLC are carrier registration categories. That said, short-code mass texting invites closer scrutiny, so vendor documentation of your list-based architecture matters more, not less, for those campaigns.

What evidence should I preserve immediately if I receive a TCPA demand letter?

Preserve your campaign configuration files, the phone number list you used, your dialing platform's technical documentation, any vendor contracts or specifications, consent records for the numbers called, and your calling logs showing timestamps and durations. Issue a litigation hold notice to anyone with access to these systems. Do not delete or overwrite anything.

Is ringless voicemail considered use of an ATDS under the TCPA?

This is genuinely unsettled. Some courts have found ringless voicemail drops are not 'calls' under the TCPA; others disagree. The FCC has not issued a definitive ruling. The ATDS question for RVMs is therefore secondary to the threshold question of whether they are calls at all. Treat RVMs as high-risk until courts or the FCC resolve the split.

How much does it cost to defend a TCPA ATDS claim through summary judgment?

Precise published data is scarce, but single-plaintiff cases that reach early summary judgment on the ATDS issue typically involve $50,000 to $200,000 in defense fees based on general TCPA litigation reporting. Class actions run much higher. A clean ATDS defense raised at the motion-to-dismiss stage can cut those costs sharply if the technical documentation is solid.

What is the statutory penalty per call under the TCPA?

Under 47 U.S.C. § 227(b)(3), the minimum statutory damages are $500 per negligent violation and $1,500 per willful or knowing violation. Courts can award up to $1,500 per call or text. In a class action, these amounts multiply by the number of class members, which is why TCPA settlements often reach seven or eight figures even for short campaigns.

Can I use the no-ATDS defense for a prerecorded message claim?

Not directly. Prerecorded or artificial voice calls to residential lines are prohibited under a separate provision, 47 U.S.C. § 227(b)(1)(B), that requires no ATDS. For cell phone calls, though, the ATDS and prerecorded-voice restrictions both live in 47 U.S.C. § 227(b)(1)(A), so defeating the ATDS element also defeats that sub-claim. Check which provision the plaintiff is actually citing.

Does human oversight of an automated campaign defeat the ATDS argument?

Human oversight alone is not enough. What matters is whether a human initiates each individual call, not whether humans supervise the campaign from above. Preview dialers where an agent clicks to call are strong. Fully automated overnight campaigns where no human action triggers each dial are weaker, even if a manager set up the campaign manually earlier in the day.

How do I find out if my dialing platform uses a random or sequential number generator?

Ask your vendor directly and request a written technical statement. Put the question to them plainly: 'Does your system use a random or sequential number generator to store or produce the telephone numbers dialed during a campaign?' Most legitimate business dialer vendors can answer clearly. If they cannot, that ambiguity is itself a compliance risk you should resolve before your next campaign.

Does the no-ATDS defense help if I am on the DNC registry side of a lawsuit?

No. Do Not Call claims under 47 U.S.C. § 227(c) and FCC regulations at 47 C.F.R. § 64.1200 are completely independent of whether an ATDS was used. A company that manually dials numbers on the National DNC Registry without a valid exemption still faces DNC liability. The ATDS defense and DNC compliance are separate tracks.

Sources

1. Legal Information Institute (Cornell Law School), 47 U.S.C. § 227 (TCPA statute text): TCPA defines ATDS as equipment using a random or sequential number generator to store or produce numbers; statutory damages are $500 to $1,500 per violation
2. Supreme Court of the United States, Facebook, Inc. v. Duguid, 592 U.S. 395 (2021): Supreme Court held an ATDS must use a random or sequential number generator to store or produce numbers; dialing from a fixed stored list does not qualify
3. U.S. Court of Appeals, Eleventh Circuit, Glasser v. Hilton Grand Vacations Co. (2020): Eleventh Circuit found that a system requiring a human to initiate each call is not an ATDS under the TCPA
4. Florida Senate, Florida Telephone Solicitation Act, Fla. Stat. § 501.059: Florida's FTSA uses an autodialer definition that may be broader than the post-Duguid federal standard, creating independent state liability
5. U.S. Court of Appeals, D.C. Circuit, ACA International v. FCC, 885 F.3d 687 (2018): D.C. Circuit vacated the FCC's 2015 expansive ATDS definition as unworkably broad
6. Federal Trade Commission, National Do Not Call Registry: FTC administers the National DNC Registry; DNC violations apply regardless of ATDS use
7. Electronic Code of Federal Regulations, 47 C.F.R. § 64.1200 (FCC TCPA implementing regulations): FCC regulations implementing TCPA including DNC requirements that apply independent of ATDS use
8. Washington State Legislature, Commercial Electronic Mail Act (CEMA), RCW 19.190: Washington's CEMA contains electronic communications restrictions with definitions that may differ from federal post-Duguid ATDS standard