August 25, 2021

Recent News

FCC Opens Proceeding to Determine if VoIP Providers Should Have Additional Anti-Robocall Obligations

On August 6, 2021, the FCC adopted a Further Notice of Proposed Rulemaking to consider additional anti-robocall requirements for interconnected VoIP provider that seek direct access to telephone numbers.  Among the changes, the FCC proposes to require interconnected VoIP provider seeking access to numbers to “certify that it will use numbering resources lawfully; will not encourage nor assist and facilitate illegal robocalls, illegal spoofing, or fraud; and will take reasonable steps to cease origination, termination, and/or transmission of illegal robocalls once discovered.”  Comments on this proposal will be due 30 days after publication of the FNPRM in the Federal Register.

CGB Issues its Second Annual Report on the Status of the Implementation of Call Blocking Technologies

On June 29, 2021 the FCC’s Consumer and Government Affairs Bureau released a Second Call Blocking Report, as required by the 2019 Call Blocking Declaratory Ruling.  This Report, a follow up to the June 2020 First Call Blocking Report, provides (1) a detailed description of call blocking services offered by voice service providers, third-party analytics companies, and device manufactures (2) an in-depth evaluation of the effectiveness of call blocking tools (3) information on the state of deployment of caller ID authentication through implementation of the STIR/SHAKEN framework and (4) an analysis of the impact of call blocking on 911 services and public safety.  

FCC Adopts Rules to Create an Online Portal for Private Entities to Report Robocall Violations

On June 17, 2021 the FCC’s Enforcement Bureau released a Report and Order implementing section 10(a) of the Pallone-Thune Telephone Robocall Abuse Criminal Enforcement and Deterrence Act (TRACED Act), which directs the Commission to “prescribe regulations to establish a process that streamlines the ways in which a private entity may voluntarily share with the Commission information relating to violations of section 227(b) or 227(e) of the Communications Act.” The Report and Order establishes procedures for private entities may submit information about suspected robocall and spoofing violations.  The rules do not supplement the complaint procedures available to consumers, and thus the portal is not open for consumer complaints of illegal robocalls.  Similarly, government entity reports of robocall or spoofing violations should be submitted via other methods as well.

FCC Issues Further Notice of Proposed Rulemaking for Implementing STIR/SHAKEN

On May 20, 2021 the FCC’s Wireline Competition Bureau released a Third Further Notice of Proposed Rulemaking (FNPR) to consider accelerating its STIR/SHAKEN requirements for a subset of small voice service providers believed to be likely to originate illegal robocalls. In its Second Caller ID Authentication Report and Order, the FCC granted some small voice service providers an additional two years to implement the STIR/SHAKEN caller ID authentication framework.  According to the FCC, a subset of these providers is originating an increasingly disproportionate amount of illegal robocalls.  The NPRM outlines a proposal to “shorten the extension for small voice service providers most likely to originate illegal robocalls by one year, so that such providers must implement STIR/SHAKEN in the IP portions of their networks no later than June 30, 2022.”  It also seeks comments on (1) “how best to identify and define the subset of small voice service providers that that are at a heightened risk of originating an especially large amount of illegal robocall traffic” and (2) “whether to adopt additional measures, including data submissions, to facilitate oversight to ensure that small voice service providers subject to a shortened extension implement STIR/SHAKEN in a timely manner.” Comments were due on or before July 9, 2021; reply Comments were due on or before August 9, 2021.

ZipDX Submits Letter of Intent to Serve as Registered Industry Consortium

As required by the Pallone-Thune Telephone Robocall Abuse Criminal Enforcement and Deterrence Act (TRACED Act), the FCC must annually select “a single consortium to conduct private-led efforts to trace back the origin of suspected unlawful robocalls.” On May 27, 2021 ZipDx LLC (ZipDX) submitted a Letter of Intent to apply for this role. The Enforcement Bureau released a Public Notice on June 17, 2021 seeking comments on the matter.  The current designated  registered consortium, USTelecom – the Boadband Association’s Industry Traceback Group (USTelecom ITG) was not required to file another Letter of Intent, as its initial application and certifications continue for the duration of subsequent years, however it did submit a Comment reaffirming its commitment to the role.  The Bureau will select the registered consortium by August 25, 2021.  Comments were due July 2, 2021.


