If twilio wants us to start filtering spam messages for these cases, they need to give us the API/tooling.
Or let us pre-register receiving numbers through an opt-in process.
I understand Twilio not wanting to be an open relay but the reported solution is not the way.
It's probably a good idea for twillio to be more reachable to any paying customer, at least until a human employee makes the determination if the customer is a spammer.
I also understand and agree with your argument about why they might have done what they did. But I still needed to counter with what I did in order to protect my business.
On Slack, we have a paid account at the standard level, we've had that for years.
One note, both Google and Apple detect that our number is Twilio, and won't let us use it for 2FA, sadly (our original use case).
If they can’t update the integration with spam filtering, then it seems like they should be using COTS software.
Also, there are other ways to solve this specific problem given that they are intent on auto-suspending my account in this type of context. I could relay the messages using a different platform as an example.
Thats not really the point though. Me not paying for the spam API or not using it when I relay messages internally to employees is not a good reason to shut my whole business down and not give me a way to contact them. This should be obvious.
I guess if twilio has negative impacts as a result of the perceived spam then that's a separate issue.