Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alert user or require phone number validation on Twilio error #491

Open
jonespm opened this issue May 14, 2024 · 0 comments
Open

Alert user or require phone number validation on Twilio error #491

jonespm opened this issue May 14, 2024 · 0 comments
Labels
backlog Effort: 24+ Effort estimated at three or more days

Comments

@jonespm
Copy link
Member

jonespm commented May 14, 2024

If a phone number gets back a failure response from Twilio then we should prevent any new messages from going to that number until the number is verified again. I think the phone verification will help some of this but seems like some errors like 30003 can happen even after verified. Verification should catch some others though

Common Twilio errors are

  • 30003 - Unreachable destination handset
  • 21211 - Invalid 'To' Phone Number
  • 30006 - Landline or unreachable carrier

A sample workflow would be

  1. Twilio sends a error message
  2. User in database is flagged in a new column as having a problem with their number
  3. When user logs in they will see a banner indicating they have a problem with their phone and need to verify it in settings before receiving messages
  4. ROHQ won't send future texts to problem numbers

It sounds like error 30003 might also just be temporary. So I'm not sure how common this is. I see about 50 30003 messages in the last 30 days. Maybe this isn't something that's high priority

@jonespm jonespm added Effort: 24+ Effort estimated at three or more days backlog labels May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Effort: 24+ Effort estimated at three or more days
Projects
None yet
Development

No branches or pull requests

1 participant