United States: D.C. Circuit Weighing FCC's Controversial 2015 TCPA Declaratory Ruling

Today, a panel of the D.C. Circuit—composed of Judges Srinivasan and Pillard and Senior Judge Edwards—heard argument in ACA International v. FCC, the consolidated appeals from the FCC's 2015 Declaratory Ruling and Order, which greatly expanded the reach of the Telephone Consumer Protection Act ("TCPA"). (An audio recording of the argument is here, and Kevin attended the argument.) The case has been closely watched, and a number of TCPA class actions around the country have been stayed to await the D.C. Circuit's decision. More detail is below the fold, but here are our quick impressions from the argument:

  • The panel asked tough questions of lawyers for both sides in an argument that went two full hours over the allotted 40 minutes.
  • The panel focused most of its attention on the FCC's new—and far-reaching—definition of an automatic telephone dialing system (ATDS, or "autodialer"). All three judges expressed discomfort with the fact that the FCC's new definition could be read to cover smartphones.
  • Judge Edwards repeatedly voiced criticisms of the FCC's expansive readings of the TCPA across the board, and may be inclined to vacate large portions of the FCC's Declaratory Ruling.
  • Judge Pillard seemed the most receptive to the FCC's arguments.
  • Judges Srinivasan was the hardest to read, but it seems possible that he might join Judge Edwards in setting aside major portions of the FCC's Declaratory Ruling.

Background

As readers of the blog may recall, the FCC's July 10, 2015 Declaratory Order and Ruling addressed 21 petitions seeking guidance regarding various requirements under the TCPA and the FCC's past regulations implementing that statute. The petitions largely focused on the rules prohibiting certain automated-dialing and texting practices, which have led to a torrent of class-action litigation seeking statutory damages that, when trebled, can reach $1,500 per call or text message.

The FCC's 2015 Declaratory Ruling covered a number of subjects. (Please read our report (pdf) for a full recap.) But today's argument in the D.C. Circuit focused largely on three issues:

  • The FCC's expanded definition of what equipment constitutes an autodialer triggering the autodialer provisions of the TCPA;
  • The FCC's attempt to impose of strict liability for all but the first call to a reassigned number, even if the caller would have no reason to know that the number had been reassigned; and
  • Whether the FCC can bar companies from limiting the manner by which consumers may revoke consent to receive autodialed calls or text messages.

Autodialer Definition

The primary focus of the argument was on the FCC's expanded definition of an autodialer. The statutory definition is "equipment which has the capacity" to "store or produce telephone numbers to be called, using a random or sequential number generator," and "to dial such numbers." 47 U.S.C. § 227(a)(1). In its Declaratory Ruling, the FCC concluded that equipment is an autodialer if it has the potential "capacity" to dial random or sequential numbers (whether generated on its own or from a preexisting list), even if that "capacity" has been "de-activated" or could be added only through "software changes" or other updates. In fact, the only device that the FCC was willing to say could not be modified to constitute an autodialer was a rotary telephone.

During the argument, the judges focused largely on the fact that most modern smartphones—as well as all computers—would fall under this definition—meaning that a person who calls a relative without the requisite prior consent would have violated the TCPA. Judge Edwards at one point observed that such an expansion of TCPA liability would be "absurd" and "not what Congress intended." He also suggested that the TCPA should be limited to prohibit only the "use" of an autodialer, and that a person using a smartphone to dial "his sister" would not be violating the TCPA.

Judges Pillard and Srinivasan were harder to read. The FCC lawyer arguing the case (Scott Noveck, who, as it happens, is a former Mayer Brown lawyer) defended the FCC's interpretation by contending that TCPA plaintiffs would be presented with intractable proof problems if defendants could avoid liability by simply claiming that they had flipped a switch on an autodialer to disable its random-call functions just before making the call at issue. Judge Pillard at some points in the argument appeared to accept that explanation. And she seemed concerned that the petitioners' view would render the TCPA would be a "dead letter," limiting its application to the random-call generators that companies stopped using decades ago.

But when the argument turned to whether smartphones would constitute autodialers under the FCC's definition, Judge Pillard did not accept the FCC's hedging. The FCC lawyer suggested that the FCC had not addressed smartphones in its Declaratory Ruling, instead inviting a future petition to ask about that issue. But Judge Pillard pointed out that the broad sweep of the 2015 Declaratory Ruling inevitably covered smartphones. And she seemed concerned that the definition of an autodialer that the FCC had adopted has caused the statute to extend beyond what Congress intended.

Judge Srinivasan's position on this issue is also difficult to predict. He stated that it seemed "impossible" to him that Congress would have intended to prohibit calls from smartphones. And at one point in the argument, he joked that receiving a call from one's grandmother on a cellphone would violate the TCPA under the FCC's view. But he pressed petitioners' counsel to concede that downloading an app needed to convert a smartphone into a true autodialer—with the ability to dial random numbers—required only "trivial effort."

