4 ms·
If someone has already written a custom integration, how hard can it be to wire it up to a spam detection API? It sounds like the integration was sending spam (
by jdavis703 5y ago
If someone has already written a custom integration, how hard can it be to wire it up to a spam detection API? It sounds like the integration was sending spam (not intentionally of course), which none the less is a TOS violation.
If they can’t update the integration with spam filtering, then it seems like they should be using COTS software.
- ChrisDutrow 5y agoI'm already using a spam detection API. But remember those things don't block all spam. 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.
- foota 5y agoIs sending an employee a message they've elected to receive ever spam in some sense? If the reflection were to an arbitrary number then I'd say so, but simply forwarding to a specific number you're working with seems... Fine. Maybe it's different too if it's a solution you're selling, but even then that's somewhat between you and the customer. I guess if twilio has negative impacts as a result of the perceived spam then that's a separate issue.
- Nexxxeh 5y agoIt was only spam on the inbound leg. On the outbound leg, it was requested and correct content.