ATDS definition under the TCPA: what actually counts in 2025

Last updated 2026-07-10

What is an ATDS under the TCPA, and why does the definition matter so much?

The Telephone Consumer Protection Act, 47 U.S.C. § 227, restricts calls and texts made with an automatic telephone dialing system, commonly called an ATDS or autodialer. If your equipment qualifies as an ATDS, you need prior express consent before you dial a cell phone. Get that wrong and each violation runs $500 to $1,500. ^[1]

The statute defines an ATDS 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] Federal courts fought over that one sentence for more than a decade. Billions of dollars rode on the answer across class actions.

Why does the exact wording matter? Because the gap between "our dialer uses a random number generator" and "our dialer calls numbers from a pre-loaded list" decides whether the TCPA even applies. If your system dials from a fixed list with no random or sequential generation, the majority reading after Facebook v. Duguid puts you outside the ATDS definition. That's a big deal for most outbound sales teams. They aren't calling random numbers. They're working specific lead lists.

The law here is still genuinely unsettled, and that should make you cautious. The FCC has issued no post-Facebook ATDS rules as of mid-2025. Several circuits are still grinding through edge cases. Plaintiffs' lawyers are creative. Knowing the definition is step one. Knowing where the live wires still are is step two.

What did the Supreme Court actually decide in Facebook v. Duguid?

Facebook v. Duguid, 592 U.S. 395 (2021), is the controlling federal authority on the ATDS definition. ^[2] Noah Duguid sued Facebook, claiming its automatic login-notification texts violated the TCPA. Facebook argued its system, which dialed from a stored list of specific numbers, was not an ATDS because it didn't use a random or sequential number generator. The Court agreed, 9-0.

Justice Sotomayor wrote for the Court: "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." ^[2] The Court applied the rule of the last antecedent, holding that the phrase "using a random or sequential number generator" modifies both "store" and "produce."

The practical result: a dialer that calls numbers pulled from a CRM or lead list, with no random or sequential generation happening during that process, does not meet the statutory definition. That covers the vast majority of modern predictive dialers and power dialers used in outbound sales.

What the Court left open matters too. It did not define "capacity." Present capacity? Potential capacity? It didn't say. It did not address systems that have a random-number-generation feature buried in their code even if nobody ever turns it on. Those gaps are where post-Facebook litigation has piled up.

How did courts and the FCC define ATDS before Facebook v. Duguid?

Before 2021, the definition was a mess. That history explains why so many settlements, some enormous, closed in that era.

The FCC's 2015 Omnibus Order took an expansive view. Equipment counted as an ATDS if it had the "potential functionality" to dial randomly or sequentially, even if that capability was never used. ^[3] Under that reading, almost any modern smartphone could theoretically qualify, never mind a sophisticated sales dialer. Courts in the Ninth Circuit largely adopted this broad view, which is one reason California became such fertile ground for TCPA class actions against tech companies.

The D.C. Circuit threw out parts of the 2015 order in ACA International v. FCC (2018), finding the FCC's capacity interpretation was arbitrary. ^[4] That created a split. Some circuits kept the broad reading. Others narrowed it. Between 2018 and 2021, where you got sued mattered enormously. A defendant in the Ninth Circuit faced far more exposure than one in the Eleventh.

Facebook v. Duguid ended the circuit split on the core question. But it did not reinstate any particular FCC order, and the FCC still has not issued new ATDS guidance under the narrower standard. That regulatory gap is real.

For a look at what broad-era exposure meant in practice, see what happened to companies like UnitedHealthcare, whose case shows how ATDS allegations combine with consent failures to produce eight-figure exposure: UnitedHealthcare TCPA case.

Does a predictive dialer or power dialer count as an ATDS after Facebook?

This is the question most outbound sales teams actually need answered.

A pure predictive dialer that pulls numbers from a database and dials them in sequence, without using a random or sequential number generator to create or select those numbers, almost certainly does not meet the post-Facebook ATDS definition. That's the honest answer most compliance lawyers will give you right now. ^[2]

But "almost certainly" is doing real work in that sentence. Here's where risk persists.

First, some dialers carry legacy code or features that technically include random number generation, even when disabled. Plaintiffs argue "capacity" still covers potential functionality. Courts have not uniformly resolved this post-Facebook. The Ninth Circuit and several district courts have generally required that the random or sequential generation feature actually be used, not merely present. ^[5] Litigation on this point continues.

Second, the voiceblast and ringless voicemail question is separate. Prerecorded voice messages carry their own TCPA restrictions under 47 U.S.C. § 227(b)(1)(A) that don't require the ATDS element at all. If you're dropping prerecorded messages, the ATDS debate is beside the point for your liability.

