Why the Autodialer Question Still Confuses Callers

A single phone call can cost you $500. Under the TCPA, statutory damages run $500 to $1,500 per call, and the autodialer definition is the threshold for that liability, according to legal analysis of the Supreme Court's ruling. Multiply that by a campaign of 10,000 calls and you can see why callers spent years losing sleep over one question: does my equipment count as an autodialer?

For most of a decade, nobody could give you a straight answer.

The trouble started with the FCC's 2015 Declaratory Ruling, which took what courts later called an "extremely broad" view of autodialer equipment. The definition swept in "potential functionalities" and even the "future possibility" of autodialing features. The D.C. Circuit invalidated that approach in ACA International v. FCC (2018), calling it an "eye-popping sweep" that, read literally, would make every smartphone in America an autodialer.

That reversal didn't settle anything. It opened a circuit split:

• The Third, Seventh, and Eleventh Circuits read the statute narrowly: an autodialer needs a random or sequential number generator.
• The Second, Sixth, and Ninth Circuits read it broadly, covering equipment that automatically dials numbers from a stored list.
• The FCC's 2020 Declaratory Ruling sided with the narrow courts, but couldn't bind the Ninth Circuit, which had held that dialing stored lists counts.

The practical consequence was grim for anyone running outbound calls. Whether your dialer was an autodialer depended on where you got sued, not on what your equipment actually did. The same platform could be lawful in Atlanta and a statutory-damages machine in San Francisco.

The FCC tried to calm things down in its 2020 ruling, responding to a petition from the P2P Alliance, a coalition of peer-to-peer messaging providers. As Hinshaw & Culbertson's analysis notes, the FCC clarified that high call volume is "not probative" of autodialer status. What matters is whether the equipment can dial random or sequential numbers without human intervention. Helpful, but not binding on courts that disagreed.

This is why list discipline mattered so much during those years, and still does. My AI Call Center reviews list source and consent records before any campaign launches, because when the equipment question is murky, the consent question is your best defense. Even when a caller uses an autodialer, prior express consent from the recipient avoids TCPA liability.

The chaos finally ended on April 1, 2021, when the Supreme Court ruled 9-0 in Facebook, Inc. v. Duguid. Over 20 parties filed amicus briefs, a measure of how much money rode on the answer. The Court chose the narrow reading, and the era of guessing ended.

The Supreme Court's Answer: Random or Sequential Number Generation

For years, courts couldn't agree on what an autodialer actually is, and the answer determined whether companies faced $500 to $1,500 in statutory damages per call. The Supreme Court settled the question on April 1, 2021, in a unanimous 9-0 decision in Facebook, Inc. v. Duguid.

To qualify as an automatic telephone dialing system, the Court held that a device must have the capacity either to store or to produce telephone numbers using a random or sequential number generator. Justice Sotomayor, writing for the majority, warned that a broader reading "would take a chainsaw to these nuanced problems when Congress meant to use a scalpel." The generator requirement applies to both storing and producing numbers, so equipment that simply dials from a stored list does not qualify.

This narrow reading reversed years of regulatory expansion. The FCC's 2015 order had defined an autodialer so broadly that the D.C. Circuit called it an "eye-popping sweep" that would sweep in every smartphone. After Duguid, the autodialer provisions apply only to equipment capable of random or sequential generation, and the Court noted the TCPA separately prohibits artificial or prerecorded voices, which is where most modern enforcement lives.

The FCC reached the same conclusion on the volume question. In a Declaratory Ruling responding to a 2018 petition from peer-to-peer messaging providers, the agency stated that high call volume "is not probative of whether the equipment is an autodialer." What matters is whether the equipment can dial random or sequential numbers without human intervention. Ten thousand calls a day proves nothing by itself.

For equipment that dials from stored, permissioned lists, the practical picture is:

• Dialing from a reviewed list of consenting contacts does not make your equipment an autodialer.
• Call volume alone can't establish autodialer status.
• Consent quality, not the equipment definition, drives most liability risk today.

That last point deserves emphasis. Even when an entity uses an autodialer, prior express consent defeats liability, and the FCC's one-to-one consent rule (effective January 27, 2025) tightened what valid consent looks like. A lead database without clear, individual permission records can become unusable overnight.

