TCPA Autodialer Claims: Discovery Into the Plaintiff’s Expert
Most TCPA autodialer claims rise or fall on one witness. To win under Section 227(b), the plaintiff has to show the equipment that called or texted had the capacity to use a random or sequential number generator. After the Supreme Court’s 2021 Duguid decision, that is hard to prove, so it usually takes an expert. Discovery is where a defendant learns whether that opinion holds up, and a company facing one of these claims often has more room to attack it than the complaint suggests.
Why does an autodialer claim usually need an expert?
Because the statute defines the equipment narrowly, and most modern systems don’t fit the definition on their face.
An autodialer, which the TCPA calls an automatic telephone dialing system, isn’t any system that sends automated calls or texts. The statute defines it as “equipment which has the capacity” to store or produce numbers “using a random or sequential number generator,” under 47 U.S.C. § 227(a)(1). Section 227(b)(1)(A)(iii) then bars calls to a cell number made with that equipment, or with an artificial or prerecorded voice, unless the caller had prior express consent. The exposure is $500 per call, and up to $1,500 per call if a court finds the violation was willful or knowing.
The Supreme Court read that definition strictly. In Facebook, Inc. v. Duguid, the Court held that a device must have “the capacity to use a random or sequential number generator to either store or produce phone numbers to be called.” A platform that dials from a saved customer list doesn’t do that, which is why the autodialer theory has shrunk since 2021.
So plaintiffs lean on experts to bridge the gap. The expert’s job is to argue that the defendant’s dialer has the latent capacity to generate numbers randomly or sequentially, even if the campaign that drew the suit dialed a loaded list. That’s a technical opinion about how a specific piece of equipment works, and a technical opinion is something a defendant can take apart in discovery.
What must the plaintiff’s expert put in the report?
A detailed written report, and that report is the defense’s first map of the opinion.
Under Rule 26(a)(2)(B), a retained expert’s report must contain “a complete statement of all opinions the witness will express and the basis and reasons for them” and “the facts or data considered by the witness in forming them.” It also has to list the expert’s qualifications, prior testimony, and compensation.
Read the “facts or data considered” list first. It tells you whether the expert examined the actual dialer that placed the calls, or worked from a vendor brochure, a user manual, and a few deposition excerpts. A capacity opinion built on marketing materials instead of the system itself is weak, and the report is where that weakness shows. If the report is thin on what the expert actually reviewed, that gap is the opening for the defense.
What can you get in discovery about the opinion?
A deposition of the expert, and the records the opinion rests on.
Rule 26(b)(4)(A) says “A party may depose any person who has been identified as an expert whose opinions may be presented at trial.” The scope is broad. Rule 26(b)(1) reaches “any nonprivileged matter that is relevant to any party’s claim or defense and proportional to the needs of the case.” Draft reports and most communications between the plaintiff’s lawyer and the expert are protected, but three things aren’t: the expert’s compensation, the facts or data the lawyer supplied, and the assumptions the lawyer asked the expert to make.
Use the deposition to pin the expert to the equipment in the case. Did the expert inspect it, or test it, or only describe a category of dialers in general? Capacity under Duguid is about what this equipment can do, not what some dialer somewhere can do. The fastest way to undercut a capacity opinion is to show the expert never looked at the system that actually placed the calls.
Your own records matter here too. The dialer’s configuration files, the logs showing how numbers were loaded and dialed, and the platform vendor’s technical documentation often contradict a general opinion that the system “can” generate numbers. A defendant who brings those records to the deposition controls the questioning.
How does Rule 702 keep an unreliable opinion out?
The judge is a gatekeeper, and the plaintiff carries the burden of getting the opinion through the gate.
Federal Rule of Evidence 702, as amended in 2023, lets an expert testify only if the proponent shows it’s “more likely than not” that the opinion meets four requirements, including that “the expert’s opinion reflects a reliable application of the principles and methods to the facts of the case.” The Supreme Court set the standard in Daubert v. Merrell Dow Pharmaceuticals, holding that “the trial judge must ensure that any and all scientific testimony or evidence admitted is not only relevant, but reliable.” The gate isn’t limited to lab science. The Court extended the same gatekeeping duty beyond scientific evidence to technical opinions in Kumho Tire Co. v. Carmichael, and an opinion about how a dialer works is a technical opinion.
The reliable-application requirement is where many capacity opinions run into trouble. An expert who concludes that a system could be modified to generate random or sequential numbers has described a hypothetical machine, not the one in the case. Several courts since Duguid have treated that gap as fatal, reading capacity to mean the equipment’s present functions, not what it might do after someone rewrites the code. Courts haven’t lined up uniformly on present versus potential capacity, so the argument isn’t automatic. But a motion to exclude an opinion that rests on a reprogrammed version of the dialer is one of the stronger tools a defendant has in these cases.
What to test in the expert’s opinion
| What to probe | Where the standard comes from | The opening it gives the defense |
|---|---|---|
| What the expert actually examined | Rule 26(a)(2)(B) report contents | A capacity opinion built on brochures, not the system, is vulnerable |
| Whether the system meets the Duguid definition | 47 U.S.C. § 227(a)(1); Facebook v. Duguid | Dialing from a stored list is not random or sequential generation |
| Present capacity versus future modification | Fed. R. Evid. 702(d); Duguid | An opinion about a reprogrammed dialer may not match the equipment in the case |
| Reliability of the method | Daubert; Kumho Tire | Technical opinions must rest on a reliable application to these facts |
What to preserve and do when an autodialer claim arrives
- Put a litigation hold on the dialer and platform data: the system configuration, the call and text logs, and the records showing how numbers were loaded and dialed for the campaign that drew the claim.
- Pull the opt-out history and the internal do-not-call logs, with dates.
- Pull the National Do Not Call Registry scrub records and the version dates used, since consent and registry defenses often decide the case before the autodialer question does.
- Collect the vendor and platform contracts and the dialer’s technical documentation, including any manuals describing how the system selects and dials numbers.
- Talk to a lawyer before responding to a demand letter, contacting the claimant, or agreeing to let the plaintiff’s expert inspect the system.
The firm’s page on defending TCPA class actions in California covers how these cases move through discovery and class certification.
Questions businesses ask about autodialer experts
Does an autodialer claim always need an expert?
Not always, but usually. If the defendant admits the equipment generated numbers randomly, no expert is needed. In most cases the system dialed a stored customer list, so the plaintiff has to argue the equipment had the capacity to generate numbers another way. That’s a technical claim about specific hardware and software, and it generally requires an expert to support it.
Can a defendant inspect the equipment the expert relied on?
Yes, and a defendant usually has the better records anyway. The dialer and its logs are typically the defendant’s own property, so the question is whether the plaintiff’s expert examined them before forming an opinion. Discovery into what the expert reviewed often matters more than a separate inspection.
What if the expert says the system could be modified to generate random numbers?
That opinion is a frequent target of a Rule 702 motion. Duguid ties capacity to what the equipment does, and an opinion about a reprogrammed or hypothetical version of the dialer may not amount to a reliable application to the facts of the case. Courts have not settled how far “capacity” reaches, so the result depends on the record and the forum.
Is a predictive dialer an autodialer under the TCPA?
It depends on how the dialer works, not on the label. After Duguid, the question is whether the equipment uses a random or sequential number generator to store or produce the numbers it calls. A predictive dialer that pulls from a loaded list generally doesn’t, but the answer turns on the specific system, which is why these cases so often come down to the equipment records and the expert.
Defending an autodialer claim
If your company has been sued over calls or texts a plaintiff says were autodialed, the dialer records and the plaintiff’s expert report will shape the defense from the first week. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including autodialer claims under Section 227(b). Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
The statute is the Telephone Consumer Protection Act at 47 U.S.C. § 227, which defines an automatic telephone dialing system in subsection (a)(1). The discovery rules are Federal Rule of Civil Procedure 26, and the admissibility standard is Federal Rule of Evidence 702.
The court decisions are Facebook, Inc. v. Duguid, 592 U.S. 395 (2021); Daubert v. Merrell Dow Pharmaceuticals, Inc., 509 U.S. 579 (1993); and Kumho Tire Co. v. Carmichael, 526 U.S. 137 (1999).
This post is general information about the Telephone Consumer Protection Act and related laws as of August 12, 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.