FCC Petitions Tracker

Kelley Drye’s Communications group prepares a comprehensive summary of pending petitions and FCC actions relating to the scope and interpretation of the TCPA.

Number of Petitions Pending

  • 30 petitions pending
  • 1 petition for reconsideration of the rules to implement the government debt collection exemption
  • 1 application for review of the decision to deny a request for an exemption of the prior express consent requirement of the TCPA for “mortgage servicing calls”
  • 1 request for reconsideration of the 10/14/16 waiver of the prior express written consent rule granted to 7 petitioners

New Petitions Filed
 
  • Enterprise Communications Advocacy Coalition – Petition for Declaratory Ruling
 
On July 30, 2021, the Enterprise Communications Advocacy Coalition (ECAC) filed a Petition for Declaratory Ruling seeking federal preemption of portions of recently enacted Florida legislation (SB 1120), which amends the Florida Do Not Call Act and the Florida Telemarketing Act.  The ECAC contends that portions of SB 1120 imposes obligations more restrictive than the TCPA Regulations and impose additional prohibitions on calls and the use of dialing equipment that are legal under federal law.  The Petition relies upon a 2003 Commission TCPA order which states that “that any state regulation of interstate telemarketing calls that differs from our rules almost certainly would conflict with and frustrate the federal scheme and almost certainly would be preempted.”
 
  • Perdue for Senate, Inc. – Petition for Declaratory Ruling
 
On July 2, 2021 Purdue for Senate, Inc. (Purdue for Senate) filed a Petition for Declaratory Ruling, asking the FCC to confirm that the Telephone Consumer Protection Act (TCPA) does not regulate ringless voicemail technology (RVM).  Specifically, Purdue for Senate wants the FCC to rule that “the delivery of a voice message directly to a voicemail box through RVM technology does not constitute a ‘call’ subject to prohibitions on the use of an automatic telephone dialing system (“ATDS”) or an artificial or prerecorded voice under Section 227(b)(1)(A)(iii) of the TCPA or Section 64.1200(a)(1)(iii) of the FCC’s rules.”  In the lead up to the January 2021 Senate runoff elections in Georgia, Purdue for Senate employed vendors that used RVM technology to deliver voice messages directly to potential voters’ voice mailboxes.  According to Purdue for Senate, these RVM transmissions fall outside of the scope of the TCPA and other FCC rules because, not only are they not “calls,” they are also not transmitted via a wireless network, and the technology does not bill the recipients of the messages.  Purdue for Senate claims that RVM technology is a “beneficial alternative” to robocalls, in that it allows non-profit organizations to relay important information without disrupting the lives of message recipients and/or adding charges to their bills. 

This is the third petition to be presented to the FCC involving ringless voicemail technology.  Two prior petitions relating to ringless voicemail were filed and subsequently withdrawn by the petitioners prior to a Commission decision. 

Upcoming Comments
  • None
Decisions Released
  • None
​Click here to see the full FCC Petitions Tracker.

 

Cases of Note

Common Ownership Does Not Establish Agency Relationship, Offer to Purchase Not “Telephone Solicitation” Under TCPA

The District of Arizona has held that common ownership of an agent and principal may not be enough to establish an agency relationship nor, therefore, vicarious TCPA liability. Rather, the plaintiff must plead specific facts showing that the purported agent controlled or directed the calls that plaintiff alleges violated the TCPA. It further held that an offer to purchase property—rather than an offer to sell a product or services—does not qualify as a “telephone solicitation” under § 227(c) of the TCPA.

