from Hacker News

Ask HN: Preferred SMS API Provider?

by llmblockchain on 7/22/24, 6:02 PM with 14 comments

I'm looking to replace Twilio, because I've never had a good experience with them. I'm looking for an API that is simple to get working and doesn't require a bunch of hoops to jump through (manual reviews, paying for verification and paying for every re-submission is not okay).
  • by fasteo on 7/22/24, 6:47 PM

    >>> manual reviews, paying for verification and paying for every re-submission is not okay

    If you are referring to senderID registration (or 10DLC in the US), then things are getting really complicated thanks to the increase in smishing and the government regulations trying to stop it. In many countries, there is a significant amount of paperwork - and sometime fees - to do to allow your traffic to flow. Along with this, SMS margins have been really tight in the last 4-5 years (think 2%-3%), so these companies need to charge you for this paperwork and many times the rejections are not coming from them, but from the telco regulatory authority in a given country.

    source: running a SMS service for the last 20 years.

  • by tripue on 7/22/24, 6:04 PM

    Hey! We might be able to help, built prelude.so for exactly that reason and many other (fraud prevention, multi-routing...). We had to built an internal solution for this back at Zenly which pushed us to create this tool!

    What is your main use case?

  • by smswhiz on 7/23/24, 3:45 PM

    Telgorithm is a good SMS API provider alternative, can't bypass registration/compliance but the process is hands on so you get help every step of the way and direct access to the technical team so you can avoid rejections/mistakes an not have to go through/pay for re-submission. Telgorithm typically sees Campaign approvals in 72hrs for customers. I'd check it out!
  • by ops3936 on 7/22/24, 6:16 PM

    I have been using Inteliquent, now part of Sinch. You can’t avoid campaign and vetting fees for any A2P traffic now.
  • by howon92 on 7/22/24, 6:14 PM

    What problems did you have with Twilio?