OTP_TWILIO_MESSAGING_SERVICE_SID setting #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Definitely. The setting just needs documentation. |
|
@psagers cool I'll commit doc changes when able |
|
@psagers added a section in the docs and tried to keep the same formatting style |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed
OTP_TWILIO_MESSAGING_SERVICE_SIDsetting that, when provided, sends from the designated Twilio messaging service and lets Twilio pick the sender SMS number instead of providing a single number.Twilio docs
We recently ran into an issue with sending OTP codes to UK (+44) numbers with our toll-free US number - UK providers have blocked SMS messages from US long code numbers. It looks like the way around this is to send from a messaging service with numbers from multiple regions.