Why the Autodialer Question Matters for Your Outreach

The stakes are immediate: TCPA statutory damages run $500 to $1,500 per unlawful call or text, and class actions multiply that exposure fast. Most businesses running dialers, CRM-based calling, or automated follow-up don't know whether their equipment legally counts as an autodialer — and the answer changed dramatically in 2021.

The Supreme Court's unanimous decision in Facebook, Inc. v. Duguid rewrote the landscape. The Court held that an autodialer must use a random or sequential number generator — whether storing or producing numbers. Equipment that simply dials from a stored list, like most modern CRM-based dialers and notification systems, generally falls outside the TCPA's autodialer definition.

That ruling resolved a circuit split in favor of the narrow view. The Second, Sixth, and Ninth Circuits had taken a broad approach; the Third, Seventh, and Eleventh Circuits had already required a generator. The Supreme Court sided with the narrow interpretation, rejecting the argument that any device automatically dialing stored numbers qualifies.

But the question isn't settled. Circuits remain split on what "capacity" means — current capabilities at the time of the call, or inherent functional design. The FCC says the definition "evolves with technology" and focuses on present capacity. Several states have their own TCPA-like laws. And consent, opt-out, calling-hours, and prohibited-lines rules still apply regardless of classification.

• Cell phones: marketing calls/texts require prior express written consent
• Landlines: non-marketing calls may proceed without consent (subject to DNC checks)
• Emergency lines: autodialed calls are completely prohibited
• Opt-out requests must be honored within 10 business days starting April 11, 2025

At Worqd, we help clients assess their outreach stack against the current legal test — not outdated assumptions. Our AI SDR and lead conversion systems are built with compliance discipline baked in: explicit consent capture, automated opt-out handling, and calling-hours guardrails. If you're unsure where your dialing technology stands, let's talk through the risk.

The Legal Definition: Random or Sequential Number Generator Required

If you dial customers from a stored contact list, you might assume you're using an autodialer. Under federal law, you're probably wrong — and that distinction carries real legal weight.

The Telephone Consumer Protection Act, at 47 U.S.C. § 227(a)(1), defines an autodialer 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. That generator phrase is the whole ballgame, and the federal regulation spells it out the same way.

For years, courts disagreed about what that meant. The Second, Sixth, and Ninth Circuits took a broad view — any device that could automatically dial a stored number qualified. The Third, Seventh, and Eleventh Circuits read the statute narrowly. The Supreme Court settled the split on April 1, 2021, in Facebook v. Duguid, ruling unanimously, 9-0, that the random or sequential number generator requirement applies whether a system stores or produces numbers.

The case itself was mundane: Noah Duguid kept getting automated Facebook login-alert texts for an account he never created. Facebook's system dialed from stored numbers, not generated ones — so the Court held it wasn't an autodialer at all. Writing for the Court, Justice Sotomayor applied the "series-qualifier canon," holding the generator phrase modifies both "store" and "produce."

The Court also rejected broader readings on practical grounds. Under the Ninth Circuit's approach, almost all modern cell phones would qualify as autodialers — meaning ordinary users could face liability for speed dial or automated text responses. The justices noted the TCPA targets equipment that risks random calls to emergency lines or tying up sequentially numbered lines, and that a broad definition would "take a chainsaw to these nuanced problems when Congress meant to use a scalpel."

For businesses, the practical takeaway is straightforward:

• Systems that dial from a stored customer list — CRM-based dialers, notification tools — generally fall outside the autodialer definition post-Duguid.
• Equipment using a random or sequential number generator still qualifies, and triggers the TCPA's consent and calling-hour rules.
• The ruling left "capacity" unresolved — circuits still split on whether it means a device's capabilities at call time or its inherent design.
• Several states have their own TCPA-like laws that may restrict automated calling regardless of the federal definition.

