How to solve Programmable SMS API Delivery issues
SMS delivery and connectivity issues is on the rise from many CPaaS Providers. I have experienced it first hand, I even tested popular CPaaS providers like Twilio, Nexmo again 5 minutes prior to writing this blog post. After many years of trying different CPaaS providers we realized that none of these popular CPaaS providers is a perfect solution to be the only connectivity option. The reason for this issue is not caused by Twilio’s platform it self, the reason can be an aggregator that Twilio uses causing such issues. Until Twilio interconnects with every single MNO in the world this issue is here to stay.
As a developer or organization relaying on CPaaS Platform like Twilio, Nexmo or Plivo, switching from one CPaaS Provider to another as not a good solution.
Each CPaaS provider have their strength and weaknesses specially on the carrier connectivity side of things and also pricing. For example while Twilio is strong in North America, Nexmo is stronger in EU and Unifonic is strong in KSA and so on, so what now, who wants to integrate with many different APIs, SDKs in one application “YUCK!”.
To solve this problem developers need a CPaaS (Communication Platform as a service ) API that allows them to Bring their own carrier connectivity for the routes where they have most traffic on and where Twilio fails to deliver great quality and connectivity.
Unfortunately Twilio and other CPaaS providers do not provide this sort of functionality at this moment, until they do here is some solutions. Continue reading…