TCPA Watch – Page 3 – Business, legal and policy developments under the Telephone Consumer Protection Act.

District Court Adopts Narrow ATDS Interpretation, Dismisses TCPA Suit

Dec 03 2018

By Joseph C. Wylie II, Molly K. McGinley, and Lexi D. Bond

A district court in Illinois recently dismissed a lawsuit against Yahoo!, Inc. (“Yahoo”) alleging violations of the Telephone Consumer Protection Act (“TCPA”), reversing its previous decision denying summary judgment. In Johnson v. Yahoo! Inc., Case No. 14-cv-2028 (N.D. Ill. Nov. 29, 2018), the court granted Yahoo’s motion for reconsideration based on recent interpretations of the definition of an automatic telephone dialing system (“ATDS”) under the TCPA, particularly the decision in ACA Int’l v. FCC, 885 F.3d 687, 695 (D.C. Cir. 2018) (previously discussed here). In its ruling, the district court rejected prior Federal Communication Commission (“FCC”) pronouncements and adopted a narrow interpretation of ATDS, holding that only a system that actually dials randomly or sequentially generated numbers can be an ATDS.

Bipartisan Bill Introduced In The Senate To Thwart Illegal Robocall Scams

Nov 27 2018

By Pamela Garvie, Amy Carnevale, Andrew Glass, Gregory Blase, Joseph Wylie, and Molly McGinley

Sen. John Thune (R-SD), chairman of the Senate Commerce Committee, and Sen. Ed Markey (D-MA), a member of the Committee and author of the Telephone Consumer Protection Act (TCPA), recently introduced S. 3655, the Telephone Robocall Abuse Criminal Enforcement and Deterrence Act (the TRACED Act), to prevent illegal robocall scams. In brief, the bill would extend the statute of limitations for the Federal Communications Commission (FCC) to pursue robocall scammers and others who intentionally violate the law, impose additional penalties on such violators, require call authentication and blocking technologies, and establish an interagency working group to explore further ways to prosecute robocallers who intentionally violate the law.

U.S. Supreme Court To Rule On Hobbs Act Deference To FCC’s TCPA Rules

Nov 14 2018

By Joseph C. Wylie II, Molly K. McGinley, and Lexi D. Bond

On November 13, 2018 the U.S. Supreme Court granted certiorari in a Telephone Consumer Protection Act (“TCPA”) case in which the Fourth Circuit vacated the district court’s holding that an unsolicited fax sent by a health information provider offering a free e-book must have a commercial goal to be considered an advertisement under the TCPA. This case presents important questions as to the scope of judicial deference to the Federal Communication Commission’s (“FCC”) rules under the Hobbs Act, which limits the ability of TCPA litigants to challenge FCC rules in private civil litigation.

In Wake of ACA Int’l, Ninth Circuit Adopts Expansive Definition of ATDS

Oct 05 2018

By: Joseph C. Wylie II, Molly K. McGinley, Nicole C. Mueller

The U.S. Court of Appeals for the Ninth Circuit recently adopted an expansive definition of the term “automatic telephone dialing system” (“ATDS”) under the Telephone Consumer Protection Act (“TCPA”). In Marks v. Crunch San Diego LLC, the panel held that, in light of ACA Int’l, the U.S. Court of Appeals for the D.C. Circuit’s landmark decision interpreting certain provisions within the TCPA (previously discussed here) and based on the panel’s own review of the TCPA, the statutory definition of an ATDS includes devices that store telephone numbers to be called, whether or not the device has the ability to generate numbers randomly or sequentially. In so holding, the Ninth Circuit splits from a number of other decisions holding that an essential element of an ATDS is the capacity to generate random or sequential numbers.

The TCPA defines ATDS as “equipment which has the capacity–(A) to store or produce telephone numbers to be called, using a random or sequential number generator; and (B) to dial such numbers.” In ACA Int’l, in brief, the D.C. Circuit invalidated the Federal Communications Commission (“FCC”)’s interpretation of two key questions raised by the statutory definition of an ATDS, namely “(i) when does a device have the ‘capacity’ to perform the two enumerated functions; and (ii) what precisely are those functions?” In so doing, the D.C. Circuit created uncertainty as to what features or attributes of a dialing system would bring it within the scope of the ATDS definition.