In Jance v. Homerun Offer LLC, Plaintiff filed suit against Homerun Offer alleging that he received 29 calls from the company making “a generic and cursory inquiry” into purchasing his house in violation of the TCPA. After conducting his own online research into the state corporate records, he learned of a second company, All Star Investments, owned by Homerun Offer’s registered agent, President, and CEO, that had made six property purchases between October 2019 and June 2020. Plaintiff hypothesized that the property purchases made by All Star Investments came about as Homerun Offer’s telemarketing efforts, and named both in his TCPA complaint.

All Star Investments moved to dismiss, arguing that Plaintiff failed to plausibly allege that it could be held vicariously liable for Homerun Offer’s calls. Defendants also both moved to dismiss Plaintiff’s § 227(c) claim prohibiting continued “telephone solicitation” after an individual requests to be put on a company’s internal do-not-call list, arguing that the calls fell outside the statutory definition of “telephone solicitation.” As to both, the Court agreed.

The Court held that Plaintiff failed to make a prima facie showing that All Star Investments had the right to substantially control Homerun Offer, and that Homerun Offer acted as All Star Investments’ agent. “The simple fact that the same individual . . . is the President and CEO of both [Defendants] as well as the parent company for both the agent and principle” was “[in]sufficient to show that All Star Investments controlled or directed Homerun Offer’s phone calls to Plaintiff.” With no agency relationship plausibly alleged in the complaint, the Court dismissed the claims against All Star Investment.

Separately, the Court dismissed Plaintiff’s claim for damages under § 227(c) of the TCPA, which prohibits an entity from continuing to initiate “telephone solicitation” after an individual requests to be put on a do-not-call list. Referencing the statutory definitions of “telephone solicitation” and “telemarketing,” the Court noted that the TCPA protects individuals from calls placed with the “purpose of encouraging the purchase of . . . property, goods, or services” by the recipient. Because the calls in question constituted an offer to purchase (rather than an offer to sell), the Court found the Complaint failed to state a claim under § 227(c) and dismissed those claims.

Not all Plaintiff’s claims were dismissed. His claims under § 227(b), which prohibits the use of an “automatic telephone dialing system” (ATDS) without the recipient’s consent survived. Noting that whether a defendant has used an ATDS is “often a fact exclusively within the defendants’ possession,” the Court found that Plaintiff’s allegations—that he had no business relationship with Defendants nor provided them with his contact information, that the caller’s numbers were attributed to a VoIP and had misleading caller ID information, that there was a brief pause before the caller began speaking on certain calls, and that the calls were generically formatted and scripted—were sufficient to plausibly allege use of an ATDS.

Jance v. Homerun Offer LLC, No. CV-20-00482-TUC-JGZ, 2021 WL 3270318 (D. Ariz. July 30, 2021)

Court Rejects Plaintiff’s Argument to Expand ATDS Definition Based on Duguid Footnote

In Hufnus v. DoNotPay, Inc., the Northern District of California granted Defendant company’s motion to dismiss after Plaintiff alleged that he had been contacted in a manner that violated the TCPA. In the June 24, 2021 order, the court found that Plaintiff’s interpretation of footnote 7 of Facebook, Inc. v. Duguid, 141 S. Ct. 1163, 1173 (2021) conflicted with Duguid’s “holding and rationale,” since Defendant in this case did not “dial random or sequential blocks of telephone numbers,” but instead used numbers provided by consumers during the registration process.

The dialing system that Defendant “used to contact [Plaintiff] merely processe[d] phone numbers supplied by consumers while signing up for [Defendant’s] services.” Plaintiff’s complaint alleged that Defendant’s dialing system stored the telephone numbers “in a random and/or sequential way; uses a random and/or sequential generator to pull from the list of numbers to send targeted text messages; and uses a random and/or sequential generator to determine the sequence in which to send messages.”  Specifically, Plaintiff relied on footnote 7 in Duguid, which states that “an autodialer might use a random number generator to determine the order in which to pick phone numbers from a preproduced list. It would then store those numbers to be dialed at a later time.” Plaintiff argued that footnote 7 expanded the definition of an ATDS to include Defendant’s dialing system.

