61–70 of 77 posts
Can one of you please point me to their (previous is fine too) FORM-Ds? my search on edgar comes up with nothing https://www.sec.gov/cgi-bin/browse-edgar?company=message&own...
I see Whatsapp support on their website but I find this very strange, Whatsapp doesn't have an official API, only some hidden endpoints for their clients that can be changed at any time. https://www.messagebird.com/en/chat-api
Cool stuff, and as a Dutch chauvinist I like that a fellow Dutch startup does well. That said, I've looked at MessageBird a bunch of times but I still don't get it. What makes them different from all the other SMS gateways out there? It's the same product everywhere: you invoke some REST API, an SMS is sent to a number and you get billed.
Good question - but all these gateways have tendency to drop messages, report weird errors, messages are sometimes delayed by hours, their MMS support if quirky, etc. I.e., if you ever worked with Twilio you will learn about "30008 Unknown error" - Twilio support tries but because "Carrier Network" problems these problems cannot be fixed. In short, reliable delivery of SMS messages internationally is still not solved…
So how does MessageBird solve this...?
Earlier quoted context omitted.
Good question - but all these gateways have tendency to drop messages, report weird errors, messages are sometimes delayed by hours, their MMS support if quirky, etc. I.e., if you ever worked with Twilio you will learn about "30008 Unknown error" - Twilio support tries but because "Carrier Network" problems these problems cannot be fixed. In short, reliable delivery of SMS messages internationally is still not solved…
Do they use any tools to monitor sms reception on real SIM cards?
Wondering why the VCs are so keen on companies that seem to be re-doing something that's been done many times (almost commodity in the case of this company) and has essentially no proprietary technology and no network effect?
$100 million revenue per year will do that, I guess they do something better than the competition https://techcrunch.com/2017/10/03/messagebird/
Earlier quoted context omitted.
Good question. However, I'm rooting for them "We founded MessageBird in 2011 after experiencing firsthand how poor the quality of service of most communication providers was at the time". It's 2017 and the incumbent (Twilio) can't explain why I get delays in inbound SMSs. They blame it all the time on carriers, but if they can work directly with carriers to improve QOS while having Twilio-like ease of use they might…
The problem is that to get an SMSC that is respected by all of the operators requires a negotiation with an aggregator who has done contracts with all of the operators. The 2nd order problem is that you don't know the quality of the relationship an aggregator has with operators until you're a customer. All carriers have a prioritization in their SMSC's and, necessarily, no aggregator is in position 1 on all carriers.…
Earlier quoted context omitted.
Good question - but all these gateways have tendency to drop messages, report weird errors, messages are sometimes delayed by hours, their MMS support if quirky, etc. I.e., if you ever worked with Twilio you will learn about "30008 Unknown error" - Twilio support tries but because "Carrier Network" problems these problems cannot be fixed. In short, reliable delivery of SMS messages internationally is still not solved…
> In short, reliable delivery of SMS messages internationally is still not solved. So how does MessageBird solve this...?
Earlier quoted context omitted.
The problem is that to get an SMSC that is respected by all of the operators requires a negotiation with an aggregator who has done contracts with all of the operators. The 2nd order problem is that you don't know the quality of the relationship an aggregator has with operators until you're a customer. All carriers have a prioritization in their SMSC's and, necessarily, no aggregator is in position 1 on all carriers.…
We have secured direct relationships with 220 carriers globally essentially skipping the aggregators. That way in terms of support in almost all cases we can at least explain what happened with the message end to end.