Plaintiff Jordan Marks filed suit against Crunch San Diego LLC (“Crunch”) after he joined the gym and received three text messages over a period of eleven months. Crunch utilized a system called Textmunication. In this system, phone numbers are captured and stored in one of three ways: an operator of the system can manually enter a phone number into the system; a current or potential customer may respond to a marketing campaign with a text; or a customer may provide a phone number by filling out a consent form on a Textmunication client’s website. A client of Textmunication can then design a marketing campaign and Textmunication will automatically send the desired messages to the stored phone numbers at a time scheduled by the client. When Crunch wants to send a text through Textmunication, a Crunch employee logs into the system, selects the recipient phone numbers, generates the content of the message, and selects the date and time for the message to be sent. The messages are then automatically sent at the appointed time.

Prior to the decision in ACA Int’l, the district court held that Textmunication was not an ATDS because it lacked the present or potential capacity “to store or produce telephone numbers to be called, using a random or sequential number generator” and granted summary judgment for Crunch. Marks appealed the decision, and following his appeal, ACA Int’l was decided. The Ninth Circuit then reversed, holding that a system could be an ATDS if it has the capacity to store a list of numbers and call those numbers automatically, even if the system does not have the ability to generate random or sequential lists of numbers. In doing so, the Ninth Circuit first reviewed the statutory definition of ATDS as set forth by Congress in 1991 and determined that the provision is ambiguous, and, accordingly, that it was appropriate to look to the context and structure of the statutory scheme. The Ninth Circuit found that Congress intended to regulate devices that make automatic calls, including those devices that make automatic calls from lists of recipients, rather than utilizing a random or sequential number generator. The Ninth Circuit rejected Crunch’s argument that because the system was not fully automatic, it did not qualify as an ATDS, holding that Congress had been clear that it was targeting equipment that could engage in automatic dialing rather than equipment that operated without any human oversight or contact. The Ninth Circuit remanded the matter back to the district court for further proceedings.

In addition to the Ninth Circuit, several other courts have discussed the effect of ACA Int’l on the definition of ATDS:

In Gonzalez v. Ocwen Loan Servicing, LLC, the Court concluded that a predictive dialer that lacks the capacity to generate random or sequential telephone numbers and dial them, but it does include a predictive dialer that has the “present ability” to do so.
In Washington v. Six Continents Hotels, Inc., the Court agreed that ACA Int’l set aside not only the FCC’s 2015 ruling but also the FCC’s historic treatment of which devices qualify as an ATDS. 16-3719, 2018 WL 4092024, at *3 (C.D. Cal. Aug. 24, 2018) The Court then determined that the complaint adequately alleged the use of an ATDS by claiming that the defendant “acquired Plaintiff’s number, stored it in a database connected to its telephonic or computer system . . . [the system] . . . has the capacity to generate random numbers . . . has the capacity to generate sequential numbers . . . [and] has the capacity to store and dial the random or sequential numbers it generates just like it stored and dialed Plaintiff’s number.” Id.
In Heard v. Nationstar Mortg. LLC, the Court held that a system that could and did store customer information for at least 24 hours and did not have the capacity to store or produce telephone numbers to be called using a random or sequential number generator fell within the definition of ATDS. 16-694, 2018 WL 4028116, at *5-6 & n.2 (N.D. Ala. Aug. 23, 2018).
In King v. Time Warner Cable Inc., the Second Circuit determined that qualification as an ATDS was limited to those devices that were “capable at the time of use” of performing the functions of an autodialer, absent any modifications to the device’s hardware or software. 849 F.3d 473, 476–77 (2d Cir. 2018).
In Dominguez ex rel Himself v. Yahoo, Inc., the Court held that, absent any evidence that the device had the capacity to generate random or sequential telephone numbers and dial those numbers, the plaintiff failed to show that the text messaging system was an ATDS in light of ACA Int’l. 894 F.3d 116, 119 (3d Cir. 2018).

Given the split among courts on how to interpret ATDS, uncertainty will continue to prevail until there is additional clarification, either from the Supreme Court or the FCC. The FCC has requested further comment from the public regarding the interpretation of the TCPA in light of this decision.

FCC Seeks Comment on TCPA Following D.C. Circuit’s Decision in ACA International

May 23 2018

By Joseph Wylie, Molly McGinley, Andrew Glass, Greg Blase, Pamela Garvie, Amy Carnevale, and Nicole Mueller

The Consumer and Governmental Affairs Bureau of the Federal Communications Commission (the “FCC”) recently issued a public notice seeking comment on issues related to interpretation and implementation of the Telephone Consumer Protection Act (the “TCPA”). The notice followed the recent decision of the United States Court of Appeals for the District of Columbia in ACA International v. FCC, in which the Circuit Court affirmed and vacated in part a rule previously issued by the FCC. Our prior coverage of ACA International can be found here.

