Case analysis · Litigation & decisions
Panzarella v. Navient: The Third Circuit Asks Whether the Call Itself Used Random or Sequential Number Generation
A debt servicer that dialed numbers drawn from its own curated account lists did not make calls "using" an automatic telephone dialing system, even assuming its dialing platform qualified as one. In Panzarella v. Navient Solutions, Inc., No. 20-2371, 37 F.4th 867 (3d Cir. June 14, 2022), the U.S. Court of Appeals for the Third Circuit affirmed summary judgment for Navient on that alternative ground.
On this page
The bottom line: in the Third Circuit, a Telephone Consumer Protection Act (TCPA) autodialer claim requires proof that the challenged call actually employed the system's random or sequential number generation capacity.
Background
Navient serviced the student loans of Matthew Panzarella, who listed his mother Elizabeth and brother Joshua as references and supplied their cell phone numbers. After he became delinquent, Navient called Elizabeth's number four times and Joshua's number fifteen times over five months. The Panzarellas filed a putative class action under 47 U.S.C. § 227(b)(1)(A)(iii).
Navient used the Interaction Dialer, software developed by Interactive Intelligence Group, Inc., which runs across several servers, including a database server managed by Microsoft SQL Server. That database server could generate random and sequential 10 digit numbers in a table, but every number it actually stored came from Navient's separate account database. The district court granted summary judgment after treating the SQL Server as separate from the dialing system.
The decision
Judge Rendell wrote for the panel, joined by Judge Scirica. Judge Greenaway concurred in the judgment.
- "Equipment" includes the whole system. Looking to the ordinary meaning of "equipment," the statute's focus on "systems," and Federal Communications Commission (FCC) rulings it treated as persuasive, the court held that an autodialer may consist of several devices that together have the required capacity. The district court erred by carving the SQL Server out of Navient's system.
- Duguid did not impose an actual use test for the definition. Navient argued that Facebook, Inc. v. Duguid requires a system to actually use a number generator to qualify as an autodialer. The majority disagreed, reading Duguid as resolving only whether "using a random or sequential number generator" modifies both "store" and "produce." Under the circuit's earlier Dominguez v. Yahoo decision, present capacity still controls. Because the record conflicted on that capacity, the court did not decide whether Navient's system was an autodialer.
- The call must use the autodialing function. The court instead focused on the prohibition on "making any call . . . using any" autodialer. Drawing on context, legislative history and Duguid's description of the harms Congress targeted, it held that a call violates § 227(b)(1)(A) only if it employs the system's capacity to use a random or sequential number generator to produce or store the numbers dialed. The opinion's "Junk Call Corp." hypothetical illustrates the point: calls placed in "automatic" mode would count, but calls placed from an imported customer list would not.
- Application. Navient drew the Panzarellas' numbers from "specific, curated borrower lists" tied to student loan accounts. There was no evidence it used random or sequential generation to call them, so summary judgment was proper.
The concurrence
Judge Greenaway agreed the SQL Server was part of the equipment, but would have held that a system must actually use a random or sequential number generator to qualify as an autodialer under § 227(a)(1), relying on Duguid's language. He would have affirmed on that ground.
Practical takeaways
- Document how each calling campaign selects numbers, and keep evidence that lists come from account or consent records.
- Separate any number generation features from production calling configurations, and record which mode was used.
- Remember that this ruling addresses only the autodialer prohibition. Prerecorded voice, do-not-call and state law claims are analyzed separately.
Not legal advice. TCPA.com provides general information, not legal advice, and is not a substitute for the advice of an attorney. Do not rely on it. Verify any action with your own licensed lawyer before you take it. See our Terms of Use.
