3 ms·
Yeah this sounds highly problematic. Maybe in the meantime you can text links to your own portal instead. I.e. "New SMS received from +123... . Read it at: http
by madars 5y ago
Yeah this sounds highly problematic. Maybe in the meantime you can text links to your own portal instead. I.e. "New SMS received from +123... . Read it at: https://your-internal-infrastructure.com/sms/[GUID] https://your-internal-infrastructure.com/sms/[GUID]" (maybe with a simple login so Twilio auto-fetch, if any, gets a benign page). That way there is no spammer-controlled message content (apart from the phone #) in the message you send. Or convert them to jpeg and send as MMS hoping that Twilio won't OCR that :D
- ChrisDutrow 5y agoYes, these are very good ideas. Didn't even think of the JPEG one, very cool!
- flippy_flops 5y agoAt a high enough volume, links will also get you blocked by carriers
- secabeen 5y agoYeah, we pass all of our twilio messages to our staff via a special Slack channel.
- ChrisDutrow 5y agoWhich pricing tier do you use? I've been thinking of starting with the for a while. Now we use a hodgepodge of Skype and WhatsApp
- throwaway220107 5y ago
- secabeen 5y agoFor which, Slack or Twilio? We have a basic twilio account, paying $1/mo for the phone number, and $0.1/msg or whatever it is. 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).
- laurensr 5y agoOr base64 encode the orginal message :p
- ChrisDutrow 5y agoIt needs to be human readable, so maybe pig latin instead