It Will All Come Out in the “Wash”: Did a Southern California District Court Just Solve the TCPA’s ACA Int’l/ATDS Conundrum Once and For All?

Sometimes the most obvious answer is the hardest one to see.

For weeks now the courts have been debating whether the 2003 and 2008 Predictive Dialer Rulings were set aside byACA Int’lor just the 2015 TCPA Omnibus ruling. Indeed, the landscape is so fractured that TCPAland.com now has a separate menu feature dedicated to tracking these cases as they come out.

But what if the answer is thatACA Int’ldidn’t set aside any specific FCC rulings at all, just the FCC’s approach to defining the functions of an ATDS in any and all of its earlier orders? That is the Eureka! moment contained within the reasoning inWash. v. Six Continents Hotels, Case No. 2:16-CV-03719-ODW-JEM, 2018 U.S. Dist. LEXIS 145639 (C.D. Cal. Aug. 24, 2018). InWashthe Court ultimately denied a Defendant’s motion to dismiss a TCPA complaint alleging unlawful text messages, but not before obliterating all previous assumptions about how theACA Int’lruling interacts with earlier FCC rulings defining an ATDS.

Going step by step, the Court first determined–and contrary to recent rulings out of the Northern District of California— that the ACA Int’ldetermination is binding across the country. The analysis by the Court is compact and clear: “As an agency can make rulings that have nationwide effect, the finding of a court of appeals in reviewing an agency ruling also has nationwide precedential effect.”Washat *6. Simple as that.

Next the Court considered whatACA Int’lactually reviewed. After noting that petitioners sought review of previous FCC orders–not just the 2015 Omnibus Order–the Court found thatACA Int’l“reaches previous orders filed by the FCC, and not just the 2015 Order immediately at issue.”Washat *6. As didSessions,PinkusandKeyesbefore it, theWashcourt noted thatACA Int’lspecifically rejected the FCC’s contention that the D.C. Circuit Court of Appeal lacked jurisdiction to review the FCC’s 2003 and 2008 Predictive Dialer Rulings.

In theWashcourt’s view,ACA Int’lset out to answer two questions regrading the TCPA’s definition of an ATDS:“(i) when does a device have the ‘capacity’ to perform the two enumerated functions; and (ii) what precisely are those functions?” SeeWashat *7, citingACA Int’lat 695. After acknowledging that the D.C. Circuit’s answer to the second question is “somewhat less clear”, theWashcourt concludes that the “matters” set aside byACA Int’l includes “both the definition of a predictive dialer as an ATDS, and the discussion of potential capacity of autodialer function.” SeeWashat *8, fn 2.

And that’s where things get interesting. When turning to an analysis of BadReyes, theWashcourt steps out of the binary world we’ve been living in and suggests that Courts have been looking at the issue of ACA Int’l‘s impact on earlier FCC rulings allwrong. Instead,Washspecifically rejects the reasoning of BadReyes noting that “[b]y its plain language, the Court inACA Int’ldid not set aside the 2015 ruling, but rather ‘the Commission’s treatment of [which functions qualify a device as an autodialer].'”Washat *8 citingACA Int’l, 885 F.3d at 703. Instead:

“As the court in ACA did not set aside a ruling, but rather the FCC’s treatment of the definition of an autodialer, this treatment was set aside from all previous FCC rulings.”

Washat *8-9

Well look at that.

The Court concludes: “It was the clear intention of the D.C. Circuit to set aside all such competing definitions until the FCC cho[o]ses to clearly establish that the ‘must be able to generate and dial random or sequential numbers’ standard is no longer a requirement for a device to be considered an ATDS.”

On behalf of TCPAland, I’d like to start a slow clap.

Washfeels like a defining moment in the seesaw battle over the ATDS definition. Just like when GoodReyescame out, I readWash andthinkof course that’s the answer. Why couldn’t I see it before?ACA Int’ldidn’t set aside any specific rulings or orders. Rather it rejected the specific reasoning of the FCC in approaching a specific matter–the definition of an ATDS. And that reasoning was clearly rejected across all of the FCC’s earlier rulings. This is similar to the analysis ofTrueBlue, of course,but theWashCourt really breaks it down into much-needed baby steps.

Notably the Court goes on to deny the Defendant’s motion to dismiss because the Plaintiff–truthfully?–alleged that the dialer has the present capacity to randomly generate numbers to be dialed.SeeWashat *10. That, the Court finds, is sufficient to state a TCPA claim under the statutory definition. Pretty non-controversial conclusion.

And–in further proof that HI is in the eye of the beholder–the Court pivots to a finding that human intervention “looks to the time a call or message is sent or dialer, not what might have happened earlier to enter the phone number into the system.”Washat *13. This, of course, is directly inconsistent with the recent ruling inRamosand underscores why texters/callers should never count on human intervention for salvation.

Photo Credit: Emiliano Arano on Pexels.com.

[View source.]