The Western District of Oklahoma recently granted a plaintiff’s motion for summary judgment against NorthStar Alarm Services, LLC (“NorthStar”) in a certified class action. The court held, in part, that NorthStar was vicariously liable for telemarketing calls that sales lead generator Yodel Technologies, LLC (“Yodel”) placed on its behalf. Braver v. NorthStar Alarm Services, LLC, No. 17-cv-0383, 2019 WL 3208651, at *1 (W.D. Okla. July 16, 2019). The case illustrates the factors that one court found relevant in a particular factual context when assessing vicarious liability issues related to a lead generator’s telemarketing calls. Continue reading
The FCC on August 1 voted to adopt enhanced Truth in Caller ID rules that will subject a broader range of “spoofed” calls to new heftier statutory civil penalty and potentially criminal sanctions for willful and knowing violations of these FCC requirements. Companies using spoofing technology should have until early 2020 to assess their operations to ensure compliance prior to these amended rules taking effect.
At its Open Meeting, the FCC adopted a Report and Order (R&O) to amend the current Truth in Caller ID rules. The text of the adopted version of the R&O was released on August 5, 2019 and largely remains unchanged since the release of the draft Second R&O. It appears that the rules adopted build upon the framework the FCC proposed in its Notice of Proposed Rulemaking from in February 2019 (click here for our earlier summary of the Notice). Overall, the Second R&O mirrors most of the FCC’s original proposals. The differences we highlight below are relatively technical, reflecting the FCC’s attempt to grapple with and clarify the scope of rule changes in light of foreseeable business use cases that may cause problems that the RAY BAUM’S Act intended to prevent.
The Northern District of Illinois recently clarified that a “revocation class” that defines a putative class as those having made “a request to stop calling [their] number” does not satisfy Rule 23(b)(3)’s predominance requirement. This memorandum opinion again highlights the significance of individualized issues of consent in a TCPA class certification process. Continue reading
On June 24, 2019, the FCC’s adopted Declaratory Ruling and Third Further Notice of Proposed Rulemaking (“Third FNPRM”) was published in the Federal Register, triggering the commenting period deadlines. We previously discussed in detail the various components of the Third FNPRM here and here. Comments on this Third FNPRM are due by Wednesday, July 24, 2019, and reply comments are due by Friday, August 23, 2019. Drinker Biddle’s TCPA team will continue to monitor this docket and related developments as they become available.
While the FCC has a record open to adopt guidance and a new definition for what it considers as an “automatic telephone dialing system” (ATDS) and related TCPA matters, there appears to be growing consensus on “Robocall” legislation in the two houses of Congress that may be moving TCPA legislation closer to reality. On the heels of the Senate passing Senate Bill 151 (entitled “Telephone Robocall Abuse Criminal Enforcement and Deterrence (TRACED) Act”)Senate Bill 151 (entitled “Telephone Robocall Abuse Criminal Enforcement and Deterrence (TRACED) Act”), the House of Representatives yesterday introduced a new bipartisan bill – House Bill 3375 – that would bolster the prospects that Congress may be able to pass legislation this year.
By directing voice service providers to deal with “unwanted calls” as part of its anti-robocall policies, the FCC seems to have moved well beyond addressing “illegal and spoofed robocalls.” The text of the FCC’s new “Call Blocking by Default” approach was released late on June 7, 2019, which, as we previously predicted, contains several changes to the draft version of the Declaratory Ruling and Third Further Proposed Rulemaking (the Third FNPRM). Depending upon your point of view, the Third FNPRM contains either a few hopeful signs that the FCC understands and is willing to address the practical effects of its highly consequential blocking edict, or troubling confirmation that it has little idea of what it has unleashed on businesses and consumers. Continue reading
Voice service providers soon may dictate which calls will reach you. The FCC honed in on “unwanted calls” when it voted at its Open Meeting today to adopt a Declaratory Ruling and Third Further Proposed Rulemaking (the Third FNPRM) permitting voice service providers to implement “Call Blocking by Default.” We are awaiting and will report on the ruling and notice when it is released. Continue reading
Businesses may dial large volumes of numbers daily for a variety of legitimate purposes. These calls now appear to have become swept up and conflated with illegal robocalls, with a number of undesirable consequences. Certainly policy makers at the FCC, in reacting to understandable concerns about fraudulent and illegal calling, have been introducing more and more opportunities for voice service and app providers to apply non-transparent, subjective standards to block calls, and further muddy the water for business callers. Continue reading
The House Energy and Commerce Committee held a hearing entitled “Legislating to Stop the Onslaught of Annoying Robocalls” on April 30, 2019, that focused on seven bills pending before the Committee. While lawmakers and witnesses generally agreed that illegal and abusive robocalls are a problem, the fix or immediate solution in the form of new legislation was less clear.
Chairman Mike Doyle (D-PA) opened the hearing by summarizing the current state of pervasive robocalls and calling for voice service providers to make available call-blocking services to all customers free of charge. Rep. Greg Walden (R-OR) shared this sentiment, emphasizing the need for a bipartisan solution with wide support. As Walden observed, robocalling is a topic that comes up at every single town hall meeting held in recent months. Several bill sponsors made opening statements regarding their respective bills, which we summarize briefly below. Continue reading
The Eastern District of Pennsylvania recently denied a motion to dismiss a TCPA claim, finding that the plaintiff had standing, that the court had jurisdiction, and that the plaintiff had adequately alleged that an ATDS had been used to place the call at issue. See Shelton v. Nat’l Gas & Elec., LLC, No. 17-4063, 2019 WL 1506378 (E.D. Pa. Apr. 5, 2019). Continue reading