The court disagreed, stating “the [Supreme] Court employed the quoted line to explain how an autodialer might both ‘store’ and ‘produce’ randomly or sequentially generated phone numbers[.]” The court looked to the amicus curiae brief cited in footnote 7, which “makes clear that the ‘preproduced list’ of phone numbers referenced in the footnote was itself created through a random or sequential number generator.” The list of numbers used by the Defendant however, were “obtained in a non-random way (specifically, from consumers who provide them).”

Thus, because the platform solely used phone numbers that had been supplied by consumers, “and not phone numbers identified in a random or sequential fashion,” the court found that Defendant’s platform did “not qualify as an autodialer under the TCPA.” The court therefore dismissed Plaintiff’s complaint with prejudice.

Hufnus v. DoNotPay, Inc., No. 20-CV-08701-VC, 2021 WL 2585488 (N.D. Cal. June 24, 2021).
 
Court Finds Standing Sufficient But Dismisses TCPA Action For Insufficient Facts Alleged

In Camunas v. National Republican Senatorial Committee, the Eastern District of Pennsylvania dismissed a TCPA case for failure to adequately plead sufficient facts showing that an ATDS was used to send the text messages at issue.

Plaintiff alleged that he received “at least six messages” from a political organization, and that the messages were “generic and obviously pre-written.” The complaint further alleged that Defendant’s website “states that its opt-in messaging program communicates using ‘recurring autodialed marketing messages.’” Defendant moved to dismiss the complaint for lack of subject matter jurisdiction, arguing that Plaintiff failed to plead an injury-in-fact, and for failure to state a claim.

Defendant challenged the Plaintiff’s standing to assert a claim based on a handful of text messages.  In denying Defendant’s motion to dismiss for lack of subject matter jurisdiction, the court held that Plaintiff “plausibly alleges he suffered an injury” and “also plausibly alleges that the injury is fairly traceable to [Defendant’s] conduct and that a favorable judicial decision would redress the alleged injury.” On this point, Defendant argued against Plaintiff’s position that the six messages should be sufficient for the injury-in-fact standing requirement. Defendant sought “to distinguish [Susinno v. Work Out World Inc., 862 F.3d 346 (3d Cir. 2017)], from the instant action by arguing that Susinno ‘involved a phone call and a one-minute prerecorded voicemail – not a small number of text messages’ and still ‘required the plaintiff actually assert and plead an injury – such as nuisance and invasion privacy.’” The court found that in this case, Plaintiff had similarly alleged that “he found [Defendant’s] unsolicited communication ‘annoying, disruptive, frustrating and an invasion of his privacy.’” Thus, the court found that it had subject matter jurisdiction over the claim.

On the 12(b)(6) motion to dismiss for failure to state a claim, the court held that Plaintiff had not plausibly alleged that Defendant “used an ATDS to send the messages at issue.” The court found that the complaint had not identified what was contained in the text messages at issue, had not identified “the phone number from which the messages were sent,” and had failed to “indicate whether that number was a short code.” The court noted that “[i]n cases involving text messages,” courts “‘have considered the nature of the message, the length of the sending number, the number of messages, and the relationship between the parties.’” Specifically, the court pointed out that “several courts have concluded that a ‘short code’ number supports an inference of ATDS use.” As such, Plaintiff had had not alleged sufficient facts “to ‘nudge’ his claim ‘across the line from conceivable to plausible.’”

Ultimately, the court denied Defendant’s motion to dismiss for lack of subject matter jurisdiction, but granted the motion to dismiss for failure to state a claim, dismissing the complaint without prejudice.

Camunas v. National Republican Senatorial Committee, No. 21-1005, 2021 WL 2144671 (E.D. Pa. May 26, 2021).