This is why list discipline matters more than dialer architecture. A managed service like My AI Call Center reviews list source and consent records before any campaign launches, and declines bought lists that lack clear permission records, because the autodialer question is now the easy part. The hard part is proving every person on your list actually agreed to hear from you, and that they can opt out the moment they change their mind.

The Definition Is Settled, But Consent Is the New Battleground

The autodialer label is largely settled. Where the money and the lawsuits now live is consent: who gave it, what they agreed to, and how fast you honor a revocation.

The Supreme Court's unanimous 9-0 decision in Facebook v. Duguid narrowed the definition to equipment that can store or produce numbers using a random or sequential number generator, which means dialing from a stored list does not qualify. Statutory damages still run $500 to $1,500 per call, so the label matters, but it is only the threshold. The FCC's one-to-one consent rule, effective January 27, 2025, requires written consent to authorize no more than one identified seller, and it closed the lead-generation loophole that let a single opt-in feed a web of marketers.

That framework is now fragmenting. In Bradford v. Sovereign Pest Control of TX, Inc., the Fifth Circuit held in February 2026 that the TCPA does not require prior express written consent, applying the Supreme Court's Loper Bright decision to reject the FCC's written-consent rule within its region. Companies there must still show consent was clear, direct, and unequivocal, with oral consent documented and independently verifiable. Other circuits may still follow the FCC framework, and state statutes can require writing regardless.

Three practical points follow:

• Consent has to name the seller you actually represent, not a vague network of partners.
• Consumers can revoke through reasonable methods, including keywords like "stop," and businesses must respond within 10 business days.
• The FCC's global revocation rule now takes effect January 31, 2027, so keep revocation handling conservative.
• A pending FCC rulemaking may eliminate predictive-dialer abandonment rules capping abandoned calls at 3% and barring disconnects before 15 seconds or four rings.

The pattern is consistent: consent quality, revocation handling, and disclosure carry the liability. My AI Call Center treats that as the starting point, reviewing list source and consent records before any campaign launches and declining bought lists without clear permission records.

How to Run Compliant Outbound Campaigns in Practice

Knowing what an autodialer is only gets you so far. The real risk in outbound calling today sits in consent quality, and TCPA statutory damages run $500 to $1,500 per call, so the cost of a sloppy list adds up fast.

Start every campaign by verifying where your list came from and what consent records back it. The FCC's one-to-one consent rule, effective January 27, 2025, requires consent to authorize no more than one identified seller, and legal analysts warn that existing lead databases may become unusable if they don't meet the new individual consent standard. A bought list without clear permission records is a liability, not an asset.

Next, document consent to a high standard. Even in the Fifth Circuit, where a February 2026 ruling rejected the written-consent requirement, companies must still show consent was clear, direct and unequivocal. Oral consent works only if you can document it and verify it independently. If you can't reconstruct who consented, when, and to what, treat the number as off-limits.

Your pre-launch checklist should cover:

• Confirm the list source and match every contact to a consent record tied to your specific offer or seller.
• Document consent to a clear and unequivocal standard, with dates and capture context.
• Honor opt-outs within 10 business days, recognizing keywords like STOP, QUIT, and UNSUBSCRIBE as valid revocations.
• Log DNC requests centrally and carry them across every campaign, not just the one where the request occurred.

Revocation handling deserves special attention. Consumers can withdraw consent through various reasonable methods, and current FCC guidance treats keyword opt-outs like "stop" as valid, with a 10-business-day response window. The FCC's global revocation rule, now extended to January 31, 2027, will raise the bar further, so keep your revocation processes conservative.

This is exactly why My AI Call Center reviews list source and consent records before any campaign launches, and flags or declines bought lists that lack clear permission records. Telling a client plainly that a list won't support the campaign, before they spend anything, costs a little goodwill. It's far cheaper than a class action.

One final habit: audit regularly. Requirements vary by location, industry, contact type, and consent status, and the rules are actively shifting through litigation and rulemaking. A list that was compliant at launch can drift out of compliance as consent ages, so re-verify before every campaign, not just your first.