60006: Invalid Phone Number

Twilio returns this error when a Verify request includes a phone number that is correctly formatted, but a downstream provider identifies it as invalid. This usually means the number is not a valid, active destination even though it was submitted in E.164 format.

• The end user entered the wrong phone number.
• The to value is formatted correctly, but the number is deactivated, suspended, or in a grace period before reassignment.
• The number is fake, fraudulent, or otherwise cannot be validated by the downstream provider.
• If you use the sna channel, the downstream provider cannot confirm that the phone number is valid for the device or SIM involved in the verification.

• Ask the user to confirm the phone number before you send the verification. For initial verification flows, display the full phone number so the user can catch typos.
• Store and submit phone numbers in E.164 format when you create a verification.
• Validate the phone number with Twilio Lookup before you start the verification. Basic Lookup performs phone number validation, and Line Type Intelligence can help you confirm that the destination is a mobile number when your flow requires one.
• Support a backup Verify channel such as email for users who cannot complete a phone-number-based verification.
• If you use Silent Network Auth, retry the verification with a channel that does not depend on the phone number.

• Verifications API
• Verification Channels
• Lookup v2 Quickstart