November 22, 2023
FCC FACT SHEET
*
Combatting Illegal Text Messages
Second Report and Order and Second Further Notice of Proposed Rulemaking in CG Docket Nos. 02-278
and 21-402, and Waiver Order in CG Docket No. 17-59
Background: This Report and Order, Further Notice of Proposed Rulemaking, and Waiver Order takes
the next step in combatting the growing problem of illegal robotexting. This item, if adopted, would
enlist service providers in the fight against illegal text messaging and would close the lead generator
loophole that has resulted in unscrupulous robocallers and robotexters inundating consumers with
unwanted and illegal robocalls and robotexts.
What the Order Would Do:
Require terminating mobile wireless providers to block all texts from a particular number when
notified by the Commission of illegal texts from that number.
Codify that the National Do-Not-Call (DNC) Registry’s protections extend to text messages.
Encourage providers to make email-to-text, a major source of illegal texts, a service that
consumers proactively opt into.
Close the lead generator loophole by making unequivocally clear that comparison shopping
websites must get consumer consent one seller at a time, and thus prohibit abuse of consumer
consent by such websites.
What the Further Notice Would Do:
Propose and seek comment on additional text blocking options, including requiring originating
mobile wireless providers to block texts from a particular number when notified by the
Commission of illegal texts from that number or risk all of their texts being blocked.
Seek comment on the current state of text authentication.
Seek comment on the traceback process for texting and whether to adopt a requirement for mobile
wireless providers to respond to traceback requests from the Commission and law enforcement.
Propose and seek comment on requiring mobile wireless providers to make email-to-text an opt-
in service.
What the Waiver Order Would Do:
Allow mobile wireless providers to use the Reassigned Numbers Database to determine whether a
number has been disconnected after the date of illegal texts in the Commission’s notification to
avoid blocking of texts from reassigned numbers.
*
This document is being released as part of a “permit-but-disclose” proceeding. Any presentations or views on the
subject expressed to the Commission or its staff, including by email, must be filed in CG Docket No. 02-278, CG
Docket No. 21-402, and CG Docket No. 17-59 which may be accessed via the Electronic Comment Filing System
(http://www.fcc.gov/ecfs). Before filing, participants should familiarize themselves with the Commission’s ex parte
rules, including the general prohibition on presentations (written and oral) on matters listed on the Sunshine Agenda,
which is typically released a week prior to the Commission’s Meeting. See 47 CFR § 1.1200 et seq.
Federal Communications Commission FCC-CIRC2312-02
Before the
Federal Communications Commission
Washington, D.C. 20554
In the Matter of
Targeting and Eliminating Unlawful Text Messages
Rules and Regulations Implementing the
Telephone Consumer Protection Act of 1991
Advanced Methods to Target and Eliminate
Unlawful Robocalls
)
)
)
)
)
)
)
)
)
)
)
)
)
CG Docket No. 21-402
CG Docket No. 02-278
CG Docket No. 17-59
SECOND REPORT AND ORDER,
SECOND FURTHER NOTICE OF PROPOSED RULEMAKING IN CG DOCKET NOS. 02-278
AND 21-402, AND WAIVER ORDER IN CG DOCKET NO. 17-59
*
Adopted: [[ ]] Released: [[ ]]
Comment Date: [30 days after Federal Register publication]
Reply Date: [45 days after Federal Register publication]
By the Commission:
TABLE OF CONTENTS
I. INTRODUCTION .................................................................................................................................. 1
II. BACKGROUND .................................................................................................................................... 5
A. The Commission’s Multi-Pronged Approach to Unwanted and Illegal Calls ................................. 7
B. Combating Unwanted and Illegal Texts ......................................................................................... 12
III. SECOND REPORT AND ORDER ...................................................................................................... 14
A. Mandatory Blocking Following Commission Notification............................................................ 16
B. National Do-Not-Call Registry ...................................................................................................... 25
*
This document has been circulated for tentative consideration by the Commission at its December open meeting.
The issues referenced in this document and the Commission’s ultimate resolution of those issues remain under
consideration and subject to change. This document does not constitute any official action by the Commission.
However, the Chairwoman has determined that, in the interest of promoting the public’s ability to understand the
nature and scope of issues under consideration, the public interest would be served by making this document
publicly available. The FCC’s ex parte rules apply and presentations are subject to “permit-but-disclose” ex parte
rules. See, e.g., 47 C.F.R. §§ 1.1206, 1.1200(a). Participants in this proceeding should familiarize themselves with
the Commission’s ex parte rules, including the general prohibition on presentations (written and oral) on matters
listed on the Sunshine Agenda, which is typically released a week prior to the Commission’s meeting. See 47 CFR
§§ 1.1200(a), 1.1203.
Federal Communications Commission FCC-CIRC2312-02
2
C. Email-to-Text messages ................................................................................................................. 28
D. Closing the Lead Generator Loophole ........................................................................................... 29
E. Text Message Authentication and Spoofing .................................................................................. 45
F. Summary of Benefits and Costs ..................................................................................................... 47
G. Legal Authority .............................................................................................................................. 51
IV. SECOND FURTHER NOTICE OF PROPOSED RULEMAKING .................................................... 56
A. Text Blocking ................................................................................................................................ 57
1. Expanding the Mandatory Text Blocking Requirement to Originating Providers and
Adding a Downstream Provider Blocking Requirement ......................................................... 58
2. Requiring Blocking of Texts Based on Reasonable Analytics ................................................ 64
3. Alternative Approaches ........................................................................................................... 68
4. Protections Against Erroneous Blocking ................................................................................. 69
B. Text Message Authentication ........................................................................................................ 70
C. Traceback ....................................................................................................................................... 73
D. E-Mail-To-Text .............................................................................................................................. 75
E. Benefits and Costs ......................................................................................................................... 76
F. Digital Equity and Inclusion .......................................................................................................... 77
G. Legal Authority .............................................................................................................................. 78
V. WAIVER ORDER ............................................................................................................................... 81
VI. PROCEDURAL MATTERS ................................................................................................................ 85
VII.ORDERING CLAUSES ....................................................................................................................... 96
Appendix A List of Commenters
Appendix B Final Rules
Appendix C Proposed Rules
Appendix D Final Regulatory Flexibility Analysis
Appendix E Initial Regulatory Flexibility Analysis
I. INTRODUCTION
1. Consumers increasingly rely on text messaging to stay in touch with friends and family,
to do business, communicate with their child’s school, and get information from their government. On
many devices, people immediately see some or all of the messages once received on the device, whereas
they have the option to ignore unwanted calls. This causes consumers to open their texts quickly because
texts are an expected trusted source of communications, not annoyance and scams.
1
The rise of junk texts
jeopardizes consumer trust in text messaging. The increase of unwanted and illegal texts also frustrate
consumers, and scam texts can cause serious harm. Scam texts can contain links to phishing campaigns
and load malware onto unsuspecting consumers’ phones, leading to fraud and other harms.
2
The Federal
Trade Commission (FTC) reports that text messaging scams cost consumers $86 million in 2020 and
$326 million in 2022.
3
Other estimates show higher losses, e.g., over $20 billion in 2022.
4
1
See CTIA, Messaging, https://www.ctia.org/homepage/messaging-channel (“The text messaging platform is one of
the most trusted forms of communication because consumers have choice and control over their text message
experience.”) (last visited Oct. 26, 2023); CTIA, Protecting Yourself from Spam Messages,
https://www.ctia.org/consumer-resources/protecting-yourself-from-spam-text-messages (“Overall, text messaging is
one of the most trusted and widely used forms of communication by consumers. In fact, Americans send over
63,600 text messages per second.”) (last visited Oct. 26, 2023).
2
SMS phishing, or smishing, is the practice of sending text messages to someone in order to trick the person into
revealing personal or confidential information which can then be used for criminal purposes. Merriam Webster
Dictionary, https://www.merriam-webster.com/dictionary/smishing (last visited Nov. 3, 2023).
3
FTC, Consumer Sentinel Network Data Book 2020 at 12 (2021),
https://www.ftc.gov/system/files/documents/reports/consumer-sentinel-network-data-book-
(continued….)
Federal Communications Commission FCC-CIRC2312-02
3
2. We take action today to stop this trend and ensure consumers can continue to trust text
messaging. We do so by building on our recent text blocking requirements. First, we require terminating
mobile wireless providers
5
to block text messages
6
from a particular number following notification from
the Commission unless their investigation determines that the identified text messages are not illegal.
Next, we codify that the National Do-Not-Call (DNC) Registry’s protections apply to text messages.
Third, we encourage providers to make email-to-text, a major source of illegal texts, a service that
consumers proactively opt into. Next, we close the lead generator loophole by prohibiting lead
generators, texters, and callers from using a single consumer consent to inundate consumers with
unwanted texts and calls when consumers visit comparison shopping websites.
3. And we propose further steps to stop unwanted texts. First, we propose a stronger
blocking requirement following Commission notification and seek comment on other options for
requiring providers to block unwanted or illegal texts. Second, we seek further comment on text message
authentication, including the status of any industry standards in development. Finally, we propose to
require, rather than simply encourage, providers to make email-to-text services opt in.
4. We also adopt a limited waiver to allow providers to use the Reassigned Numbers Database
(RND) to determine whether a number that the Commission has ordered to be blocked has been
permanently disconnected. This waiver will help prevent blocking of lawful texts from a new subscriber
to the number.
II. BACKGROUND
5. While combatting unwanted and illegal calls has long been one of the Commission’s top
consumer protection priorities, combatting unwanted and illegal text messages is a comparatively new
focus.
7
Just like unwanted and illegal calls, unwanted and illegal texts defraud and harass consumers.
(Continued from previous page)
2020/csn_annual_data_book_2020.pdf (2020 Consumer Sentinel Data Book); FTC, Consumer Sentinel Network
Data Book 2022 at 12 (2023), https://www.ftc.gov/system/files/ftc_gov/pdf/CSN-Data-Book-2022.pdf (2022
Consumer Sentinel Data Book). See also FTC, Consumer Sentinel Network Data Book 2021 at 12,
https://www.ftc.gov/reports/consumer-sentinel-network-data-book-2021 (2022) (2021 Consumer Sentinel Data
Book). As the Joint Consumer Commenters observe, the FTC data are based solely on reports made by consumers
and represent only a fraction of the universe of losses from text scams; the actual losses to consumers from text-
initiated frauds are, undoubtedly, exponentially greater. Joint Consumer Commenters at 3.
4
Robokiller, The Robokiller Phone Scam Report: 2022 Insights & Analysis, at 4 (2023), https://assets.website-
files.com/61f9a8793a878d7f71c5505d/6400e06e514500224ad26830_The%20Robokiller%20phone%20scam%20re
port%20-%202022%20insights%20%26%20analysis.pdf (Robokiller 2022 Report). Robokiller observes that, in
2022, 225.7 billion spam texts were sent, a 157% increase from 2021’s then-record 87.8 billion. Id. at 5. Robokiller
estimates the loss to robotext scams at $13 billion, for the first half of 2023, a $4 billion increase from the first half
of 2022. Robokiller, The Robokiller Phone Scam Report: 2023 Midyear Insights & Analysis, at 4 (2023),
https://assets.website-files.com/61f9a8793a878d7f71c5505d/64ca6ccf1f5e962fae3e55e3_Robokiller%20Mid-
Year%20Report%202023.pdf (Robokiller 2023 Report).
5
In this order, we use “provider” to mean a mobile wireless provider that provides text messaging services. Where
we refer to providers of voice calls, we use the term “voice service provider,” which may include originating,
intermediate, or terminating voice service providers.
6
We use the definition of text message in section 64.1600(o) of our rules in this proceeding. The scope of our
decision regarding text messages is limited to those originating from North American Numbering Plan (NANP)
numbers that use the wireless networks, e.g., SMS and MMS, not over-the-top (OTT) messaging, such as iMessage
and WhatsApp, or Rich Communications Services (RCS); 47 CFR § 64.1600(o) et seq.
7
Since 2003, the Commission has interpreted “call” in section 227(b)(1)(A) of the Communications Act of 1934, as
amended (Act or Communications Act) to include both voice calls and text messages. This order distinguishes
“calls” (voice) from “texts” for purposes of our blocking and other actions today even though they are both “calls”
under the statute.
Federal Communications Commission FCC-CIRC2312-02
4
Robokiller estimates that these texts increased by over 300% between 2020 and 2022.
8
These texts can
result in real financial loss to consumers.
9
6. Robocalls and robotexts can both annoy and defraud consumers, but robotexts can be
particularly pernicious. Robotexts are delivered directly to consumers phones and can include links to
phishing websites that look identical to legitimate websites, easily tricking potential victims into
providing personal or financial information.
10
Or, the link itself may be the threat.
11
Simply clicking on a
scam link could load malware onto phones that provides opportunities for theft of passwords, personally
identifiable information, and other credentials, without consumer consent or knowledge.
12
A. The Commission’s Multi-Pronged Approach to Unwanted and Illegal Calls
7. Unwanted and illegal texts reach the same consumers and may even come from the same
sources as unwanted and illegal calls. Our long-standing work on robocalls thus informs our new work
on robotexts.
8. Telephone Consumer Protection Act and National Do-Not-Call Registry. The TCPA and
the Commission’s implementing rules require callers to obtain consumer consent for certain calls and
texts sent using an automatic telephone dialing system (autodialer) or made using a prerecorded or
artificial voice.
13
If a robocall or robotext includes or introduces an advertisement or constitutes
telemarketing, the prior express consent must be in writing.
14
The Commission has clarified that Internet-
to-phone text messages, which are sent via the Internet to a provider and then routed to a consumer’s
phone over the provider’s wireless network, are also covered by the TCPA.
15
The Commission’s DNC
8
Robokiller 2022 Report at 4. Robokiller observes that, in 2022, fraudsters sent 225.7 billion spam texts, a 157%
increase from 2021’s then-record 87.8 billion. Id. at 5. According to Robokiller, Americans received 78 billion
robotexts in the first half of 2023, an increase of 18% from the first half of 2022. Robokiller 2023 Report at 4.
9
See, e.g., 2020 Consumer Sentinel Data Book at 12; 2021 Consumer Sentinel Data Book at 12; 2022 Consumer
Sentinel Data Book at 12; Robokiller 2022 Report at 4; Robokiller 2023 Report at 4.
10
See, e.g., FTC, Consumer Advice, How to Recognize and Avoid Phishing Scams,
https://consumer.ftc.gov/articles/how-recognize-and-avoid-phishing-scams (last visited Nov. 3, 2023); AT&T,
Cyber Aware, Text Message Scams, https://about.att.com/pages/cyberaware/ni/blog/text_scams (last visited Nov. 3,
2023); Verizon, Account Security, Smishing and Spam Text Messages, https://www.verizon.com/about/account-
security/smishing-and-spam-text-messages (last visited Nov. 3, 2023).
11
FTC, Consumer Advice, How to Recognize and Avoid Phishing Scams, https://consumer.ftc.gov/articles/how-
recognize-and-avoid-phishing-scams (last visited Nov. 3, 2023).
12
FTC, Consumer Advice, How to Recognize, Remove, and Avoid Malware, https://consumer.ftc.gov/articles/how-
recognize-remove-avoid-malware (last visited Nov. 6, 2023).
13
47 U.S.C § 227(b)(1)(A); 47 CFR § 64.1200(a)(1); see also 47 CFR § 64.1200(a)(9) (providing exemptions to
(a)(1)(iii) and noting that “the term ‘call’ includes a text message, including a short message service (SMS) call”).
This restriction applies to calls directed to wireless numbers, as well as to emergency numbers and other specified
locations. For autodialed or prerecorded-voice telemarketing calls to wireless numbers, prior express consent must
be written. See 47 CFR § 64.1200(a)(2); Rules and Regulations Implementing the Telephone Consumer Protection
Act of 1991, CG Docket No. 02-278, Report and Order, 27 FCC Rcd 1830, 1838, para. 20 (2012) (2012 TCPA
Order). The seller bears the “burden of demonstrating that a clear and conspicuous disclosure was provided and that
unambiguous consent was obtained.” 2012 TCPA Order, 27 FCC Rcd at 1844, para. 33. In the Facebook v. Duguid
decision, the Supreme Court clarified that “a necessary feature of an autodialer under § 227(a)(1)(A) is the capacity
to use a random or sequential number generator to either store or produce phone numbers to be called.” Facebook,
Inc. v. Duguid, 141 S.Ct. 1163, 1173 (2021) (Facebook).
14
See 47 CFR § 64.1200(a)(2).
Federal Communications Commission FCC-CIRC2312-02
5
rules protect consumers from unwanted telephone solicitations or telemarketing calls to wireless
16
and
wireline phones when the consumer has added the number to the National DNC Registry.
17
9. Call Blocking, Robocall Mitigation, and Caller ID Authentication. To better protect
consumers from bad actors that do not comply with the restrictions under the TCPA and National DNC
Registry or otherwise place illegal calls or texts, the Commission has taken further steps to combat illegal
calls. This includes ensuring consumers have a say in which calls ring their phones, restoring faith in
caller ID and making callers easier to identify, and holding voice service providers responsible for the
calls they originate or transmit.
10. Of particular interest here, the Commission has authorized providers to block calls in
certain instances,
18
adopted safe harbors to ensure that providers are not subject to liability for blocking
within certain constraints,
19
and in some cases mandated blocking of certain categories of calls that are
highly likely to be illegal.
20
These rules require certain voice service providers to block calls following
notification of illegal traffic by the Commission and that providers immediately downstream block their
traffic if they fail to do so.
21
And the Commission has adopted rules mandating that voice service
providers respond to traceback requests
22
and requiring originating, terminating, and intermediate voice
service providers to implement the STIR/SHAKEN caller ID authentication framework in the IP portions
(Continued from previous page)
15
Rules and Regulations Implementing the Telephone Consumer Protection Act of 1991, CG Docket No. 02-278, 30
FCC Rcd 7961, 8019-20, paras. 113-15 (2015) (2015 TCPA Declaratory Ruling and Order) (describing services that
allow senders to initiate texts via the Internet rather than via an individual phone where those texts look functionally
equivalent to the recipient).
16
In the 2003 TCPA Order, the Commission concluded that the National DNC Registry should allow for the
registration of wireless telephone numbers, and that such action will better further the objectives of the TCPA and
the Do-Not-Call Act
. Rules and Regulations Implementing the Telephone Consumer Protection Act of 1991, CG
Docket No. 02-278, Report and Order, 18 FCC Rcd 14014, 14037-38, para. 33 (2003) (2003 TCPA Order).
17
2003 TCPA Order, 18 FCC Rcd at 14033-39, 14116, paras. 25-36, 166; 47 CFR § 64.1200(c)(2), (e). The
National DNC Registry currently protects over 246 million telephone numbers from telemarketing sales calls, or
“telephone solicitations.” See FTC National Do-Not-Call Registry Data Book for Fiscal Year 2022, (Nov. 2022)
https://www.ftc.gov/reports/national-do-not-call-registry-data-book-fiscal-year-2022. The TCPA defines a
“telephone solicitation” as “the initiation of a telephone call or message for the purpose of encouraging the purchase
or rental of, or investment in, property, goods, or services, which is transmitted to any person” but not including
calls or messages made with prior express invitation or permission, to any person with whom the caller has an
established business relationship, or by a tax exempt nonprofit organization. 47 U.S.C. § 227(a)(4).
18
See 47 CFR § 64.1200(k)(1), (2).
19
See 47 CFR § 64.1200(k)(3), (4), (11).
20
See 47 CFR § 64.1200(o).
21
47 CFR § 64.1200(n)(5), (n)(6).
22
47 CFR § 64.1200(n)(1). Traceback is the process of following the call path back to the point of origin. In the
Gateway Provider Order and Further Notice, the Commission enhanced the existing traceback requirement to
require gateway providers to respond to traceback requests within 24 hours. Advanced Methods to Target and
Eliminate Unlawful Robocalls, Call Authentication Trust Anchor, CG Docket No. 17-59, WC Docket No. 17-97,
Sixth Report and Order in CG Docket No. 19-59, Fifth Report and Order in WC Docket No. 17-97, Order, Seventh
Further Notice of Proposed Rulemaking in CG Docket No. 17-59 & Fifth Further Notice of Proposed Rulemaking in
WC Docket No. 17-97, 37 FCC Rcd 6865, 6894-97, paras. 65-71 (2022) (Gateway Provider Order and Further
Notice). In the May 2023 Call Blocking Order, we expanded that enhanced requirement to cover all domestic voice
service providers. Advanced Methods to Target and Eliminate Unlawful Robocalls, Call Authentication Trust
Anchor, CG Docket No. 17-59, WC Docket No . 17-97, paras. 21-28 (May 2023 Call Blocking Order).
Federal Communications Commission FCC-CIRC2312-02
6
of their networks.
23
Taken together, these requirements help identify bad actors—both callers and voice
service providers—and stop these calls at their source.
11. Enforcement. The Commission has also taken enforcement action to protect consumers
against illegal calls. For example, the Sumco Forfeiture Order found that certain robocall campaigns
violated the TCPA for reasons including the telemarketers’ failure to obtain prior express written consent
before initiating telemarketing calls to wireless phones and residential lines.
24
And the Commission
recently required all voice service providers immediately downstream from a specific gateway provider to
block and cease accepting all traffic from that gateway provider after it repeatedly allowed transmission
of illegal robocalls into the United States.
25
B. Combating Unwanted and Illegal Texts
12. The Commission for the first time required providers to block certain texts that are highly
likely to be illegal in March of 2023.
26
The Commission required providers to block—at the network
level—texts purporting to be from North American Numbering Plan (NANP)
27
numbers on a reasonable
23
See Call Authentication Trust Anchor, Implementation of TRACED Act Section 6(a)—Knowledge of Customers by
Entities with Access to Numbering Resources, WC Docket Nos. 17-97 and 20-67, Report and Order and Further Notice
of Proposed Rulemaking, 35 FCC Rcd 3241, 3252, para. 24 (2020) (requiring originating and terminating providers to
implement STIR/SHAKEN) (First Caller ID Authentication Order); Call Authentication Trust Anchor, WC Docket
No. 17-97, Second Report and Order, 36 FCC Rcd 1859, 1876-97, paras. 36-73, (providing implementation
extensions to certain providers) (Second Caller ID Authentication Order); Gateway Provider Order and Further
Notice, 37 FCC Rcd at 6886-894, paras. 51-63 (requiring gateway providers, a subset of intermediate providers, to
implement STIR/SHAKEN); Call Authentication Trust Anchor, WC Docket No. 17-97, Sixth Report and Order and
Further Notice of Proposed Rulemaking, FCC 23-18 (Mar. 17, 2023) at paras. 15-27 (2023 Caller ID Authentication
Order) (requiring non-gateway intermediate providers that receive unauthenticated calls directly from originating
providers to authenticate calls with STIR/SHAKEN by December 31, 2023); 47 CFR §§ 64.6301, 64.6302, 64.6304.
STIR/SHAKEN caller ID authentication helps confirm that the caller ID is not spoofed, or otherwise provides
information regarding what the signing voice service provider knows to be true about the caller and its right to use
the number. Protocols developed by the Secure Telephony Identity Revisited (STIR) working group of the Internet
Engineering Task Force (IETF) work with the Signature-based Handling of Asserted information using toKENs
(SHAKEN) implementation standards created by the Alliance for Telecommunications Industry Solutions (ATIS)
and the SIP Forum. See First Caller ID Authentication Order, 35 FCC Rcd 3241, 3244-46, paras. 5-10.
24
Sumco Panama SA, et al , EB File No. EB-TCD-21-00031913, Forfeiture Order, FCC 23-64, at 12-13, paras. 25-
26 (Aug. 3, 2023) (Sumco Forfeiture Order).
25
One Eye LLC, EB Docket No. 22-174, Final Determination Order, DA 23-389, at 1, 2-3, paras. 1, 5 (May 2023)
(One Eye). More recently, issued an Initial Determination Order against One Owl Telecom for the apparent
transmission of illegal traffic. One Owl Telecom Inc., EB Docket No. 22-174, Initial Determination Order, DA 22-
174 (Sept. 2023).
26
See generally Targeting and Eliminating Unlawful Text Messages, Rules and Regulations Implementing the
Telephone Consumer Protection Act of 1991, CG Docket Nos. 02-278, 21-402, Report and Order and Further Notice
of Proposed Rulemaking, FCC 23-21 (Mar. 17, 2023) (Text Blocking Order and Further Notice). Previously, the
Commission’s Enforcement Bureau had investigated instances of robotexting. See, e.g., Emanuel (Manny)
Hernandez, Click Cash Marketing, LLC, and Rock Solid Traffic, Citation and Order, Unauthorized Text Message
Violations, 33 FCC Rcd 12382 (EB 2018) (Hernandez); Public Notice, FCC Enforcement Advisory, Robotext
Consumer Protection, Text Message Senders Must Comply With The Telephone Consumer Protection Act, 31 FCC
Rcd 12615 (EB 2016).
27
The NANP is the basic numbering scheme for the telecommunications networks located in American Samoa,
Anguilla, Antigua, Bahamas, Barbados, Bermuda, British Virgin Islands, Canada, Cayman Islands, Dominica,
Dominican Republic, Grenada, Jamaica, Montserrat, Saint Maarten, St. Kitts & Nevis, St. Lucia, St. Vincent, Turks
& Caicos Islands, Trinidad & Tobago, and the United States (including Puerto Rico, the U.S. Virgin Islands, Guam,
and the Commonwealth of the Northern Mariana Islands). 47 CFR § 52.5(d).
Federal Communications Commission FCC-CIRC2312-02
15
who argue that consumers deserve protection against calls that go beyond the scope of consent, a scope
that can be reasonably inferred from the purpose of the website at which they gave that consent.
85
We
believe that texters and callers are capable of implementing this standard and, when in doubt, will err on
the side of limiting that content to what consumers would clearly expect. As a result, we decline to adopt
a definition of “logically and topically” at this time as some commenters suggest.
86
36. Preserving Comparison Shopping Websites and Ease of Compliance. Our new rule
protects consumers while preserving the ability of comparison shopping websites to provide consumers
with comparison shopping opportunities.Such websites are useful both to consumers, who are seeking
specific goods and services, and businesses, including small businesses seeking new customers.
87
37. Websites, including comparison shopping websites, can use a variety of means for
collecting one-to-one consent for multiple sellers to comply with our rule. For instance, the website may
offer a consumer a check box list that allows the consumer to specifically choose each individual seller
that they wish to hear from.
88
Alternatively, the comparison shopping website may offer the consumer a
clickthrough link to a specific business so that the business itself may gather express written consent from
the consumer directly. Our rule does not prohibit comparison shopping websites from obtaining leads
through valid consent and provides multiple opportunities for responsible comparison shopping websites
to obtain leads for potential callers.
38. The rule we adopt today best balances the needs of businesses to utilize lead generation
services to make calls to potential buyers with protecting consumers from a deluge of unwanted robocalls
and robotexts. We thus disagree with those commenters who argue that this rule unduly harms business,
including small businesses.
89
First, our rules already require that callers and texters obtain valid consent.
90
The rule we adopt today helps callers and texters, including small businesses, by providing legal certainty
as to how to meet their burden of proof when they have obtained consent via a third party. Our rule does
not prevent small business from obtaining leads from third party comparison shopping websites or from
making calls pursuant to those leads. They may continue to do so as long as they can clearly demonstrate
that they have obtained consent consistent with the rules we adopt today.
39. Further, callers and texters may avail themselves of other options for providing
comparison shopping information to consumers, e.g., manually dialed or non-prerecorded or artificial
voice calls or texts, email, or information displayed directly on the third party website. We find that the
rule we adopt today provides the best balance between protecting consumers from unwanted and illegal
calls and the need for small businesses to use leads generated by third parties to sell their goods and
services. Indeed, small businesses themselves may utilize comparison shopping services when
comparison shopping for business services and our rule protects these businesses from having their own
85
See, e.g., USTelecom Comments at 5; VON Comments at 7-8; Chandler Comments at 1; QuinStreet Comments at
7; Letter from Lucas Bell, Director, Government Relations, Zillow Group, to Marlene H. Dortch, Secretary, Federal
Communications Commission (Oct. 27, 2023) at 3 (Zillow ex parte).
86
See, e.g., UHC Comments at 4; PACE Comments at 5; Bankers Joint Commenters Reply at 13-16.
87
See, e.g., OLA Comments at 3 (observing that small-dollar lead generators often connect underserved consumers
with credit providers willing to quickly help solve the needs of the credit challenged); REACH Comments at 4 (lead
generators can be “an engine that drives a huge number of small and independent companies that do not have their
own robust marketing team”).
88
Joint Consumer Commenters Reply at 13; State Attorneys General Reply at 17.
89
See, e.g., OLA Comments at 3-4; REACH Comments at 4-5; SolarReviews Comments at 4; Letter from Eric J.
Troutman, counsel for EXP Realty, to Marlene H. Dortch, Secretary, Federal Communications Commission at 1-2
(Nov. 16, 2023) (EXP Realty ex parte).
90
2015 TCPA Declaratory Ruling and Order, 30 FCC Rcd at 7989-7993, paras. 47-54.
Federal Communications Commission FCC-CIRC2312-02
8
appropriate action after receiving notice.
34
17. We agree with commenters that support requiring terminating providers to block in these
instances.
35
As one commenter noted, “[i]t is imperative that the Commission use every available tool to
stop bad actors from sending texts to consumers that are illegal” and “[w]hen an entity is on notice from
the Commission that a sender is transmitting suspected illegal texts, the entity should investigate and
potentially block texts from that sender.”
36
A similar model has worked well in the call blocking context
37
and allows the Enforcement Bureau to take clear, decisive action to protect consumers.
18. We thus disagree with commenters that argue a blocking mandate is inappropriate
because either providers already block texts or that the mandate may not otherwise significantly reduce
the volume of illegal texts.
38
These commenters offer no specific or compelling evidence that providers
consistently block all text traffic the Enforcement Bureau might identify as illegal.
39
Undisputed public
data makes clear that unwanted and illegal texts are rising as is the financial loss that accompanies them.
40
If providers’ voluntary efforts alone were enough to protect consumers, we would not see that trend.
Thus, we believe that, just as with call blocking, a block-upon-notice requirement complements, rather
than supplants, the work providers already do. The rule we adopt serves as an important backstop to
ensure that consumers are protected against illegal texts.
19. Our experience with call blocking demonstrates that the Enforcement Bureau can act
quickly and identify illegal traffic that providers have not blocked, and we see no reason to believe that it
cannot do so here. We thus disagree with commenters who argue that the blocking process we adopt
today may be slower, and thus less effective, than voluntary blocking measures by providers.
41
Nothing
we require slows voluntary blocking – providers can (and we expect them to) continue to block and to
improve their blocking going forward. Our new requirements instead will ensure they block texts their
current blocking fails to capture, a necessary complement to their existing work. Providers that argue
texters will have moved on to new numbers by the time the Enforcement Bureau identifies their texts
point to no specific evidence to that effect. Indeed, we believe that some texters undoubtedly use
numbers until their texts no longer reach recipients at all. And, as detailed further below, we disagree
with the comment that our requirements would unduly increase costs.
42
We believe that providers are
already familiar with the similar call blocking requirements and extending those to texting should not
34
The rule we adopt does not fully mirror the requirement for voice service providers. For example, here
terminating providers must block texts, while in call blocking the obligation is on gateway or originating providers.
As a result, failure to comply will not lead to all immediate downstream providers blocking all of the identified
provider’s traffic since there are no providers downstream from a terminating provider. Instead, terminating
providers that fail to comply may be subject to our traditional enforcement process, including monetary forfeitures.
35
See, e.g., ECAC Comments at 2-3; Bankers Joint Commenters Reply at 9; State Attorneys General Reply at 19-
20; VON Comments at 3-4 (supporting requiring blocking but also urging the Commission to add a traceback
component and ensure that traffic is illegal before requiring blocking).
36
Bankers Joint Commenters Reply at 9.
37
See, e.g., One Eye.
38
See, e.g., CTIA Comments at 7-8 & Reply at 5; M
3
AAWG Comments at 4; T-Mobile Reply at 2-5; Twilio Reply
at 3-7; Letter from Scott Bergmann, Senior Vice President, Regulatory Affairs, CTIA to Marlene H. Dortch,
Secretary, Federal Communications Commission (July 25, 2023) at 1-2 (CTIA ex parte).
39
See, e.g. CTIA Comments at 7-8 & Reply at 5; T-Mobile Reply at 2-5; Twilio Reply at 7.
40
See, e.g., 2020 Consumer Sentinel Data Book at 12; 2021 Consumer Sentinel Data Book at 12; 2022 Consumer
Sentinel Data Book at 12; Robokiller 2022 Report at 4; Robokiller 2023 Report at 4.
41
See, e.g., M
3
AAWG Comments at 4; NetNumber Comments at 2-6; T-Mobile Reply at 3-4.
42
CCA Comments at 2-3.
Federal Communications Commission FCC-CIRC2312-02
9
represent a material additional burden.
20. We adapt the call blocking rule to text blocking to recognize important differences. First,
we agree with commenters that there may not be a provider directly analogous to a gateway voice service
provider in texting.
43
We therefore we require only terminating mobile wireless providers to block.
Second, we do not require text blockers to also block traffic “substantially similar” to the traffic the
Enforcement Bureau identifies to avoid blocking based on analytics that could lead to over blocking.
44
Texters that run afoul of this rule and find all texts from a particular number blocked can obtain a new
number and, as long as they do not then use that number to send illegal texts, will not be blocked under
this rule. This approach addresses record concerns about liability for blocking incorrectly, as well as
potential burdens if we adopted a more expansive rule.
45
We also believe blocking based on a specific
number or numbers identified by the Enforcement Bureau will be competitively neutral.
46
Additionally,
we modify the process the Enforcement Bureau must follow, including not requiring an Initial
Determination Order or Final Determination Order. These steps are unnecessary, because there is no
requirement for downstream providers to block, and in fact no downstream providers at all, so a provider
does not lose access to the network if it fails to comply.
21. Notification of Suspected Illegal Texts. Under our new rules, the Enforcement Bureau
may notify terminating providers of suspected illegal texts from a number or numbers. The Notification
of Suspected Illegal Texts shall: (1) identify the number(s) used to originate the suspected illegal texts and
the date(s) the texts were sent or received; (2) provide the basis for the Enforcement Bureau’s reasonable
belief that the identified texts are unlawful;
47
(3) cite the statutory or regulatory provisions the suspected
illegal texts appear to violate; and (4) direct the provider receiving the notice that it must comply with
section 64.1200(s) of the Commission’s rules. The Notification of Suspected Illegal Texts shall specify a
reasonable time frame for the notified provider to complete its investigation and report its results to
Enforcement Bureau.
48
22. Responses to a Notification of Suspected Illegal Texts. Upon receiving such notice, the
provider must promptly investigate the texts and number(s) identified in the notice and begin blocking all
texts from the identified number(s) within the timeframe specified in the Notification of Suspected Illegal
Texts unless its investigation determines that the identified texts are legal. The provider must report to
the Enforcement Bureau the results of its investigation, including a certification that it is blocking texts
from the identified number(s) or, if it determines that the texts are lawful, an explanation as to why it has
reasonably concluded that the texts are not illegal.
43
See, e.g., CTIA Comments at 10.
44
See, e.g., ECAC Comments at 4 (The common use of content analysis in text message blocking means that there
is more opportunity and risk for overly broad interpretations of “substantially similar traffic.”); CTIA Reply at 13
(“A bright-line rule requiring mandatory blocking based on the content of certain text messages (e.g., URLs) would
only increase the incidences of blocking legitimate text messages.”).
45
CCA Comments at 2-3.
46
See, e.g., INCOMPAS Comments at 5; VON Comments at 3-4.
47
The Notification should include any relevant nonconfidential evidence from credible sources.
48
In our call blocking rules, we require the Enforcement Bureau to specify a timeframe of no fewer than 14 days for
a notified gateway provider to complete its investigation and report its results. 47 CFR § 64.1200(n)(5)(i)(A). Here,
however, we allow the Enforcement Bureau discretion to select a different response time, as the consequences of a
terminating mobile wireless provider failing to comply with the deadline are less significant than in call blocking,
where the ultimate consequence of a gateway provider failing to comply with our blocking rule is that immediate
downstream providers will block all of the provider’s traffic. See id. § 64.1200(n)(6). We note that the Enforcement
Bureau will need to be able demonstrate that whatever timeframe it establishes, if shorter than 14 days, is
reasonable.
Federal Communications Commission FCC-CIRC2312-02
10
23. If the provider cannot block further texts from some or all of the numbers because some
or all of the numbers have been reassigned, the provider shall promptly notify the Enforcement Bureau of
this fact and include any information it has obtained that demonstrates the number has been reassigned.
49
If, at any time in the future, the provider determines that the number has been reassigned, it shall notify
the Enforcement Bureau and cease blocking. In such instances, we encourage providers to continue to
use other available methods to protect their customers.
24. We do not adopt any additional protections in case of erroneous blocking, but any
individual or entity that believes its texts are being blocked under this rule in error can make use of the
point of contact required under section 64.1200(r) of the Commission’s rules.
50
If the provider determines
that blocking should cease, it should notify the Enforcement Bureau of that finding, including any
evidence that supports that finding.
B. National Do-Not-Call Registry
25. We adopt our proposal to codify the National DNC
51
Registry’s existing protections to
text messages.
52
Texters must have the consumer’s prior express invitation or permission before sending
a marketing text to a wireless number in the DNC Registry. The Commission previously concluded that
the national database should allow for the registration of wireless telephone numbers and that such action
will further the objectives of the TCPA and the Do-Not-Call Act.
53
Our action is consistent with federal
court opinions
54
and will deter both illegal texts and make DNC enforcement easier.
26. Commenters generally support this step.
55
As the Joint Consumer Commenters observe,
section 64.1200(e) of the Commission’s rules explicitly applies its DNC regulations to wireless telephone
numbers and it would be anomalous to conclude that text messages to wireless numbers are “calls” for
one part of the Commission’s TCPA rules but not for the DNC protections.
56
27. We disagree with a commenter that our proposal could undermine basic security
protections because third-party, two-factor authentication providers could be prohibited from contacting
49
We strongly encourage providers to make an effort to determine whether a number has been reassigned in order to
avoid blocking lawful texts from a different source. The Reassigned Numbers Database (RND) should be a useful
tool for accomplishing this, and we are adopting a waiver to permit such use of the RND. See infra paras. 100-103.
50
47 CFR § 64.1200(r).
51
The Commission stated in the 2003 TCPA Order that “wireless subscribers may participate in the national do-not-
call list” and “we will presume wireless subscribers who ask to be put on the national do-not-call list to be
‘residential subscribers’” for purposes of our DNC rules. 2003 TCPA Order, 18 FCC Rcd at 14039, para. 36.
52
Text Blocking Order and Further Notice at paras. 55-57.
53
2003 TCPA Order, 18 FCC Rcd at 14037-38, para. 33. In the 2003 TCPA Order, the Commission, pursuant to
section 227(c) of the Communications Act, adopted a national do-not-call registry, maintained by the FTC, to
provide residential consumers with a one-step option to prohibit unwanted telephone solicitations. 2003 TCPA
Order, 18 FCC Rcd at 14034-35, para. 28.
54
See, e.g., Barton v. Temescal Wellness, LLC, 525 F. Supp.3d 195 (D. Mass. 2021) (Barton); Sagar v. Kelly Auto.
Group, Inc., No. 21-cv-10540-PBS, 2021 WL 5567408 (D. Mass. Nov. 29, 2021) (Sagar); Hall v. Smosh Dot Com,
Inc., 72 F.4th 983, 986 (9th Cir. 2023) (Hall).
55
See, e.g., State Attorneys General Reply at 21 (stating that this is a common-sense approach to eliminate any
potential confusion in the industry and has the added benefit of providing protection to consumers regardless of
whether the texting party utilizes an autodialer); Joint Consumer Commenters at 13-15; M
3
AAWG Comments at 4;
CCA Comments at 5; Dobronski Comments at 9; Subbaiah Comments at 1; Shields Reply at 1-3.
56
Joint Consumer Commenters at 13-15.
Federal Communications Commission FCC-CIRC2312-02
11
end users whose numbers are on the National DNC Registry.
57
Two-factor authentication providers can
simply avoid including solicitation or telemarketing in their texts. Such parties have other ways to
contact their customers who may be on the DNC registry, such as obtaining their written consent for a
text or call, or through email.
C. Email-to-Text messages
28. We encourage providers to make email-to-text an opt-in service as a way to reduce the
number of fraudulent text messages consumers receive.
58
We do so in response to several commenters
that observe texts originating from email addresses, rather than telephone numbers, account for a
significant percentage of fraudulent text messages.
59
For example, ZipDX states that email-to-text
gateways enable anyone to send a text message to a mobile subscriber in relative anonymity.
60
Commenters state that the email-to-text messages process allows the sender to be anonymous because the
text is sent from an email account on a computer, not a phone number.
61
Commenters also observe a
spike in text impersonation scams originating from email-to-text gateways.
62
Below we seek comment on
requiring providers to make this service opt-in.
D. Closing the Lead Generator Loophole
29. We now make it unequivocally clear that texters and callers must obtain a consumer’s
prior express written consent from a single seller at a time on the comparison shopping websites that often
are the source of lead generation, thus closing the lead generator loophole.
63
Lead-generated
communications are a large percentage of unwanted calls and texts and often rely on flimsy claims of
consent to bombard consumers with unwanted robocalls and robotexts.
64
While many comparison
shopping websites that involve lead generation (i.e., websites that generate a consumer “lead” for a seller)
benefit consumers by enabling them to quickly compare goods and services and discover new sellers,
65
57
INCOMPAS Comments at 6.
58
The Commission previously concluded that the equipment used to originate Internet-to-phone text messages to
wireless numbers via email or via a wireless carrier’s web portal is an “automatic telephone dialing system” as
defined in the TCPA, and therefore calls made using the equipment require consent. 2015 TCPA Declaratory
Ruling and Order, 30 FCC Rcd at 8017-8022, paras. 111-122.
59
ZipDX Comments at 2; Somos Reply at 5; Bankers Joint Commenters Reply at 8.
60
ZipDX Comments at 2.
61
ZipDX Comments at 2; Somos Reply at 5 (brand impersonation scams are increasingly widespread form of text
scam).
62
Somos Reply at 5; Bankers Joint Commenters Reply at 8 (observing that bad actors are distributing large volumes
of SMS phishing messages from email addresses (which convert the e-mail message to an SMS text message)).
63
In the Further Notice of Proposed Rulemaking, we sought comment on a proposal that for TCPA consent “prior
express written consent to receive calls or texts must be made directly to one entity at a time.” Text Blocking Order
and Further Notice at para. 61.
64
USTelecom Comments at 2.
65
See, Federal Trade Commission, Follow The Lead: An FTC Workshop On Lead Generation (Oct. 30, 2015) at 5
(available at https://www.ftc.gov/system/files/documents/videos/follow-lead-ftc-workshop-lead-generation-part-
1/lgw-transcript-pt1.pdf) (noting that lead generation is a well-established industry that offers benefits to both
consumers and advertisers). But see also Federal Trade Commission, “Follow the Lead” Workshop, a Staff
Perspective (Sept. 2016) (available at https://www.ftc.gov/system/files/documents/reports/staff-perspective-follow-
lead/staff_perspective_follow_the_lead_workshop.pdf) (observing that consumers who fill out web forms may not
realize they are operated by lead generators, i.e., not merchants, or may not know that this information can be sold
and re-sold multiple times).
Federal Communications Commission FCC-CIRC2312-02
29
copy of any written presentation or a memorandum summarizing any oral presentation within two
business days after the presentation (unless a different deadline applicable to the Sunshine period applies).
Persons making oral ex parte presentations are reminded that memoranda summarizing the presentation
must (1) list all persons attending or otherwise participating in the meeting at which the ex parte
presentation was made, and (2) summarize all data presented and arguments made during the
presentation. If the presentation consisted in whole or in part of the presentation of data or arguments
already reflected in the presenter’s written comments, memoranda or other filings in the proceeding, the
presenter may provide citations to such data or arguments in his or her prior comments, memoranda, or
other filings (specifying the relevant page and/or paragraph numbers where such data or arguments can be
found) in lieu of summarizing them in the memorandum. Documents shown or given to Commission
staff during ex parte meetings are deemed to be written ex parte presentations and must be filed
consistent with section 1.1206(b) of the Commission’s rules. In proceedings governed by section 1.49(f)
of the Commission’s rules or for which the Commission has made available a method of electronic filing,
written ex parte presentations and memoranda summarizing oral ex parte presentations, and all
attachments thereto, must be filed through the electronic comment filing system available for that
proceeding, and must be filed in their native format (e.g., .doc, .xml, .ppt, searchable .pdf). Participants in
this proceeding should familiarize themselves with the Commission’s ex parte rules.
172
91. Filing of Comments and Reply Comments. Pursuant to sections 1.415 and 1.419 of the
Commission’s rules, 47 CFR §§ 1.415, 1.419, interested parties may file comments and reply comments
on or before the dates indicated on the first page of this document. Comments may be filed using the
Commission’s Electronic Comment Filing System (ECFS). See Electronic Filing of Documents in
Rulemaking Proceedings, 63 FR 24121 (1998).
• Electronic Filers: Comments may be filed electronically using the Internet by accessing the
ECFS: www.fcc.gov/ecfs.
• Paper Filers: Parties who choose to file by paper must file an original and one copy of each
filing.
• Filings can be sent by commercial overnight courier, or by first-class or overnight U.S. Postal
Service mail. All filings must be addressed to the Commission’s Secretary, Office of the
Secretary, Federal Communications Commission.
• Commercial overnight mail (other than U.S. Postal Service Express Mail and Priority Mail)
must be sent to 9050 Junction Drive, Annapolis Junction, MD 20701. U.S. Postal Service first
class, Express, and Priority mail must be addressed to 45 L Street NE, Washington, D.C. 20554.
• Effective March 19, 2020, and until further notice, the Commission no longer accepts any hand
or messenger delivered filings. This is a temporary measure taken to help protect the health and
safety of individuals, and to mitigate the transmission of COVID-19. See FCC Announces
Closure of FCC Headquarters Open Window and Change in Hand-Delivery Policy, Public
Notice, 35 FCC Rcd 2788 (OMD 2020).
92. People with Disabilities. To request materials in accessible formats for people with
disabilities (Braille, large print, electronic files, audio format), send an e-mail to [email protected] or call
the Consumer and Governmental Affairs Bureau at 202-418-0530 (voice).
93. Availability of Documents. Comments, reply comments, ex parte submissions, and the
Second Report and Order and Second Further Notice of Proposed Rulemaking will be available via
ECFS. Documents will be available electronically in ASCII, Microsoft Word, and/or Adobe Acrobat.
When the FCC Headquarters reopens to the public, documents will also be available for public inspection
172
47 CFR § 1.49(f).
Federal Communications Commission FCC-CIRC2312-02
30
during regular business hours in the FCC Reference Center, Federal Communications Commission, 45 L
Street NE, Washington, D.C. 20554.
94. Providing Accountability Through Transparency Act: The Providing Accountability
Through Transparency Act requires each agency, in providing notice of a rulemaking, to post online a
brief plain-language summary of the proposed rule.
173
Accordingly, the Commission will publish the
required summary of this Further Notice of Proposed Rulemaking on https://www.fcc.gov/proposed-
rulemakings.
95. Additional Information. For additional information on this proceeding, contact Jerusha
Burnett, [email protected], 202 418-0526, or Mika Savir, [email protected], 202 418-0384, both
of the Consumer and Governmental Affairs Bureau, Consumer Policy Division.
VII. ORDERING CLAUSES
96. Accordingly, IT IS ORDERED, pursuant to sections 4(i), 4(j), 227, 251(e), 301, 303,
307, and 316 of the Communications Act of 1934, as amended, 47 U.S.C. §§ 154(i), 154(j), 227, 251(e),
301, 303, 307, and 316, that this Second Report and Order and Second Further Notice of Proposed
Rulemaking IS ADOPTED.
97. IT IS FURTHER ORDERED that this Second Report and Order SHALL BE
EFFECTIVE 30 days after publication in the Federal Register, except that the amendments to section 47
CFR § 64.1200(f)(9), which may contain new or modified information collection requirements, will not
become effective until six months after publication in the Federal Register or 30 days after notice that the
Office of Management and Budget has completed review of any information collection requirements that
the Consumer and Governmental Affairs Bureau determines is required under the Paperwork Reduction
Act, whichever is later. The Commission directs the Consumer and Governmental Affairs Bureau to
announce the effective date for section 64.1200(f)(9) by subsequent Public Notice.
98. IT IS FURTHER ORDERED, that, the Commission’s rule restricting access to the
Reassigned Numbers Database only to callers to determine whether a number has been permanently
disconnected for the purpose of making lawful calls or sending lawful texts IS WAIVED to the extent
described in the Waiver Order (Section V) to allow mobile wireless providers to access the Reassigned
Numbers Database to determine whether a number has been permanently disconnected since the date(s)
of the suspected illegal texts described in a Notification of Suspected Illegal Texts.
99. IT IS FURTHER ORDERED that the Commission’s Consumer and Governmental
Affairs Bureau, Reference Information Center, SHALL SEND a copy of this Second Report and Order
and Second Further Notice of Proposed Rulemaking, including the Final Regulatory Flexibility Analysis,
to the Chief Counsel for Advocacy of the Small Business Administration.
173
5 U.S.C. § 553(b)(4). The Providing Accountability Through Transparency Act, Pub. L. No. 118-9 (2023),
amended section 553(b) of the Administrative Procedure Act.
Federal Communications Commission FCC-CIRC2312-02
14
on the website.
78
We require consent to one seller at a time, but this requirement does not specify how
many sellers can be listed on the web page; if the web page seeks to obtain prior express written consent
from multiple sellers, the webpage must obtain express consent separately for each seller.
79
In addition,
other sellers can be included on the web page for reasons other than obtaining consent, e.g., for contact
that does not require TCPA prior express written consent, or with information allowing the consumer to
contact the seller directly.
80
These commenters have not offered any data on why the number of sellers
they suggest is better than a different number of sellers.
34. Clear and Conspicuous Disclosure and Logically and Topically Related. We adopt two
additional protections to further guard against consent abuse. First, the one-to-one consent must come
after a clear and conspicuous disclosure to the consenting consumer that they will get robotexts and/or
robocalls from the seller. “Clear and conspicuous” means notice that would be apparent to a reasonable
consumer.
81
In addition, if compliance with the federal Electronic Signatures in Global and National
Commerce Act (the E-Sign Act)
82
is required for the consumer’s signature, then all the elements of E-
Sign must be present.
83
35. Second, we adopt our proposal that robotexts and robocalls that result from consumer
consent obtained on comparison shopping websites must be logically and topically related to that
website.
84
Thus, for example, a consumer giving consent on a car loan comparison shopping website does
not consent to get robotexts or robocalls about loan consolidation. We therefore agree with commenters
78
See, e.g., NAMIC Comments at 4 (proposing no more than 10); AAAB Comments at 1 (specify the maximum
number); SEIA Comments at 3 (proposing three); Chandler Comments at 2 (proposing five). We also do not adopt
the proposal to add to the definition of consent the types or categories of property, goods, or services about which
the person agrees to be called; the total number of callers that may call the person; and the maximum time period(s)
in which such callers may call the person. IMC Comments at 3. We also decline to limit how many times one seller
can call a consumer, as the issue is outside the scope of this proceeding. Drip Comments at 3-4 (proposing five calls
in 24 hours from one company).
79
See infra para. 38, (noting that "the website may offer a consumer a check box list that allows the consumer to
choose each individual caller that they wish to hear from”).
80
Our rules also require that the written consent agreement “include a clear and conspicuous disclosure” providing
certain information to the person signing, 47 CFR § 64.1200(f)(9), an additional requirement website publishers
must follow.
81
47 CFR § 64.2401(e). We use the same definition for junk fax opt-out notice requirements. See Rules and
Regulations Implementing the Telecommunications Consumer Protection Act of 1991, Junk Fax Prevention Act of
2005, CG Docket 02-278, Report and Order and Third Order on Reconsideration, 21 FCC Rcd 3787, 3801, para. 26
(2006) (Consistent with the definition in our truth-in-billing rules, “clear and conspicuous” for purposes of the opt-
out notice means a notice that would be apparent to a reasonable consumer.).
82
Pub. L. No. 106-229, 114 Stat. 464 (2000) (codified at 15 U.S.C. §§ 7001-7006). The E-Sign Act establishes
rules for satisfying a requirement for a writing or a signature with their electronic equivalents. Joint Consumer
Commenters Reply at 5-7 (observing that the rules of the federal E-Sign Act apply whenever agreements consenting
to telemarketing calls are entered into online); Aug. 7 Congressional at 1 (“Although telemarketers routinely ignore
the requirements of the E-Sign Act, the legislation’s mandate for E-Sign consent before writings can be provided in
electronic records in 15 U.S.C. § 7001(c) is fully applicable.”).
83
See, e.g., Joint Consumer Commenters at 31-32 & Reply at 5-7; State Attorneys General Reply at 14-15. In the
2012 TCPA Order, the Commission concluded that consent obtained in compliance with the E-Sign Act will satisfy
the requirements of our rule, including permission obtained via an email, web site website form, text message,
telephone keypress, or voice recording. 2012 TCPA Order, 27 FCC Rcd at 1844, para. 34. Although we are
amending our prior express written consent TCPA rule here, we continue to find that compliance with the federal E-
Sign Act will satisfy the requirements of our revised rule.
84
Text Blocking Order and Further Notice at para. 61.
Federal Communications Commission FCC-CIRC2312-02
15
who argue that consumers deserve protection against calls that go beyond the scope of consent, a scope
that can be reasonably inferred from the purpose of the website at which they gave that consent.
85
We
believe that texters and callers are capable of implementing this standard and, when in doubt, will err on
the side of limiting that content to what consumers would clearly expect. As a result, we decline to adopt
a definition of “logically and topically” at this time as some commenters suggest.
86
36. Preserving Comparison Shopping Websites and Ease of Compliance. Our new rule
protects consumers while preserving the ability of comparison shopping websites to provide consumers
with comparison shopping opportunities.Such websites are useful both to consumers, who are seeking
specific goods and services, and businesses, including small businesses seeking new customers.
87
37. Websites, including comparison shopping websites, can use a variety of means for
collecting one-to-one consent for multiple sellers to comply with our rule. For instance, the website may
offer a consumer a check box list that allows the consumer to specifically choose each individual seller
that they wish to hear from.
88
Alternatively, the comparison shopping website may offer the consumer a
clickthrough link to a specific business so that the business itself may gather express written consent from
the consumer directly. Our rule does not prohibit comparison shopping websites from obtaining leads
through valid consent and provides multiple opportunities for responsible comparison shopping websites
to obtain leads for potential callers.
38. The rule we adopt today best balances the needs of businesses to utilize lead generation
services to make calls to potential buyers with protecting consumers from a deluge of unwanted robocalls
and robotexts. We thus disagree with those commenters who argue that this rule unduly harms business,
including small businesses.
89
First, our rules already require that callers and texters obtain valid consent.
90
The rule we adopt today helps callers and texters, including small businesses, by providing legal certainty
as to how to meet their burden of proof when they have obtained consent via a third party. Our rule does
not prevent small business from obtaining leads from third party comparison shopping websites or from
making calls pursuant to those leads. They may continue to do so as long as they can clearly demonstrate
that they have obtained consent consistent with the rules we adopt today.
39. Further, callers and texters may avail themselves of other options for providing
comparison shopping information to consumers, e.g., manually dialed or non-prerecorded or artificial
voice calls or texts, email, or information displayed directly on the third party website. We find that the
rule we adopt today provides the best balance between protecting consumers from unwanted and illegal
calls and the need for small businesses to use leads generated by third parties to sell their goods and
services. Indeed, small businesses themselves may utilize comparison shopping services when
comparison shopping for business services and our rule protects these businesses from having their own
85
See, e.g., USTelecom Comments at 5; VON Comments at 7-8; Chandler Comments at 1; QuinStreet Comments at
7; Letter from Lucas Bell, Director, Government Relations, Zillow Group, to Marlene H. Dortch, Secretary, Federal
Communications Commission (Oct. 27, 2023) at 3 (Zillow ex parte).
86
See, e.g., UHC Comments at 4; PACE Comments at 5; Bankers Joint Commenters Reply at 13-16.
87
See, e.g., OLA Comments at 3 (observing that small-dollar lead generators often connect underserved consumers
with credit providers willing to quickly help solve the needs of the credit challenged); REACH Comments at 4 (lead
generators can be “an engine that drives a huge number of small and independent companies that do not have their
own robust marketing team”).
88
Joint Consumer Commenters Reply at 13; State Attorneys General Reply at 17.
89
See, e.g., OLA Comments at 3-4; REACH Comments at 4-5; SolarReviews Comments at 4; Letter from Eric J.
Troutman, counsel for EXP Realty, to Marlene H. Dortch, Secretary, Federal Communications Commission at 1-2
(Nov. 16, 2023) (EXP Realty ex parte).
90
2015 TCPA Declaratory Ruling and Order, 30 FCC Rcd at 7989-7993, paras. 47-54.
Federal Communications Commission FCC-CIRC2312-02
16
phones inundated with unwanted calls and texts.
40. While we find that our rule does not unduly burden callers or comparison shopping
websites, we nonetheless give texters and callers, and any third party websites they obtain consent
through, a six-month implementation period to make the necessary changes to ensure consent complies
with our new requirement.
91
This implementation period should provide both lead generators and the
callers that rely on the leads they generate ample time to implement our new requirements.
41. Burden of Proof for Valid Consent. We take this opportunity to reiterate that the burden
is on the texter or caller to prove that they have consent that satisfies the TCPA and our rules.
92
They may
not, for example, rely on comparison websites or other types of lead generators to retain proof of consent
for calls the seller makes. And, in all cases, the consent must be from the consumer. “Fake leads” that
fabricate consumer consent do not satisfy the TCPA or our rules.
93
In addition, the consumer’s consent is
not transferrable or subject to sale to another caller because it must be given by the consumer to the
seller.
94
42. Relationship to ACA Declaratory Ruling. We find that the rule we adopt today does not
upset the precedent established in our ACA Declaratory Ruling. In the ACA Declaratory Ruling, the
Commission determined that “the provision of a cell phone number to a creditor . . . reasonably evidences
prior express consent by the cell phone subscriber to be contacted at that number regarding the debt.”
95
The Commission emphasized that such consent would be deemed granted “only if the wireless number
was provided by the consumer to the creditor, and that such number was provided during the transaction
that resulted in the debt owed.”
96
43. Further, the Commission concluded that the creditor would be responsible for
demonstrating that the consumer had provided consent because the “creditors are in the best position to
have records kept in the usual course of business showing such consent, such as purchase agreements,
sales slips, and credit applications.”
97
Therefore, “[c]alls placed by a third party collector on behalf of that
creditor are treated as if the creditor itself placed the call.”
98
In other words, the ACA Declaratory Ruling
concerned calls regarding a specific transaction for which calls would be related solely to that specific
transaction. The Commission determined that calls made on behalf of the creditor would be treated as if
they were placed by the creditor itself because the creditor would have kept the best records of consent
91
This period for implementation will be six months following Federal Register publication of this Report and Order
or 30 days after announcement in the Federal Register of the Paperwork Reduction Act approval of the information
collection in this new rule, whichever is later. The Consumer and Governmental Affairs Bureau will announce the
effective date for section 64.1200(f)(9) by Public Notice.
92
2015 TCPA Declaratory Ruling and Order, 30 FCC Rcd at 7989-7990, para. 47.
93
See, e.g., Dobronski Comments at 3-10; Joint Consumer Commenters at 2-6 & Reply at 7-12; State Attorneys
General Reply at 2-5: USTelecom Comments at 2; Letter from David Frankel, ZipDX, to Marlene H. Dortch,
Secretary, Federal Communications Commission, at 10-11 (May 15, 2023) (ZipDX ex parte).
94
Section 64.1200(f)(9) provides that prior express written consent for a call or text message must be directly to one
individual seller at a time. Consumer consent to be contacted by one seller is not consent to be contacted by another
seller who purchased the lead from the first seller.
95
Rules and Regulations Implementing the Telephone Consumer Protection Act Of 1991, Request of ACA
International for Clarification and Declaratory Ruling, Declaratory Ruling, 23 FCC Rcd 559, 564, para. 9 (2008)
(ACA Declaratory Ruling).
96
Id. at 564-65, para. 10.
97
Id. at 565, para. 10.
98
Id.
Federal Communications Commission FCC-CIRC2312-02
17
related to that specific transaction.
44. By contrast, the rule we adopt today for prior express written consent concerns the precursor
to a transaction. That is, the lead generator is not otherwise engaged in business with the consumer for
which another entity is calling on behalf of the lead generator. Rather, the lead generator is merely
facilitating consent for another business to engage in marketing of a potential future specific transaction
with the called party. Because the calling party has not engaged in a specific transaction on which to base
its consent, we find that our rule—and specifically, placing the burden on the caller—is consistent with
the ACA Declaratory Ruling as well as other Commission precedent.
99
E. Text Message Authentication and Spoofing
45. We decline to adopt at this time caller ID authentication requirements for text. We agree
with commenters that number spoofing in the SMS/MMS domain is rare at this time and that providers
that originate texts generally permit their customers to initiate those texts only from numbers for which
they are the assignee.
100
46. In addition, several commenters observe that the wireless industry is evaluating
authentication technologies that could address text-specific issues. For example, there is active work by
the Internet Engineering Task Force on text authentication standards, and ATIS’s IP-NNI Task Force is
exploring whether technical standards that work to enhance existing mitigations should be pursued.
101
For
these reasons, we decline to adopt caller ID authentication requirements for text messages. We seek
further comment below on the issues of number spoofing and new technical standards for caller ID
authentication.
F. Summary of Benefits and Costs
47. Our conservative estimate of the total loss from unwanted and illegal texts is $16.5
billion annually, which reflects both a substantial increase in the number of spam texts in recent years (the
nuisance cost), and an increase in financial losses due to text scams. We continue to estimate the
nuisance cost of spam texts to be 5 cents per text.
102
This cost is multiplied by 225.7 billion spam texts
sent annually
103
and the result is $11.3 billion in total nuisance cost. In addition, we estimate financial
losses due to text scams to be $5.2 billion. This figure is based on the $2 billion financial loss figure
estimated previously,
104
scaled up to reflect the increased volume of spam texts.
105
Our estimate is
99
See, e.g., GroupMe, Inc./Skype Communications S.A.R.L Petition For Expedited Declaratory Ruling, Rules and
Regulations Implementing the Telephone Consumer Protection Act Of 1991, CG Docket No. 02-278, Declaratory
Ruling, 29 FCC Rcd 3442, 3446, para. 11 (2014) (finding that, while consent may be obtained and conveyed
through an intermediary, the caller remains liable for initiating or making autodialed text messages to wireless
numbers in the event consent was not actually obtained).
100
See, e.g., CTIA Comments at 12-15; ECAC Comments at 6; M
3
AAWG Comments at 5; NetNumber Comments
at 7; ZipDX Comments at 1; CTIA Reply at 7-9; T-Mobile Reply at 5-6 (explaining that message sender
authentication is already happening and the Commission does not need to mandate a technology solution); Twilio
Reply at 7-8.
101
See, e.g., INCOMPAS Comments at 5; CTIA Reply at 8-9; T-Mobile Reply at 6.
102
Text Blocking Order and Further Notice at para. 45.
103
Robokiller 2022 Report at 5.
104
Text Blocking Order and Further Notice at para. 45.
105
The number of spam texts was estimated to be 86 billion when the Commission first estimated the financial harm
of text scams to be $2 billion. Targeting and Eliminating Unlawful Text Messages, CG Docket No. 21-402, Notice of
Proposed Rulemaking, 37 FCC Rcd 11618, 11632, at paras. 43-44 (2022) (Text Blocking NPRM). The Robokiller
2022 Report states that the number of spam texts has increased to 225.7 billion, as of 2022, an amount 2.62 times the
original amount. Robokiller 2022 Report at 5.
Federal Communications Commission FCC-CIRC2312-02
18
conservative; for example, Robokiller estimates the financial losses from text scams alone to be
approximately $20 billion in 2022, and this figure does not include the nuisance costs of spam texts.
106
Further, the total loss from unwanted and illegal calls is relevant for our consideration of the benefit
generated by closing the lead generator loophole. We reiterate the harm of unwanted and illegal calls to
be at least $13.5 billion annually.
107
We note that this is also a conservative estimate; for example,
Robokiller estimates the financial losses due to robocall scams to be $33 billion for the first half of
2023.
108
48. We expect the actions we take today will impose minimal costs on mobile wireless
providers and comparative shopping websites. Nothing in the record demonstrates that requiring
terminating providers to block texts when notified by the Commission of suspected illegal texts would
impose significant costs on mobile wireless providers. Further, we expect that terminating providers aim
to minimize texts that subject their customers to nuisance and receiving notifications from the
Commission would assist in that effort and help providers improve customer satisfaction. With respect to
our action codifying that text messages are covered by the National DNC Registry’s protections, we see
no additional cost to providers.
49. We also see very little cost to providers as a result of our encouragement to make email-
to-text an opt-in service. Providers who do not take up this option will incur no additional cost and, for
those providers who do so, we assume that the benefits of making email-to-text an opt-in service, e.g.,
more satisfied customers, outweighs the costs of setting up an opt-in program and marketing it to their
subscribers. Similarly, we believe closing the lead generator loophole so that prior express written
consent can only be given directly from a consumer to a single seller-caller at a time will result in only
small additional costs for comparative shopping websites. Such practices should lead to greater customer
satisfaction that may benefit such websites.
50. Based on the analysis of the anticipated benefits and costs discussed above, we believe
the benefits of the rules adopted in this Report and Order significantly outweigh their costs. Even if these
rules eliminate only a small share of unwanted and illegal texts and calls, the benefits would be
substantial, given the magnitude of the likely losses from such texts and calls.
G. Legal Authority
51. We rely on the TCPA to adopt rules applicable to mobile wireless text messaging
providers,
109
including our blocking requirement. First, the TCPA gives the Commission authority over
the unsolicited text messages within the scope of this order.
110
The TCPA, in relevant part, restricts
certain autodialed calls to wireless telephone numbers absent the prior express consent of the called
party.
111
The Commission has found that, for the purposes of the TCPA, texts are included in the term
“call.”
112
Because the Commission has authority to regulate certain text messages under the TCPA,
106
Robokiller 2022 Report at 4.
107
First Caller ID Authentication Order, 35 FCC Rcd at 3263, paras. 47-48.
108
Robokiller 2023 Report at 9.
109
CTIA specifically supported use of the TCPA, as well as the Truth-in-Caller ID Act for this purpose. CTIA
Comments at 11-12.
110
The Commission stated in the 2003 TCPA Order that the authority to regulate telemarketing derives from the
TCPA. 2003 TCPA Order, 18 FCC Rcd at 14070, para. 95. The Commission also observed that Congress
anticipated “that the FCC, under its TCPA rulemaking authority, might need to consider changes in technologies.”
Id. at 14092, para. 132.
111
47 U.S.C. § 227(b)(1)(A).
112
2003 TCPA Order, 18 FCC Rcd at 14115, para. 165.
Federal Communications Commission FCC-CIRC2312-02
19
particularly messages sent using an autodialer and without the consent of the called party, we have legal
authority to require providers to block text messages violate the TCPA. The TCPA also provides
authority for our consent requirements and our codification that text messages are covered by the National
DNC Registry.
113
52. We therefore disagree with RILA that we do not have the legal authority to expand the
DNC restrictions to text messages because Congress did not include text messages in the statute and no
appellate court has construed the National DNC Registry’s restrictions to include text messages.
114
The
DNC restrictions have long applied to wireless phones
115
and the Commission and courts have long held
that text messages are calls under the TCPA.
116
Further, we are codifying that text messages are included
in the National DNC Registry’s protections—a position that the Commission and several courts have
previously taken
117
—we are not expanding the National DNC Registry’s restrictions.
53. To the extent that the Commission may direct providers to block texts where an
autodialer has not been used, we further find authority under section 251(e) of the Communications Act.
Section 251(e) provides us independent jurisdiction to prevent the abuse of NANP resources, regardless
of the classification of text messaging.
118
Requiring blocking of a particular number that has sent known
illegal texts ensures that entities sending illegal texts cannot continue to abuse NANP resources to further
their illegal schemes. We therefore disagree with CTIA, which has argued that reliance on section 251(e)
“would raise unnecessary questions about the scope of the Commission’s authority, given that text
messaging is an information service.”
119
This is consistent with our approach in calling, where we have
found that our authority under this section does not hinge on whether a voice service provider is a
common carrier.
120
54. We also find that we have authority under Title III of the Act to adopt these measures.
Title III “endow[s] the Commission with ‘expansive powers’ and a ‘comprehensive mandate to
“encourage the larger and more effective use of radio in the public interest.”’
121
Section 303 of the Act
grants the Commission authority to establish operational obligations for licensees that further the goals
and requirements of the Act if such obligations are necessary for the “public convenience, interest, or
113
47 U.S.C. § 227(c) (granting the Commission rulemaking authority to protect residential telephone subscribers’
privacy rights).
114
RILA Reply at 5-8.
115
See 47 CFR § 64.1200(e); 2003 TCPA Order, 18 FCC Rcd at 14115-16, paras. 165-66.
116
2003 TCPA Order, 18 FCC Rcd at 14115, para. 165; Campbell-Ewald Co. v. Gomez, 577 U.S. 153, 156 (2016)
(“A text message to a cellular telephone, it is undisputed, qualifies as a ‘call’ within the compass of §
227(b)(1)(A)(iii).”); Satterfield v. Simon & Schuster, Inc., 569 F.3d 946, 952 (9th Cir. 2009) (“[W]e hold that a text
message is a ‘call’ within the meaning of the TCPA.”).
117
See, e.g., Hernandez, 33 FCC Rcd at 12386, para. 10; Barton, 525 F. Supp.3d 195; Mantha, 2022 WL 325722;
Visco v. Creditors Relief, LLC, No. 20-cv-12303-DJC, 2022 WL 488495 (D. Mass. Feb. 17, 2022); Eagle v. GVG
Capital, LLC, No. 22-cv-00638-SRB, 2023 WL 1415615 (W.D. Mo. Jan. 31, 2023); Pariseau v. Built USA, LLC,
619 F. Supp.3d 1203 (M.D. Fla. 2022); Sagar, 2021 WL 5567408; Hall, 72 F.4th at 986.
118
See May 2023 Call Blocking Order at para. 66. There, the Commission noted that “this particularly applies
where callers spoof caller ID for fraudulent purposes and therefore exploit numbering resources” but did no limit is
scope to cases where spoofing is a factor. Id.
119
CTIA Comments at n. 37
120
See, e.g., May 2023 Call Blocking Order at para. 66.
121
Cellco Partnership v. FCC, 700 F.3d 534, 542 (D.C. Cir. 2012) (Cellco Partnership) (upholding the
Commission's authority under Title III to adopt data roaming rules) (quoting Nat’l Broad. Co. v. United States, 319
U.S. 190, 219 (1943) (Nat’l Broad Co.) (quoting 47 U.S.C. § 303(g)).
Federal Communications Commission FCC-CIRC2312-02
20
necessity” and are not inconsistent with other provisions of law.
122
In particular, section 303(b) authorizes
the Commission to “[p]rescribe the nature of the service to be rendered by each class of licensed stations
and each station within each class,” and that is what our notice requirement and blocking rule addresses
here.
123
In addition, sections 307 and 316 of the Act allow the Commission to authorize the issuance of
licenses or adopt new conditions on existing licenses if such actions will promote public interest,
convenience, and necessity.
124
We find the requirements we adopt for mobile wireless providers after
they are on notice of suspected illegal text messages are necessary to protect the public from illegal text
messages and that such a requirement is in the public interest.
55. Because we find that the sources of authority identified above provide sufficient authority
for the rules we adopt today, we find it unnecessary to address other possible sources of authority to adopt
these rules.
IV. SECOND FURTHER NOTICE OF PROPOSED RULEMAKING
56. Because bad actors continue to evolve in their methods of defrauding consumers, in this
Second Further Notice of Proposed Rulemaking, we seek comment on a number of additional steps to
better protect consumers from unwanted and illegal texts. First, we seek comment on additional blocking
requirements and related approaches. Second, we seek further comment on text message authentication.
Finally, we seek comment on whether to make email-to-text an opt-in service.
A. Text Blocking
57. We propose and seek comment on additional text blocking options to better protect
consumers from illegal texts. Specifically, we first propose and seek comment on extending the text
blocking requirement we adopt in the Report and Order
125
to include originating providers, and to require
all immediate downstream providers to block the texts from providers that fail to block after Commission
notification. We also seek additional comment on whether to require this blocking to be based on
number, source, the “substantially similar” traffic standard,
126
or some other standard. Next we seek
comment on requiring providers to block texts based on content-neutral reasonable analytics. Third, we
seek comment on traceback for text messaging, including whether to adopt a traceback response
requirement for text messaging. Fourth, we seek comment on any other rules we could adopt to
effectively protect consumers from illegal texts. Finally, we seek comment on any additional protections
that may be necessary in case of erroneous blocking.
1. Expanding the Mandatory Text Blocking Requirement to Originating
Providers and Adding a Downstream Provider Blocking Requirement
58. Requiring Originating Provider Blocking. We propose and seek comment on extending
the requirement to block following Commission notification of illegal texts to other providers generally,
122
47 U.S.C. § 303.
123
See Cellco Partnership, 700 F.3d at 543 (“Like other rules that govern Title III services, the data roaming rule
merely defines the form mobile-internet service must take for those who seek a license to offer it.”). We find
several other provisions of Section 303 relevant here. See 47 U.S.C. § 303(g) (requiring the Commission to
“encourage the larger and more effective use of radio in the public interest”); id. § 303(r) (authorizing the
Commission to “[m]ake such rules and regulations and prescribe such restrictions and conditions, not inconsistent
with law, as may be necessary to carry out the provisions of this Act”).
124
See 47 U.S.C. §§ 307, 316; see also Cellco Partnership, 700 F.3d at 543 (recognizing section 316 as additional
Title III authority for our data roaming rules).
125
See 47 CFR § 64.1200(s); supra paras. 16-24.
126
47 CFR § 64.1200(n)(5), (n)(6); see also Gateway Provider Order and Further Notice, 37 FCC Rcd at 6897-
6901, paras. 74-86; May 2023 Call Blocking Order, at paras. 29-48 (effective Jan. 8, 2024).
Federal Communications Commission FCC-CIRC2312-02
21
and originating providers specifically. We believe that originating providers are similar to gateway or
originating voice service providers in that they are the first U.S.-based provider in the text path and that
applying an analogous rule to originating providers could help ensure that these providers are properly
incentivized to stop illegal texts even before we send any notice. We seek comment on this view.
59. We seek comment on whether and, if so, how to define originating providers here. Is the
originating provider the first provider in the text path, and therefore in a similar position to a gateway or
originating voice service provider? Are there other providers in the path that are more similar to a
gateway provider? Alternatively, should we apply these rules to some other entity in the chain to better
protect consumers? The call blocking rules help hold bad-actor voice service providers responsible for
the calls they allow onto the network by denying those voice service providers access to the network
entirely when they have demonstrated noncompliance. Is there a particular type of entity in the texting
ecosystem that is more likely to either intentionally or negligently shield those sending illegal texts?
60. Blocking Standard. We propose to require originating providers to block all texts from a
particular source following Commission notification. We seek comment on this proposal. Is this an
appropriate standard for blocking? How might originating providers determine the source of a particular
text or texts in order to comply with this rule? Alternatively, should we require blocking based on the
number or numbers, as we do for terminating providers in the Report and Order?
127
If so, how effective is
such a requirement? If not, should we also change the standard for terminating providers to match the
standard for originating providers, or do originating providers have access to more information, making a
broader requirement to block based on source appropriate?
61. Should we limit the length of time for which blocking is required? If so, how long should
we require providers to block? Alternatively, should we require originating and/or terminating providers
to block using the “substantially similar” standard applied in our call blocking rules?
128
We believe that
texting may present concerns unique from calling that justify a different standard, or require additional
guidance for compliance. For example, while a voice service provider will not have the content of a
particular call prior to that call reaching the recipient, a texting provider likely does have access to this
information. Given that, should we require that blocking be content as well as competitively-neutral?
Are there any other standards we should consider?
62. Blocking Process. We seek comment on whether the process for voice service providers
should be applied here to texting. Our current rules for call blocking lay out a detailed process that must
be followed before requiring all immediate downstream providers to block all of an identified voice
service provider’s traffic.
129
Is this process appropriate for the texting environment, or are the differences
between texting and calling that justify modifications? Several commenters expressed concerns about the
delays inherent in this process.
130
While the process works well for calling,
131
delays may have different
consequences in the texting context.
63. Is a delay particularly significant when dealing with texts compared to calls? Why or
why not? If so, are there changes we could make to address this issue while still ensuring that providers
are afforded sufficient due process? For example, should we continue to allow 14 days for the originating
127
Supra paras. 16-24.
128
See 47 CFR § 64.1200(n)(5), (n)(6).
129
These steps include a Notification of Suspected Illegal Traffic, time for the provider to investigate and respond,
and an Initial Determination Order with additional time to respond before the Enforcement Bureau may adopt a
Final Determination Order requiring all immediate downstream providers to block. 47 CFR § 64.1200(n)(5)-(6).
130
See, e.g., M
3
AAWG Comments at 4; NetNumber Comments at 4-6 & Reply at 2-3; T-Mobile Reply at 3-4.
131
See, e.g., One Eye; see also Urth Access, Sumco Forfeiture Order.
Federal Communications Commission FCC-CIRC2312-02
22
provider to investigate and respond following the Notification of Suspected Illegal Texts or, as we did for
the terminating provider rule we adopt in the Report and Order, should we change that time frame?
Should we establish a different docket for text blocking Orders, or use the same docket used for call
blocking?
2. Requiring Blocking of Texts Based on Reasonable Analytics
64. We seek comment on requiring or incentivizing providers to block texts based on
reasonable analytics. Our call blocking rules provide a safe harbor for the blocking of unwanted calls
based on reasonable analytics on an opt-out basis.
132
In addition, our call blocking rules provide a safe
harbor for the blocking of calls without consumers’ consent and calls that are highly likely to be illegal
based on reasonable analytics.
133
In both cases, we require that analytics are applied in a non-
discriminatory, competitively neutral manner.
134
The Commission also recently sought comment on
requiring terminating voice service providers to offer opt-out blocking services for calls that are highly
likely to be illegal.
135
We have not yet addressed text blocking based on reasonable analytics.
65. Blocking Standard. We seek comment on whether and how to define reasonable
analytics for this purpose. The record indicates that many providers already make use of analytics or
other techniques to block illegal texts.
136
What analytics do providers use to identify unwanted or illegal
texts? If providers are reluctant to share specifics to avoid tipping off bad actors we seek comment on
broad criteria that providers may use. For example, a call-blocking program might block calls based on a
combination of factors, such as: large bursts of calls in a short timeframe, low average call duration, low
call completion ratios, invalid numbers placing a large volume of calls, etc.
137
66. We seek comment on whether, and to what extent, providers use volumetric triggers to
identify bad traffic. Do any of the call-blocking reasonable analytics factors apply to text and, if so,
which ones? Are there other content-neutral factors that are more likely to indicate that a text is illegal
that do not apply in the calling context? If we adopt such a rule, are there any necessary modifications we
should make to accommodate small businesses? As we noted above, the content of a text is available to
the provider at the time that blocking occurs, which is not generally true for calls.
138
If we require
providers to block based on reasonable analytics, should we therefore require that these analytics be
content-neutral? Should we also require that the blocking be non-discriminatory and competitively
neutral? Alternatively, are there ways we could encourage this blocking without requiring it? Are there
any other issues we should consider?
67. Safe Harbor. Because texting is currently classified as an information service, we do not
believe that providers need safe harbor protections to engage in this type of blocking. We seek comment
on this belief. Do providers risk liability when they block erroneously? If so, what can we do to reduce
that risk while still ensuring that wanted, lawful texts reach consumers?
132
47 CFR § 64.1200(k)(3).
133
47 CFR § 64.1200(k)(11).
134
See 47 CFR § 64.1200(k)(3)(iv), (k)(11)(v).
135
May 2023 Call Blocking Order, at paras. 71-75.
136
See, e.g., CTIA Comments at 7-8; M
3
AAWG Comments at 4; NetNumber Reply at 3; Twilio Reply at 3-6. CTIA
explains that considerations involved in investigating and blocking potentially illegal messages are different from
those involved in imposing similar obligations on international gateway voice providers, for a variety of reasons,
including the ever-evolving tactics used by bad actors to send spam text messages (e.g., brand impersonation, SIM
boxes, snowshoe messaging, etc.). CTIA Comments at 10.
137
See 2019 Call Blocking Declaratory Ruling, 34 FCC Rcd at 4888, para. 35.
138
See supra para. 60.
Federal Communications Commission FCC-CIRC2312-02
23
3. Alternative Approaches
68. We seek comment on alternative blocking or mitigation rules we could adopt to target
unwanted and illegal texts and better protect consumers. Are there approaches we have not considered
here that would stop illegal texts and protect consumers? What can the Commission do to encourage or
require providers to adopt these approaches? For example, can the Commission take steps to encourage
information sharing between providers?
4. Protections Against Erroneous Blocking
69. If we adopt additional text blocking requirements, should we also adopt additional
protections against erroneous text blocking? Our rules already require providers to provide a point of
contact for blocking issues.
139
Considering that providers can and do block texts, is this sufficient, or are
other protections necessary? If so, what protections should we adopt? For example, should we do as one
commenter suggests and create a white list for “legitimate research organizations and/or research
campaigns”
140
or other entities, or would doing so raise legal or policy concerns? Similarly, should we
require some form of notification when texts are blocked,
141
similar to our requirement when calls are
blocked based on reasonable analytics? If so, how can providers send a notification technically? Should
we require notification only to certain categories of blocking? Or, should we, as one commenter suggests,
require providers to give “advance notice when a number is flagged as suspicious and may be blocked”
along with several other protections?
142
What are the risks and benefits of each approach?
B. Text Message Authentication
70. We seek additional comment on text message authentication and spoofing. We have so
far declined to adopt authentication requirements for texting.
143
The record thus far is mixed on the
feasibility of such a requirement, with commenters noting that the STIR/SHAKEN caller ID
authentication system is designed to work only on IP networks.
144
Further, the record indicates that
number spoofing is comparatively rare in SMS and MMS.
145
71. We believe it is important to continue to build a record on these issues and ensure that we
are aware of any new developments or concerns. We therefore seek further comment on the need for and
feasibility of text authentication. In particular, commenters should address whether number spoofing is
an issue in text messaging and, if so, the extent of the problem. If number spoofing is uncommon, are
there steps we can take to ensure that it remains the exception rather than the rule? Do bad actors use
other spoofing techniques, such as identity spoofing? If so, what can we do to address this problem?
Commenters should also discuss any new or in-process technical standards for authentication in text
messaging, including their current status and any timelines for development. What issues will these new
tools address? If the new technical standards are designed to prevent number spoofing, is this evidence of
139
47 CFR § 64.1200(r).
140
AAPOR Comments at 3-5.
141
See, e.g., CCA Comments at 5; INCOMPAS Comments at 4; RMAI Comments at 3; Bankers Joint Commenters
Reply at 12-13.
142
RMAI Comments at 3.
143
See Text Blocking Order and Further Notice, at para. 37; supra paras. 44-45.
144
Text Blocking Order and Further Notice at para. 37 & note 107.
145
See, e.g., ECAC Comments at 6; M
3
AAWG Comments at 5; NetNumber Reply at 6-8; ZipDX Comments at 1;
Twilio Reply at 7-8.
Federal Communications Commission FCC-CIRC2312-02
24
a more significant spoofing issue than commenters
146
acknowledged in response to the Further Notice? If
so, should the Commission act more quickly in this area, rather than waiting for the standards bodies to
finish their work?
72. We seek comment on whether we should require industry to regularly update us with its
progress on text authentication. We believe doing so would ensure that we have the most up-to-date
information available without having to adopt further Notices of Proposed Rulemaking covering this
topic. Is this belief correct? If so, how often should we require industry to update us and how should we
determine when further updates are no longer required? For example, should we set a six-month cycle for
updates over the next two years? Or should we require some other update cycle and endpoint?
C. Traceback
73. Traceback has been a key part of our strategy for combating illegal calls.
147
We seek
comment on whether we should require a response to traceback requests for texting. We seek comment
on requiring providers to respond to traceback requests from the Commission, civil or criminal law
enforcement within 24 hours, consistent with our existing rule for gateway voice service providers and
our recently adopted rule for all voice service providers that will take effect in January 8, 2024.
148
Should
we also include the industry traceback consortium as an entity authorized to conduct traceback of texts, or
is there some other entity that should be included? Is traceback for texting similar enough to traceback
for calls for such a requirement to be effective? Are there any changes we should make to the rule to
ensure that traceback works for texts? How should we handle aggregators and cloud platforms? Are
there other issues we should consider in adopting a traceback requirement?
74. We seek comment on the specifics of the traceback process for texts, as well as any
obstacles to industry-led traceback efforts that may work alongside or in place of rules we may establish.
Are tracebacks typically conducted for texting? If so, what does the process look like? Are there types of
providers that are routinely reluctant to respond to these requests? Is information from traceback
processes shared and then incorporated into blocking decisions? Are there network modifications,
standards, or changes to software or hardware that would enable efficient texting traceback? If we adopt a
traceback requirement for texting, are there any necessary modifications we should make to accommodate
small business? Is there anything else we should know about traceback for texting?
D. E-Mail-To-Text
75. In the Order, we encourage providers to make email-to-text an opt in service. We now
propose to require providers to do so, so that subscribers wishing to receive these types of messages
would first have to opt in to the service.
149
Would such a rule reduce the quantity of fraudulent text
messages consumers receive? Does the anonymity of email-to-text make it more attractive to fraudulent
texters? Commenters should discuss any drawbacks to requiring providers to block such messages if the
consumer has not opted in to such service. For example, would this result in blocking important or urgent
messages? If so, how could we reduce this risk? Are there alternatives to making this service opt in that
146
Such commenters argue that number spoofing in the text message domain is comparatively rare. See, e.g.,
ZipDX Comments at 1-2; CTIA Comments at 12-14 & Reply at 7-8; M
3
AAWG Comments at 5; ECAC Comments
at 6; NetNumber Comments at 7; Twilio Reply at 7-8.
147
47 CFR § 64.1200(n)(1).
148
Id.
149
Commenters state that the email-to-text messages process allows the sender to be anonymous because the text is
sent from an email account on a computer, not a phone number. ZipDX Comments at 2; Somos Reply at 5
(observing a spike in text impersonation scams originating from email-to-text gateways, which permit a message to
appear as sent from someone else’s number or from an email address, and stating they are an increasingly popular
method for scammers to impersonate brands using the text messaging channel).
Federal Communications Commission FCC-CIRC2312-02
25
would have a similar effect? If so, what are they and how would they compare? Commenters should
discuss how we should define “email-to-text service.” Are there analogous services that should be
covered, e,g., voicemail-to-text? We seek comment on the details of any opt-in requirement and if the
opt-in should be in writing. Must it be stand-alone and conspicuous? Will providers have the burden of
demonstrating opt-in decisions? Are there any other issues we should consider in adopting a rule?
E. Benefits and Costs
76. We estimate that the total harm of unwanted and illegal texts is at least $16.5 billion. As
discussed in the Order,
150
Robokiller estimates that Americans received 225.7 billion spam texts in
2022.
151
Assuming a nuisance harm of 5 cents per spam text, we estimate total nuisance harm to be $11.3
billion (i.e., 5 cents multiplied by 225.7 billion spam texts). Further, we estimate that an additional $5.3
billion of harm occurs annually due to fraud. Previously, we estimated the harm due to fraud from scam
texts at $2 billion.
152
In the Order, we revised this figure upward in proportion with the increase in spam
texts, resulting in an estimate of $5.3 billion.
153
We believe this estimate is conservative, given that
Robokiller estimates financial losses due to fraud through text messaging to be $20 billion, and this figure
does not include the nuisance costs of spam texts.
154
We seek comment on these estimates of harm and on
the costs of the proposals to reduce the harm of unwanted and illegal texts outlined in this FNPRM. The
Commission will analyze any detailed cost data received in comments.
F. Digital Equity and Inclusion
77. The Commission, as part of its continuing effort to advance digital equity for all,
155
including people of color and others who have been historically underserved, marginalized, and adversely
affected by persistent poverty and inequality, invites comment on any equity-related considerations
156
and
benefits (if any) that may be associated with the proposals and issues discussed herein. Specifically, we
seek comment on how our proposals may promote or inhibit advances in diversity, equity, inclusion, and
accessibility.
G. Legal Authority
78. In the Second Further Notice of Proposed Rulemaking, we seek comment on several
150
See supra para. 46.
151
Robokiller 2022 Report at 5.
152
Text Blocking Order and Further Notice at para 43. See also Text Blocking NPRM , 37 FCC Rcd at 11632, para
44.
153
The volume of spam texts in 2022 (225.7 billion) was 2.62 times the previous annual amount (86 billion per
year). Our calculation scales up the $2 billion fraud harm by this factor, resulting in an estimated harm of $5.3
billion.
154
Robokiller 2022 Report at 4.
155
Section 1 of the Communications Act provides that the FCC “regulat[es] interstate and foreign commerce in
communication by wire and radio so as to make [such service] available, so far as possible, to all the people of the
United States, without discrimination on the basis of race, color, religion, national origin, or sex.” 47 U.S.C. § 151.
156
We define the term “equity” consistent with Executive Order 13985 as the consistent and systematic fair, just,
and impartial treatment of all individuals, including individuals who belong to underserved communities that have
been denied such treatment, such as Black, Latino, and Indigenous and Native American persons, Asian Americans
and Pacific Islanders and other persons of color; members of religious minorities; lesbian, gay, bisexual,
transgender, and queer (LGBTQ+) persons; persons with disabilities; persons who live in rural areas; and persons
otherwise adversely affected by persistent poverty or inequality. See Exec. Order No. 13985, 86 Fed. Reg. 7009,
Executive Order on Advancing Racial Equity and Support for Underserved Communities Through the Federal
Government (Jan. 20, 2021).
Federal Communications Commission FCC-CIRC2312-02
26
issues: (i) additional blocking requirements and related approaches to protect consumers from illegal
texts; (ii) text message authentication; and (iii) whether to make email-to-text an opt-in service. We seek
comment on our authority to adopt each of these three measures. The Commission has authority to
regulate certain text messages under the TCPA, particularly with regard to messages sent using an
autodialer and without the consent of the called party. We seek comment on whether we have legal
authority to adopt rules addressing these issues under the TCPA or the TRACED Act. For example, is
our TCPA jurisdiction sufficient to support our blocking proposals, and does the TRACED Act provide
us with additional authority to adopt these rules?
79. Similarly, does the TCPA grant us sufficient authority to adopt the rules we discuss
regarding requiring email-to-text to be an opt-out service? Commenters should also discuss whether we
have authority for our proposals under section 251(e) of the Act, which provides us “exclusive
jurisdiction over those portions of the North American Numbering Plan that pertain to the United
States,”
157
particularly to adopt any authentication, traceback, or blocking requirements. The Commission
found authority to implement STIR/SHAKEN for voice service providers under section 251(e) of the Act
in order to prevent the fraudulent exploitation of numbering resources.
158
Does section 251(e) of the Act
grant us authority to adopt implementation of authentication for text messages?
80. We seek comment on our authority under the Truth in Caller ID Act for these proposals.
The Commission found that it has authority under this statute to adopt a blocking requirement in the Text
Blocking Order and Further Notice.
159
The Commission also found authority under this provision to
mandate STIR/SHAKEN implementation, explaining that it was “necessary to enable voice service
providers to help prevent these unlawful acts and to protect voice service subscribers from scammers and
bad actors.”
160
We seek comment on whether that same reasoning applies here. We also seek comment
on whether we have authority for these proposals under Title III of the Act. Are there any other sources
of authority we could rely on to adopt any of the rules we discuss in this Second Further Notice of
Proposed Rulemaking?
V. WAIVER ORDER
81. We adopt a waiver, sua sponte, for a period of 12 months, to commence on the effective
date of section 64.1200(s) of the Commission’s rules, specifically to allow mobile wireless providers to
access the RND to determine whether a number has been permanently disconnected since the date of the
suspected illegal text described in the Notification of Suspected Illegal Texts. We delegate authority to
the Consumer and Governmental Affairs Bureau to extend the term of this waiver, if needed. The
Commission established the RND to allow callers to determine whether a telephone number has been
permanently disconnected after a date certain and therefore is no longer assigned to the party the caller
wants to reach.
161
The Commission’s rules require providers ensure the efficient use of telephone
numbers by reassigning a telephone number to a new consumer after it is disconnected by the previous
subscriber.
162
When a number is reassigned, callers may inadvertently reach the new consumer who now
has the reassigned number (and may not have consented to calls from the calling party). To mitigate
these occurrences, in the Reassigned Numbers Report and Order, the Commission established a single,
157
47 U.S.C. § 251(e).
158
STIR/SHAKEN Order, 35 FCC Rcd at 3260-61, para. 42.
159
Text Blocking Order and Further Notice, at para. 39.
160
STIR/SHAKEN Order, 35 FCC Rcd at 3262, para. 44.
161
See Advanced Methods to Target and Eliminate Unlawful Robocalls, CG Docket No. 17-59, Second Report and
Order, 33 FCC Rcd 12024, 12029, para. 11 (2018) (Reassigned Numbers Report and Order).
162
Id. at 12027, para. 5 (citing 47 CFR § 52.15); see 47 CFR § 52.15(f)(1)(ii) (addressing aging of numbers).
Federal Communications Commission FCC-CIRC2312-02
27
comprehensive database to contain reassigned number information from each provider that obtains North
American Numbering Plan (NANP) U.S. geographic numbers, which enables any caller to verify whether
a telephone number has been reassigned before calling that number.
163
82. We strongly encourage providers to determine whether a number has been reassigned in
order to avoid blocking lawful texts from a different source using the number. One way to make this
determination is through use of the RND. However, the use of the RND in this manner is outside of the
original scope of the RND and disallowed by the Reassigned Numbers Report and Order, which states
that the RND is “available only to callers who agree in writing that the caller (and any agent acting on
behalf of the caller) will use the database solely to determine whether a number has been permanently
disconnected since a date provided by the caller for the purpose of making lawful calls or sending lawful
texts.”
164
83. However, when it adopted the Reassigned Numbers Report and Order, the Commission
stated that it would address requests to access to the database for other lawful purposes through its waiver
process.
165
Under this process, the Commission may waive its rules for good cause shown.
166
Good cause
for a waiver may be found if special circumstances warrant a deviation from the general rule and such
deviation will serve the public interest.
167
We find that permitting providers to access the RND for the
purpose of determining if a number has been permanently disconnected after the date of a suspected
illegal text described in a Notification of Suspected Illegal Texts would prevent erroneous blocking of
text messages (if the number had been reassigned) and is good cause to grant this waiver, sua sponte. A
subsequent user of the number that had previously been used for suspected illegal texts should not be
subject to erroneous blocking, particularly as this can be avoided by such access to the RND, and this
consequent reduction in erroneous blocking would serve the public interest. We thus find good cause for
such a waiver, for accessing the RND for this purpose.
84. We therefore adopt a waiver, sua sponte, for a period of 12 months, to commence on the
effective date of section 64.1200(s) of the Commission’s rules, specifically for accessing the RND to
determine whether a number has been permanently disconnected since the date of the suspected illegal
text described in the Notification of Suspected Illegal Texts. Providers may access the RND for this
purpose in the same manner as they would to determine whether a number has been permanently
disconnected since a date provided by the caller for the purpose of making lawful calls or sending lawful
texts.
168
163
Reassigned Numbers Report and Order, 33 FCC Rcd at 12031, para. 19; see also id. at 12033-34, paras. 24-25.
164
Id. at 12034, para. 26.
165
See id. at n.68.
166
See 47 CFR § 1.3; Northeast Cellular Tel. Co. v. FCC, 897 F.2d 1164, 1166 (D.C. Cir. 1990). Our rules also
expressly provide that any rule may be waived by the Commission on its own motion. See 47 CFR § 1.3.
167
See Northeast Cellular, 897 F.2d at 1166. Courts have recognized that the Commission may take into account
considerations of hardship, equity, or more effective implementation of overall policy on an individual basis. See
WAIT Radio v. FCC, 418 F.2d 1153, 1159 (D.C. Cir. 1969).
168
The certification statement for use of the RND will need to be modified to cover this use. We anticipate that the
certification would be substantially similar to “The user agrees and warrants that it, and any agent acting on its
behalf, will access and use the reassigned numbers database to: 1) determine whether a number has been
permanently disconnected since a date selected by the user, or its agent, for the purpose of making lawful calls or
sending lawful texts. The date selected will be a date that the user, or its agent, reasonably and in good faith believes
the person it intends to call or text could be reached at that number; or 2) Determine if a number that the
Commission’s Enforcement Bureau has directed a provider to block has been permanently disconnected and
therefore if such blocking should cease. The date selected will be the latest date given for a suspected illegal text
from the number by the Commission’s Enforcement Bureau in its Notification of Suspected Illegal Texts.”
Federal Communications Commission FCC-CIRC2312-02
28
VI. PROCEDURAL MATTERS
85. Paperwork Reduction Act. This document may contain new and modified information
collection requirements subject to the Paperwork Reduction Act of 1995 (PRA), Public Law 104-13. All
such new or modified information collection requirements will be submitted to the Office of Management
and Budget (OMB) for review under section 3507(d) of the PRA. OMB, the general public, and other
federal agencies will be invited to comment on any new or modified information collection requirements
contained in this proceeding. In addition, we note that pursuant to the Small Business Paperwork Relief
Act of 2002, Public Law 107-198, see 44 U.S.C. 3506(c)(4), we previously sought specific comment on
how the Commission might further reduce the information collection burden for small business concerns
with fewer than 25 employees. In this present document, we have assessed the effects of our requirement
that providers block texts following notification from the Enforcement Bureau of fraudulent texts from a
particular source. We find that, to the extent this requirement constitutes an information collection, such
collection will not present a substantial burden for small business concerns with fewer than 25 employees
and that any such burdens would be far outweighed by the benefits to consumers from blocking text
messages that are highly likely to be illegal.
86. This document may also contain proposed new or modified information collection
requirements. The Commission, as part of its continuing effort to reduce paperwork burdens, invites the
general public and the Office of Management and Budget (OMB) to comment on any proposed
information collection requirements contained in this document, as required by the Paperwork Reduction
Act of 1995, Public Law 104-13. In addition, pursuant to the Small Business Paperwork Relief Act of
2002, Public Law 107-198, see 44 U.S.C. 3506(c)(4), we seek specific comment on how we might further
reduce the information collection burden for small business concerns with fewer than 25 employees.
87. Regulatory Flexibility Act. The Regulatory Flexibility Act of 1980, as amended
(RFA),
169
requires that an agency prepare a regulatory flexibility analysis for notice and comment
rulemakings, unless the agency certifies that “the rule will not, if promulgated, have a significant
economic impact on a substantial number of small entities.”
170
Accordingly, we have prepared a Final
Regulatory Flexibility Analysis (FRFA) concerning the impact of the rule changes contained in the
Report and Order on small entities. The FRFA is set forth in Appendix D.
88. We have also prepared an Initial Regulatory Flexibility Analysis (IRFA) concerning the
potential impact of the rule and policy changes contained in the Second Further Notice of Proposed
Rulemaking. The IRFA is set forth in Appendix E. Written public comments are requested on the IRFA.
Comments must be filed by the deadlines for comments on the Second Further Notice of Proposed
Rulemaking indicated on the first page of this document and must have a separate and distinct heading
designating them as responses to the IRFA.
89. Congressional Review Act. The Commission will submit this draft Report and Order,
Further Notice of Proposed Rulemaking, and Waiver Order to the Administrator of the Office of
Information and Regulatory Affairs, Office of Management and Budget, for concurrence as to whether
this rule is “major” under the Congressional Review Act, 5 U.S.C. § 804(2). The Commission will send a
copy of this Second Report and Order, Second Further Notice of Proposed Rulemaking, and Waiver
Order to Congress and the Government Accountability Office pursuant to 5 U.S.C. § 801(a)(1)(A).
90. Ex Parte Rules. The proceeding shall be treated as a “permit-but-disclose” proceeding in
accordance with the Commission’s ex parte rules.
171
Persons making ex parte presentations must file a
169
See 5 U.S.C. § 603. The RFA, see 5 U.S.C. § 601, et seq., has been amended by the Small Business Regulatory
Enforcement Fairness Act of 1996 (SBREFA), Pub. L. No. 104-121, Title II, 110 Stat. 847 (1996).
170
5 U.S.C. § 605(b).
171
47 CFR §§ 1.1200 et seq.
Federal Communications Commission FCC-CIRC2312-02
29
copy of any written presentation or a memorandum summarizing any oral presentation within two
business days after the presentation (unless a different deadline applicable to the Sunshine period applies).
Persons making oral ex parte presentations are reminded that memoranda summarizing the presentation
must (1) list all persons attending or otherwise participating in the meeting at which the ex parte
presentation was made, and (2) summarize all data presented and arguments made during the
presentation. If the presentation consisted in whole or in part of the presentation of data or arguments
already reflected in the presenter’s written comments, memoranda or other filings in the proceeding, the
presenter may provide citations to such data or arguments in his or her prior comments, memoranda, or
other filings (specifying the relevant page and/or paragraph numbers where such data or arguments can be
found) in lieu of summarizing them in the memorandum. Documents shown or given to Commission
staff during ex parte meetings are deemed to be written ex parte presentations and must be filed
consistent with section 1.1206(b) of the Commission’s rules. In proceedings governed by section 1.49(f)
of the Commission’s rules or for which the Commission has made available a method of electronic filing,
written ex parte presentations and memoranda summarizing oral ex parte presentations, and all
attachments thereto, must be filed through the electronic comment filing system available for that
proceeding, and must be filed in their native format (e.g., .doc, .xml, .ppt, searchable .pdf). Participants in
this proceeding should familiarize themselves with the Commission’s ex parte rules.
172
91. Filing of Comments and Reply Comments. Pursuant to sections 1.415 and 1.419 of the
Commission’s rules, 47 CFR §§ 1.415, 1.419, interested parties may file comments and reply comments
on or before the dates indicated on the first page of this document. Comments may be filed using the
Commission’s Electronic Comment Filing System (ECFS). See Electronic Filing of Documents in
Rulemaking Proceedings, 63 FR 24121 (1998).
• Electronic Filers: Comments may be filed electronically using the Internet by accessing the
ECFS: www.fcc.gov/ecfs.
• Paper Filers: Parties who choose to file by paper must file an original and one copy of each
filing.
• Filings can be sent by commercial overnight courier, or by first-class or overnight U.S. Postal
Service mail. All filings must be addressed to the Commission’s Secretary, Office of the
Secretary, Federal Communications Commission.
• Commercial overnight mail (other than U.S. Postal Service Express Mail and Priority Mail)
must be sent to 9050 Junction Drive, Annapolis Junction, MD 20701. U.S. Postal Service first
class, Express, and Priority mail must be addressed to 45 L Street NE, Washington, D.C. 20554.
• Effective March 19, 2020, and until further notice, the Commission no longer accepts any hand
or messenger delivered filings. This is a temporary measure taken to help protect the health and
safety of individuals, and to mitigate the transmission of COVID-19. See FCC Announces
Closure of FCC Headquarters Open Window and Change in Hand-Delivery Policy, Public
Notice, 35 FCC Rcd 2788 (OMD 2020).
92. People with Disabilities. To request materials in accessible formats for people with
disabilities (Braille, large print, electronic files, audio format), send an e-mail to [email protected] or call
the Consumer and Governmental Affairs Bureau at 202-418-0530 (voice).
93. Availability of Documents. Comments, reply comments, ex parte submissions, and the
Second Report and Order and Second Further Notice of Proposed Rulemaking will be available via
ECFS. Documents will be available electronically in ASCII, Microsoft Word, and/or Adobe Acrobat.
When the FCC Headquarters reopens to the public, documents will also be available for public inspection
172
47 CFR § 1.49(f).
Federal Communications Commission FCC-CIRC2312-02
30
during regular business hours in the FCC Reference Center, Federal Communications Commission, 45 L
Street NE, Washington, D.C. 20554.
94. Providing Accountability Through Transparency Act: The Providing Accountability
Through Transparency Act requires each agency, in providing notice of a rulemaking, to post online a
brief plain-language summary of the proposed rule.
173
Accordingly, the Commission will publish the
required summary of this Further Notice of Proposed Rulemaking on https://www.fcc.gov/proposed-
rulemakings.
95. Additional Information. For additional information on this proceeding, contact Jerusha
Burnett, [email protected], 202 418-0526, or Mika Savir, [email protected], 202 418-0384, both
of the Consumer and Governmental Affairs Bureau, Consumer Policy Division.
VII. ORDERING CLAUSES
96. Accordingly, IT IS ORDERED, pursuant to sections 4(i), 4(j), 227, 251(e), 301, 303,
307, and 316 of the Communications Act of 1934, as amended, 47 U.S.C. §§ 154(i), 154(j), 227, 251(e),
301, 303, 307, and 316, that this Second Report and Order and Second Further Notice of Proposed
Rulemaking IS ADOPTED.
97. IT IS FURTHER ORDERED that this Second Report and Order SHALL BE
EFFECTIVE 30 days after publication in the Federal Register, except that the amendments to section 47
CFR § 64.1200(f)(9), which may contain new or modified information collection requirements, will not
become effective until six months after publication in the Federal Register or 30 days after notice that the
Office of Management and Budget has completed review of any information collection requirements that
the Consumer and Governmental Affairs Bureau determines is required under the Paperwork Reduction
Act, whichever is later. The Commission directs the Consumer and Governmental Affairs Bureau to
announce the effective date for section 64.1200(f)(9) by subsequent Public Notice.
98. IT IS FURTHER ORDERED, that, the Commission’s rule restricting access to the
Reassigned Numbers Database only to callers to determine whether a number has been permanently
disconnected for the purpose of making lawful calls or sending lawful texts IS WAIVED to the extent
described in the Waiver Order (Section V) to allow mobile wireless providers to access the Reassigned
Numbers Database to determine whether a number has been permanently disconnected since the date(s)
of the suspected illegal texts described in a Notification of Suspected Illegal Texts.
99. IT IS FURTHER ORDERED that the Commission’s Consumer and Governmental
Affairs Bureau, Reference Information Center, SHALL SEND a copy of this Second Report and Order
and Second Further Notice of Proposed Rulemaking, including the Final Regulatory Flexibility Analysis,
to the Chief Counsel for Advocacy of the Small Business Administration.
173
5 U.S.C. § 553(b)(4). The Providing Accountability Through Transparency Act, Pub. L. No. 118-9 (2023),
amended section 553(b) of the Administrative Procedure Act.
Federal Communications Commission FCC-CIRC2312-02
31
100. IT IS FURTHER ORDERED that the Office of the Managing Director, Performance
Evaluation and Records Management, SHALL SEND a copy of this Second Report and Order in a report
to be sent to Congress and to the Governmental Accountability Office pursuant to the Congressional
Review Act, see 5 U.S.C. § 801(a)(1)(A).
FEDERAL COMMUNICATIONS COMMISSION
Marlene H. Dortch
Secretary
Federal Communications Commission FCC-CIRC2312-02
32
APPENDIX A
List of Commenters
Commenter Abbreviated Name Date Filed
1 American Association of
Ancillary Benefits
AAAB 5/5/23
2 American Association for
Public Opinion Research
AAPOR 5/2/23
3 (Anonymous) Small
Business
Small Business 4/7/23
4 Assurance IQ, LLC Assurance 5/8/23
5 Balboa Digital/Kevin
Wagoner
Balboa Digital 4/17/23
6 Campaign Verify, Inc. Campaign Verify 5/8/23
7 Chandler, Corey Chandler 5/8/23
8 Competitive Carriers
Association
CCA 5/8/23
9 Concerned Citizen Concerned Citizen 5/8/23
10 Connors, James Connors 4/17/23
11 Consumer Consent Council C3 5/8/23
12
CTIA —The Wireless
Association®
CTIA 5/8/23
13 Dobronski, Mark W. Dobronski 5/8/23
14 Drips Holdings, LLC Drips 5/8/23
15 Earl, William J. Earl 5/3/23
16 Enterprise
Communications
Advocacy Coalition
ECAC 5/8/23
17 Harvey, Brian Harvey 5/8/23
18 Haskins, Hayden Haskins 5/8/23
19 High Tech Forum/Richard
Bennett
High Tech Forum 4/16/23
20 INCOMPAS INCOMPAS 5/8/23
21 Insurance Marketing
Coalition
IMC 5/8/23
22 Keller, Richard Keller 5/9/23
23 LendingTree, LLC LendingTree 5/8/23
Federal Communications Commission FCC-CIRC2312-02
33
24 Messaging Malware
Mobile Anti-Abuse
Working Group
M
3
AAWG 5/4/23
25 National Association of
Mutual Insurance
Companies/Thomas Karol
NAMIC 5/8/23
26 National Consumer Law
Center, on behalf of its
low-income clients,
Electronic Privacy
Information Center,
Appleseed Foundation,
Consumer Action,
Consumer Federation of
America, National
Association of Consumer
Advocates, National
Association of State Utility
Consumer Advocates,
National Consumers
League, Public Citizen,
Public Knowledge, U.S.
PIRG
Joint Consumer
Commenters
5/8/23
27 NetNumber, Inc. NetNumber 5/8/23
28 Online Lenders
Alliance/Michael Day
OLA 5/8/23
29 Professional Association
for Customer Engagement
PACE 5/8/23
30 Pain, Edmond and
Stodolak, David
Pain and Stodolak 5/8/23
31 Presley, Richard Presley 4/11/23
32 QuinStreet, Inc. QuinStreet 5/8/23
33
Receivables Management
Assoc International
RMAI 5/8/23
34
Responsible Enterprises
Against Consumer
Harassment, Mutual
Benefit Corporation/Eric
Troutman
REACH
5/8/23 and 5/9/23
(amendment to
comments to correct
spellings, etc.)
35 Rubenstein, Mark Rubenstein 3/28/23
36 Schwab, Thomas J. (filed
in 02-278)
Schwab 4/17/23
37 Shields, Joe Shields 5/9/23
38 Solar Energy Industries SEIA 5/8/23
Federal Communications Commission FCC-CIRC2312-02
34
Association
39 SolarReviews SolarReviews 4/19/23
40 Subbaiah, Kelly Subbaiah 3/28/23
41 UnitedHealthcare UHC 5/8/23
42 USTelecom – The
Broadband Association
USTelecom 5/8/23
43 Voice on the Net Coalition VON 5/8/23
44 Williamson, Sydney Williamson 3/28/23
45 ZipDX, LLC ZipDX 5/8/23
Reply Commenter and
Ex Parte
Abbreviated name Date Filed
1
28 State Attorneys
General (Steve Marshall,
Alabama; Treg Taylor,
Alaska; Kristin K. Mayes,
Arizona; Rob Bonta,
California; Philip J.
Weiser, Colorado;
William Tong,
Connecticut; Brian L.
Shwalb, District of
Columbia; Kwame Raoul,
Illinois; Aaron M. Frey,
Maine; Anthony G.
Brown, Maryland; Andrea
Joy Campbell,
Massachusetts; Dana
Nessel, Michigan; Keith
Ellison, Minnesota; Lynn
Fitch, Mississippi;
Matthew J. Platkin, New
Jersey; Josh Stein, North
Carolina; Drew H.
Wrigley, North Dakota;
Dave Yost, Ohio; Gentner
Drummond, Oklahoma;
Ellen F. Rosenblum,
Oregon; Michelle A.
Henry, Pennsylvania;
Alan Wilson, South
Carolina; Jonathan
Skrmetti, Tennessee;
Charity R. Clark,
Vermont; Jason Miyares,
Virginia; Bob Ferguson,
State Attorneys General 6/6/23
Federal Communications Commission FCC-CIRC2312-02
35
Washington; Joshua L.
Kaul, Wisconsin; Bridget
Hill, Wyoming)
2 American Bankers
Association, ACA
International, American
Financial Services
Association, Bank Policy
Institute, Credit Union
National Association,
Mortgage Bankers
Association, National
Association of Federally-
Insured Credit Unions,
National Council of
Higher Education
Resources, and Student
Loan Servicing Alliance
Bankers Joint
Commenters
6/6/23
3 Competitive Carriers
Association
CCA 6/6/23
4 Connors, James Connors 6/7/23
5 Contact Care Compliance Contact Care
Compliance
5/18/23
6 Crisp, Marcus Crisp 6/7/23
7 CTIA —The Wireless
Association®
CTIA 6/6/23
8 Dobronski, Mark Dobronski 6/7/23
9 Douglas, John Douglas 6/6/23
10
Insurance Marketing
Coalition
IMC 6/6/23
11 Keller, Richard Keller
6/4/23 (two replies
filed, one is an express
comment)
12 LendingTree, LLC LendingTree 6/6/23
13 Madame Mohawk Madame Mohawk 6/26/23
14 National Consumer Law
Center, on behalf of its
low-income clients,
Electronic Privacy
Information Center,
Appleseed Foundation,
Consumer Action,
Consumer Federation of
America, National
Joint Consumer
Commenters
6/6/23
Federal Communications Commission FCC-CIRC2312-02
36
Association of Consumer
Advocates, National
Association of State
Utility Consumer
Advocates, National
Consumers League,
Public Citizen, Public
Knowledge, U.S. PIRG
15 NetNumber, Inc. NetNumber 6/6/23
16 Powell, William J. Powell 5/9/23
17 Provenant Provenant 6/6/23
18 Responsible Enterprises
Against Consumer
Harassment, Mutual
Benefit Corporation/Eric
Troutman
REACH 6/5/23
19 Retail Industry Leaders
Association
RILA 5/9/23
20 Rural Wireless
Association, Inc.
RWA 6/6/23
21 Shields, Joe Shields 6/6/23
22 Solar Energy Industries
Association
SEIA 6/6/23
23 Somos, Inc. Somos 6/6/23
24 Subbaiah, Kelly Subbaiah 6/5/23
25 T-Mobile USA, Inc. T-Mobile 6/6/23
26 Twilio, Inc. Twilio 6/6/23
27 Westbrook, Ken Westbrook 7/26/23
28 Williams, Marjorie Williams 6/6/23
29 ZipDX, LLC ZipDX 5/15/23 and 6/5/23
30 Letter from Scott
Bergmann, Senior Vice
President, Regulatory
Affairs, CTIA, to Marlene
H. Dortch, Secretary,
Federal Communications
Commission (July 25,
2023)
CTIA July 25 ex parte 7/25/23
31 Letter from Scott
Bergmann, Senior Vice
President, Regulatory
Affairs, CTIA, to Marlene
H. Dortch, Secretary,
CTIA Aug. 2 ex parte 8/2/23
Federal Communications Commission FCC-CIRC2312-02
37
Federal Communications
Commission (Aug. 2,
2023)
32 Letter from United States
Senators Ben Ray Luján,
Edward J. Markey, Peter
Welch, Chris Van Hollen,
Elizabeth Warren, Angus
S. King, Jr., Richard J.
Durbin, Martin Heinrich,
Mark R. Warren, Gary C.
Peters, Ron Wyden, Amy
Klobuchar, to
Chairwoman Jessica
Rosenworcel, Federal
Communications
Commission (Aug. 7,
2023)
Aug. 7 Congressional 8/7/23
33 Letter from Missy
Meggison, Co-Executive
Director, Consumer
Relations Consortium, to
Federal Communications
Commission (Aug. 9,
2023).
CRC Aug. 9 ex parte 8/9/23
35 Letter from Scott
Bergmann, Senior Vice
President, Regulatory
Affairs, CTIA, to Marlene
H. Dortch, Secretary,
Federal Communications
Commission (Aug. 23,
2023)
CTIA Aug. 23 ex parte 8/23/23
36 Letter from Yaron Dori
and Jorge Ortiz, counsel
to QuinStreet, to Marlene
H. Dortch, Secretary,
Federal Communications
Commission (Aug. 30
2023)
QuinStreet ex parte 8/30/23
37 Letter from Steven A.
Augustino and Josh
Myers, counsel to
LendingTree, LLC to
Marlene H. Dortch,
Secretary, Federal
Communications
Commission (Sept. 8,
LendingTree ex parte 9/8/23
Federal Communications Commission FCC-CIRC2312-02
38
2023)
38
Letter from Eric J.
Troutman, REACH, to
Marlene H. Dortch,
Secretary, Federal
Communications
Commission (Sept. 15,
2023)
REACH Sept. 15 ex
parte
9/15/23
39
Letter from Michael H.
Pryor, Brownstein, Hyatt,
Farber, Schreck LLP, to
Marlene H. Dortch,
Secretary, Federal
Communications
Commission (Sept. 18,
2023)
ABA Sept. 18 ex parte 9/18/23
40
Letter from Eric J.
Troutman, REACH, to
Marlene H. Dortch,
Secretary, Federal
Communications
Commission (Sept. 20,
2023)
REACH Sept. 20 ex
parte
9/20/23
41
Letter from Steven A.
Augustino and Josh
Myers, counsel to
NetNumber, Inc. to
Marlene H. Dortch,
Secretary, Federal
Communications
Commission (Sept. 21,
2023)
NetNumber ex parte 9/21/23
42 Letter from Eric J.
Troutman, REACH, to
Marlene H. Dortch,
Secretary, Federal
Communications
Commission (Sept. 26,
2023)
REACH Sept. 26 ex
parte
9/26/23
43 Letter from David
Frankel, ZipDX, to
Marlene H. Dortch,
Secretary, Federal
Communications
Commission (Sept. 26,
2023
ZipDX Sept. 26 ex parte 9/26/23
44 Letter from Michael H.
Pryor, Brownstein, Hyatt,
ABA Sept. 26 ex parte 9/26/23
Federal Communications Commission FCC-CIRC2312-02
39
Farber, Schreck LLP, to
Marlene H. Dortch,
Secretary, Federal
Communications
Commission (Sept. 26,
2023)
45 Letter from Lucas Bell,
Director, Government
Relations, Zillow Group,
to Marlene H. Dortch,
Secretary, Federal
Communications
Commission (Oct. 27,
2023)
Zillow ex parte 10/27/23
46
Letter from Eric J.
Troutman, REACH, to
Marlene H. Dortch,
Secretary, Federal
Communications
Commission (Oct. 31,
2023)
REACH Oct. 31 ex parte 10/31/23
47
Letter from Eric J.
Troutman, REACH, to
Marlene H. Dortch,
Secretary, Federal
Communications
Commission (Nov. 2,
2023)
REACH Nov. 2 ex parte 11/2/23
48
Letter from Michael H.
Pryor, Brownstein, Hyatt,
Farber, Schreck LLP, to
Marlene H. Dortch,
Secretary, Federal
Communications
Commission (Nov. 9,
2023)
Credit Union National
Association Nov. 9 ex
parte
11/9/23
49
Letter from Michael H.
Pryor, Brownstein, Hyatt,
Farber, Schreck LLP, to
Marlene H. Dortch,
Secretary, Federal
Communications
Commission (Nov. 15,
2023)
ABA Nov. 15 ex parte 11/15/23
50 Letter from Eric J.
Troutman, counsel for
EXP Realty, to Marlene
H. Dortch, Secretary,
EXP Realty ex parte 11/16/23
Federal Communications Commission FCC-CIRC2312-02
40
Federal Communications
Commission (Nov. 16,
2023)
Federal Communications Commission FCC-CIRC2312-02
41
APPENDIX B
Final Rules
The Federal Communications Commission amends Parts 0 and 64 of Title 47 of the Code of Federal
Regulations as follows:
PART 0—COMMISSION ORGANIZATION
Subpart A—Organization
1. Amend section 0.111(a) by revising paragraph (27) to read:
(27) Identify suspected illegal calls and texts and provide written notice to voice service or mobile
wireless providers. The Enforcement Bureau shall: (1) identify with as much particularity as possible the
suspected traffic or texts; (2) cite the statutory or regulatory provisions the suspected traffic or texts
appear to violate; (3) provide the basis for the Enforcement Bureau’s reasonable belief that the identified
traffic or texts are unlawful, including any relevant nonconfidential evidence from credible sources such
as the industry traceback consortium or law enforcement agencies; and (4) direct the voice service
provider receiving the notice that it must comply with section 64.1200(n)(2) of the Commission’s rules or
direct the mobile wireless provider receiving the notice that it must comply with 64.1200(s) of the
Commission’s rules.
PART 64—MISCELLANEOUS RULES RELATING TO COMMON CARRIERS
Subpart L—Restrictions on Telemarketing, Telephone Solicitation, and Facsimile Advertising
2. Amend § 64.1200 by revising paragraph (e) to add “or text messages,” to read as follows:
(e) The rules set forth in paragraph (c) and (d) of this section are applicable to any person or entity
making telephone solicitations or telemarketing calls or text messages to wireless telephone numbers to
the extent described in the Commission’s Report and Order, CG Docket No. 02–278, FCC 03–153,
“Rules and Regulations Implementing the Telephone Consumer Protection Act of 1991.”
3. Amend § 64.1200 by revising the first full paragraph of paragraph (f)(9) to read as follows:
(f)(9) The term prior express written consent means an agreement, in writing, that bears the signature of
the person called that clearly and conspicuously authorizes no more than one identified seller to deliver or
cause to be delivered to the person called advertisements or telemarketing messages using an automatic
telephone dialing system or an artificial or prerecorded voice. Calls must be logically and topically
associated with the interaction that prompted the consent and the agreement must identify the telephone
number to which the signatory authorizes such advertisements or telemarketing messages to be delivered.
(i) The written agreement shall include a clear; and conspicuous disclosure informing the person signing
that:
(A) By executing the agreement, such person authorizes the seller to deliver or cause to be delivered to
the signatory telemarketing calls using an automatic telephone dialing system or an artificial or
prerecorded voice; and
(B) The person is not required to sign the agreement (directly or indirectly), or agree to enter into such an
agreement as a condition of purchasing any property, goods, or services. The term “signature” shall
include an electronic or digital form of signature, to the extent that such form of signature is recognized as
a valid signature under applicable federal law or state contract law.
Federal Communications Commission FCC-CIRC2312-02
42
4. Amend § 64.1200 by adding paragraph (s) to read as follows:
(s) A terminating mobile wireless provider must, upon receipt of a Notification of Suspected Illegal Texts
from the Commission through its Enforcement Bureau, take the actions described in this paragraph (s),
including, when required, blocking all texts from the identified number or numbers. The Enforcement
Bureau will issue a Notification of Suspected Illegal Texts that identifies the number(s) used and the
date(s) the texts were sent or received; provides the basis for the Enforcement Bureau’s reasonable belief
that the identified texts are unlawful; cites the statutory or regulatory provisions the identified texts appear
to violate; and directs the provider receiving the notice that it must comply with this section. The
Enforcement Bureau’s Notification of Suspected Illegal Texts shall give the identified provider a
reasonable amount of time to comply with the notice. Each notified provider must promptly investigate
the identified texts and report the results of that investigation to the Enforcement Bureau within the
timeframe specified in the Notification of Suspected Illegal Texts. The provider must include a
certification that it is blocking all texts from the number or numbers and will continue to do so unless:
(1) the provider determines that the identified texts are not illegal, in which case it shall provide
an explanation as to why the provider reasonably concluded that the identified texts are not illegal and
what steps it took to reach that conclusion, or;
(2) the provider learns that the number has been reassigned, in which case the provider shall
promptly notify the Enforcement Bureau of this fact and include any information it has obtained that
demonstrates that the number has been reassigned. If, at any time in the future, the provider determines
that the number has been reassigned, it should notify the Enforcement Bureau and cease blocking.
Federal Communications Commission FCC-CIRC2312-02
43
APPENDIX C
Proposed Rules
The Federal Communications Commission amends Part 64 of Title 47 of the Code of Federal Regulations
as follows:
PART 64—MISCELLANEOUS RULES RELATING TO COMMON CARRIERS
Subpart L—Restrictions on Telemarketing, Telephone Solicitation, and Facsimile Advertising
1. Amend section 64.1200 by revising paragraph (s) to reread:
(s) A mobile wireless provider must:
(1) If a terminating or originating provider, upon receipt of a Notification of Suspected Illegal
Texts from the Commission through its Enforcement Bureau, take the actions described in this paragraph
(s)(1), including, when required, blocking all texts from the identified number, if a terminating provider,
or source, if an originating provider, as appropriate. The Enforcement Bureau will issue a Notification of
Suspected Illegal Texts that identifies with as much particularity as possible the suspected illegal texts
including the number(s) used and the date(s) the texts were sent or received; provides the basis for the
Enforcement Bureau’s reasonable belief that the identified texts are unlawful; cites the statutory or
regulatory provisions the identified texts appear to violate; and directs the provider receiving the notice
that it must comply with this section. The Enforcement Bureau’s Notification of Suspected Illegal Texts
shall give the identified provider a reasonable amount of time to comply with the notice. Each notified
provider must promptly investigate the identified texts and report the results of that investigation to the
Enforcement Bureau within the timeframe specified in the Notification of Suspected Illegal Texts.
(i) The provider must include a certification that it is blocking all texts from the number, if a
terminating provider, or source, if the originating provider, and will continue to do so unless:
(A) the provider determines that the identified texts are not illegal, in which case it shall provide
an explanation as to why the provider reasonably concluded that the identified texts are not illegal and
what steps it took to reach that conclusion; or
(B) the provider learns that the number has been reassigned and, if an originating provider, the
source cannot be otherwise identified in a content-neutral and competitively-neutral manner, in which
case the provider shall promptly notify the Enforcement Bureau of this fact and include any information it
has obtained that demonstrates that the number has been reassigned. If, at any time in the future, the
provider determines that the number has been reassigned, it should notify the Enforcement Bureau and
cease blocking unless the provider is an originating provider and further blocking of the source can be
done in a content-neutral and competitively-neutral manner.
(ii) If the mobile wireless provider is an originating provider, the Enforcement Bureau must allow
at least 14 days for that provider to comply with the Notification of Suspected Illegal Texts. If the mobile
wireless provider is a terminating provider and the Enforcement Bureau does not provide a minimum of
14 days and the notified provider needs additional time, up to a total of 14 days, the provider should
promptly notify the Enforcement Bureau and may take up to a total of 14 days to fully comply without
penalty.
(iii) If an originating mobile wireless provider fails to respond to the Notification of Suspected
Illegal Texts, the Enforcement Bureau determines that the response is insufficient, the Enforcement
Bureau determines that the provider is continuing to originate texts from the same source that could be
blocked after the timeframe specified in the Notification of Suspected Illegal Texts, or the Enforcement
Federal Communications Commission FCC-CIRC2312-02
44
Bureau determines based on the evidence that the texts are illegal despite the provider’s assertions, the
Enforcement Bureau may issue an Initial Determination Order to the provider stating the Bureau’s initial
determination that the provider is not in compliance with this section. The Initial Determination Order
shall include the Enforcement Bureau’s reasoning for its determination and give the provider a minimum
of 14 days to provide a final response prior to the Enforcement Bureau making a final determination on
whether the provider is in compliance with this section.
(i) If an originating mobile wireless provider does not provide an adequate response to the Initial
Determination Order within the timeframe permitted in that Order or continues to originate texts from the
same source onto the U.S. network, the Enforcement Bureau may issue a Final Determination Order
finding that the provider is not in compliance with this section. The Final Determination Order shall be
published in EB Docket No. 22-174 at. A Final Determination Order may be issued up to one year after
the release date of the Initial Determination Order, and may be based on either an immediate failure to
comply with this rule or a determination that the provider has failed to meet its ongoing obligation under
this rule to block all texts from the identified source.
(2) When notified by the Commission through its Enforcement Bureau that a Final Determination
Order has been issued finding that an originating mobile wireless provider has failed to block as required
under paragraph (s)(1) of this section, block and cease accepting all texts received directly from the
identified originating provider beginning 30 days after the release date of the Final Determination Order.
This paragraph (s)(2) applies to any provider immediately downstream from the originating provider. The
Enforcement Bureau shall provide notification by publishing the Final Determination Order in EB Docket
No. 22–174 at https://www.fcc.gov/ecfs/search/search-filings. Providers must monitor EB Docket No. 22–
174 and initiate blocking no later than 30 days from the release date of the Final Determination Order.
Federal Communications Commission FCC-CIRC2312-02
45
APPENDIX D
Final Regulatory Flexibility Analysis
1. As required by the Regulatory Flexibility Act of 1980 (RFA),
1
as amended, an Initial
Regulatory Flexibility Analysis (IRFA) was incorporated in Targeting and Eliminating Unlawful Text
Messages, Rules and Regulations Implementing the Telephone Consumer Protection Act of 1991, Further
Notice of Proposed Rulemaking (FNPRM), released March 2023.
2
The Federal Communications
Commission (Commission) sought written public comment on the proposals in the FNPRM, including
comment on the IRFA. The Commission received no comments in response to the IRFA. This present
Final Regulatory Flexibility Analysis (FRFA) conforms to the RFA.
3
A. Need for, and Objectives of, the Second Report and Order
2. The Second Report and Order continues the Commission’s efforts to stop the growing
tide of unwanted and illegal texts by building on the text blocking requirements from the March 2023
Text Blocking Order.
4
While mobile wireless providers voluntarily block a significant number of
unwanted and illegal texts, many of these harmful texts still reach consumers. The Second Report and
Order requires terminating mobile wireless providers to block texts from a particular source following
notification from the Commission; codifies that the National Do-Not-Call (DNC) Registry protections
apply to text messages; encourages mobile service providers to make email-to-text an opt-in service; and
revises our definition of prior express written consent making clear that consent must be to one seller at a
time, and the seller must be logically and topically related to the content of the website on which consent
is obtained.
B. Summary of Significant Issues Raised by Public Comments in Response to the IRFA
3. There were no comments filed that specifically addressed the proposed rules and policies
presented in the IRFA.
C. Response to Comments by the Chief Counsel for Advocacy of the Small Business
Administration
4. Pursuant to the Small Business Jobs Act of 2010, which amended the RFA, the
Commission is required to respond to any comments filed by the Chief Counsel for Advocacy of the
Small Business Administration (SBA), and to provide a detailed statement of any change made to the
proposed rules as a result of those comments.
5. The Chief Counsel did not file any comments in response to the proposed rules in this
proceeding.
1
5 U.S.C. § 603. The RFA, 5 U.S.C. §§ 601-612, has been amended by the Small Business Regulatory
Enforcement Fairness Act of 1996 (SBREFA), Pub. L. No. 104-121, Title II, 110 Stat. 857 (1996).
2
Targeting and Eliminating Unlawful Text Messages, Rules and Regulations Implementing the Telephone Consumer
Protection Act of 1991, CG Docket Nos. 02-278, 21-402, Report and Order and Further Notice of Proposed
Rulemaking, FCC 23-21 (Mar. 17, 2023) (Text Blocking Order and Further Notice).
3
See 5 U.S.C. § 604.
4
Text Blocking Order and Further Notice at 7-14,-paras. 13-31.
Federal Communications Commission FCC-CIRC2312-02
46
D. Description and Estimate of the Number of Small Entities to Which the Rules Will
Apply
6. The RFA directs agencies to provide a description of and, where feasible, an estimate of
the number of small entities that may be affected by the rules and policies adopted herein.
5
The RFA
generally defines the term “small entity” as having the same meaning as the terms “small business,”
“small organization,” and “small governmental jurisdiction.”
6
In addition, the term “small business” has
the same meaning as the term “small business concern” under the Small Business Act.
7
A “small
business concern” is one which: (1) is independently owned and operated; (2) is not dominant in its field
of operation; and (3) satisfies any additional criteria established by the SBA.
8
7. Small Businesses, Small Organizations, Small Governmental Jurisdictions. Our actions,
over time, may affect small entities that are not easily categorized at present. We therefore describe, at
the outset, three broad groups of small entities that could be directly affected herein.
9
First, while there
are industry specific size standards for small businesses that are used in the regulatory flexibility analysis,
according to data from the Small Business Administration’s (SBA) Office of Advocacy, in general a
small business is an independent business having fewer than 500 employees.
10
These types of small
businesses represent 99.9% of all businesses in the United States, which translates to 33.2 million
businesses.
11
8. Next, the type of small entity described as a “small organization” is generally “any not-
for-profit enterprise which is independently owned and operated and is not dominant in its field.”
12
The
Internal Revenue Service (IRS) uses a revenue benchmark of $50,000 or less to delineate its annual
electronic filing requirements for small exempt organizations.
13
Nationwide, for tax year 2020, there
were approximately 447,689 small exempt organizations in the U.S. reporting revenues of $50,000 or less
according to the registration and tax data for exempt organizations available from the IRS.
14
5
Id. § 604 (a)(4).
6
5 U.S.C. § 601(6).
7
5 U.S.C. § 601(3) (incorporating by reference the definition of “small-business concern” in the Small Business
Act, 15 U.S.C. § 632). Pursuant to 5 U.S.C. § 601(3), the statutory definition of a small business applies “unless an
agency, after consultation with the Office of Advocacy of the Small Business Administration and after opportunity
for public comment, establishes one or more definitions of such term which are appropriate to the activities of the
agency and publishes such definition(s) in the Federal Register.”
8
15 U.S.C. § 632.
9
See 5 U.S.C. § 601(3)-(6).
10
See SBA, Office of Advocacy, “What’s New With Small Business?,”https://advocacy.sba.gov/wp-
content/uploads/2023/03/Whats-New-Infographic-March-2023-508c.pdf. (Mar. 2023)
11
Id.
12
See 5 U.S.C. § 601(4).
13
The IRS benchmark is similar to the population of less than 50,000 benchmark in 5 U.S.C § 601(5) that is used to
define a small governmental jurisdiction. Therefore, the IRS benchmark has been used to estimate the number of
small organizations in this small entity description. See Annual Electronic Filing Requirement for Small Exempt
Organizations – Form 990-N (e-Postcard), “Who must file,” https://www.irs.gov/charities-non-profits/annual-
electronic-filing-requirement-for-small-exempt-organizations-form-990-n-e-postcard. We note that the IRS data
does not provide information on whether a small exempt organization is independently owned and operated or
dominant in its field.
14
See Exempt Organizations Business Master File Extract (EO BMF), “CSV Files by Region,”
https://www.irs.gov/charities-non-profits/exempt-organizations-business-master-file-extract-eo-bmf. The IRS
(continued….)
Federal Communications Commission FCC-CIRC2312-02
47
9. Finally, the small entity described as a “small governmental jurisdiction” is defined
generally as “governments of cities, counties, towns, townships, villages, school districts, or special
districts, with a population of less than fifty thousand.”
15
U.S. Census Bureau data from the 2017 Census
of Governments
16
indicate there were 90,075 local governmental jurisdictions consisting of general
purpose governments and special purpose governments in the United States.
17
Of this number, there were
36,931 general purpose governments (county,
18
municipal, and town or township
19
) with populations of
less than 50,000 and 12,040 special purpose governments—independent school districts
20
with enrollment
populations of less than 50,000.
21
Accordingly, based on the 2017 U.S. Census of Governments data, we
estimate that at least 48,971 entities fall into the category of “small governmental jurisdictions.”
22
10. Wireless Telecommunications Carriers (except Satellite). This industry comprises
establishments engaged in operating and maintaining switching and transmission facilities to provide
(Continued from previous page)
Exempt Organization Business Master File (EO BMF) Extract provides information on all registered tax-
exempt/non-profit organizations. The data utilized for purposes of this description was extracted from the IRS EO
BMF data for businesses for the tax year 2020 with revenue less than or equal to $50,000 for Region 1-Northeast
Area (58,577), Region 2-Mid-Atlantic and Great Lakes Areas (175,272), and Region 3-Gulf Coast and Pacific Coast
Areas (213,840) that includes the continental U.S., Alaska, and Hawaii. This data does not include information for
Puerto Rico.
15
See 5 U.S.C. § 601(5).
16
13 U.S.C. § 161. The Census of Governments survey is conducted every five (5) years compiling data for years
ending with “2” and “7”. See also Census of Governments, https://www.census.gov/programs-
surveys/cog/about.html.
17
U.S. Census Bureau, 2017 Census of Governments – Organization Table 2. Local Governments by Type and
State: 2017 [CG1700ORG02], https://www.census.gov/data/tables/2017/econ/gus/2017-governments.html. Local
governmental jurisdictions are made up of general purpose governments (county, municipal and town or township)
and special purpose governments (special districts and independent school districts). See also tbl.2. CG1700ORG02
Table Notes Local Governments by Type and State_2017.
18
See id. at tbl.5. County Governments by Population-Size Group and State: 2017 [CG1700ORG05],
https://www.census.gov/data/tables/2017/econ/gus/2017-governments.html. There were 2,105 county governments
with populations less than 50,000. This category does not include subcounty (municipal and township)
governments.
19
See id. at tbl.6. Subcounty General-Purpose Governments by Population-Size Group and State: 2017
[CG1700ORG06], https://www.census.gov/data/tables/2017/econ/gus/2017-governments.html. There were 18,729
municipal and 16,097 town and township governments with populations less than 50,000.
20
See id. at tbl.10. Elementary and Secondary School Systems by Enrollment-Size Group and State: 2017
[CG1700ORG10], https://www.census.gov/data/tables/2017/econ/gus/2017-governments.html. There were 12,040
independent school districts with enrollment populations less than 50,000. See also tbl.4. Special-Purpose Local
Governments by State Census Years 1942 to 2017 [CG1700ORG04], CG1700ORG04 Table Notes Special Purpose
Local Governments by State Census Years 1942 to 2017.
21
While the special purpose governments category also includes local special district governments, the 2017 Census
of Governments data does not provide data aggregated based on population size for the special purpose governments
category. Therefore, only data from independent school districts is included in the special purpose governments
category.
22
This total is derived from the sum of the number of general purpose governments (county, municipal and town or
township) with populations of less than 50,000 (36,931) and the number of special purpose governments -
independent school districts with enrollment populations of less than 50,000 (12,040), from the 2017 Census of
Governments - Organizations tbls. 5, 6 & 10.
Federal Communications Commission FCC-CIRC2312-02
48
communications via the airwaves.
23
Establishments in this industry have spectrum licenses and provide
services using that spectrum, such as cellular services, paging services, wireless Internet access, and
wireless video services.
24
The SBA size standard for this industry classifies a business as small if it has
1,500 or fewer employees.25 U.S. Census Bureau data for 2017 show that there were 2,893 firms in this
industry that operated for the entire year.26 Of that number, 2,837 firms employed fewer than 250
employees.27 Additionally, based on Commission data in the 2022 Universal Service Monitoring Report,
as of December 31, 2021, there were 594 providers that reported they were engaged in the provision of
wireless services.
28
Of these providers, the Commission estimates that 511 providers have 1,500 or fewer
employees.
29
Consequently, using the SBA’s small business size standard, most of these providers can be
considered small entities.
11. All Other Telecommunications. This industry is comprised of establishments primarily
engaged in providing specialized telecommunications services, such as satellite tracking, communications
telemetry, and radar station operation.
30
This industry also includes establishments primarily engaged in
providing satellite terminal stations and associated facilities connected with one or more terrestrial
systems and capable of transmitting telecommunications to, and receiving telecommunications from,
satellite systems.
31
Providers of Internet services (e.g., dial-up ISPs) or Voice over Internet Protocol
(VoIP) services, via client-supplied telecommunications connections are also included in this industry.
32
The SBA small business size standard for this industry classifies firms with annual receipts of $35 million
or less as small.
33
U.S. Census Bureau data for 2017 show that there were 1,079 firms in this industry that
operated for the entire year.
34
Of those firms, 1,039 had revenue of less than $25 million.
35
Based on this
23
See U.S. Census Bureau, 2017 NAICS Definition, “517312 Wireless Telecommunications Carriers (except
Satellite),” https://www.census.gov/naics/?input=517312&year=2017&details=517312.
24
Id.
25
13 CFR § 121.201, NAICS Code 517312 (as of 10/1/22, NAICS Code 517112).
26
U.S. Census Bureau, 2017 Economic Census of the United States, Employment Size of Firms for the U.S.: 2017,
Table ID: EC1700SIZEEMPFIRM, NAICS Code 517312,
https://data.census.gov/cedsci/table?y=2017&n=517312&tid=ECNSIZE2017.EC1700SIZEEMPFIRM&hidePrevie
w=false.
27
Id. The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that
meet the SBA size standard.
28
Federal-State Joint Board on Universal Service, Universal Service Monitoring Report at 26, Table 1.12 (2022),
https://docs.fcc.gov/public/attachments/DOC-391070A1.pdf.
29
Id.
30
See U.S. Census Bureau, 2017 NAICS Definition, “517919 All Other Telecommunications,
https://www.census.gov/naics/?input=517919&year=2017&details=517919.
31
Id.
32
Id.
33
See 13 CFR § 121.201, NAICS Code 517919 (as of 10/1/22, NAICS Code 517810).
34
See U.S. Census Bureau, 2017 Economic Census of the United States, Selected Sectors: Sales, Value of Shipments,
or Revenue Size of Firms for the U.S.: 2017, Table ID: EC1700SIZEREVFIRM, NAICS Code 517919,
https://data.census.gov/cedsci/table?y=2017&n=517919&tid=ECNSIZE2017.EC1700SIZEREVFIRM&hidePrevie
w=false.
35
Id. The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that
meet the SBA size standard. We also note that according to the U.S. Census Bureau glossary, the terms receipts and
revenues are used interchangeably, see https://www.census.gov/glossary/#term_ReceiptsRevenueServices.
(continued….)
Federal Communications Commission FCC-CIRC2312-02
49
data, the Commission estimates that the majority of “All Other Telecommunications” firms can be
considered small.
E. Description of Projected Reporting, Recordkeeping and Other Compliance
Requirements for Small Entities
12. The Second Report and Order includes new or modified reporting, recordkeeping, and
compliance requirements for small and other entities. This includes requiring terminating mobile wireless
providers to block texts from a particular source following notification from the Commission. Providers
must promptly investigate the texts and source identified in the notice, begin blocking the identified texts
if illegal, and report the results of the investigation to the Enforcement Bureau. If the provider is unable
to block further texts from that source because the number has been reassigned, and the source cannot be
otherwise identified in a content and competitively neutral manner, the provider should promptly notify
the Enforcement Bureau. If the provider determines at a later date that the number has been reassigned, it
should notify the Enforcement Bureau, and cease blocking unless further blocking of the source can be
done in a content and competitively neutral manner. Providers that fail to comply may be subject to
enforcement penalties, including monetary forfeiture.
13. The Second Report and Order also codifies that the National DNC Registry protections
apply to text messages, and encourages mobile service providers to make email-to-text an opt-in service.
Additionally, it revises our definition of prior express written consent making clear that consent must be
only to one single seller-caller to one single consumer at a time, and the seller must be logically and
topically related to the content of the website on which consent is obtained. Small entities may comply
with the Telephone Consumer Protection Act (TCPA) and contact consumers by obtaining consent from
the consumer to one seller at a time. The Commission expects that small and other providers already
taking significant measures to block illegal texts and will not find it burdensome to comply with these
new obligations.
36
Any such burdens would be far outweighed by the benefits to consumers from
blocking text messages that are highly likely to be illegal.
F. Steps Taken to Minimize Significant Economic Impact on Small Entities, and
Significant Alternatives Considered
14. The RFA requires an agency to provide, “a description of the steps the agency has taken
to minimize the significant economic impact on small entities…including a statement of the factual,
policy, and legal reasons for selecting the alternative adopted in the final rule and why each one of the
other significant alternatives to the rule considered by the agency which affect the impact on small entities
was rejected.”
37
15. In the Second Report and Order, the Commission adopted text blocking rules modeled
after the call blocking rules, but modified the new rules to account for the differences in the technology
and delivery of text messages, and adopted requirements similar to those service providers were already
familiar to reduce any additional burdens.
38
For example, a terminating provider will be required to block
text messages only after it has received notice from the Commission’s Enforcement Bureau. Second, text
blockers are not required to block traffic “substantially similar” to the traffic the Enforcement Bureau
identifies to avoid blocking on content analysis, which could lead to over blocking.
39
This modification
(Continued from previous page)
36
Second Report and Order paras. 16-18.
37
5 U.S.C. § 604(a)(6).
38
Second Report and Order paras. 17-19.
39
Second Report and Order para. 17.
Federal Communications Commission FCC-CIRC2312-02
50
will reduce concerns about liability for blocking incorrectly, as well as potential burdens if the
Commission adopted a more expansive rule. While commenters suggested a blocking mandate is
inappropriate because providers already take action to block text messages,
40
the Commission found
commenters made general assertions, but offered no compelling evidence that they consistently block all
traffic the Enforcement Bureau might identify.
G. Report to Congress
16. The Commission will send a copy of the Second Report and Order, including this FRFA,
in a report to be sent to Congress pursuant to the Congressional Review Act.
41
In addition, the
Commission will send a copy of the Second Report and Order, including this FRFA, to the Chief Counsel
for Advocacy of the SBA. The Second Report and Order and FRFA (or summaries thereof) will also be
published in the Federal Register.
42
40
Id. para. 18.
41
5 U.S.C. § 801(a)(1)(A).
42
Id. § 604(b).
Federal Communications Commission FCC-CIRC2312-02
51
APPENDIX E
Initial Regulatory Flexibility Analysis
1. As required by the Regulatory Flexibility Act of 1980, as amended
(RFA)
1
the Commission
has prepared this Initial Regulatory Flexibility Analysis (IRFA) of the possible significant economic
impact on a substantial number of small entities by the policies proposed
in this Second Further Notice of
Proposed Rulemaking (Second Further Notice). Written public comments are requested on this IRFA.
Comments must be identified as responses to the IRFA and must be filed by the deadlines for comments
in the Second Further Notice The Commission will send a copy of this entire Second Further Notice,
including this IRFA, to the Chief Counsel for Advocacy of the Small Business Administration (SBA).
2
In
addition, the Second Further Notice and the IRFA (or summaries thereof) will be published in the Federal
Register.
3
A. Need for, and Objectives of, the Proposed Rules
2. In the Second Further Notice, the Commission proposes additional action to stop
unwanted and illegal text messages that may harass and defraud consumers. Specifically, the
Commission proposes extending the call blocking requirements to require all downstream providers to
block the texts from upstream providers that fail to block after Commission notification. The
Commission also seeks comment on requiring providers to block texts based on content-neutral analytics,
and on whether it is appropriate to adopt a 24-hour traceback response requirement for text messaging.
The Second Further Notice also requests comment on alternative approaches to protect consumers from
unwanted texts, and any additional protections that may be necessary in case of erroneous blocking. In
addition, we seek comment on the viability of text authentication, and whether we should require industry
updates on its feasibility. Finally, the Commission proposes requiring providers to make email-to-text an
opt-in service,.
B. Legal Basis
3. The proposed action is authorized pursuant to sections 4(i), 4(j), 227, 301, 303, 307, and
316 of the Communications Act of 1934, as amended, 47 U.S.C. §§ 154(i), 154(j), 227, 301, 303, 307,
and 316.
C. Description and Estimate of the Number of Small Entities to Which the Proposed
Rules Will Apply
4. The RFA directs agencies to provide a description of and, where feasible, an estimate of
the number of small entities that may be affected by the proposed rules and policies, if adopted.
4
The
RFA generally defines the term “small entity” as having the same meaning as the terms “small business,”
“small organization,” and “small governmental jurisdiction.”
5
In addition, the term “small business” has
the same meaning as the term “small business concern” under the Small Business Act.
6
A “small
1
5 U.S.C. § 603. The RFA, see 5 U.S.C. §§ 601-612, was amended by the Small Business Regulatory Enforcement
Fairness Act of 1996 (SBREFA), Pub. L. No. 104-121, Title II, 110 Stat. 857 (1996)
2
5 U.S.C. § 603(a).
3
Id.
4
Id.§ 603(b)(3).
5
Id. § 601(6).
6
Id. § 601(3) (incorporating by reference the definition of “small-business concern” in the Small Business Act, 15
U.S.C. § 632). Pursuant to 5 U.S.C. § 601(3), the statutory definition of a small business applies “unless an agency,
after consultation with the Office of Advocacy of the Small Business Administration and after opportunity for public
(continued….)
Federal Communications Commission FCC-CIRC2312-02
52
business concern” is one which: (1) is independently owned and operated; (2) is not dominant in its field
of operation; and (3) satisfies any additional criteria established by the SBA.
7
5. Small Businesses, Small Organizations, Small Governmental Jurisdictions. Our actions, over
time, may affect small entities that are not easily categorized at present. We therefore describe, at the
outset, three broad groups of small entities that could be directly affected herein.
8
First, while there are
industry specific size standards for small businesses that are used in the regulatory flexibility analysis,
according to data from the Small Business Administration’s (SBA) Office of Advocacy, in general a
small business is an independent business having fewer than 500 employees.
9
These types of small
businesses represent 99.9% of all businesses in the United States, which translates to 33.2 million
businesses.
10
6. Next, the type of small entity described as a “small organization” is generally “any not-for-
profit enterprise which is independently owned and operated and is not dominant in its field.”
11
The
Internal Revenue Service (IRS) uses a revenue benchmark of $50,000 or less to delineate its annual
electronic filing requirements for small exempt organizations.
12
Nationwide, for tax year 2020, there
were approximately 447,689 small exempt organizations in the U.S. reporting revenues of $50,000 or less
according to the registration and tax data for exempt organizations available from the IRS.
13
7. Finally, the small entity described as a “small governmental jurisdiction” is defined generally
as “governments of cities, counties, towns, townships, villages, school districts, or special districts, with a
population of less than fifty thousand.”
14
U.S. Census Bureau data from the 2017 Census of
(Continued from previous page)
comment, establishes one or more definitions of such term which are appropriate to the activities of the agency and
publishes such definition(s) in the Federal Register.”
7
15 U.S.C. § 632.
8
See 5 U.S.C. § 601(3)-(6).
9
SBA, Office of Advocacy, “What’s New With Small Business?,” https://advocacy.sba.gov/wp-
content/uploads/2023/03/Whats-New-Infographic-March-2023-508c.pdf. (Mar. 2023)
10
Id.
11
See 5 U.S.C. § 601(4).
12
The IRS benchmark is similar to the population of less than 50,000 benchmark in 5 U.S.C § 601(5) that is used to
define a small governmental jurisdiction. Therefore, the IRS benchmark has been used to estimate the number of
small organizations in this small entity description. See Annual Electronic Filing Requirement for Small Exempt
Organizations – Form 990-N (e-Postcard), “Who must file,”https://www.irs.gov/charities-non-profits/annual-
electronic-filing-requirement-for-small-exempt-organizations-form-990-n-e-postcard. We note that the IRS data
does not provide information on whether a small exempt organization is independently owned and operated or
dominant in its field.
13
See Exempt Organizations Business Master File Extract (EO BMF), “CSV Files by Region,”
https://www.irs.gov/charities-non-profits/exempt-organizations-business-master-file-extract-eo-bmf. The IRS
Exempt Organization Business Master File (EO BMF) Extract provides information on all registered tax-
exempt/non-profit organizations. The data utilized for purposes of this description was extracted from the IRS EO
BMF data for businesses for the tax year 2020 with revenue less than or equal to $50,000 for Region 1-Northeast
Area (58,577), Region 2-Mid-Atlantic and Great Lakes Areas (175,272), and Region 3-Gulf Coast and Pacific Coast
Areas (213,840) that includes the continental U.S., Alaska, and Hawaii. This data does not include information for
Puerto Rico.
14
See 5 U.S.C. § 601(5).
Federal Communications Commission FCC-CIRC2312-02
53
Governments
15
indicate there were 90,075 local governmental jurisdictions consisting of general purpose
governments and special purpose governments in the United States.
16
Of this number, there were 36,931
general purpose governments (county,
17
municipal, and town or township
18
) with populations of less than
50,000 and 12,040 special purpose governments—independent school districts
19
with enrollment
populations of less than 50,000.
20
Accordingly, based on the 2017 U.S. Census of Governments data, we
estimate that at least 48,971 entities fall into the category of “small governmental jurisdictions.”
21
8. Wireless Carriers and Service Providers. Wireless Telecommunications Carriers (except
Satellite) is the closest industry with a SBA small business size standard applicable to these service
providers.
22
The SBA small business size standard for this industry classifies a business as small if it has
1,500 or fewer employees.
23
U.S. Census Bureau data for 2017 show that there were 2,893 firms that
operated in this industry for the entire year.
24
Of this number, 2,837 firms employed fewer than 250
15
13 U.S.C. § 161. The Census of Governments survey is conducted every five (5) years compiling data for years
ending with “2” and “7”. See also Census of Governments, https://www.census.gov/programs-
surveys/cog/about.html.
16
U.S. Census Bureau, 2017 Census of Governments – Organization Table 2. Local Governments by Type and
State: 2017 [CG1700ORG02], https://www.census.gov/data/tables/2017/econ/gus/2017-governments.html. Local
governmental jurisdictions are made up of general purpose governments (county, municipal and town or township)
and special purpose governments (special districts and independent school districts). See also tbl.2. CG1700ORG02
Table Notes Local Governments by Type and State_2017.
17
See id. at tbl.5. County Governments by Population-Size Group and State: 2017 [CG1700ORG05],
https://www.census.gov/data/tables/2017/econ/gus/2017-governments.html. There were 2,105 county governments
with populations less than 50,000. This category does not include subcounty (municipal and township)
governments.
18
See id. at tbl.6. Subcounty General-Purpose Governments by Population-Size Group and State: 2017
[CG1700ORG06], https://www.census.gov/data/tables/2017/econ/gus/2017-governments.html. There were 18,729
municipal and 16,097 town and township governments with populations less than 50,000.
19
See id. at tbl.10. Elementary and Secondary School Systems by Enrollment-Size Group and State: 2017
[CG1700ORG10], https://www.census.gov/data/tables/2017/econ/gus/2017-governments.html. There were 12,040
independent school districts with enrollment populations less than 50,000. See also tbl.4. Special-Purpose Local
Governments by State Census Years 1942 to 2017 [CG1700ORG04], CG1700ORG04 Table Notes Special Purpose
Local Governments by State_Census Years 1942 to 2017.
20
While the special purpose governments category also includes local special district governments, the 2017 Census
of Governments data does not provide data aggregated based on population size for the special purpose governments
category. Therefore, only data from independent school districts is included in the special purpose governments
category.
21
This total is derived from the sum of the number of general purpose governments (county, municipal and town or
township) with populations of less than 50,000 (36,931) and the number of special purpose governments -
independent school districts with enrollment populations of less than 50,000 (12,040), from the 2017 Census of
Governments - Organizations tbls. 5, 6 & 10.
22
See U.S. Census Bureau, 2017 NAICS Definition, “517312 Wireless Telecommunications Carriers (except
Satellite),” https://www.census.gov/naics/?input=517312&year=2017&details=517312.
23
See 13 CFR § 121.201, NAICS Code 517312 (as of 10/1/22, NAICS Code 517112).
24
See U.S. Census Bureau, 2017 Economic Census of the United States, Employment Size of Firms for the U.S.:
2017, Table ID: EC1700SIZEEMPFIRM, NAICS Code 517312,
https://data.census.gov/cedsci/table?y=2017&n=517312&tid=ECNSIZE2017.EC1700SIZEEMPFIRM&hidePrevie
w=false.
Federal Communications Commission FCC-CIRC2312-02
54
employees.
25
Additionally, based on Commission data in the 2021 Universal Service Monitoring Report,
as of December 31, 2020, there were 797 providers that reported they were engaged in the provision of
wireless services.
26
Of these providers, the Commission estimates that 715 providers have 1,500 or fewer
employees.
27
Consequently, using the SBA’s small business size standard, most of these providers can be
considered small entities.
9. All Other Telecommunications. This industry is comprised of establishments primarily
engaged in providing specialized telecommunications services, such as satellite tracking, communications
telemetry, and radar station operation.
28
This industry also includes establishments primarily engaged in
providing satellite terminal stations and associated facilities connected with one or more terrestrial
systems and capable of transmitting telecommunications to, and receiving telecommunications from,
satellite systems.
29
Providers of Internet services (e.g. dial-up ISPs) or Voice over Internet Protocol
(VoIP) services, via client-supplied telecommunications connections are also included in this industry.
30
The SBA small business size standard for this industry classifies firms with annual receipts of $35 million
or less as small.
31
U.S. Census Bureau data for 2017 show that there were 1,079 firms in this industry that
operated for the entire year.
32
Of those firms, 1,039 had revenue of less than $25 million.
33
Based on this
data, the Commission estimates that the majority of “All Other Telecommunications” firms can be
considered small.
D. Description of Projected Reporting, Recordkeeping, and Other Compliance
Requirements for Small Entities
10. The Second Further Notice includes proposals that may alter the Commission’s current
information collection, reporting, recordkeeping, or compliance requirements for small entities.
Specifically, the proposal to extend call blocking mandates to require all downstream providers to block
the texts from upstream providers that fail to block after Commission notification, and requiring providers
to block texts based on content-neutral analytics would create new obligations for small entities and other
providers. Similarly, establishing a 24-hour traceback response requirement for text messaging and
requiring providers to make email-to-text an opt in service would also impose new compliance
obligations on all providers, including small businesses.
25
Id. The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that
meet the SBA size standard.
26
Federal-State Joint Board on Universal Service, Universal Service Monitoring Report at 26, Table 1.12 (2021),
https://docs.fcc.gov/public/attachments/DOC-379181A1.pdf.
27
Id.
28
See U.S. Census Bureau, 2017 NAICS Definition, “517919 All Other Telecommunications,
https://www.census.gov/naics/?input=517919&year=2017&details=517919.
29
Id.
30
Id.
31
See 13 CFR § 121.201, NAICS Code 517919 (as of 10/1/22, NAICS Code 517810).
32
See U.S. Census Bureau, 2017 Economic Census of the United States, Selected Sectors: Sales, Value of Shipments,
or Revenue Size of Firms for the U.S.: 2017, Table ID: EC1700SIZEREVFIRM, NAICS Code 517919,
https://data.census.gov/cedsci/table?y=2017&n=517919&tid=ECNSIZE2017.EC1700SIZEREVFIRM&hidePrevie
w=false.
33
Id. The available U.S. Census Bureau data does not provide a more precise estimate of the number of firms that
meet the SBA size standard. We also note that according to the U.S. Census Bureau glossary, the terms receipts and
revenues are used interchangeably, see https://www.census.gov/glossary/#term_ReceiptsRevenueServices.
Federal Communications Commission FCC-CIRC2312-02
55
11. Additional blocking requirements, if adopted, such as requiring originating providers to
block texts after notification from the Commission that the texts are likely to be illegal should not be a
burden for small entities due to the fact that mobile wireless providers are currently blocking texts that are
likely to be illegal.
34
We anticipate the information we receive relating to cost and benefit analyses will
help the Commission identify and evaluate relevant compliance matters for small entities, including
compliance costs and other burdens that may result from the proposals and inquiries we make in the
Second Further Notice.
E. Steps Taken to Minimize Significant Economic Impact on Small Entities, and
Significant Alternatives Considered
12. The RFA requires an agency to describe any significant, specifically small business,
alternatives that it has considered in reaching its approach, which may include the following four
alternatives, among others: “(1) the establishment of differing compliance or reporting requirements or
timetables that take into account the resources available to small entities; (2) the clarification,
consolidation, or simplification of compliance or reporting requirements under the rule for such small
entities; (3) the use of performance, rather than design, standards; and (4) and exemption from coverage
of the rule, or any part thereof, for such small entities.”
35
13. In the Second Further Notice the Commission considered and seeks comment on several
alternatives that may significantly impact small entities. As we evaluate additional blocking requirements
to protect consumers from illegal texts, we seek comment on how to define originating providers, and
whether we should apply these rules to some other entity in the chain to better protect consumers. We
propose blocking messages based on their source, but consider alternatively whether they should be
blocked on other criteria such as traffic that is “substantially similar” to blocked texts. In addition, we
seek comment on alternatives to requiring providers to block texts based on content-neutral reasonable
analytics. We also request comment on alternatives to the proposed blocking or mitigation rules that
would help to protect consumers from unwanted and illegal texts. The Commission expects to fully
consider whether any of the costs associated with the proposed text blocking requirements can be
alleviated for small entities and any alternatives to minimize the economic impact for small entities
following the review of comments filed in response to the Second Further Notice.
F. Federal Rules that May Duplicate, Overlap, or Conflict with the Proposed Rules
14. None.
34
Second Report and Order paras. 16-18.
35
5 U.S.C. § 603(c)(1)–(4).