Skip to main content
Menu Icon
Close

InfoBytes Blog

Financial Services Law Insights and Observations

Filter

Subscribe to our InfoBytes Blog weekly newsletter and other publications for news affecting the financial services industry.

  • FCC chair asks Congress to act on robocalls

    Federal Issues

    In December, FCC Chair Jessica Rosenworcel sent a letter to twelve senators in response to their June 2022 letter inquiring about combating robocalls. In the letter, Rosenworcel highlighted the FCC’s efforts to combat robocalls by discussing the agency’s “important” proposed rules, adopted in May, to ensure gateway providers that channel international call traffic comply with STIR/SHAKEN caller ID authentication protocols and validate the identity of the providers whose traffic they are routing to help weed out robocalls (covered by InfoBytes here). She also highlighted the FCC’s enforcement efforts, such as a December action where the FCC announced a nearly $300 million fine against an auto warranty scam robocall campaign for TCPA and Truth in Caller ID Act violations—“largest robocall operation the FCC has ever investigated” (covered by InfoBytes here).

    Rosenworcel requested additional authority from Congress to combat robocalls and robotexts more effectively. Specifically, Rosenworcel asked the senators to “fix the definition of autodialer” – since robotexts are neither prerecorded nor artificial voice calls, the TCPA only provides consumers protection from robotexts if they are sent from autodialers. She further noted that the Supreme Court's decision in Facebook v. Duguid (covered by a Buckley Special Alert) narrowed the definition of autodialer under the TCPA, resulting in the law only covering equipment that generates numbers randomly and sequentially. She wrote that as a result, “equipment that simply uses lists to generate robotexts means that fewer robotexts may be subject to TCPA protections, and as a result, this decision may be responsible for the rise in robotexts.” Among other things, she also requested that Congress update the TCPA to permit for administrative subpoenas for all types of non-content customer records, and for Congress to grant the FCC the authority and resources to increase court enforcement of fines.

    Federal Issues FCC STIR/SHAKEN Robocalls U.S. Senate TCPA Truth in Caller ID Act

  • FCC acts to stop international robocalls

    Agency Rule-Making & Guidance

    On May 19, the FCC unanimously adopted proposed rules to ensure gateway providers that channel international call traffic comply with STIR/SHAKEN caller ID authentication protocols and validate the identity of the providers whose traffic they are routing to help weed out robocalls. As part of the agency’s robocall mitigation efforts, the proposed rules would require gateway providers to (i) “develop and submit traffic mitigation plans to the Robocall Mitigation Database”; (ii) “apply STIR/SHAKEN caller ID authentication to all unauthenticated foreign-originated Session Initiation Protocol (SIP) calls with U.S. North American Numbering Plan (NANP) numbers”; and (iii) “respond to traceback requests in 24 hours, block calls where it is clear they are conduits for illegal traffic, and implement ‘know your upstream provider’ obligations.”

    “Gateway providers serve as a critical choke-point for reducing the number of illegal robocalls received by American consumers,” the FCC stated in its announcement. “The new rules require gateway providers to participate in robocall mitigation, including blocking efforts, take responsibility for illegal robocall campaigns on their networks, cooperate with FCC enforcement efforts, and quickly respond to efforts to trace illegal robocalls to their source.” Non-compliance may cause a gateway provider to lose its ability to operate. The FCC also announced it is requesting further comments on a proposal to expand robocall mitigation requirements to intermediate providers in the U.S. and not just gateway providers. The agency will also decide whether anti-robocall and spoofing rules should also apply to these intermediate providers, as they are currently not required to certify with the Robocall Mitigation Database.

    Requiring domestic entry points to use STIR/SHAKEN, register in the Robocall Mitigation Database, and comply with traceback requests from the FCC and law enforcement will help the agency “figure out where these junk calls are originating from overseas,” FCC Chairwoman Jessica Rosenworcel said in a statement. “These measures will help us tackle the growing number of international robocalls. Because we can’t have these scam artists multiplying abroad and hiding from our regulatory reach. We also can’t have them hiding from our state counterparts.” To aid efforts, the FCC announced that to date 36 states have signed memoranda of understanding with the agency to share resources and information to reduce robocalls.

    Agency Rule-Making & Guidance FCC Robocalls STIR/SHAKEN State Issues State Attorney General

Upcoming Events