First, the FCC seeks comment on the TCPA definition of “automatic telephone dialing system.” The TCPA defines an automatic telephone dialing system as “equipment which has the capacity—(A) to store or produce telephone numbers to be called, using a random or sequential number generator; and (B) to dial such numbers.” The FCC had previously interpreted the term “capacity” to include a device “even if, for example, it requires the addition of software to actually perform the functions described in the definition.” The ACA International Court set that definition aside—finding that the agency’s “capacious understanding of a device’s ‘capacity’ lies considerably beyond the agency’s zone of delegated authority” and that it would have “the apparent effect of embracing any and all smartphones.” The FCC seeks comment on how to interpret “capacity” in light of the guidance provided in ACA International, specifically seeking comment on how to more narrowly interpret the word “capacity” to better comport with congressional findings and the intended reach of the statute.

The FCC further seeks comment on the functions a device must be able to perform to qualify as an automatic telephone dialing system. The FCC seeks comment on whether equipment can be considered an automatic telephone dialing system if the equipment cannot itself dial random or sequential numbers. And the FCC seeks comment on whether the prohibition on making certain calls using an automatic telephone dialing system should apply to equipment that has the ability to use such technology but does not actually use it in making the call.

Second, the FCC seeks comment on how to treat calls to reassigned wireless numbers under the TCPA where the statute carves out calls “made with the prior express consent of the called party” from its prohibitions. The FCC seeks comment specifically on the definition of “called party:” does it refer to the person the caller expected to reach (or reasonably expected to reach) or the person that the caller actually reached, i.e., the wireless number’s present-day subscriber? Further, does it include the “customary user” (e.g., the close relative on a subscriber’s family calling plan)?

Third, the FCC seeks comment on how a called party may revoke prior express consent to receive robocalls. The ACA International Court found that (1) “a party may revoke her consent through any reasonable means clearly expressing a desire to receive no further messages from the caller,” and (2) such a standard means “callers . . . have no need to train every retail employee on the finer points of revocation” and have “every incentive to avoid TCPA liability by making available clearly-defined and easy-to-use opt-out methods.” The FCC now seeks input on what, if any, opt-out methods exist that would be sufficiently clearly defined and easy to use such that “any effort to sidestep the available methods in favor of idiosyncratic or imaginative revocation requests might well be seen as unreasonable” for unwanted calls (i.e., saying “stop calling” in response to a live caller, offering opt-out through a website, or responding with “stop” to unwanted texts; and whether callers must offer all or some combination of such methods to qualify).

Fourth, the FCC seeks renewed comment on two pending petitions for reconsideration of the FCC’s Broadnet Declaratory Ruling, in which the FCC determined that the TCPA does not apply to calls made by or on behalf of the federal government in the conduct of official government business, except when a call made by a contractor does not comply with the government’s instructions. The petitions seek reconsideration of the FCC’s interpretation of “persons” under the TCPA, and clarification of whether federal government contractors, regardless of their status as common-law agents, are “persons” under the TCPA. The FCC now seeks comment on whether contractors acting on behalf of federal, state, and local governments are “persons” for purposes of the TCPA.

Fifth, the FCC seeks renewed comment on the pending petition for reconsideration of its 2016 Federal Debt Collection Rules, which seeks reconsideration of several aspects of the rules, including the applicability of the TCPA limits on calls to reassigned wireless numbers. Referring to the holding in ACA International, the FCC seeks renewed comment on “this and other issues” raised by the petition.

Comments are due by June 13, 2018 and reply comments are due by June 28, 2018.

This public notice, along with recent congressional hearings considering legislation applicable to telephone calls (previously discussed here), demonstrates that in the wake of ACA International, the laws and regulations applicable to outbound calling will continue to evolve.

Congress Holds Hearings on Abusive Robocalls and Caller ID Spoofing – Possible Legislative or Regulatory Changes Requires Close Watch

May 16 2018

By Pamela Garvie and Amy Carnevale

The Senate Commerce Committee and House Energy and Commerce Committee held back-to-back hearings late last month on abusive robocalls and caller ID spoofing and how to combat them. Committee members and witnesses both highlighted the fact that robocalls and ID spoofing have “exploded in recent years” and several noted that “over 3 billion calls were placed [in March] alone” and “about a quarter of these calls are scam calls.” Further, because the technology used to place robocalls and to spoof are evolving technically, the number of calls continues to grow. There was broad agreement on both committees that consumer education, aggressive Federal Communications Commission (“FCC”) and Federal Trade Commission (“FTC”) enforcement actions, and the use of new ID verification and robocall-blocking technologies are important tools in combating these calls. However, Republicans and Democrats and business and consumer witnesses are generally split on the question of whether legitimate businesses are part of the problem and whether the Telephone Consumer Protection Act (“TCPA”) needs to be reformed or conversely expanded through new legislation and regulations. This focus on abusive/illegal robocalls and split on the TCPA presents both risks and potential opportunities for businesses and, consequently, requires close watch.

