It's not so much the willingness to eat shit, but that no matter the service I use, I will have to eat shit, so who's shit tastes least bad for the benefits.

A lot of VoIP/SMS providers exist, but compared to Twilio, they are just DIY API and SIP providers, which might be what we as developers want, but not what a business "needs".

Out of curiosity, what do you actually need out of a VoIP/SMS provider beyond "send and receive SIP" and "send and receive SMS"?

I'll give you that SIP is quite complex to deal with (aka the existing tooling around it is shit - the least shit is SipSorcery in C# but requires quite a bit of low-level code to get anywhere), but SMS is trivial as it maps nicely to HTTP's request/response paradigm. Just write whatever logic you want in a PHP/etc script, drop it on shared hosting, and enjoy better uptime (your shared hosting provider doesn't have the budget to keep paying techbros to constantly mess with the system, so it will be more stable).

It’s this. You went to a buffet but all they have is shit pie.

"Commode-ification" - when everything is shit, so it doesn't matter what you choose.

The conspiracy of service degradation: as long as every other provider sucks, the consumer never can expect better.

Alpha tested with lightbulbs but is now a clear strategy taught to MBAs