In December 2007, Public Knowledge (joined by several other public interest groups] filed a Petition For Declaratory Ruling asking the Federal Communications Commission (FCC) to clarify that both SMS Text Messaging and short codes are “Title II” telecommunications services. Put another way, we asked the FCC to reaffirm the basic statutory language that if you use telephones and the telephone network to send information from one telephone number to another, it meets the definition of “telecommunications service.” (47 U.S.C. 153(53)) We did this because earlier in 2007 Verizon had blocked NARAL from using its short code for political action alerts. While we thought there might be some question about short codes, it seemed pretty obvious from reading the statute that when you send “information between or among points of the users choosing, without change in the form or content as sent and received” (definition of “telecommunications”), over the phone network, using phone numbers that it is a “telecommunications service.”
Sigh.
On the anniversary of the repeal of net neutrality, FCC Chair Ajit Pai now proposes another goodie for carriers – classifying both short codes and text messages as Title I “information service” rather than a Title II telecommunications service. As this is even more ridiculous than last year’s reclassification of broadband as Title I, the draft Order relies primarily on the false claim that classifying text messaging as Title I is an anti-robocall measure. As we at PK pointed out a bunch of times when the wireless carriers first raised this argument back in 2008 – this is utter nonsense. Email, the archetypal Title I information service, is (as Pai himself pointed out over here) chock full of spam. Furthermore, as Pai pointed out last month, the rise in robocalls to mobile phones has nothing to do with regulatory classification and is primarily due to the carriers not implementing existing technical fixes. (And, as the Wall St J explained in this article, robocallers have figured out how to get paid just for connecting to a live number whether or not you answer, which involves a kind of arbitrage that does not work for text messages.)
As if that were not enough, the FCC issued a declaratory ruling in 2015, reaffirmed in 2016, that carriers may block unwanted calls or texts despite being Title II common carriers. There is absolutely nothing, nada, zip, zero, that classifying text messages as Title II does that makes it harder to combat spam. By contrast, Title II does prevent a bunch of blocking of wanted text messages as an anticompetitive conduct which we have already seen (and which is occurring fairly regularly on a daily basis, based on the record in the relevant FCC proceeding (08-7). This includes blocking immigrants rights groups, blocking health alerts, blocking information about legal medical marijuana, and blocking competing services. We should therefore treat the claims by industry and the FCC that only by classifying text messaging as “information services” can we save consumers from a rising tide of spam for what they are – self-serving nonsense designed to justify stripping away the few remaining enforceable consumer rights.
Once again, beyond the obvious free expression concerns and competition concerns, playing cutesy games with regulatory definitions will have a bunch of unintended consequences that the draft order either shrugs off or fails to consider. Notably:
- Classifying texting as Title I will take revenue away from the Universal Service Fund (USF). This will further undermine funds to support rural broadband.
- Classifying texting as Title I disrupts the current automatic roaming framework established by the FCC in 2007.
- Classifying texting as Title I may, ironically, take it out of the jurisdiction of the Robocall statute (Telephone Consumer Protection Act (TCPA) of 1991).
- Trashing whatever consumer protections, we have for text messages, and taking one more step to total administrative repeal of Title II completely. Which sounds like fun if you are a carrier but leaves us operating without a safety net for our critical communications infrastructure (as I’ve been writing about for almost ten years).
I unpack all of this below.
