Preview and Click-to-Dial Dialers Under the TCPA: Autodialer or Not?

A preview dialer shows an agent a customer’s record, then waits for the agent to dial. A click-to-dial system places the call when a person clicks a number. Neither dials from a random or sequential number generator, so after the Supreme Court’s 2021 decision in Facebook v. Duguid, neither is usually an automatic telephone dialing system under the Telephone Consumer Protection Act. That ends the autodialer claim. It does not end a company’s exposure, and the demand letter rarely says so.

What are preview dialers and click-to-dial systems?

Both are ways to call from a list while keeping a person in the loop for every call.

A preview dialer pulls up the next contact and the account notes, then holds until the agent decides to dial. A click-to-dial system, sometimes called click-to-call, places the call when the agent clicks a number or a button on the screen. In both, a person decides when each call goes out and to whom, and the equipment waits for that decision. That design is usually a deliberate compliance choice, because it keeps the system away from the one piece of technology the TCPA’s autodialer rule is built around.

Contrast that with a predictive dialer, which places calls automatically, often several at once, and connects whoever answers to the next free agent. Predictive dialing is where most of the old autodialer litigation came from. Preview and click-to-dial systems sit at the other end of the spectrum, and the difference matters to the statute.

Does a preview or click-to-dial dialer count as an autodialer under the TCPA?

Usually not, and the reason is the statutory definition the Supreme Court locked in.

The TCPA defines an automatic telephone dialing system, the autodialer the statute restricts, 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,” under 47 U.S.C. § 227(a)(1). In plain terms, an autodialer is equipment that invents the numbers it calls. In Facebook, Inc. v. Duguid, 592 U.S. 395 (2021), the Court held that “a necessary feature of an autodialer under §227(a)(1)(A) is the capacity to use a random or sequential number generator to either store or produce phone numbers to be called.” Equipment that dials from a list someone loaded, the Court explained, does not fit.

A preview or click-to-dial system dials the number in front of the agent, from a stored customer or lead list, one call at a time. It is not generating numbers at random or in sequence. So the autodialer claim under 47 U.S.C. § 227(b) almost always fails on the equipment alone. That is also why the pure autodialer theory has shrunk since 2021, a point worth reading alongside what still counts as an autodialer after Duguid.

One caution on the word “capacity.” Plaintiffs sometimes argue that a platform has the latent capacity to generate numbers even if the business never turns that function on. Courts after Duguid look at what the equipment actually does in the configuration the company ran, not at a feature buried in a settings menu. The safer course is to be able to show the configuration, not just to assert it, which is a records problem more than a legal one.

If it is not an autodialer, is the call safe under the TCPA?

No. This is the trap, and it is where businesses that bought a dialer for its compliance story get surprised.

Section 227(b) actually bars two different things. It bars calls to a cell number made “using any automatic telephone dialing system or an artificial or prerecorded voice” without the called party’s consent, under 47 U.S.C. § 227(b). That is an either-or. A prerecorded voice is a recorded message that plays in place of a live person. If a preview or click-to-dial campaign drops a voicemail, plays a recorded greeting, or uses an artificial voice to open the call, the recorded-voice half of the statute applies no matter how the number was dialed. Beating the autodialer definition does nothing for that claim. The same risk runs through artificial and AI-voice calls, which the statute treats as artificial voices.

The Do Not Call rules are the bigger exposure for a list-based calling operation. They live in a separate part of the statute, 47 U.S.C. § 227(c)(5), and the FCC’s implementing rules at 47 C.F.R. § 64.1200. They turn on whether a call is a telephone solicitation to a number the company should not have called, such as a number on the National Do Not Call Registry (the federal list consumers join to stop sales calls) or a number that already asked the company to stop. None of that cares what kind of dialer placed the call. A human clicking the button is not a defense to a Do Not Call claim. The private claim belongs only to someone who has received “more than one telephone call within any 12-month period by or on behalf of the same entity,” under 47 U.S.C. § 227(c)(5), so a single call is not a Do Not Call case, but a campaign that calls the same person twice can be.

How do plaintiffs still go after these systems?

They point the case at something other than the dialer, and they test whether the human intervention was real.

Expect three moves. First, the recorded-voice angle: if any message, prompt, or voicemail on the call was a recording, the complaint leans on the artificial-or-prerecorded-voice clause and the dialer question falls away. Second, the Do Not Call angle: the complaint alleges the number sat on the Registry or had made a stop request, which makes the dialing technology beside the point. Third, a challenge to the human-in-the-loop story itself, arguing that the agent’s “click” was a rubber stamp over a system that really did the selecting. That last one is the same fight that runs through soundboard calls, where a live agent plays recorded clips: the closer the human role gets to a formality, the harder the defense gets.

