Hacker News new | ask | show | jobs
by oogali 899 days ago
This is likely because of industry regulations around A2P (application-to-person ) messaging that had a due date of August 31, 2023.

It's not just Twilio, you would have experienced this with nearly every SMS API provider. Across the different vendors I work with, I received numerous emails from each one advising me to come into compliance or risk my messages being rejected.

https://help.salesmessage.com/en/articles/6650461-changes-to...

https://www.telgorithm.com/news/10dlc-registration-required/

https://support.referrizer.com/support/solutions/articles/10...

2 comments

> It's not just Twilio, you would have experienced this with nearly every SMS API provider. Across the different vendors I work with, I received numerous emails from each one advising me to come into compliance or risk my messages being rejected.

From what I can tell, the telcos aren't performing any enforcement, even tho the deadlines and extensions are long past. Not to say they won't but the endeavor seems to have a stall vibe going on.

Some of that might be related to having major mass-campaign requirements placed on small biz who occasionally send a handful of texts (often non-sales) from their workstation phone apps.

At least I hope this is why it has stalled. Sending a few texts during a customer service session shouldn't be regulated as if it were a blast of 1M SMS ads.

Had a good experience regarding this with one of the SMS API providers - Message Central.