37 F.4th 867
3rd Cir.2022Background
- Navient used an Interactive Intelligence (ININ) Interaction Dialer integrated with a Microsoft SQL Server database to place outbound calls regarding delinquent student loans.
- Matthew Panzarella listed his mother (Elizabeth) and brother (Joshua) as references; Navient called their cellphones multiple times after Matthew became delinquent.
- Plaintiffs sued under the TCPA, alleging Navient called their cellphones without prior express consent using an automatic telephone dialing system (ATDS) in violation of 47 U.S.C. § 227(b)(1)(A)(iii).
- The District Court granted summary judgment for Navient after treating the SQL Server as separate from the ININ dialing system and concluding the dialer lacked ATDS capacity.
- The Third Circuit held the SQL Server is part of the dialing “equipment,” and that the ATDS definition can encompass combined devices, but affirmed summary judgment on alternative grounds: the record shows Navient dialed curated account-based lists rather than using random/sequential number generation, so the calls were not made "using" an ATDS.
Issues
| Issue | Plaintiff's Argument | Defendant's Argument | Held |
|---|---|---|---|
| Whether Navient's dialing setup (ININ + SQL Server) qualifies as an ATDS under §227(a)(1) | ININ system plus SQL Server together have capacity to store/produce numbers and dial, so they form an ATDS | SQL Server is distinct third-party database and ININ alone cannot generate random/sequential numbers, so not an ATDS | Court: SQL Server properly considered part of the dialing "equipment," so District Court erred to exclude it for ATDS inquiry (no final ATDS determination reached) |
| Whether Duguid means an ATDS must actually use a random/sequential number generator (actual-use) rather than merely have capacity | Plaintiffs: ATDS definition focuses on capacity; present capacity suffices | Navient: Duguid requires actual use of a generator to qualify as an ATDS | Court: Duguid resolved a different question (store vs produce); it does not hold ATDS must have actually used a generator. Capacity standard remains controlling for ATDS eligibility |
| Whether the calls were made "using" an ATDS under §227(b)(1)(A) (i.e., whether TCPA liability attaches) | Calls placed by Navient used the ININ System (an ATDS) to contact cellphones without consent | Navient: Even if system could qualify as ATDS, it did not use random/sequential generation—calls came from curated account lists, not autodialed random/sequential numbers | Held: For liability, calls must employ ATDS autodialing functionality (random/sequential generation to store/produce numbers). Record shows Navient dialed targeted account lists, not via random/sequential generation; no TCPA violation. |
| Whether summary judgment should be affirmed | Plaintiffs: District Court erred in excluding SQL Server and should have allowed ATDS fact question to proceed | Navient: Entitled to summary judgment because it did not "use" an ATDS to call plaintiffs | Held: Affirmed (on alternative grounds): even assuming ATDS status, no evidence calls were made using autodialing functionality, so summary judgment for Navient is proper. |
Key Cases Cited
- Facebook, Inc. v. Duguid, 141 S. Ct. 1163 (2021) (interpreting whether the modifier "using a random or sequential number generator" applies to both "store" and "produce" in the ATDS definition)
- Dominguez v. Yahoo, Inc., 894 F.3d 116 (3d Cir. 2018) (adopting capacity-based test: present capacity to generate/dial random or sequential numbers qualifies as ATDS)
- ACA Int’l v. FCC, 885 F.3d 687 (D.C. Cir. 2018) (treating combinations of equipment as potentially forming an ATDS when used together)
- Mims v. Arrow Fin. Servs., LLC, 565 U.S. 368 (2012) (overview of TCPA scope and private right of action)
- Gager v. Dell Fin. Servs., LLC, 727 F.3d 265 (3d Cir. 2013) (characterizing TCPA as remedial and interpreting ATDS-related issues in context)