State law adds another layer. Several states restrict automated or recorded sales calls on their own terms, with their own definitions, and a few reach calls that the federal autodialer rule would not. A dialer setup that clears Duguid can still draw a claim under a state statute, so the analysis does not stop at the federal line.

Claim theory Statute or rule Per-violation exposure What answers it
Autodialed call to a cell number 47 U.S.C. § 227(b) $500, up to $1,500 if willful or knowing The equipment is not an ATDS under Duguid because a person launches each call
Artificial or prerecorded voice call 47 U.S.C. § 227(b) $500, up to $1,500 if willful or knowing A live agent spoke and no recording played, or the called party consented
Call to a Do Not Call Registry number 47 U.S.C. § 227(c)(5) Up to $500, up to $1,500 if willful or knowing Registry scrub records, an established business relationship, or the reasonable-procedures defense
Call after an internal stop request 47 U.S.C. § 227(c)(5) and FCC rules Up to $500, up to $1,500 if willful or knowing Logged stop requests honored on time, plus written do-not-call procedures

Damages run per call. Section 227(b)(3) sets the figure at “$500 in damages for each such violation, whichever is greater,” under 47 U.S.C. § 227(b)(3), and a court may increase it to as much as $1,500 if it finds the violation willful or knowing. The Do Not Call provision carries its own affirmative defense for a company that has “established and implemented, with due care, reasonable practices and procedures to effectively prevent telephone solicitations” against the rules, under § 227(c)(5). Written scrub procedures and honored stop requests are what that defense is made of.

What a company should preserve and do when a dialer claim arrives

The dialer label on the sales brochure will not decide the case. The records of how the equipment actually ran will. Keep this list short and do it early:

  1. Put a litigation hold on the dialer and platform data the moment a demand or complaint arrives, including the records of how each number was selected and who launched each call.
  2. Pull the vendor’s technical description of the system and, more to the point, the configuration the company actually ran during the campaign, with dates.
  3. Pull the National Do Not Call Registry scrub records and the version dates used for the campaign.
  4. Pull the internal do-not-call and opt-out logs, plus any recorded, voicemail, or artificial-voice audio files the campaign used.
  5. Collect the lead-source and vendor contracts and the calling scripts, then talk to a lawyer before answering the demand letter, contacting the person who complained, or offering anything to settle.

For the bigger picture of how these claims move once they are filed, the firm’s California TCPA defense lawyers page covers how autodialer and Do Not Call cases proceed through federal and California courts.

If your company is being sued over dialer calls

If your company is accused of using an autodialer, the first question is almost always how the equipment actually selected and dialed the numbers, and the answer usually lives in the platform’s own records, not in the demand letter’s description of them.

Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving autodialer and Do Not Call calls. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.

Questions people ask about preview and click-to-dial dialers

Is a preview dialer an autodialer under the TCPA?

Usually not. The TCPA’s autodialer definition, as the Supreme Court read it in Duguid, requires equipment that uses a random or sequential number generator to store or produce the numbers it calls. A preview dialer dials from a stored list, one contact at a time, after an agent decides to place the call. That design does not meet the definition, so the autodialer claim typically fails.

Does click-to-dial avoid the TCPA?

No. Click-to-dial usually defeats the autodialer theory, but the TCPA also restricts calls that use an artificial or prerecorded voice and calls that violate the Do Not Call rules. Those claims do not depend on how the number was dialed. A company that clears the autodialer definition still has to answer for recorded-voice calls and for calls to Registry or stop-requested numbers.

What is the difference between a preview dialer and a predictive dialer?

A preview dialer waits for a person to launch each call after reviewing the contact. A predictive dialer places calls automatically, often several at once, and routes answered calls to available agents. Predictive dialing is where most autodialer litigation started. The human-launched design of a preview dialer is what keeps it away from the statute’s autodialer definition.

Can a business still be sued for a single call from a preview dialer?

Yes. A single call can support an artificial-or-prerecorded-voice claim under Section 227(b) if a recording played. The Do Not Call private action is different: it requires more than one call within a 12-month period from or for the same entity, so one call will not support that particular theory, though it can still draw a demand.

Sources

The primary sources for this post are the Telephone Consumer Protection Act at 47 U.S.C. § 227, which supplies the autodialer definition and the private rights of action, the Supreme Court’s decision in Facebook, Inc. v. Duguid, 592 U.S. 395 (2021), and the FCC’s calling and Do Not Call rules at 47 C.F.R. § 64.1200.

This post is general information about the Telephone Consumer Protection Act and related laws as of August 1, 2026. It is not legal advice, and reading it does not create an attorney-client relationship. Courts and the FCC change the rules in this area often, and the outcome of any claim depends on its facts. Past results do not guarantee future outcomes.

← Back to Blog

Let’s Talk.