Trade Groups Petition the FCC to Adopt a Narrow Interpretation of Autodialer Under the TCPA

May 09 2018

By: Andrew C. Glass, Gregory N. Blase, Joseph Wylie, Molly McGinley, Pamela Garvie, Amy Carnevale, Roger L. Smerage, and Hollee M. Watson

A coalition of trade groups recently petitioned the Federal Communications Commission (the “Commission”), urging it to adopt a narrow interpretation of “Automated Telephone Dialing System” (“ATDS” or, commonly, “autodialers”) under the Telephone Consumer Protection Act (“TCPA”). The petition, filed on behalf of the U.S. Chamber of Commerce and other trade associations, follows the March 2018 decision of the U.S. Court of Appeals for the D.C. Circuit that vacated several key elements of the Commission’s 2015 TCPA Order. ACA Int’l v. Fed. Comm. Comm’n, 885 F.3d 687, 692, 701 (D.C. Cir. 2018). Among other things, the D.C. Circuit set aside the Commission’s 2015 interpretation of what constitutes an ATDS. The court held that the Commission’s interpretation of the term ATDS was “unreasonably expansive” and “‘offer[ed] no meaningful guidance’ to affected parties in material respects on whether their equipment is subject to the statute’s autodialer restrictions.” Because of the limited scope of the matter before it, the D.C. Circuit did not itself interpret the term ATDS, but instead provided guidance for the Commission as to how the term should be defined.

District Court Finds No Violation of First Amendment in TCPA Suit Brought By Coalition of Bi-Partisan Political Organizations

Apr 09 2018

By Andrew C. Glass, Gregory N. Blase, Christopher J. Valente, Michael R. Creta, and Elma Delic

The U.S. District Court for the Eastern District of North Carolina recently rejected a First Amendment challenge to a portion of the Telephone Consumer Protection Act (“TCPA”), 47 U.S.C. § 227(b)(1)(A)(iii). In American Association of Political Consultants, Inc., et al. v. Sessions, et al., Case No. 5:16-cv-00252-D (E.D.N.C.), a bi-partisan coalition of political groups sued the federal government. The coalition asserted that the TCPA’s prohibition on making auto-dialed calls or texts to cell phones without the requisite consent (the “cell phone ban”) imposes a content-based restriction on speech that does not pass strict scrutiny and is unconstitutionally under-inclusive. (The plaintiffs’ complaint was previously discussed here.) The government defended the TCPA’s constitutionality.

Court Finds Website Owner Did Not Send Text Messages Initiated by its Users and thus Did Not Violate the TCPA

Mar 22 2018

By Andrew C. Glass, Gregory N. Blase, Roger L. Smerage, and Matthew T. Houston

In a recent decision, the U.S. District Court for the Northern District of Illinois found that the host of an automobile website did not violate the Telephone Consumer Protection Act, 47 U.S.C. § 227 (“TCPA”), by providing its users a platform to send automated text messages regarding car listings. In Serban v. CarGurus, Inc., Case No. 1:16-cv-02531 (N.D. Ill. Mar. 12, 2018), a user of the defendant’s website mistyped her telephone number when attempting to send herself a car listing. In doing so, the user performed a multi-step process—including selecting the “Send to Phone” option, entering the telephone number, and clicking a “Send” button—to generate a text message automatically created by CarGurus based on the car selected. As a result of the mistyped telephone number, the text message was transmitted to the plaintiff rather than the user.

D.C. Circuit Strikes Key Elements of FCC’s 2015 Order Interpreting the TCPA, Upholds Certain Provisions

Mar 19 2018

By Joseph Wylie, Andrew C. Glass, Molly K. McGinley, Gregory N. Blase, Nicole C. Mueller, and Roger L. Smerage.

On March 16, 2018, in a long-awaited decision, the U.S. Court of Appeals for the District of Columbia Circuit vacated key provisions of the 2015 Federal Communications Commission order regarding the Telephone Consumer Protection Act, 47 U.S.C. § 227, including provisions regarding the definition of an autodialer and calls to reassigned wireless numbers. Click here for a full discussion of the decision.