The stakes are real: statutory damages run $500 to $1,500 per unlawful call or text, and class actions multiply exposure quickly. Attorneys at Duane Morris predicted the ruling would "shrink the universe of devices that count as an autodialer" and significantly reduce viable TCPA suits.

This is why, when you're checking a growth partner's compliance practices, the autodialer question is only the starting point. At Worqd, outreach is built on personalized, permission-aware contact to relevant accounts — with explicit consent captured up front — because consent and opt-out discipline apply no matter how your equipment is classified.

What Counts and What Doesn't After Duguid

After Duguid, the question stops being "can this machine dial automatically?" and becomes a much narrower one: does it use a random or sequential number generator? That single distinction now separates everyday business calling tools from equipment that carries $500 to $1,500 in statutory damages per unlawful call or text.

What generally does NOT qualify. Equipment that dials from a stored list — without random or sequential number generation — falls outside the TCPA's autodialer definition. That includes most modern CRM-based dialers, appointment reminder systems, and customer notification platforms. In fact, the system at issue in Duguid itself was Facebook's security alert tool, which texted numbers from a stored list, and the Supreme Court held it was not an autodialer. As Duane Morris attorneys noted, the ruling "will shrink the universe of devices that count as an autodialer."

What DOES qualify. Equipment with the capacity to store or produce numbers using a random or sequential number generator, and then dial them, still meets the statutory definition. The Court rejected the Ninth Circuit's looser standard, applying the series-qualifier canon so the generator phrase modifies both "store" and "produce," per the controlling analysis.

Here's where it gets murky. Duguid left the meaning of "capacity" unresolved, and the circuits remain split:

• The Second, Third, and D.C. Circuits look at a device's capabilities at the time of the call.
• The Seventh, Ninth, and Eleventh Circuits ask about the device's inherent functional design.
• The FCC now focuses on present capacity — a system must actually dial automatically, not merely be modifiable to do so, according to compliance guidance.

The FCC's position also keeps shifting. It previously folded predictive dialers into the definition, reasoning that random or sequential generation might be obsolete, but the Congressional Research Service notes the Supreme Court refused to stretch the statutory text beyond its specific technological language. The FCC's interpretation "evolves with technology," so classification today is not a permanent answer.

That matters especially for AI-driven calling and voice agents — technology the existing sources simply don't classify. If you're evaluating a growth partner like Worqd that uses AI systems for fast follow-up and lead conversion, the equipment question is exactly what to raise: ask how calls are placed, whether numbers come from stored consented lists, and what consent and opt-out safeguards are in place. Consent discipline — prior express written consent, automated opt-out mechanisms, and the 10-business-day opt-out deadline effective April 11, 2025 — applies regardless of how a dialer is classified.

Finally, don't treat the federal definition as the whole picture. Several states maintain their own TCPA-like laws that restrict automated calling and texting even where Duguid's narrow federal reading would not, and the CRS warns that a technology-specific definition may require future amendments as callers adopt new tools. Given the stakes, legal counsel should review any calling stack before it scales.

Compliance Rules That Apply No Matter How Your Equipment Is Classified

It's tempting to read the Supreme Court's narrow autodialer definition as a free pass. It isn't. Most of the compliance rules that trip up businesses apply regardless of how your dialing equipment is classified — and violations still carry statutory damages of $500 to $1,500 per unlawful call, text, or fax.

Prior express written consent remains the baseline for marketing calls and texts to cell phones. Since the FCC's 2012 rule revisions, telemarketers must obtain this consent before making autodialed or prerecorded-voice calls, and the old "established business relationship" exception no longer gets you around it, according to the FDIC's consumer compliance examination manual.

Opt-out discipline just got stricter, too. Starting April 11, 2025, marketers must honor opt-out requests within 10 business days, per ActiveProspect's TCPA compliance guidance. After someone opts out, you may send exactly one clarifying text — and it can't contain any marketing content.

Operational rules apply no matter what equipment you use:

