Flowroute is $.004 https://www.flowroute.com/sms/faq/
Introducing Worldwide SMS Messaging
41–50 of 66 posts
Re: Introducing Worldwide SMS Messaging
#42When I did programmatic SMS for a project ~10 years ago, I just used SMTP and the email equivalent of the SMS address. I haven't done similar projects since then, so I'm curious if there is some reason that approach would no longer work.
In addition to having to know the carrier, the text message itself sometimes includes email-style metadata (like FROM, SUBJECT, MESSAGE, etc) that varies by carrier, so its difficult to control the experience. Its one of those things thats good for a personal project but not for a service that sends lots of text messages to users. I didn't know this until I just tried it, but doing it over email supports replies (at…
In the app I had built (for NBA) I think we just asked people for their carrier name. Or we may have used a lookup service - I don't recall.
Re: Introducing Worldwide SMS Messaging
#43Marginally 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/
Considering that Twilio hosts with AWS, that will be a tough price war for Twilio to win.
Can we contrast the aggressive Amazon platform vs customer dynamic with other cloud providers?
Why would a new company opt for Amazon at the risk of being copied and competed with as we're seeing with Netflix, Twilio, and numerous Amazon store vendors? Why not go with Google or Microsoft?
Re: Introducing Worldwide SMS Messaging
#44Earlier quoted context omitted.
Considering that Twilio hosts with AWS, that will be a tough price war for Twilio to win.
Can we contrast the aggressive Amazon platform vs customer dynamic with other cloud providers? Why would a new company opt for Amazon at the risk of being copied and competed with as we're seeing with Netflix, Twilio, and numerous Amazon store vendors? Why not go with Google or Microsoft?
Think like a customer.
Netflix has a lot of customers, IMO because they developed great recommendation IP, they have a large content library, and have invested heavily into customer acquisition and marketing to build a consumer brand.
Netflix will use AWS infrastructure if it benefits their business and go elsewhere if it doesn't. The fact that the two companies compete in some ways is pretty much irrelevant to Netflix's (operational) decision of hosting provider.
Re: Introducing Worldwide SMS Messaging
#45Marginally 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/
Considering that Twilio hosts with AWS, that will be a tough price war for Twilio to win.
Twilio's cost structure is probably dominated by SMS charges from telco operators and customer acquisition, not their AWS bill. So I doubt it, but feel free to cite data that shows I'm wrong. (I read their s-1 and I don't think it got into that granularity of cost accounting)
Re: Introducing Worldwide SMS Messaging
#46Marginally 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/
They need to fix many things, it doesn't seem they have a good knowledge and experience on the sms messaging world. 1) have a specific price for every single network makes it impossible to calculate which will be the final real cost for each country 2) it's crazy expensive outside the US. Every player in the SMS industry is 4x lower on average. IE: http://www.mailup.com/pricing/sms/ 3) they don't support text as a se…
> 3) they don't support text as a sender. In many countries you can have "MyCompany" as a sender instead of a generic number or short code. This makes the communication much more effective.
They do support it in some countries [1]:
> AWS.SNS.SMS.SenderID > A custom ID that contains up to 11 alphanumeric characters, including at least one letter and no spaces. The sender ID is displayed as the message sender on the receiving device. For example, you can use your business brand to make the message source easier to recognize.
> Support for sender IDs varies by country. For example, messages delivered to U.S. phone numbers will not display the sender ID.
> If you do not specify a sender ID, the message will display a long code as the sender ID in supported countries. For countries that require an alphabetic sender ID, the message displays NOTICE as the sender ID.
[1]: http://docs.aws.amazon.com/sns/latest/dg/sms_publish-to-phon...
Re: Introducing Worldwide SMS Messaging
#47Earlier quoted context omitted.
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 t…
Yes -- this is why it seems risky to invest in Twilio long-term.
Sure, they have the developers today, but if WhatsApp leaves, and Amazon can cross-sell more of their existing customers what they'd otherwise get from Twilio, that's a big problem long-term. Twilio has a bit of a moat with their carrier/provider relationships, but that won't hold up against Amazon's entry.
Time will tell, I guess. The stock has been going crazy the past few days, though
Re: Introducing Worldwide SMS Messaging
#48Earlier quoted context omitted.
Considering that Twilio hosts with AWS, that will be a tough price war for Twilio to win.
Twilio's cost structure is probably dominated by SMS charges from telco operators and customer acquisition, not their AWS bill. So I doubt it, but feel free to cite data that shows I'm wrong. (I read their s-1 and I don't think it got into that granularity of cost accounting)
But they also spend a bundle with AWS... Amazon can reach the same pricing with the telcos, but will have lower infrastructure costs. Twilio would honestly be a good acquisition for AWS, but maybe Bezos feels like doing it himself.
Re: Introducing Worldwide SMS Messaging
#49Earlier quoted context omitted.
Considering that Twilio hosts with AWS, that will be a tough price war for Twilio to win.
Can we contrast the aggressive Amazon platform vs customer dynamic with other cloud providers? Why would a new company opt for Amazon at the risk of being copied and competed with as we're seeing with Netflix, Twilio, and numerous Amazon store vendors? Why not go with Google or Microsoft?
Because it works? Apple still spends billions buying parts from Samsung, even while locked in a patent infringement lawsuit.
Re: Introducing Worldwide SMS Messaging
#50India pricing is atleast twice the price of any decent SMS provider in the country at 0.0045 USD per transactional SMS.
Do you know any good SMS providers for India with a nice API? I am looking for one and can't decide which one is good.
We've been using SMS Gupshup and are pretty happy with their services.