Subscribe to our InfoBytes Blog weekly newsletter and other publications for news affecting the financial services industry.
District Court allows TCPA action to proceed, citing 9th Circuit autodialer definition as binding law
On January 17, the U.S. District Court for the District of Arizona denied a cable company’s motion to stay a TCPA action, disagreeing with the company’s arguments that the court should wait until the FCC releases new guidance on what constitutes an automatic telephone dialing system (autodialer) before reviewing the case. A consumer filed a proposed class action against the company, arguing that the company violated the TCPA by autodialing wrong or reassigned telephone numbers without express consent. The company moved to stay the case, citing the FCC’s May 2018 notice (covered by InfoBytes here), which sought comments on the interpretation of the TCPA following the D.C. Circuit’s decision in ACA International v. FCC (setting aside the FCC’s 2015 interpretation of an autodialer as “unreasonably expansive”). The company argued that the FCC would “soon rule on what constitutes an [autodialer], a ‘called party,’ in terms of reassigned number liability, and a possible good faith defense pursuant to the TCPA,” all of which would affect the company’s liability in the proposed class action. The court rejected these arguments, citing as binding law Marks v. Crunch San Diego, LLC, a September 2018 decision from the U.S. Court of Appeals for the 9th Circuit that broadly defined what constitutes an autodialer under the statute (covered by InfoBytes here), and therefore, determining there was nothing to inhibit the court from proceeding with the case. As for the FCC’s possible future guidance on the subject, the court concluded, “there seems little chance that any guidance from the FCC, at some unknown, speculative, future date, would affect this case.”
On November 29, the U.S. District Court for the District of New Jersey partially denied a company’s motion to dismiss proposed class action allegations that it violated the TCPA when it used an automatic telephone dialing system (ATDS) to send unsolicited text messages to customers’ cell phones that resulted in additional message and data charges. According to the opinion, the company sent three text messages to the plaintiff who responded to two of them. The first message gave the plaintiff the option to send “STOP” to opt out or “HELP” to receive assistance. Because the plaintiff texted “HELP” in response, the court found that the plaintiff consented to receiving the company’s second message; the court found that the third follow-up message was permissible because it was a single “confirmatory message” sent after the plaintiff texted “STOP” after receiving the second follow-up message. However, the court determined that the plaintiff satisfied the burden of showing at this stage in the proceedings that the first text message was sent from a company with whom he had no prior relationship and had not provided consent. “When an individual sends a message inviting a responsive text, there is no TCPA violation,” the judge ruled. “The TCPA prohibits a party from using an ATDS ‘to initiate any telephone call to any residential telephone line using an artificial or prerecorded voice to deliver a message without the prior express consent of the called party,’ unless the call falls within one of the statute’s enumerated exemptions.”
The court further denied the company’s motion to stay pending the FCC’s interpretation of what qualifies as an ATDS in light of the decision reached by the D.C. Circuit in ACA International v. FCC, stating, among other things, that the company “has not established the FCC proceedings will simplify or streamline the issues in this matter” and that the plaintiff is entitled to discovery concerning the company’s communication devices.
On November 13, the U.S. District Court for the District of Minnesota held that a bank’s predictive dialing systems do not violate the Telephone Consumer Protection Act (TCPA), granting summary judgment for the bank. According to the opinion, a customer of a national bank changed his phone number and his previous number was reassigned to the plaintiff in the case. The customer did not inform the bank he had changed his phone number, and between September 2015 and December 2015, the bank called the plaintiff’s cell phone 140 times. The plaintiff subsequently informed the bank he was not a customer and the bank ceased calling the cell phone number. In January 2016, the plaintiff filed a complaint alleging the company violated the TCPA by placing auto-dialed calls to his cell phone. The court stayed the action pending the result of the D.C. Circuit case ACA International v. FCC (covered by a Buckley Sandler Special Alert), which narrowed the FCC’s 2015 interpretation of “autodialer” under the TCPA.
In reviewing cross-motions for summary judgment, the court disagreed with the plaintiff that the company’s predictive dialing systems qualified as an autodailer under the TCPA. Citing to ACA International, the court noted that predictive dialers are not always autodialers under the Act, the equipment must have the capacity to randomly or sequentially generate numbers to dial, and the plaintiff failed to provide sufficient evidence to prove the systems has this capability. Moreover, the court rejected the plaintiff’s argument that it should follow the 9th Circuit, which recently broadened the definition of autodialer under the TCPA (covered by InfoBytes here), concluding that other courts’ narrow interpretations were more persuasive (InfoBytes coverage available here).
On October 30, the U.S. District Court for the Western District of Wisconsin denied a company’s motion to dismiss allegations that it violated the TCPA when it used a predictive dialer to try to collect a debt from the plaintiff. According to the opinion, the plaintiff alleged the company called him repeatedly without permission in an attempt to collect a debt using a predictive dialer. The company moved to dismiss because the plaintiff did not allege that the company used an autodialer with the ability to dial random or sequential phone numbers, which the company argued was required by the TCPA. The court found that a predictive dialer is an autodialer under the TCPA even if it does not generate random or sequential numbers. This conclusion was based on a 2003 FCC ruling, which stated that predictive dialers are autodialers “even if the device does not dial random or sequentially generated numbers.” The court further noted that the decision reached by the D.C. Circuit in ACA International v. FCC—which set aside the FCC’s 2015 interpretation of an autodialer as unreasonably expansive—did not invalidate the FCC’s 2003 order. (See previous Buckley Sandler Special Alert on ACA International here.) Based on this analysis, the court concluded that the plaintiff had established the three elements necessary to allege a TCPA violation.
On October 30, the U.S. Court of Appeals for the 9th Circuit denied a California gym’s petition for a rehearing en banc of the court’s September decision reviving a TCPA putative class action. As previously covered by InfoBytes, the appeals court vacated a district court order granting summary judgment in favor of the gym, concluding that there was a genuine issue of material fact as to whether the text system used by the gym—which stores numbers and dials them automatically to send the messages—qualified as an “autodialer” under the TCPA. Notably, in vacating the summary judgment order, the 9th Circuit performed its own review of the statutory definition of an autodialer in the TCPA, because the recent D.C. Circuit opinion in ACA International v. FCC (covered by a Buckley Sandler Special Alert) set aside the FCC’s definition. Through this review, the appeals court concluded that the TCPA defined an autodialer broadly as “equipment which has the capacity—(i) to store numbers to be called, or (ii) to produce numbers to be called, using a random or sequential number generator—and to dial such numbers automatically (even if the system must be turned on or triggered by a person).”
FCC seeks comments on interpretation of TCPA definition of autodialer following 9th Circuit decision
On October 3, the FCC’s Consumer and Governmental Affairs Bureau released a notice seeking comment on the interpretation of the TCPA in light of a recent 9th Circuit decision, which broadened the definition of an automatic telephone dialing system (autodialer) under the TCPA. As previously covered in InfoBytes, on September 20, the 9th Circuit held that the TCPA’s definition of an autodialer includes equipment with the capacity to store numbers to be called and to automatically dial such numbers whether or not those numbers have been generated by a random or sequential number generator. The court, however, declared the statutory definition of an autodialer to be “ambiguous on its face” and, thus, it looked to the context and structure of the TCPA in reaching its conclusion regarding the scope of the definition.
The FCC issued the notice “to supplement the record developed in response” to a prior notice issued last May, which sought comments on the interpretation of the TCPA following the D.C. Circuit’s decision in ACA International v. FCC. (See previous InfoBytes coverage on the May 2018 notice here.) Specifically, the FCC seeks comments on the following issues relevant to developing an interpretation of the TCPA’s definition of autodialer: (i) To the extent the definition of an autodialer is ambiguous, how should the FCC exercise its discretion to interpret such ambiguities? (ii) Does the 9th Circuit’s interpretation mean that any device with the capacity to dial stored numbers automatically qualifies as an autodialer? (iii) What devices have the capacity to store numbers, and do smartphones have such capacity? and (iv) What devices that have the capacity to dial stored numbers also have the capacity to automatically dial such numbers and do smartphones have such capacity?
Comments are due October 17 with reply comments due October 24.
On September 24, the U.S. District Court for the Middle District of Florida held that a hotel calling system, which required human intervention before a call was placed, does not qualify as an automatic telephone dialing system (autodialer) under the TCPA. The plaintiff filed the putative class action complaint alleging the hotel chain used an autodialer to call her cell phone without her consent. The hotel moved for summary judgment, arguing that the system did not qualify as an autodialer under the TCPA because it required a hotel agent to click “Make Call” before the system dialed the number. The court agreed, concluding that the defining characteristic of an autodialer is “the capacity to dial numbers without human intervention,” which the court noted remains unchanged even in light of the D.C. Circuit decision in ACA International v. FCC (covered by a Buckley Sandler Special Alert here). Because the calling system would not initiate an outbound call without an agent clicking the “Make Call” button, the court determined the plaintiff’s TCPA claim failed and granted summary judgment for the hotel chain.
On September 20, the U.S. Court of Appeals for the 9th Circuit vacated the district court’s order granting summary judgment in a TCPA action, in light of the recent D.C. Circuit opinion in ACA International v. FCC (covered by a Buckley Sandler Special Alert). The case arises from a plaintiff’s allegations that a California gym violated the TCPA by sending three text messages to the plaintiff’s cell phone. In October 2014, the district court granted summary judgment for the gym, holding that the automatic text messaging system used by the gym was not an “automatic telephone dialing system” (autodialer) under the TCPA because it lacked the capacity “to store or produce telephone numbers to be called, using a random or sequential number generator.” In 2016, the 9th Circuit stayed the appeal of the district court’s ruling pending the ACA International decision, which was issued in March of this year. In ACA International, the D.C. Circuit struck down the FCC’s definition of an autodialer, reasoning that the FCC’s definition “unreasonably, and impermissibly” included all smartphones while inadequately describing the functions that made a device an autodialer.
Because the ACA International decision set aside the FCC’s definition, the 9th Circuit performed its own review of the statutory definition of an autodialer in the TCPA. Through this review, the court concluded that the TCPA defined an autodialer as “equipment which has the capacity—(i) to store numbers to be called, or (ii) to produce numbers to be called, using a random or sequential number generator—and to dial such numbers automatically (even if the system must be turned on or triggered by a person).” Because the text system used by the gym stores numbers and dials them automatically to send the messages to the stored list of phone numbers, the 9th Circuit held there is a genuine issue of material fact as to whether the system qualified as an “autodialer” and remanded the case to district court for further proceedings.
On August 2, the U.S. District Court for the District of New Jersey denied a mortgage company’s motions to dismiss in two putative class actions (opinions available here and here) alleging violations of the Telephone Consumer Protection Act (TCPA) for unsolicited phone calls. In both cases, the mortgage company requested the court dismiss the action or, in the alternative, stay the proceedings pending guidance from the FCC regarding what constitutes an automatic telephone dialing system (autodialer) in light of the D.C. Circuit decision in ACA International v. FCC. (Covered by a Buckley Sandler Special Alert; InfoBytes coverage on the FCC’s notice seeking comment on what constitutes an autodialer, available here.) In each of the actions, consumers allege the company violated the TCPA by placing unsolicited calls to their phones using an autodialer. In denying both motions, the judge rejected the company’s argument, in one case, that it was not using “a random or sequential number generator” because the preloaded numbers belonged to the company’s customers rather than members of the public, reasoning that just because the population of numbers which may be dialed are pre-selected does not make the calling system, the next number being dialed, less random. Moreover, in the second case, the judge rejected the company’s assertion that written consent was not needed because the calls were placed to a number of customers with existing debt. The court noted the calls were regarding refinancing services and “calls to customers soliciting refinance are ‘telemarketing’ calls for a new product requiring prior express written consent under the TCPA.” As for the requests to stay the proceedings, the court held in both cases that it is unnecessary to stay the case because “whatever guidance the FCC may issue in the future will not alter the statutory definition of an [autodialer]” or previous unchanged FCC guidance pursuant to which the court decided the motions to dismiss.
On June 26, the U.S. Court of Appeals for the 3rd Circuit affirmed summary judgment for a global internet media company holding that the plaintiff failed to show the equipment the company used fell within the definition of “automatic telephone dialing system” (autodialer) based the recent holding by the D.C. Circuit in ACA International v. FCC. (Covered by a Buckley Sandler Special Alert.) The decision results from a lawsuit filed by a consumer alleging the company’s email SMS service, which sent a text message every time a user received an email, was an “autodialer” and violated the TCPA. The consumer had not signed up for the service, but had purchased a cellphone with a reassigned number and the previous owner had elected to use the SMS service. Ultimately, the consumer received almost 28,000 text messages over 17 months. In 2014, the district court granted summary judgment for the company concluding that the email service did not qualify as an autodialer. In light of the FCC’s 2015 Declaratory Ruling—which concluded that an autodialer is not limited to its current functions but also its potential functions—the 3rd Circuit vacated the lower court’s judgment. On remand, the lower court again granted summary judgment in favor of the company.
In reaching the latest decision, the 3rd Circuit interpreted the definition of an autodialer as it would prior to the 2015 Declaratory Ruling in light of the D.C. Circuit’s recent holding, which struck down the part of the FCC’s 2015 Ruling expanding the definition to potential capacity. The appellate court held that the consumer failed to show that the email SMS service had the present capacity to function as an autodialer.
- Kathryn L. Ryan to discuss "NMLS usage" at the NMLS Annual Conference & Training
- Jeffrey S. Hydrick to discuss "State legislative update" at the NMLS Annual Conference & Training
- Kathryn L. Ryan to speak at the "Business model primer" at the NMLS Annual Conference & Training
- Daniel P. Stipano to discuss "Dynamic customer due diligence and beneficial ownership from KYC to ongoing CDD and the new rule implementation" at the Puerto Rican Symposium of Anti-Money Laundering
- Michelle L. Rogers to discuss "Preparing for servicing exams in the current regulatory environment" at the Mortgage Bankers Association National Mortgage Servicing Conference & Expo
- Jon David D. Langlois to discuss "Regulatory risks of convenience fees" at the Mortgage Bankers Association National Mortgage Servicing Conference & Expo
- APPROVED Webcast: NMLS Annual Conference & Ombudsman Meeting: Review and recap
- Brandy A. Hood to discuss "Keeping your head above water in flood insurance compliance" at the Mortgage Bankers Association National Mortgage Servicing Conference & Expo
- Melissa Klimkiewicz to discuss "Servicing super session" at the Mortgage Bankers Association National Mortgage Servicing Conference & Expo
- Daniel P. Stipano to discuss "Lessons learned from recent high profile enforcement actions" at the Florida International Bankers Association AML Compliance Conference
- Moorari K. Shah to provide "Regulatory update – California and beyond" at the National Equipment Finance Association Summit
- Sasha Leonhardt and John B. Williams to discuss "Privacy" at the National Association of Federally-Insured Credit Unions Spring Regulatory Compliance School
- Aaron C. Mahler to discuss "Regulation B/fair lending" at the National Association of Federally-Insured Credit Unions Spring Regulatory Compliance School
- Heidi M. Bauer to discuss "'So you want to form a joint venture' — Licensing strategies for successful JVs" at RESPRO26
- Jonice Gray Tucker to discuss "Small business & regulation: How fair lending has evolved & where are we heading?" at CBA Live
- Jonice Gray Tucker to to discuss "DC policy: Everything but the kitchen sink" at CBA Live
- Daniel P. Stipano to discuss "Lessons learned from ABLV and other major cases involving inadequate compliance oversight" at the ACAMS International AML & Financial Crime Conference
- Daniel P. Stipano to discuss "A year in the life of the CDD final rule: A first anniversary assessment" at the ACAMS International AML & Financial Crime Conference
- Moorari K. Shah to discuss "State regulatory and disclosures" at the Equipment Leasing and Finance Association Legal Forum
- Hank Asbill to discuss "Pay no attention to the man behind the curtain: Addressing prosecutions driven by hidden actors" at the National Association of Criminal Defense Lawyers West Coast White Collar Conference
- Daniel P. Stipano to discuss "Keep off the grass: Mitigating the risks of banking marijuana-related businesses" at the ACAMS AML Risk Management Conference
- Daniel P. Stipano to discuss "Mid-year policy update" at the ACAMS AML Risk Management Conference
- Benjamin W. Hutten to discuss "Requirements for banking inherently high-risk relationships" at the Georgia Bankers Association BSA Experience Program