Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"Taking a wild guess – but is there a chance that people using Twilio as their personal phone provider are not their target customer group?"

I attended Signal 2018 and was told that (Twilio) "couldn't wait to see" what I built. I was handed IoT SIM cards and carrier SIM development kits and attended workshops and seminars exploring exactly these sort of use-cases.

I was also told by many highly placed individuals in product development that the CEO was personally enthusiastic about exactly these sort of use-cases.

So yes, I did some homework and made an attempt to align my incentives (I pay actual money for every SMS I send) with those of the company.

Now all of that has changed - in large part due to their own (bad) behavior.

"... I can kind of see how that's pushing the boundaries of the product a bit."

Agreed - that is my point and the source of my frustration.

Server alerts and (literal) fire alarms should not be a "campaign". If they are, I'm using the wrong tool.

If I need to define an opt-out message to SMS my kids, I'm using the wrong tool.

Twilio is explicitly telling us - loudly and emphatically - that they are the wrong tool.

I wanted telco infra. I got toys for children.



It looks like you still have this kind of capability. You might need to adjust settings and supply KYC info as requirements change. From the Fraud Guard docs, "You can mark known phone numbers using the Safe List feature so they are never blocked."




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: