SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Why Was My Toll-Free Verification Rejected?

Question

Why was my toll-free verification rejected?

 

Product

Programmable Messaging
 

Environment

legacy Twilio Console 

 

Answer

If your Toll-Free verification request fails for eligible reasons, you can correct and resubmit your request. For a full list of eligible rejection reasons see below.

If eligible,you can resubmit your Toll Free verification after correcting the identified content violation either via the Twilio Console or API.

If your verification is eligible for resubmission, you can edit your submission and resubmit it to Twilio for review. It's best to edit and resubmit within 7 days. When no edit is received within 7 days, the submissions will expire. An expired submission will be reviewed, but is no longer prioritized, so time to process is similar to a new submission. Continue on to find the category your rejection falls under and take the necessary action.

Notice: As of February 2026, we are seeing a high volume of rejections related to the following reasons due to new regulatory requirement needs.

Error Code Rejection Category Rejection Reason Correction Needed
30475 Invalid Opt-in Opt-in not sufficient: Cannot combine consent for messaging with requirement for service

Ensure your opt-in mechanism is not forcing the consumer to opt-in to messaging as a requirement of using your service.

  • Ensure your opt-in mechanism is a distinct action during a consumer's sign up for your service.
  • An opt-in call-to-action (CTA) with a checkbox must be unchecked by default.

Consent cannot be a requirement for your business's service. A business may not combine collecting a consumer's phone number with opting-in to receive marketing messaging. 

30498 Invalid Opt-in Opt-in workflow must match submission details

Verify the opt-in workflow description in your submission matches the actual opt-in example provided.

  • Update either the opt-in workflow description or the provided example to ensure consistency
  • Make sure your description accurately reflects your actual opt-in process
  • Provide examples that match the exact opt-in method you've described
  • Ensure all aspects of your submission align with your actual business practices
30509 Opt-in URL not accessible The URL provided for your opt-in example is inaccessible. 

Provide a publicly accessible URL that does not require login credentials

  • Verify the URL is functional and leads directly to the opt-in example before submission
  • Host the opt-in example on a public page specifically for verification purposes

If the opt-in process is behind authentication, provide screenshots instead

  • If using screenshots, ensure they clearly show the complete opt-in process
30521 Opt-in data sharing Opt-in data cannot be shared with third parties

Ensure your verification states that you do not share or sell mobile phone numbers, SMS opt-in data, or text messaging originator consent with third parties or affiliates for marketing or promotional purposes.

  • Remove all language that allows sharing opt-in data with third parties
  • If applicable  ensure to state mobile information may be shared only with service providers that assist in delivering our services.
  • Update your privacy policy and terms to include specific language prohibiting the sharing of consent:
    • "The above excludes text messaging originator opt-in data and consent; this information will not be shared with any third parties."
  • Ensure your business practices maintain consent as a direct 1:1 agreement between consumer and message sender
  • Make it clear that opt-in cannot be transferred or sold

 

Rejection types eligible for resubmission

Rejection codes that are eligible for resubmission can be resolved. Please take the corrective action(s) outlined in the linked error code(s) from table above, and then re-submit your Toll-Free Verification request with the updated information.

Error Code Rejection Category/Reason
30482 Business email must use an official domain
30483 Contact must be a business representative
30484 Business name and official records do not match
30485 Official business registration documents required
30487 Charitable organization must provide 501(c)(3) verification
30488 Doing Business As (DBA) name must be accurately provided
30527 Business Registration Number is missing or invalid
30489 Website must be established and active
30490 Social platform must be established and active
30491 Website is password-protected or requires login
30492 Business website URL must display branding
30493 Privacy policy or terms URL missing or inaccessible
30494 Independent Software Vendor (ISV) or reseller name must be provided
30495 Projected message volume exceeds use case limits
30496 Use case and use case summary are inconsistent
30497 Use case summary is incomplete
30498 Opt-in workflow must match submission details
30499 Message content doesn't align with use case
30486 HELP keyword response must meet requirements
30501 Political campaigns must have a Campaign Verify token
30502 Political campaigns must submit Federal Election Commission (FEC) ID
30503 Confirmation message missing required details
30504 Single opt-in cannot cover multiple use cases
30505 Opt-in must be optional, not mandatory
30506 Opt-ins must clearly reflect end business
30507 Opt-in does not match use case
30508 Pre-selected opt-in checkbox is not allowed
30509 Opt-in URL not accessible
30510 Opt-in example must be complete and branded
30511 Verbal consent script must be provided
30512 Age gate required for age-restricted content
30513 Opt-in not sufficient: language unclear
30515 Valid opt-in required for all submissions
30516 Double opt-in required for this use case
30517 Shopping cart reminders must follow specific guidelines
30518 Call-to-action missing required disclosures
30519 Privacy policy required for personal data collection
30520 Privacy policy mentions sharing opt-in data
30521 Opt-in data cannot be shared with third parties
30522 SMS terms must be accessible and compliant
30525 Public URL shorteners not allowed
30527 Business Registration Number is Missing or Invalid

 

