Live data from Hacker News

Introducing Worldwide SMS Messaging

mobile.awsblog.com

1–10 of 66 posts

Re: Introducing Worldwide SMS Messaging

#5
Excellent news - I have been waiting for this for a while.

NOTE: Seems to be having issues sending SMSs to Australian mobile numbers - I've been tweaking and sending on the dashboard for a while now and nothing is coming through. Never mind - early days yet.

Am surprised at the cost differences between countries too - seems to be a lot more expensive than other third part SMS services I am using at the moment. (Comparatives - .009 cents for most US carriers, and 19 cents for most Aussie carriers!)

Re: Introducing Worldwide SMS Messaging

#8
post #7

Marginally cheaper than Twilio for USA: $0.00645 vs. $0.0075 Much more expensive in Europe (e.g. major networks in Poland Twilio $0.03467, AWS $0.03897 - 0.07711) https://www.twilio.com/sms/pricing http://aws.amazon.com/sns/sms-pricing/

Clickatell is compatible to twillio and they have a nice validation api

https://www.clickatell.com/detailed-pricing-and-coverage/

Re: Introducing Worldwide SMS Messaging

#9
post #4
post #3

I wonder how this will affect newly IPOed twilio

Considering it does NOT look to support inbound or voice probably very little impact. (edit) i some how always forget the most important NOT operators.

Low impact in the short term, potentially huge impact in medium term (1-2 years). The pattern for other AWS services is that they will drive down price until they are low price provider and quickly close feature gaps. Adding inbound to SMS seems like a natural next step.

Also, SMS is a substantial part of Twilio's business. Even though Twilio has been adding new extensions to their product, the majority of usage is tied to a small set of API calls.

Twilio now has a company with a huge developer audience going straight after their core business. One that is willing to be very aggressive on price to win share.

Re: Introducing Worldwide SMS Messaging

#10
Really nice to have precise SMS delivery reports automatically pushed to Cloudwatch Logs. Makes it fit very nicely into the whole AWS offering (eg. automatically trigger a Lambda function to act upon a failed delivery).
Post reply on HN