You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Twilio sends a error message
User in database is flagged in a new column as having a problem with their number
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
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
The text was updated successfully, but these errors were encountered:
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
A sample workflow would be
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
The text was updated successfully, but these errors were encountered: