It seems pretty easy (and cheap), but it seems like it has a lot of limitations that would bug me trying to use it in a real-world situation.
For example, you'd need to have a short display name to conserve characters on SMS, but email subscribers would see that short name as well. Also, having the SMS messages automatically prefixed is kind of annoying (but I understand why they do it).
Also, email subscribers get both the subject and body of the message, while SMS subscribers get just the subject. So that means you'll probably need to put a short URL at the end of the subject line, which of course would also show up in the email subject line and look ugly.
I think this is pretty awesome for internal things like notifying sysadmins or texting you every time you get a sale, but I don't know if I would use it for anything customer-facing.
It is only in the US, 5% of the mobile world market. With the Nexmo Amazon SNS lib you can reach the rest of the world without much change of your code. of course with a direct to carrier model that reduce cost and improve deliverability. Here is more info to get started: http://nexmo.zendesk.com/entries/20636661-get-international-...
For example, you'd need to have a short display name to conserve characters on SMS, but email subscribers would see that short name as well. Also, having the SMS messages automatically prefixed is kind of annoying (but I understand why they do it).
Also, email subscribers get both the subject and body of the message, while SMS subscribers get just the subject. So that means you'll probably need to put a short URL at the end of the subject line, which of course would also show up in the email subject line and look ugly.
I think this is pretty awesome for internal things like notifying sysadmins or texting you every time you get a sale, but I don't know if I would use it for anything customer-facing.