Why You Still Can't Text 911

Illustration for article titled Why You Still Can't Text 911

Just this past Friday, the FCC voted to require all mobile carriers and "interconnected text providers" (i.e. iMessage) to allow their customers to text 911 by by next year. Which would be great except for one, itty-bitty little problem: The FCC can't do actually anything about it.


While the federal government does (theoretically) have jurisdiction over mobile carriers, that's only half of the equation. As the National Journal points out, if your state doesn't have a call center system in place that can handle texts to 911, it doesn't matter whether your carrier sends the message or not—nothing's there to catch it.

According to the National Journal:

About 2 percent of emergency call centers around the country are prepared to handle text messages, and the FCC does not have authority to require that capability.

Instead, the decision to require or not require call centers to be text-compatible belongs with individual states and counties.

Vermont became the first state to adopt text-to-911 statewide this year after an early trial with Verizon in 2012 dispelled "urban legends" that a flood of text messages would result.

While traditional phone calls are almost always preferred (the location-tracking data they provide is far more reliable), emergency texts could be a lifesaver in situations of domestic abuse where the caller is forced to hide. For now, though, all the FCC can really do is hope the move encourages states to match carrier requirements. Because until they do, anyone attempting to text 911 in a non-compatible state will just get a failure-to-send bounce-back message in return.

Our current means of texting, though, are little more than a bandaid for what's to come—Next Generation 911. But until we get that system in place, and until states start picking up the slack—we're stuck with a phone call. [National Journal]


Judith Waite Allee

Stupid smart phone. If I were hiding, it would be sure to give me away somehow. When I turn down the volume, it goes "blip, blip, blip" at each of the 7 volume levels all the way down (with decreasing loudness). Apparently, it's letting you sample the sound levels to help you decide which one you want.

Swiping the phone to unlock the screen generates the sound of a canoe oar dipping into the river. Even with the sound turned completely OFF at a meeting, it whistles each time I get a text. Don't even get me started on the notifications—I keep turning them off, and next day, they somehow auto-reset to "on."

It's still better, though, than my old phone, which used to announce with a loud signature piece of music when I turned it off. . . in the middle of a meeting. Which kinda defeats the purpose. At least the new one doesn't do THAT.

Texts sometimes go through when calls won't, especially away from the metro areas. And vice vice—occasionally I don't get texts until hours later, and then I may get several at once. I imagine as the towers improve, that will be less problematic. I have one of those cheap-o pre-paid services that lease towers from Sprint, but the service gets access to only a limited number of their towers. Most low-income people have my kind of phone, rather than a plan.

Maybe this kind of discussion will cause some positive changes in usability that will benefit us whenever we want to be quiet, whether or not we are in crisis.