Third, the FCC has signaled it may issue new guidance. A 2023 FCC rulemaking notice asked for comment on ATDS-related issues, so the ground could shift. ^[6]

Here's the bottom line. If you run a list-based outbound dialer with no random number generation features, you're on much safer ground post-Facebook than pre-2021. You're not risk-free.

Dialer Type	Random/Sequential Generator Used?	ATDS After Facebook?	Key Risk
Predictive dialer (list-based)	No	Likely No	Buried capacity argument
Power dialer (click-to-call from CRM)	No	Almost certainly No	Prerecorded message rules still apply
True robocaller (random number generation)	Yes	Yes	Core TCPA violation
Hybrid system with RNG feature (even if off)	Potentially	Disputed	Capacity argument; circuit-dependent
VOIP with auto-sequence from imported list	No	Likely No	State law may still apply

What is the "capacity" question, and why do lawyers still fight about it?

Even after Facebook, plaintiffs argue that "capacity" in the statute means something broader than what the equipment currently does. The argument goes like this: if the software could be modified to add random number generation, or if a feature sits in the codebase but is turned off, the equipment still has the "capacity" to function as an ATDS.

The Ninth Circuit addressed this in Borden v. eFinancial, LLC (2022), holding that a system must actually use a random or sequential number generator to qualify as an ATDS. ^[5] That helps defendants. But district courts around the country have reached different conclusions on specific dialer architectures, and the FCC hasn't weighed in with binding post-Facebook guidance.

What this means for your compliance review is simple. Get documentation of how your dialing system actually works. Get a written technical description from your vendor. Ask specifically whether any component of the system ever uses a random or sequential number generator for any purpose. If the vendor can't answer that question clearly, that's a red flag.

The tcpa-news section of this site tracks court decisions on ATDS capacity questions as they come out.

What is the definition of a "current customer" under the TCPA, and does it change ATDS rules?

The phrase "current customer" lives in the TCPA's established business relationship (EBR) framework, which applies differently depending on the type of call you're making.

For calls to residential landlines using a prerecorded message, the TCPA and FCC rules create an EBR exemption. If someone is your current customer (meaning an ongoing relationship, more than a single past transaction), you may call them with a prerecorded message without prior express consent in some circumstances. ^[7] The FCC has defined EBR to include a relationship based on a prior purchase, transaction, or inquiry within the preceding 18 months, or a business relationship the consumer has not yet terminated. ^[3]

Here's what most people miss. The EBR and "current customer" concepts do not exempt you from the ATDS rules for cell phones. Under 47 U.S.C. § 227(b)(1)(A), you need prior express consent to call a cell phone with an ATDS or prerecorded voice, period. There is no current-customer exception for cell phone calls made with an ATDS. ^[1] The FCC's 2012 order explicitly removed the EBR exemption for prerecorded calls to cell phones. ^[8]

So "current customer" matters a lot for landline prerecorded calls. It matters somewhat for internal DNC list requirements (you generally handle a DNC request from a current customer differently than one from a cold prospect, though you must stop calling anyone who asks). And it matters essentially nothing for ATDS calls to cell phones.

If you're calling current customers on their cell phones with any equipment that could be characterized as an ATDS, you still need their prior express written consent. The relationship doesn't save you.

One nuance: the TCPA has a narrow healthcare exception under the FCC's 2015 and later orders for providers calling patients. It's specific to healthcare and carries its own requirements. It is not a general current-customer carve-out.

What types of calls and texts does the ATDS definition actually cover?

The ATDS definition in 47 U.S.C. § 227(b)(1) covers two main scenarios: calls to cell phones and calls to residential lines. ^[1]

For cell phones, you cannot use an ATDS or prerecorded voice without prior express consent. This covers both voice calls and text messages. The FCC confirmed in 2003 that SMS text messages are "calls" under the TCPA, and that ruling has held up consistently. ^[7]

For residential landlines, the prerecorded voice restrictions apply (consent or EBR required), but purely ATDS-dialed calls without a prerecorded message to a landline are treated differently. Many telemarketing calls to landlines fall under the national DNC rules rather than the ATDS provision.

Emergency calls are exempt from the ATDS restrictions. So are calls by or on behalf of a tax-exempt nonprofit, calls to anyone who gave prior express consent, and a few other narrow carve-outs. ^[1]

For text messaging, the relationship between the ATDS definition and consent is where most of the current compliance action sits. If you run a text marketing program, read our guide to text message marketing for the full picture. Even post-Facebook, SMS platforms that use any sequenced sending logic draw scrutiny.

