
What qualifies as an autodialer?
Key Facts
- The Supreme Court unanimously ruled in Facebook v. Duguid that an autodialer must use a random or sequential number generator.
- TCPA penalties reach $1,500 per call, making consent verification worth every check.
- The FCC clarified in February 2024 that AI-generated voices count as artificial voices requiring prior express consent.
- Robocall and robotext complaints are consistently the FCC's top consumer complaint category.
- The Duguid ruling explicitly excludes predictive dialing to known numbers from the autodialer ban.
- Justice Sotomayor warned a broad autodialer reading would take "a chainsaw to these nuanced problems when Congress meant to use a scalpel."
- The FCC proposed rules in September 2024 requiring callers to disclose AI-generated calls.
Why the Autodialer Question Confuses So Many Callers
Ask three vendors whether your AI calling platform counts as an autodialer and you'll likely get three different answers. Some say the Supreme Court settled the question years ago. Others warn that everything with a dial button is a liability. For a business planning outbound campaigns, that confusion is expensive.
The stakes are concrete. The TCPA carries penalties of up to $1,500 per call, and unwanted robocalls and robotexts are consistently the FCC's top category of consumer complaints. A single campaign with the wrong assumptions can stack up thousands of calls' worth of exposure.
Part of the confusion comes from the law itself. The TCPA was written in 1991, long before cloud dialers, CRM-triggered calls, or AI voice agents existed. Courts spent a decade arguing over whether equipment that merely stores and dials known numbers qualified, until the Supreme Court answered unanimously in April 2021. In Facebook v. Duguid, the Court held that an autodialer must use a random or sequential number generator to store or produce numbers. Justice Sotomayor noted that a broader reading would expose ordinary cell phone users to liability for speed dialing.
That ruling narrowed one definition. It didn't end compliance, and this is where the conflicting advice usually comes from. The same technology can sit outside the autodialer ban and still trigger TCPA liability through other rules:
- AI-generated voices are treated as "artificial or prerecorded voices" under the TCPA, per the FCC's February 2024 ruling, so prior express consent is still required.
- Do Not Call obligations under the Telemarketing Sales Rule remain fully in effect regardless of dialing technology.
- B2B calling is not a blanket exemption; state mini-TCPA laws, personal wireless numbers, and recording rules still apply.
- The FCC has proposed additional rules requiring disclosure when callers use AI-generated voices.
For AI-powered calling specifically, the practical risk has shifted. Whether your system qualifies as an autodialer matters less than whether your contact lists carry documented consent, whether your calls disclose AI use, and whether opt-outs are honored immediately. That's why at My AI Call Center every campaign starts with a list and consent review before launch, and why we tell you plainly if a list won't support the campaign.
Getting the definition right matters, but it's only the first gate. The rest of this guide walks through what the current rules actually require.
ctaText: Run structured outbound campaigns on approved, permissioned lists. Campaigns start at 9¢ per connected minute, with the full price quoted before launch. socialProofText: Every campaign passes a list and consent review before launch, and opt-outs are honored immediately across all campaigns.
The Supreme Court's Definition: Random or Sequential Number Generation
On April 1, 2021, the Supreme Court answered a question that had divided federal courts for years: what actually counts as an autodialer under the TCPA? In Facebook v. Duguid, all nine justices agreed on a narrow, text-based answer. A device qualifies as an automatic telephone dialing system (ATDS) only if it can store or produce telephone numbers using a random or sequential number generator and dial those numbers, according to SCOTUSblog's analysis of the ruling.
The Court reached that reading through grammar. The statute says a system must have the capacity to store or produce numbers "using a random or sequential number generator." The justices applied the series-qualifier canon, holding that the modifier applies to both verbs in the series, "store" and "produce." So a system that dials numbers from a fixed, known list doesn't qualify, even if it stores millions of them.
Why did the Court insist on this narrow reading? Because the alternative had absurd consequences. A broader definition covering any equipment that stores and dials numbers would sweep in "virtually all modern cell phones," exposing ordinary users to steep TCPA liability for things like speed dialing or automated text responses. Justice Sotomayor put it memorably: expanding the definition that way "would take a chainsaw to these nuanced problems when Congress meant to use a scalpel." If the 1991 statute is outdated, she wrote, updating it "must fall to Congress," not the courts.
The practical result matters for anyone running outbound calling. Most telemarketing calls go to numbers known to belong to a specific, intended recipient, not numbers generated at random or in sequence. The ruling effectively removes those targeted calls from the scope of the autodialer ban, and it explicitly excludes modern predictive dialing from the definition, provided no artificial or prerecorded voice is used. As BCLP's legal analysis notes, the decision is likely to stem the tide of TCPA litigation and gives callers a consistent nationwide standard.
But don't start the party just yet, as BCLP warns. Narrowing the autodialer definition removes one gate, and only one. The TCPA still prohibits artificial and prerecorded voice calls without prior express consent, with penalties up to $1,500 per call, and Do Not Call restrictions remain fully in force. That's why the list itself, not the dialing technology, is where compliance risk now lives.
This is how we approach it at My AI Call Center: campaigns run against approved, permissioned, or reviewed lists only, with the list source and consent records checked before anything launches. Dialing known, targeted numbers keeps you outside the autodialer ban. Keeping your consent records in order keeps you outside everything else.
Why a Narrow Autodialer Definition Doesn't Get You Off the Hook
It's tempting to read the narrow autodialer definition as a green light. If your dialing system only calls known, targeted numbers, the ATDS ban arguably doesn't apply. But that's only one gate in the fence, and plenty of callers trip over the others.
The TCPA still prohibits artificial and prerecorded voice calls without prior express consent, and the FCC clarified in February 2024 (ruling FCC-24-17) that AI-generated voices count as artificial voices. That means a conversational AI caller doesn't get a pass just because it sounds natural. Consumer telemarketing using artificial or prerecorded voices generally requires prior express written consent, and violations can run up to $1,500 per call.
The FCC isn't done. In September 2024, it proposed rules that would define "AI-generated calls" and require callers to disclose when consumers are hearing one. According to the FCC's proposed rulemaking, robocall and robotext complaints are consistently the agency's top category of consumer complaints, so expect this area to keep tightening.
Even if your dialing tech dodges the autodialer label, several obligations still apply:
- Artificial and prerecorded voice rules, now explicitly covering AI-generated voices under FCC-24-17.
- Do Not Call restrictions under the Telemarketing Sales Rule, which remain in effect regardless of what equipment you dial with.
- State mini-TCPA laws, which add their own consent, quiet-hour, and registration requirements.
- Recording rules, since some jurisdictions require all-party consent to record a call.
B2B callers should pay particular attention here. Many business calls are exempt from federal Do Not Call provisions, but that's not a universal safe harbor. TCPA restrictions still apply to personal wireless numbers, state laws still bind, and internal opt-outs still matter. A "business call" to someone's personal cell phone can create real exposure.
The practical takeaway: your compliance risk now hinges less on whether your system qualifies as an autodialer and more on consent records, artificial-voice rules, DNC obligations, and disclosure. That's why we review list source and consent records before any My AI Call Center campaign launches, disclose AI assistance on every call, and honor opt-outs across all campaigns. If a bought list lacks clear permission records, we'll tell you plainly before you spend anything, because a narrow autodialer definition won't protect you if the consent underneath the campaign is missing.
How to Run Compliant Outbound Campaigns: A Practical Checklist
TCPA penalties run up to $1,500 per call, so the difference between a compliant campaign and an expensive one usually comes down to what you checked before the first dial. Here's what to verify before you spend anything.
Start with the list, not the script. Ask where each number came from and what permission exists to call it. A bought list without clear consent records is the single biggest risk factor in outbound, because the narrowed autodialer definition from Facebook v. Duguid doesn't shield you from artificial-voice or DNC rules.
Then work through the rest of the gates:
- Treat AI voices as artificial voices. The FCC confirmed in 2024 that AI-generated voices fall under the TCPA's artificial or prerecorded voice rules, which means prior express consent is required before you dial.
- Disclose AI on every call. The FCC has proposed a rule requiring callers to tell consumers when they're receiving an AI-generated call. Disclosing now puts you ahead of that requirement.
- Honor STOP and REVOKE opt-outs immediately. Log every DNC request and carry it into your suppression records across all campaigns.
- Check jurisdiction before launch. State quiet hours, day restrictions, mini-TCPA laws, and all-party recording consent rules vary, and B2B calling is not a blanket exemption.
- Decline lists without clear permission records. If the list won't support the campaign, say so before any spend happens.
Consent is the real compliance gate now. The Supreme Court narrowed what counts as an autodialer, but it left the artificial-voice, DNC, and state-law obligations fully intact. Your exposure depends on audience, number type, consent status, jurisdiction, and disclosure, so each of those needs a documented answer before launch.
This is exactly why list and consent review sits before scripting and spend in how My AI Call Center runs campaigns. A list that won't support the goal gets flagged up front, so you decide with full information instead of finding out mid-campaign.
Every item above protects the same thing: your right to keep calling the people who actually want to hear from you. Build the habit now and you won't rebuild it under pressure later.
Ready to run outbound campaigns against approved, permissioned lists? Managed AI calling from 9¢ per connected minute, with list and consent review before anything launches.
Plan My CampaignFrequently Asked Questions
Does my AI calling system count as an illegal autodialer?
If I'm not an autodialer, why do I still need to worry about TCPA rules?
Do I need special permission to use AI voices in my outbound campaigns?
Is B2B calling exempt from all robocall regulations?
What is the biggest compliance risk for AI calling campaigns today?
How do I ensure my AI calling campaign stays compliant?
The Autodialer Question Is Settled, Your Consent Records Aren't
The Supreme Court's unanimous ruling in Facebook v. Duguid settled the definition: an autodialer must use a random or sequential number generator. But that answer only clears one gate. The rules that still matter, artificial-voice restrictions that now cover AI-generated voices, Do Not Call obligations, state mini-TCPA laws, and disclosure requirements, all turn on the same thing: your list and the consent records behind it. With penalties up to $1,500 per call, a campaign built on shaky permissions is the real exposure, not your dialing technology. Before your next outbound push, ask three questions: Where did this list come from? What permission exists to call it? Can I document it? If any answer is unclear, fix it before the first dial. That's why My AI Call Center reviews list source and consent records before anything launches, and tells you plainly if a list won't support the campaign. Ready to run structured campaigns against approved, permissioned lists, starting at 9¢ per connected minute? Plan your campaign with the full price quoted before launch.