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.


January 18, 2021

Webinar recording — Complying with the TRACED Act made simple

January 15, 2021

FCC proposes rules on SHAKEN certificate revocation for noncompliance

January 4, 2021

FCC issues further restrictions on robocalls

December 18, 2020

SIPNOC webinar recording available—Rich Call Data and Out-of-Band SHAKEN

November 30, 2020

Service providers request SHAKEN extensions

November 20, 2020

FCC SHAKEN Second Report and Order deadlines

November 18, 2020

U.S. STI-GA to update the Service Provider Code token access policy for STIR/SHAKEN

November 3, 2020

Comments on caller ID authentication best practices

November 2, 2020

STIR/SHAKEN, least cost routing and attestation

October 28, 2020

Reply comments on caller ID authentication progress

October 26, 2020

Standards-based STIR/SHAKEN

October 21, 2020

SHAKEN benefits for enterprise callers

October 19, 2020

PASSporTs used with STIR/SHAKEN

October 19, 2020

How to register with the STI Policy Administrator to authenticate calls with STIR/SHAKEN

October 14, 2020

October 14, 2020

International SHAKEN — how that might work

October 7, 2020

Best practices for call authentication – first proposal

October 5, 2020

Three requirements from the FCC SHAKEN orders that will apply to most U.S. providers

September 30, 2020

FCC approves second order on SHAKEN

September 28, 2020

SHAKEN, robocall mitigation, or both?

September 16, 2020

Robocall mitigation program mandate

June 25, 2020

Open source Call Placement Service advances SHAKEN call authentication for all