The panel also heard a lot of argument about whether equipment that dials numbers from a preselected list—rather than generated at random or sequentially—constitutes an autodialer. But it was difficult to tell from the questions how the panel was leaning on this issue. At least two judges—Srinivasan and Pillard—seemed concerned that a company could avoid liability under the petitioners' approach by calling from a list of "all numbers in New York City." Nonetheless, the panel struggled with how the FCC's ruling that dialing numbers from a list could be squared with the statutory language of the TCPA.

Reassigned Numbers

Another issue that arose during the argument—one that arises frequently in TCPA litigation—is whether the TCPA is violated when a business attempts to place a call to one customer (who consented to receive such calls) but, because the phone number has been reassigned, the call turns out to be received by another person who does not consent to be called. The FCC has concluded that such calls violate the TCPA. The FCC ruled that the caller must have the consent "not of the intended recipient of the call, but of the current subscriber (or nonsubscriber customary user of the phone)." The FCC then adopted a safe harbor for the first call to a reassigned number, after which the company would be "deemed" to have actual or "constructive knowledge" that the number was no longer valid.

Petitioners contended that the FCC's ruling rested on a mistaken reading of the statute, arguing that if the intended recipient of the call has consented, the TCPA does not impose liability. And petitioners observed that as soon as the actual recipient of the calls objects, any further calls would trigger TCPA liability, as Congress intended.

It was difficult to tell whether the panel was accepting the petitioners' interpretation as the only reasonable one, rendering the FCC's contrary interpretation impermissible. Two of the judges (Srinivasan and Edwards) remarked at different times that the FCC's safe harbor appeared to be insufficient, as companies will frequently not learn from the first call or text to a reassigned number of the change in subscriber. (For example, the call may go to an uninformative voicemail box, or a text message may receive no response.)

The panel also seemed to offer a mixed reception to the FCC's explanation that the rule involved a tradeoff, and that the FCC could properly determine that consumers should not bear the risk of having to receive calls to reassigned numbers. Judge Srinivasan noted, however, that another purpose of the TCPA was to protect calls made in compliance with the rules from liability, and that the FCC's rule would chill companies from making those calls for fear of inadvertently calling a reassigned number.

Revocation of Consent

The final issue on which the panel focused extensively was whether companies may restrict the means by which a consumer may revoke consent to be called. In the Declaratory Ruling, the FCC determined that consumers may revoke consent "in any reasonable manner," and barred callers from "designating an exclusive means to revoke." The FCC provided several examples of what it deemed to be "reasonable" methods of revoking consent: in "writing," "by way of a consumer-initiated call" to the company, a request made during "a call initiated or made by the company," an in-person request at a company store, such as "an in-store bill payment location."

Judge Edwards observed that this rule was impractical for businesses. Judge Srinivasan similarly remarked that, for example, large companies can be reached at many phone numbers, and it would be difficult for them to monitor every number in order to try to record a revocation of consent.

Judge Pillard suggested, however, that the FCC was arguably forcing companies to come up with such an easy way to revoke consent that consumers would not try to do so by other means, which would eliminate the problem of having to "herd cats." But as petitioners' counsel pointed out in response, at least some consumers might still try to revoke consent in individualized ways, presenting companies with the difficult task of trying to record all consents. The end result, especially in combination with the FCC's rule imposing strict liability on calls to reassigned numbers, would be to prevent companies from being able to rely on a consumer's consent to be called.

A number of the judges asked whether consumers and companies can nonetheless enter into an agreement as to how consent may be revoked. The FCC lawyer agreed that they could, as long as the agreement was "voluntary" rather than on a "take-it-or-leave-it" basis.

The Bottom Line

It is always difficult to predict from argument how a judge—and especially a panel of judges—will rule. Certainly it is possible that some or all of the judges asked seemingly hostile questions not to signal disagreement with a position, but to probe the limits of that position.

That said, it seems possible that there were at least two votes on the panel to require the FCC to reconsider its approach to the definition of an autodialer, and perhaps also with respect to the safe harbor for calls to reassigned numbers. It is also possible that the panel might direct the FCC to provide greater clarity regarding how opt-out or revocation requests might work.

Originally published October 19, 2016

Visit us at mayerbrown.com

Mayer Brown is a global legal services provider comprising legal practices that are separate entities (the "Mayer Brown Practices"). The Mayer Brown Practices are: Mayer Brown LLP and Mayer Brown Europe – Brussels LLP, both limited liability partnerships established in Illinois USA; Mayer Brown International LLP, a limited liability partnership incorporated in England and Wales (authorized and regulated by the Solicitors Regulation Authority and registered in England and Wales number OC 303359); Mayer Brown, a SELAS established in France; Mayer Brown JSM, a Hong Kong partnership and its associated entities in Asia; and Tauil & Chequer Advogados, a Brazilian law partnership with which Mayer Brown is associated. "Mayer Brown" and the Mayer Brown logo are the trademarks of the Mayer Brown Practices in their respective jurisdictions.

© Copyright 2016. The Mayer Brown Practices. All rights reserved.

This Mayer Brown article provides information and comments on legal issues and developments of interest. The foregoing is not a comprehensive treatment of the subject matter covered and is not intended to provide legal advice. Readers should seek specific legal advice before taking any action with respect to the matters discussed herein.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
 
In association with
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.