• Calling hours are restricted to 8 AM–9 PM in the recipient's local time, and state rules may differ.
• Autodialed calls to emergency lines and hospitals are completely prohibited, regardless of consent.
• Autodialed or prerecorded calls must include an automated interactive opt-out mechanism.
• Do-Not-Call checks still apply — an established business relationship permits calls to DNC-registered consumers only within 18 months of a purchase or 3 months of an inquiry.

The FTC adds a separate layer. Its Telemarketing Sales Rule doesn't define "autodialer" at all — it's deliberately technology-neutral, noting that "it makes no difference whether a company makes or receives calls using low-tech equipment or the newest technology," as the FTC's business guidance explains. Abandoned-call rules and prerecorded-message restrictions live here, entirely outside the Duguid analysis.

State law is the other blind spot. The Supreme Court's ruling addressed only the federal definition, and Duane Morris attorneys note that several states maintain TCPA-like laws that may limit automated calling and texting even where the federal definition doesn't reach. The Congressional Research Service adds that circuits remain split on what "capacity" means — so classification itself isn't fully settled.

The practical takeaway: treat consent, opt-out speed, calling hours, and state rules as non-negotiable infrastructure in your outreach process, not as questions that depend on your dialer. This is exactly why permission-aware outreach matters more than equipment classification — at Worqd, every lead-handling path we build starts from explicit consent, because fast follow-up only works when it's compliant follow-up.

When in doubt, get legal counsel to review your specific setup. The definition "evolves with technology," and the cost of guessing wrong is measured per call.

How to Audit Your Calling Stack: A Practical Checklist

Knowing the legal definition of an autodialer is only half the battle. The other half is auditing your own calling and texting systems to see where you actually stand — before a plaintiff's attorney does it for you.

Start with the random or sequential number generator test. For each system that dials or texts on your behalf, document whether it stores or produces numbers using a random or sequential number generator. After the Supreme Court's unanimous Facebook v. Duguid ruling, equipment that simply dials from a stored list — like most modern CRM-based dialers and notification systems — generally falls outside the TCPA's autodialer definition. Get your vendor's answer in writing, not just a sales rep's verbal assurance.

Next, don't treat the equipment question as settled. Circuits remain split on what "capacity" means — current capabilities at the time of the call versus inherent functional design — according to a Congressional Research Service analysis. The FCC focuses on a system's present capacity, and its definition evolves with technology, so re-run this audit whenever you change providers or add features.

Then audit the compliance layer that applies regardless of how your equipment is classified:

• Consent records: Confirm you hold prior express written consent for marketing calls and texts to cell phones, and that every record is documented and retrievable.
• Opt-out handling: Verify an automated interactive opt-out mechanism runs on autodialed or prerecorded calls, and that opt-outs are honored within 10 business days — a deadline that took effect April 11, 2025, per ActiveProspect's compliance guidance.
• Calling windows: Restrict outreach to 8 AM–9 PM in the recipient's local time.
• State laws: Check TCPA-like statutes in every state you call into, since several states restrict automated calling even where the federal definition doesn't apply, as Duane Morris attorneys note.

Finally, bring in counsel. Statutory damages run $500 to $1,500 per unlawful call or text, and class actions multiply that exposure fast. Given the unresolved circuit splits and evolving FCC interpretation, multiple legal sources recommend expert review before you assume your stack is clean.

There's also a design principle hiding inside this checklist: the safest outreach is outreach people asked for. Worqd builds its follow-up motion around exactly that idea — permission-aware, personalized outreach to relevant accounts, with explicit consent captured at booking ("I agree to be contacted about my request") and AI SDRs that respond to inbound inquiries in under 60 seconds rather than blasting contacts who never raised a hand. Fast follow-up and legal discipline aren't rivals; speed only matters when it's aimed at people who actually want to hear from you.

Audit your systems, document everything, and let consent — not volume — drive your calling strategy.