The albertsons-safeway-tcpa-settlement case is a useful example of how text message campaigns run into TCPA trouble even when companies believe their consent systems are solid.

How does the FCC's ongoing rulemaking affect the ATDS definition today?

The FCC is the agency Congress charged with implementing the TCPA, and it periodically issues orders and rules that shape how courts apply the statute. After Facebook v. Duguid narrowed the definition, the FCC's existing ATDS guidance (mainly from 2003, 2012, and 2015) is partly inconsistent with the Supreme Court's ruling. ^[3][6]

In 2023, the FCC issued a Notice of Proposed Rulemaking on several TCPA issues, including consent and lead generation. ^[6] It has not yet issued a full post-Facebook ATDS definition order. That leaves compliance professionals in a gap. The Supreme Court has set the floor, but the FCC guidance that courts also lean on hasn't been fully updated.

Why does FCC rulemaking matter even after a Supreme Court decision? Because the FCC's rules can go beyond the statute's minimum (as long as they don't conflict), and the FCC can clarify ambiguities the Court left alone, like the "capacity" question and how specific dialer architectures get classified. Courts also give the FCC deference on technical telecommunications matters.

The practical implication: stay tuned. A new FCC ATDS order in the next year or two could either cement the narrow Facebook reading or add restrictions that catch platforms your current counsel called fine. Build a compliance review calendar, not a one-time analysis.

What are the TCPA penalties if your equipment is found to be an ATDS?

The statutory penalty for a TCPA violation is $500 per call or text. ^[1] If the violation is willful or knowing, a court can treble that to $1,500 per call or text. There's no cap on the number of violations in a class action.

Take a typical outbound campaign sending 100,000 texts. A finding of ATDS use without consent translates to $50 million in statutory damages at the base rate, or $150 million if trebled. That math is why TCPA class actions settle for serious money. The credit-one-tcpa-settlement and cash-app-tcpa-class-action-settlement cases both show what those numbers look like in practice.

The good news post-Facebook: if your equipment genuinely doesn't meet the ATDS definition, plaintiffs have to clear a higher bar to sue. Many cases that would have been filed under the pre-2021 broad reading simply don't get filed now, because the ATDS element is harder to plead. Several district courts have granted motions to dismiss where plaintiffs couldn't allege specific facts about random or sequential number generation. ^[5]

The bad news: TCPA plaintiffs' lawyers adapt. Complaints now include detailed allegations about dialer architecture. Some depose a defendant's engineers as a first move. The shift has raised the cost of early defense even when you ultimately win.

For teams building outbound compliance programs from scratch, LeadCompliant's free compliance kit includes a dialer-classification worksheet that helps you document why your equipment does or doesn't qualify as an ATDS. That's exactly the kind of contemporaneous record that helps in early motion practice.

How should outbound sales teams actually reduce ATDS risk right now?

Get written technical documentation from your dialer vendor. This is the single most practical thing you can do. You want a statement, ideally with a technical description of the system architecture, confirming that the system does not use a random or sequential number generator to store or produce telephone numbers. Keep that document. If you switch vendors, get it again.

Keep detailed consent records. Even if your equipment isn't an ATDS, you'll still face consent-based claims if you call cell phones for telemarketing. Prior express written consent (the higher standard for telemarketing calls and texts) requires a clear disclosure and an unambiguous agreement. Document when and how you obtained each consent. ^[8]

Honor revocations immediately. The FCC's 2024 one-to-one consent work and existing guidance both make clear that consumers can revoke consent at any time by any reasonable means, and that revocation must be honored within a short timeframe. ^[6] A system that doesn't scrub revocations quickly is a liability regardless of the ATDS question.

Scrub against the national DNC registry. The ATDS definition is separate from DNC compliance. Even if your dialer is not an ATDS, you cannot call numbers on the national DNC list for telemarketing without a prior business relationship or written consent. ^[10] See the how-to-stop-robocalls guide for a consumer-side view that also explains the rules callers have to follow.

For teams running text campaigns, the full picture of SMS obligations goes well beyond ATDS classification. Our guide to text messaging marketing covers opt-in language, opt-out handling, and carrier-level requirements that operate independently of the ATDS question.

And account for state law. California, Florida, Washington, and several other states have their own autodialer or robocall laws that may apply even when federal TCPA exposure is low. The post-Facebook federal safe harbor doesn't reach state claims.

Which court cases after Facebook v. Duguid show where the ATDS lines are drawn today?

A few post-2021 decisions are worth knowing by name because they show how courts apply the Facebook standard to real dialer systems.

Borden v. eFinancial, LLC (9th Cir. 2022): The Ninth Circuit, historically the most plaintiff-friendly circuit on TCPA issues, held that a system must actually use a random or sequential number generator, not merely have the potential to do so. ^[5] That was a real win for defendants and brought the Ninth Circuit in line with the Supreme Court's reasoning.

Multiple district court decisions post-Facebook have dismissed ATDS claims where plaintiffs offered only conclusory allegations about autodialer use, without specific facts about random or sequential number generation. This raised the pleading bar meaningfully.

Other cases have tested whether specific platforms, including some CRM-integrated dialers and marketing automation tools, cross the ATDS line. Results have been mixed and fact-specific. The outcome usually turns on the exact architecture and how well each side documents it.

The truist-bank-tcpa-class-action-settlement case is a practical example of how large financial institutions handle TCPA ATDS claims in settlement, and the kaiser-tcpa-settlement-claim-deadline case shows how healthcare-sector ATDS allegations have played out.

Nobody has a clean dataset on ATDS dismissal rates post-Facebook across all districts. The closest aggregated analysis is from the WebRecon litigation database, which tracks TCPA filing trends. Their data shows TCPA suit filings dropped notably in 2021 and 2022 following Facebook, then trended back up as plaintiff firms adapted their complaints. The post-Facebook landscape rewards defendants with good documentation and punishes those who can't explain their technology.

Frequently asked questions

Does the ATDS definition cover text messages or only phone calls?

Yes, it covers texts. The FCC ruled in 2003 that SMS text messages are "calls" under the TCPA, and courts have consistently applied the ATDS restrictions to text message campaigns. If your platform uses a random or sequential number generator to send texts, you need prior express written consent just as you would for a voice call. The Facebook v. Duguid ruling applies equally to texts and calls.

What is the definition of a current customer under the TCPA?

The FCC defines a current customer under the established business relationship framework as someone with an ongoing relationship based on a prior purchase or transaction within the last 18 months, or an active business relationship not yet terminated. This matters for landline prerecorded call exemptions. It does NOT exempt you from ATDS consent requirements for cell phones. You still need prior express written consent to call a current customer's cell phone with an autodialer.

Is a predictive dialer an ATDS after the Facebook ruling?

A list-based predictive dialer that does not use a random or sequential number generator is very likely not an ATDS under the post-Facebook standard. The Ninth Circuit's 2022 Borden v. eFinancial decision confirmed the system must actually use random or sequential number generation, not merely have the potential. Get written confirmation from your vendor that no such feature exists in your system's architecture and keep that documentation.

What happens if my dialer has a random number generation feature that's turned off?

This is the live dispute. Plaintiffs argue "capacity" means potential capability, so a buried or disabled RNG feature still qualifies the equipment as an ATDS. Most post-Facebook courts have rejected that argument, requiring actual use of the feature. But it's circuit-dependent and fact-specific. If your system has any RNG feature, even disabled, get legal advice about your specific architecture and consider disabling or removing the feature at the code level.

Do I need ATDS consent if I'm calling my own customers?

For cell phones, yes. The TCPA's ATDS restriction for cell phones has no current-customer exception. You need prior express consent regardless of the relationship. For telemarketing calls, you need prior express written consent. The established business relationship exemption applies only to prerecorded voice calls to residential landlines, not to ATDS calls to cell phones. Many companies get this wrong and pay for it.

What is prior express written consent under the TCPA?

Prior express written consent, required for telemarketing calls and texts made with an ATDS or prerecorded voice, means a written agreement that clearly discloses the caller's identity and that the consumer will receive autodialed or prerecorded calls or texts, and that the consumer's signature is not a condition of any purchase. It must be clear and conspicuous. The FCC's 2012 order set this standard, effective October 2013.

How much can a TCPA ATDS violation cost per call?

The statute sets $500 per violation, trebled to $1,500 for willful or knowing violations. There's no per-campaign cap. In a class action covering 100,000 calls, exposure is $50 million at base rate or $150 million trebled. Courts have discretion on whether to treble but routinely do so when companies ignore repeated consumer complaints or failed to keep consent records.

Does the TCPA ATDS definition apply to ringless voicemail?

Ringless voicemail (RVM) is regulated under the prerecorded voice message provision of 47 U.S.C. § 227(b)(1), not necessarily the ATDS provision. The FCC has treated RVMs as calls subject to TCPA restrictions, though formal rulemaking on this is not fully settled as of mid-2025. You need consent to drop a prerecorded voicemail to a cell phone regardless of whether an ATDS is involved.

Can state autodialer laws apply even if my equipment isn't an ATDS under federal law?

Yes. Florida's FTSA, California's CIPA, and several other state laws have their own definitions of automated or autodialed calling equipment, which may be broader than the federal post-Facebook standard. A dialer that's not an ATDS under federal law can still trigger state liability. Florida's FTSA in particular has generated significant litigation against companies who thought they were safe after the Facebook ruling.

Has the FCC updated its ATDS guidance after Facebook v. Duguid?

Not fully as of mid-2025. The FCC's primary ATDS guidance still comes from its 2003 and 2015 orders, which predate the Supreme Court's ruling and are partly inconsistent with it. The FCC issued a 2023 NPRM on related consent issues but hasn't released a post-Facebook ATDS definition order. This regulatory gap means you're operating on Supreme Court precedent plus case-by-case circuit court decisions.

What documentation should I keep to defend an ATDS claim?

Keep a written technical description from your dialer vendor confirming it doesn't use a random or sequential number generator. Document every consent you collected, including the timestamp, method, and exact disclosure language shown to the consumer. Keep DNC scrub records with dates. If you receive revocation requests, document when you received them and when you stopped calling. This paperwork wins motions to dismiss and discourages class cert.

Do the TCPA ATDS rules apply to B2B calls to business cell phones?

Yes. The TCPA's ATDS restrictions apply to any call to a cellular telephone number regardless of whether the recipient is a business or a consumer. There is no B2B exemption for ATDS calls to cell phones. If you call a business contact on their mobile number with an ATDS, you still need their prior express consent. Many B2B teams don't realize this.

What did the ACA International v. FCC case decide about the ATDS definition?

The D.C. Circuit in ACA International v. FCC (2018) vacated the FCC's 2015 interpretation that equipment qualifies as an ATDS based on potential functionality alone. The court found the FCC's capacity definition was arbitrary and inconsistent. This created a circuit split that persisted until Facebook v. Duguid resolved the core statutory question in 2021. ACA International was the beginning of the end for the broad ATDS reading.

Is there a way to send automated texts legally without running ATDS risk?

The cleanest path is collecting clear prior express written consent before sending any automated texts, regardless of whether your platform is technically an ATDS. Consent-based programs built on double opt-in, with documented timestamps and clear disclosures, eliminate most ATDS exposure and also protect against consent-revocation claims. Don't rely solely on the argument that your platform isn't an ATDS. Consent is the real defense.

Sources

1. U.S. Code, 47 U.S.C. § 227, Telephone Consumer Protection Act: ATDS definition, $500 per violation penalty, $1,500 for willful violations, prohibition on ATDS calls to cell phones without prior express consent
2. U.S. Supreme Court, Facebook, Inc. v. Duguid, 592 U.S. 395 (2021): ATDS requires random or sequential number generator to store or produce numbers; systems that only dial from stored lists do not qualify
3. FCC, In the Matter of Rules and Regulations Implementing the TCPA, 2015 Omnibus Declaratory Ruling and Order (30 FCC Rcd 7961): FCC 2015 broad ATDS capacity interpretation; established business relationship definition including 18-month lookback period
4. U.S. Court of Appeals, D.C. Circuit, ACA International v. FCC, 885 F.3d 687 (D.C. Cir. 2018): D.C. Circuit vacated FCC 2015 ATDS capacity interpretation as arbitrary; created circuit split on ATDS definition
5. U.S. Court of Appeals, Ninth Circuit, Borden v. eFinancial, LLC, 53 F.4th 1230 (9th Cir. 2022): System must actually use random or sequential number generator to qualify as ATDS; potential capacity alone insufficient post-Facebook
6. FCC, Notice of Proposed Rulemaking, CG Docket No. 21-402, 2023 TCPA Consent and Lead Generation Rules: FCC 2023 NPRM on TCPA consent and lead generation; FCC signaled possible new ATDS guidance; one-to-one consent rulemaking
7. FCC, Rules and Regulations Implementing the TCPA, 2003 Order (18 FCC Rcd 14014): FCC 2003 order confirming SMS texts are calls under TCPA; established business relationship framework for landline prerecorded calls
8. FCC, 2012 TCPA Order, Prior Express Written Consent Rule, 77 Fed. Reg. 34233: FCC 2012 order requiring prior express written consent for telemarketing calls and texts to cell phones; removed EBR exemption for prerecorded calls to cell phones, effective October 16, 2013
9. Cornell Law School, Legal Information Institute, 47 CFR 64.1200 (TCPA implementing regulations): Federal regulations implementing TCPA restrictions; text messages covered under TCPA; ATDS rules apply to SMS and consent requirements
10. FTC, National Do Not Call Registry for Businesses: Businesses must scrub against national DNC registry before telemarketing calls regardless of ATDS status; $500 per call penalty applies under TCPA and FTC TSR