
We’ll keep you up to speed on all the breaking ATDS cases across the country. Every time a new ATDS case breaks we’ll be the first to spread the news and keep you updated with this easy to navigate page.
Here’s your TCPAworld ATDS review updated as of July 8, 2020.
Cases Holding Random or Sequential Number Generation is Required for Equipment to Qualify as an ATDS
A number of 2018 decisions—including one from the Third Circuit Court of Appeal— held that random or sequential number generation is required for a device to qualify as an ATDS under the TCPA. See:
- Dominguez v. Yahoo, Inc., 2018 U.S. App. LEXIS 17350 (3rd Cir. June 26, 2018)(systems that lack the present capacity to dial randomly or sequentially do not qualify as an ATDS under the TCPA);
- Lord v. Kisling, Case No. 1:17-CV-01739, 2018 U.S. Dist. LEXIS 116288 (N.D. Oh. July 12, 2018)(failure to allege random or sequential number generation sufficient to justify dismissal of TCPA text message case)
- Pinkus v. Sirius Xm Radio, 16 C 10858, 2018 U.S. Dist. LEXIS 125043 (N.D. Ill. July 26, 2018)(failure to allege random or sequential number generation fatal to TCPA complaint);
- Gary v. TrueBlue, Inc., Case No. 17-cv-10544, 2018 WL 3647046 (E.D. Mich. Aug. 1, 2018)(random or sequential number generation necessary to assert TCPA claim);
- Keyes v. Ocwen Loan Servicing, No. 17-cv-11492, 2018 U.S. Dist. LEXIS 138445, at *15 (E.D. Mich. Aug. 16, 2018)(Aspect predictive dialer not an ATDS because did not dial using random or sequential number generator);
- Wash. v. Six Continents Hotels, Case No. 2:16-CV-03719-ODW-JEM, 2018 U.S. Dist. LEXIS 145639 (C.D. Cal. Aug. 24, 2018)(random or sequential number generation required);
- Fleming v. Associated Credit Servs., No. 16-3382 (KM) (MAH), 2018 U.S. Dist. LEXIS 163120 (D.N.J. Sep. 21, 2018) (ATDS required to produce numbers using a random or sequential number generator);
- Stewart L. Roark v. Credit One Bank, N.A., No. CV 16-173 (PAM/ECW), 2018 WL 5921652 (D. Minn. Nov. 13, 2018)(random or sequential number generation required).
- Johnson v. Yahoo!, Inc., No. 14-cv-02028 (N.D. Ill. Nov. 29, 2018)(statutory definition of ATDS unambiguously required random or sequential number generation capacity).
- Richardson v. Verde Energy United States, No. 15-6325, 2018 U.S. Dist. LEXIS 212558, (E.D. Pa. Dec. 14, 2018) (requires random or sequential number generation required).
- Harbach v. Usaa Fed. Sav. Bank, Case No. 15-CV-2098-CJW-KEM, 2019 U.S. Dist. LEXIS 3687 (N.D. Iowa Jan. 9, 2019)(random or sequential number generation needed to state TCPA claim).
- Asher v. Quicken Loans, Inc., Case No. 2:17-cv-1203, 2019 WL 131854 (D. Utah Jan. 8, 2019)(equipment must have capacity to call using a random or sequential number generator but the specific call at issue need not have been placed using that capacity.)
- Folkerts v Seterus, Inc., Case No. 17 c 4171, 2019 U.S. Dist. Lexis 42347 (N.D. Ill. Mar. 15, 2019)(random or sequential number generation required for a system to qualify as an ATDS)
- Gadelhak v. AT&T Servs., No. 17-cv-01559 (March 29, 2019)(refusing to follow Marks in favor of requiring “random or sequential number generation.)
- Zanard v. Bank of Am. & Specialized Loan Servicing, No. 3:15-cv-1208 (MPS), 2019 U.S. Dist. LEXIS 72425 (D. Conn. April 30, 2019)(random and sequential number generation required);
- Zeidel v. Nat’l Gas & Elec., LLC, 18-cv-06792, 2019 U.S. Dist. LEXIS 83988 (N.D. Ill. May 17, 2019).
- Bader v. Navient Solutions, LLC, 2019 U.S. Dist. LEXIS 100396 (N.D.Ill June 14, 2019)(random or sequential number generation is required to state ATDS claim)
- Snow v. General Electric, No. 5:18-CV-511-FL, 2019 U.S. Dist. LEXIS 99760 (E.D.N.C. June 14, 2019)(text message case dismissed with prejudice for lack of random and sequential number generation allegations)
- Adams v. Safe Home Sec., Civil Action No. 3:18-cv-03098-M, 2019 U.S. Dist. LEXIS 126522 (N.D. Tx. July 30, 2019)(Chief Judge of ND Tx holds that predictive dialers are not ATDS and dialers must use random or sequential number generator to qualify under the TCPA)
- Smith v. Navient Solutions, LLC, 2019 U.S. Dist. LEXIS 131231 (W.D. Pa. Aug. 4, 2019)(rejecting Marks and requiring random and sequential number generation).
- Morgan v. On Deck Capital, CASE NO. 3:17-CV-00045, 2019 U.S. Dist. LEXIS 147757 (W.D. Va. Aug. 29, 2019)(applying statutory definition but concluding manual process might have used system with “capacity” to dial randomly or sequentially.)
- Brown v. Ocwen Loan Servicing Llc, Case No. 8:18-cv-136-T-60AEP, 2019 U.S. Dist. LEXIS 151236 (M.D. F. Sept. 5 2019)(MSJ for defense– predictive dialer is not an ATDS unless it can dial randomly or sequentially)
- Johnson v. Capital One Servs., No. 18-cv-62058, 2019 U.S. Dist. LEXIS 159633 (S.D. Fla. Sept. 16, 2019)(summary judgment on ATDS issue in collection call case).
- Reed v. Quicken Loans, No. 3:18-cv-3377, 2019 U.S. Dist. LEXIS 159935 (N.D. Tex. Sept. 3, 2019)(motion to dismiss on ATDS issues granted in phone call case.)
- Denova v. Ocwen Loan Servicing, CASE NO. 8:17-cv-2204-T-23AAS, 2019 U.S. Dist. LEXIS 163014 (M.D. Fl. Sept. 24, 2019)(rejecting Magistrate Judge recommendation to deny summary judgment in reliance on 2003 and 2008 predictive dialer rulings.)
- Rivero v. D’Jais, Civil Action No.: 18-12697 (FLW) (ZNQ), 2019 U.S. Dist. LEXIS 170246, (D. N.J. Sept. 30, 2019)(ATDS requires random or sequential number generation– but mere capacity to send messages in such fashion is all that is required; manually sent messages might still qualify.)
- Morgan v. Adventist Health System/Sunbelt, Inc., et al., Case No. 6:18-cv-1342-Orl-78DCI (M.D. Fl., Jan. 13, 2020)(Random or sequential number generation required for device to qualify as an ATDS).
- Glasser v. Hilton Grand Vacaitons, Case No. 18-14499 (11th Cir. Jan. 27, 2020 Decided)(Game changing appellate court decision rejecting Marks and holding directly–after lengthy analysis–that ATDS definition requires random and sequential number generation.)
- Gadelhak v. AT&T Services, No. 19-1738 (7th Cir. Feb. 19, 2020)(Adopting requirement of the use of a random or sequential number generator for a system to qualify as an ATDS.)
- Perez v. Quicken Loans, Inc., Case No. 19-cv-2072, 2020 U.S. Dist. LEXIS 53476 (N.D. Ill. March 27, 2020) (imposing heightened pleadings standard in post-Gadelhak world.)
- Dotson v. Dish Network L.L.C., 2:19-CV-21, 2020 U.S. Dist. LEXIS 48783 (S.D. Ga. March 19, 2020)(following Glasser and entering summary judgment for defendant.)
- Hagood v. Portfolio Recovery Assocs., Case No. 3:18-CV-1510-NJR, 2020 U.S. Dist. LEXIS 47507 (S.D. Ill. March 19, 2020) (following Gadelhak and entering summary judgment for Defendant).
- Decapua v. Metro. Prop. & Cas. Ins. Co., C.A. No. 18-590 WES, 2020 U.S. Dist. LEXIS 47695 (D. R.I. March 18, 2020)(Applying statutory ATDS definition and rejecting argument that potential excel spreadsheet randomization converts system into ATDS)
- Mosley v. General Revenue Corp., Civil Action No. 1:20-cv-01012-JES-JEH, 2020 U.S. Dist. LEXIS 127055 (C.D. Ill. July 20, 2020)(following Gadelhak and determining debt collection calls not subject to TCPA).
Cases Holding Random or Sequential Number Generation is Not Required
The case law departing from the statutory view is fractured.
Duran v. LaBoom Disco
On the one hand are cases following the approach of the recent Second Circuit Court of Appeal decision in Duran v. La Boom Disco, case no. 19-600-cv, (2nd Cir. 2020). These cases hold, in essence, that the FCC’s 2003 and 2008 Predictive Dialer Orders were not set aside by ACA Int’l and that the TCPA’s ATDS definition continues to apply to predictive dialers and other systems that call automatically from a list of numbers.
Cases Following Duran Approach
Marks v. Crunch
Similarly, but distinctly, the Ninth Circuit Court of Appeals decision in Marks v. Crunch holds that the FCC’s 2003 and 2008 Orders are set aside but that the statutory definition does not require random or sequential number generation—instead, Marks holds that a dialer is an ATDS if it has the capacity to store numbers to be called and to dial such numbers automatically (even if the system must be turned on or triggered by a person.)
Cases Following Marks
- Keifer v. Hosopo Corp., Case No. 3:18-cv-1353, 2018 U.S. Dist. Lexis 183468 (S.D. Cal. Oct. 25, 2018) (following Marks in holding that the statutory definition of ATDS does not require equipment to “create or develop the numbers dialed on its own”);
- Adams v. Ocwen, Case No. 18-81028, Dkt # 23 (M.D. Fl. Oct. 29, 2018) (following Marks in holding that the statutory definition of ATDS includes a device that stores telephone numbers to be called, whether or not those numbers have been generated by a random or sequential number generator);
- Shupe v. Capital One Bank USA NA, No. CV-16-00571-TUC-JGZ, 2018 U.S. Dist. LEXIS 183456 (D. Ariz. Oct. 25, 2018)(following Marks but determining that summary judgment in favor of Defendant was still appropriate on evidence before it);
- Singer v. Las Vegas Ath. Clubs, Case No.: 2:17-cv-01115-GMN-VCF, 2019 U.S. Dist. LEXIS 48838 (D. Nv. March 25, 2019);
- Gonzales v. Hosopo Corporation, 2019 WL 1533295 (D. Mass. Apr. 9, 2019)(following Marks);
- Espejo v. Santander, Case No. 11 c 8987, Dkt. No. 250 (N.D. Ill. June 12 2019)(ATDS definition is vague but calling from a list is all that is necessary)
- Allan v. Pennsylvania Higher Education Assistance Agency, No. 2:14-cv-54 (W.D. Mich. Aug. 19, 2019)(following Marks and extending reach of Marks to Michigan and Sixth Circuit for the first time);
- McCullough v. Maximum Title Loans Llc, No. CV-19-00717-PHX-JJT, 2019 U.S. Dist. LEXIS 141323 (D. Az. Aug. 20, 2019)(following Marks at pleadings stage to overrule MTD);
- Wilson v. Pa. Higher Educ. Assistance Agency, Case No. 2:14-CV-54 2019 U.S. Dist. LEXIS 139740 (W.D. Mich. Aug. 19, 2019)(Court follows Marks and finds Avaya predictive dialer to be an ATDS.)
- Bodie v. Lyft, Inc., Case No.: 3:16-cv-02558-L-NLS 2019 U.S. Dist. LEXIS 172998 (S.D. Cal. Oct. 4, 2019)(following Marks in motion to dismiss ATDS regarding Twilio text message platform);
- Castillo v. Caesars Entm’t Corp., Case No.: 2:18-cv-02297-GMN-NJK, 2019 U.S. Dist. LEXIS 169810 (D. Nv. Sept. 30, 2019)(Applying Marks to text message platform at MSJ phase).
- Johnson v. Comodo Group, Case No. 16-4469, DKT # 221 (D. N.J. Jan. 31, 2020)(finding VICIdialer is an ATDS as all predictive dialers are ATDS under Marks, which court follows.)
- Meza v. Sirius XM Radio Inc., Case No.: 17-CV-02252-AJB-JMA, 2020 U.S. Dist. LEXIS 32379 (S.D. Cal. Feb. 25, 2020)
- Pederson v. Donald J. Trump for President, Civil No. 19-2735 (JRT/HB), 2020 U.S. Dist. LEXIS 99974 (D. Minn. June 8, 2020) (huge ruling by Chief Judge of D. Minn. that swings Eighth Circuit toward Marks view.)
- Hayhurst v. Keller Williams Realty, 1:19CV657, 2020 U.S. Dist. LEXIS 128877 (M.D.N.C. July 22, 2020)(rejecting Gadelhak and following Marks)
Notably a few cases also refuse to follow Marks and criticize its reasoning:
- Roark v. Credit One Bank, N.A., No. 16-173 (PAM/ECW), 2018 U.S. Dist. LEXIS 193252 (D. Minn. Nov. 13, 2018)(Finding that Dominguez reasoning was “more persuasive” than Marks, and that ATDS is a device that has the present capability to randomly or sequentially generate numbers to dial.)
- Harbach v. Usaa Fed. Sav. Bank, Case No. 15-CV-2098-CJW-KEM, 2019 U.S. Dist. LEXIS 3687 (N.D. Iowa Jan. 9, 2019)(Refusing to follow Marks as “overly broad” interpretation of the TCPA.)
- Gadelhak v. AT&T Servs., No. 17-cv-01559 (March 29, 2019)(refusing to follow Marks in favor of requiring “random or sequential number generation.)
- Smith v. Navient Solutions, LLC, 2019 U.S. Dist. LEXIS 131231 (W.D. Pa. Aug. 4, 2019)(rejecting Marks and requiring random and sequential number generation).
- Glasser v. Hilton Grand Vacaitons, Case No. 18-14499 (11th Cir. Jan. 27, 2020 Decided)(Game changing appellate court decision rejecting Marks and holding directly–after lengthy analysis–that ATDS definition requires random and sequential number generation.)
- Gadelhak v. AT&T Services, No. 19-1738 (7th Cir. Feb. 19, 2020)(Adopting requirement of the use of a random or sequential number generator for a system to qualify as an ATDS.)
At least one other court also determined that dialers that call automatically qualify under the TCPA in 2018 although the reasoning was not particularly clear:
- Heard v. Nationstar Mortg. LLC, Case No.: 2:16-cv-00694-MHH, 2018 U.S. Dist. LEXIS 143175 (N.D. Ala. Aug. 23, 2018)(Avaya predictive dialer met the statutory definition of an ATDS regardless of FCC rulings.)
Human Intervention Cases
Following the 2015 TCPA Omnibus ruling a large number of cases focused on human intervention as a way to bring some sanity to the extremely broad ATDS formulation the FCC handed down.
With the 2015 TCPA Omnibus overturned, however, the focus of recent decisions has been on the functionalities an ATDS must perform rather than on human intervention. Nonetheless, with Marks and LaBoom focusing on “automatic” dialing—and with the FCC set to determine whether automated functionalities must actually be “used” to trigger statutory coverage as part of its Public Notice—understanding the role of “human intervention” in the ATDS equation remains a priority.
As in previous years, there is little consistency in court decisions addressing human intervention. As I have written recently, human intervention appears to be in the eye of the beholder to some degree.
For instance, some courts continue to consider human intervention in the process of compiling dialer lists as sufficient to remove equipment from statutory coverage. See:
- Gaza v. Auto Glass America, LLC, Case No. 8:17-cv-01811, Doc. No. 42 (M.D. Fl. Nov. 2, 2019)( creation of a dialer list by virtue of manual review of invoices and other documents to create an excel spreadsheet of phone numbers and contact info sufficient human intervention to defeat inference of ATDS usage)
- Ramos v. Hopele of Fort Lauderdale, No. 17-62100-CIV-MORE, 2018 U.S. Dist. LEXIS 139947 (S.D. Fla. Aug. 16, 2018)(human intervention of physically inputting numbers, drafting messages, selecting recipients, choosing date and time to send the message, and manually hitting a “send” button sufficient)
- Decapua v. Metro. Prop. & Cas. Ins. Co., C.A. No. 18-00590-WES 2019 U.S. Dist. LEXIS 168061 (D. R.I. Sept. 30, 2019)(Following Ramos and concluding that mass blast text messages violated the “spirit but not the letter” of the TCPA based upon human intervention needed in selecting the timing and recipients of messages.)
- Beal v. Outfield Brew House, 2020 U.S. Dist. LEXIS 22487 (manually entered numbers that were “shuffled” and texted automatically was sufficient human intervention.)
Not all cases agree, however, and numerous decisions have rejected human intervention as insufficient if it is not employed at the time numbers are dialed. Indeed the Second Circuit Court of Appeal held–as a matter of law–that the same EZ Texting platform at issue in Gaza and Ramos actually is an ATDS, after all. What a mess.
On the other hand, the Eleventh Circuit Court of Appeal has held that a call is made with human intervention anytime a call is made as a result of “an employee’s choice” to initiate each call.
Whatever else may be sufficient, courts continue to consider “click to dial” systems outside the purview of statutory coverage—perhaps even applying Marks. See:
- Hatuey v. IC Sys., No. 1:16-cv-12542-DPW, 2018 U.S. Dist. LEXIS 193713 (D. Mass. Nov. 14, 2018)(granting MSJ on ATDS use because – even under the broadest reading of the definition of ATDS – click to dial was not an ATDS.)
- Maddox v. CBE Grp., Inc., No.: 1:17-cv-1909-SCJ, 2018 WL 2327037 (N.D. Ga. May 22, 2018)(click to dial meets “human intervention test”);
- Glasser v. Hilton Grand Vacations Co., No. 8:16-cv-952-JDW-AAS, 2018 U.S. Dist. LEXIS 162867 (M.D. Fla. Sep. 24, 2018) (click to dial meets “human intervention” test).