FCC proposed rules on robotexting and robocall prevention

The Federal Communications Commission (FCC) has proposed rules to prevent robotexting and robocalls to reassigned numbers. Here are the details.

Declaratory ruling on text messaging

FCC Chairman Ajit Pai

This rule would clearly establish that text messaging services are information services, not telephone services. This distinction would allow carriers to continue to use robotext blocking and anti-spoofing measures to protect consumers from unwanted text messages, called robotexts.

“Americans rely on and trust text messaging,” said FCC Chairman Ajit Pai. “That’s why we need to act to prevent a deluge of spam texts and scam messages.”

Order to create database of reassigned numbers

This order would call for the creation of a single, comprehensive database of reassigned numbers. This information would be provided by phone companies that obtain North American Numbering Plan U.S. geographic numbers.

Millions of telephone numbers are reassigned each year. While reassigning numbers is an efficient use of the number pool, it can cause problems for everyone involved:

  • Subscribers with reassigned numbers get unwanted calls intended for the previous telephone number holders.
  • Subscribers miss calls from parties they forgot to notify after changing their phone numbers.
  • Organizations with prior authorized consent are unable to contact their customers and inadvertently annoy new number holders instead.

The reassigned numbers database would enable legitimate callers to check whether a number has been reassigned and thereby avoid making unwanted calls.

Chairman Pai explained, “I’m also proposing new rules to help reduce robocalls to reassigned numbers by creating a database that will help legitimate businesses stop calling those numbers.”

The FCC will discuss these items at its Open Commission Meeting on December 12, 2018.


Oct 20, 2021

STI-GA announces support for enhanced SHAKEN functionality

Oct 18, 2021

STIR/SHAKEN statistics for September 2021

Oct 5, 2021

Out-of-Band SHAKEN with a private Call Placement Service

Sep 29, 2021

Many SHAKEN certifications, few SHAKEN-authorized providers

Sep 15, 2021

STIR/SHAKEN statistics for August 2021

Sep 13, 2021

FCC proposes additional robocall rules for gateway providers

Sep 8, 2021

FCC asks whether to revise SHAKEN mandate extensions

Sep 1, 2021

Robocalls down in August—trend, or blip?

August 26, 2021

Rich Call Data and Delegate Certificates—a great pairing

August 18, 2021

Fifty-one state AGs ask FCC to shorten SHAKEN extension

August 16, 2021

Canadian regulator changes service provider SHAKEN qualifications

August 11, 2021

July 2021 STIR/SHAKEN statistics

August 9, 2021

FCC establishes SHAKEN revocation appeals process

August 4, 2021

Are SHAKEN and robocall mitigation preventing unlawful robocalls?

July 28, 2021

Who should sign SHAKEN calls?

July 26, 2021

Spam robocalls and SHAKEN attestation

July 15, 2021

SHAKEN for TDM standards approved

July 14, 2021

SHAKEN attestation statistics for early July 2021

July 2, 2021

June 2021 STIR/SHAKEN statistics

July 1, 2021

Robocall Mitigation Database filing statistics

June 29, 2021

Robocaller tried to hack SHAKEN

June 15, 2021

May 2021 STIR/SHAKEN statistics

June 11, 2021

Webinar recording — Preparing for SHAKEN in Canada

June 9, 2021

Robocall Mitigation Database filing statistics

June 7, 2021

U.S. — Canada cross-border SHAKEN

May 25, 2021

Press release — New Out-of-Band SHAKEN whitepaper available

May 13, 2021

February 17, 2021

ClearIP Out-of-Band SHAKEN enhancements