Rejection types ineligible for resubmission

Each of the below rejection errors are due to forbidden messaging categories, and are therefore ineligible for resubmission. Please note that in addition to Toll-Free Messaging content restrictions, any use cases that violate Twilio's Acceptable Use Policy or Messaging Policy are also not allowed on Twilio's platform, regardless of number/sender type or destination country.

Notice: Users who disagree with their rejection can Contact Support to request an appeal. In your request, please include the original ticket number (if applicable), the details of your appeal, and the subject line "Toll-Free Verification Rejection Appeal for (your business name or number)".

Also, we now provide a "Delete" option in the Twilio Console and API for situations where you may have experienced a rejection in one of the categories below, but fully understand the reason for rejection and simply need to submit a new request. In such instances, you'd need to delete the rejected verification record on your Twilio account before you'll see the option to submit a new one. You can find more details on when or when not to use the delete option here.

Error Code Rejection Category/Reason
30440 Unknown Error
30441 Disallowed - SHAFT - Sex
30442 Disallowed - Spam
30443 Disallowed - Loan marketing
30444 Disallowed - Fraud
30455 Disallowed: SHAFT - Hate
30456 Disallowed - SHAFT - Alcohol
30457 Disallowed - SHAFT - Firearms
30458 Disallowed - SHAFT - Tobacco/Vape
30459 Disallowed - SHAFT - Cannabis/CBD
30460 Disallowed - Third party Debt Collection
30461 Disallowed - Gambling
30462 Disallowed - Sweepstakes
30463 Disallowed - Stock Alerts
30464 Disallowed - Cryptocurrency
30465 Disallowed - Risk Investment/Get Rich Quick Schemes
30466 Disallowed - Debt reduction
30467 Disallowed - Credit Repair
30468 Disallowed - Third party lead generation
30469 Disallowed - Illegal Substances/articles
30470 High risk - Third-party lead generation services and marketing: Deceptive marketing
30480 Disallowed - Phishing
30481 Customer Requested Cancellation
30523 High-risk domain reputation detected
30524 Potential fraud risk identified
30526 High-risk domain issues
30528 Disallowed: Non-federally compliant use case
30529 Disallowed: Alcohol promotions without age verification

Additional Information 

What happens to my verification if my Toll-Free number is rejected?

If your Toll-Free number is rejected for one of the reasons listed in the Rejection types eligible for resubmission table above, you will have up to 7 days to provide an amended submission with the information / changes requested, which allows you to keep your spot in line. After 7 days, if your Toll-Free number submission is not amended it will expire and you will lose your spot in line. You can still edit and resubmit an expired submission, but will no longer be prioritized, so the time to process is similar to a new submission.

If your Toll-Free number is rejected and is listed in the Rejection types ineligible for resubmission table above, your Toll-Free number will not be able to send messages and your traffic will be blocked with a 30032 error.

 

How do I remediate my verification with Business Registration Number related rejections?

If your Toll-Free number is rejected with a 30527 error. Edit your submission by removing the the fields listed below and resubmitting:

 

Business Registration Number
Business Registration Authority
Business Registration Country
Business Type

 

My verification request was rejected, and is ineligible for resubmission - What can I do?

If your Toll-Free Verification request was rejected and is ineligible, you may be able to use another Twilio product to reach your recipients.

The Twilio Sendgrid Email API is an option for many of the above use cases. For example, cannabis- or CBD-related messaging may be conducted via email, as long as you have proper age gating in place and are sending toward recipients in a locale where the substance is legal. In addition, the Twilio Programmable Voice product is not subject to the same carrier restrictions as SMS.

For more information about cannabis-related messaging alternatives, see Can I send cannabis or CBD-related messaging traffic on Twilio.

Have more questions? Submit a request
Powered by Zendesk