US Carriers Requiring Shortcodes – Developer Hostility Hits a New High

The SMTP gateways provided by US carriers kinda suck. Sure, at least we have something, European carriers don’t even have SMTP available. But that’s no excuse for the sucking. I need to deliver messages to myself from production servers, I’m currently doing operations and need to get the notifications as the events happen. I would really like to deliver them to other members of my team. Seems like it should be a simple enough thing.

So even though I’m paying for getting the messages, I decided to swallow my anger and pay an SMS aggregator to deliver me messages. First I started out looking at SimpleWire cause I had used them before. But found that the require a shortcode now:

Simplewire Starter Packages are for non-US and non-Canadian traffic only. All U.S. and Canadian carriers now require a short code to be provisioned for all Simplewire customers.

A shortcode in order to send SMS messages, that’s just stupid I thought. So instead I went to Clickatell, which seemed to have no restrictions of the sort…. except I wasn’t getting some of the messages I sent through Clickatell. I contacted support and got this back:

The US has introduced strict control over messages sent from applications to handsets through the use of short codes. All traffic to US handsets require a valid short code registered with the different networks. Clickatell’s short code has been blocked by T-Mobile due to more than one service(different content from multiple users) sent over one short code which is not allowed and we can not say when other providers could take the same action.

I’m just blown away here. Seriously, this is insane. Just when the mobile environment seems like it can’t get any more hostile toward developers the carriers go and do something like this. People always ask me why we don’t get more carriers involved in the Mobile Monday events, this is demonstration of their mentality. They do not care about you developers and application providers. I don’t know why it’s hard to believe when there are fantastic examples of their hostility like this.

Now I have to map out a route from my house to the office that has 100% wifi coverage. Fuckers.

This entry was posted in ThisIsMobility. Bookmark the permalink.

15 Responses to US Carriers Requiring Shortcodes – Developer Hostility Hits a New High

  1. Ben says:

    Mike,

    Not sure what you mean about European carriers not providing SMTP – all of them in the UK provide it to send e-mail from your phone and none of the carriers I’ve used block access to 3rd party SMTP servers either. The carrier’s servers aren’t always the most reliable, but they are there!

    Do you mean e-mail to SMS conversion instead? i.e. sending an e-mail to @carrier.com sends an SMS to that number.

    Ben

  2. Go to your happy place, Mike. :) This too shall pass.

  3. miker says:

    Ben, yes, that’s what I’m talking about. The email to SMS gateways seem to be less popular in Europe than they are in the US.

  4. I think the reason for the lack of e-mail to SMS gateways in Europe (or one reason anyway) has been the history of SMS interoperability here. In the US, until very recently, the only way to GET an SMS to someone was to email it. Carriers simply didn’t promote peer-to-peer SMS because it largely did not function across networks. European carriers also wanted to protect their SMS revenue, of course, and you can’t charge the sender (calling-party-pays) when they are sending an e-mail from the open Internet.

    My analysis: the move you’ve described by US carriers will just drive more developers to adopt alternative messaging technologies (such as mobile IM), and at the end of the day the losers will really be the carriers. But hey, what do I know?

  5. Don’t forget, you also have to pay $500/month for a shortcode “lease” or $1,000/month for a “vanity” shortcode.

  6. miker says:

    Dan, I really hope you’re right, and I’ll do whatever I can to make it happen. However, I want to get reliable notifications to my handset today, and this is forcing me to look outside of mobile to service my needs. There’s simply nothing available today for a realistic cost and effort that gets me what I need. I imagine the same will be true for others, folks will start wandering away, and everyone will use this as further proof that mobile isn’t a workable environment yet.

  7. There was a lot of email to sms gateway in the early days of sms (98-99) until operators realize how big this market was. SMS were not free, but of course email was free. So then operators stopped these email to sms gateway….

    But in europe, it’s only the sender who pay, not the receiver. Note sure, but in the us, you pay when you receive alerts, right?

  8. miker says:

    Thomas, yes, you pay both ways in the US, The sender pays, and receiver pays. There are email to SMS gateways in the US still, they’re just very unreliable, relatively slow, tend to repeat and/or drop messages, and relatively easy to get blacklisted by. They’re great for a quick hack, but really not a great platform to work on top of.

  9. this thing is bullshit…

    to Dan, who wrote “This too shall pass.” yes, sure, the problem is this is new; it wasn’t that way… and now having to wait 2+ years for this to settle is no good…

    ceo

  10. Pingback: C. Enrique Ortiz Mobility Weblog

  11. Jason Devitt says:

    I feel for you.

    Take a look at 4INFO’s ‘open platform’ – http://open.4info.net/.

    Don’t know if there’s any permissioning; i.e. anyone might be able to sign for your alerts if they know how. You may not care.

  12. Pingback: Mike Rowehl: This is Mobility » Blog Archive » Non-SMS Mobile Messaging

  13. Pingback: Mike Rowehl: This is Mobility » Blog Archive » Bye Bye T-Mobile

  14. Pingback: Mike Rowehl: This is Mobility » Blog Archive » Messaging, Widgets, IM …. IA?