Open jobannon opened 1 year ago
You should be able to either purchase a short code in Twilio, or import one you've obtained a lease for elsewhere, then set up a Twilio Messaging Service and attach the short code and any other numbers you want to send from to that Messaging Service. Twilio can map senders in the Messaging Service to different locales.
Then in FusionAuth, when you set up your Twillio Messenger under Settings / Messengers, just use the Twilio Messaging Service Id
instead of a From phone number
. The ID is the Messaging Service SID from Twilio.
It seems like this is all handled by Twilio - and is not related to FusionAuth?
We should document this.
Support Anti-Spam Measures in Twillio Integration
Problem
Some countries have implemented an anti-spam calling policy. A special shortcode is needed in these cases to allow a legitimate phone call/sms to proceed. This code is typically inserted into the From Phone number and then the call or SMS message is allowed to proceed.
Solution
Allow a FusionAuth lambda (so similar) to ingest the call information (and user consent status) that is requesting to send an SMS message, then based on the caller's origin apply a short code if appropriate.
Alternatives/workarounds
Accept that some SMS messages will not be sent in countries with anti-spam measures without applying the procedures required to be in compliance
Additional context
A consent-gathering feature may need to be built into FusionAuth as well.
Internal ticket 73107
Community guidelines
All issues filed in this repository must abide by the FusionAuth community guidelines.
How to vote
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.