Live data from Hacker News

MessageBird raises $60M Series A

blog.messagebird.com

71–77 of 77 posts

Re: MessageBird raises $60M Series A

#71
post #49

Earlier quoted context omitted.

$100 million revenue per year will do that, I guess they do something better than the competition https://techcrunch.com/2017/10/03/messagebird/

Their market (sending SMS to consumers) is dying, replaced by app notifications.

It may be but probably not that soon since there are a lot of countries not on smartphones, some industries have multiple dominant players, and users may not want to deal with an app from each player, e.g., car dealers, etc.

Re: MessageBird raises $60M Series A

#72

Earlier quoted context omitted.

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.

To be clear, you are operating a SMSC and have signed SMSC interop agreements as a CLEC operator with 220 carriers globally?

I'd love clarity on this (specifically because it's hard for me to believe you've done smsc integration 220 times already).

Re: MessageBird raises $60M Series A

#73
post #64

Earlier quoted context omitted.

> In short, reliable delivery of SMS messages internationally is still not solved. So how does MessageBird solve this...?

see my comment above.

So that error doesn't exist in MessageBird? I don't get it. Is it not dependent on carriers as well? I'm asking how they technically do things differently that would absolve them from encountering that issue.

Re: MessageBird raises $60M Series A

#74

Earlier quoted context omitted.

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.

To be clear, you are operating a SMSC and have signed SMSC interop agreements as a CLEC operator with 220 carriers globally?

Yes, we run our own SMSC but in terms of functionality like routing and quality control we go way beyond what a normal carrier would be able to. CLEC is a US specific term and not needed to sign direct agreements with carriers. We operate our own SS7 stack, global titles and mobile network codes. This way we can interconnect with carriers as a carrier. Deploying an on-premise SMSC or E1's would be an old-school way of doing this. Most carriers use either Sigtran or connectivity through their SCCP provider.

Re: MessageBird raises $60M Series A

#75
post #73

Earlier quoted context omitted.

see my comment above.

So that error doesn't exist in MessageBird? I don't get it. Is it not dependent on carriers as well? I'm asking how they technically do things differently that would absolve them from encountering that issue.

When you connect directly to a carrier you get so called PTT codes back (industry standard). Not all carriers do this the same way but we standardize this and return them like shown at the link below. When your provider uses a lot of in-between providers its harder to return errors correctly. https://developers.messagebird.com/docs/smserrorcodes

Re: MessageBird raises $60M Series A

#76
post #43

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?

Yes - we run our own network of real sims for quality control that we only use for ourselves.
Post reply on HN