Question
Why was my toll-free verification rejected?
Product
Programmable Messaging
Environment
legacy Twilio Console
Answer
A rejected Toll-Free Verification request means the review found an issue with your business information, messaging use case, consent process, or supporting evidence. Start with the Twilio error code and rejection details returned for your request. Correct every issue listed before submitting updated information.
What changes on September 15, 2026?
From September 15, 2026, more specific rejection codes identify individual issues, including missing Call-to-Action (CTA) disclosures, missing Terms of Service disclosures, and incomplete consent evidence. New codes are shared with A2P 10DLC where the rejection meaning matches. Some existing error meanings and corrective instructions also change for this release.
The guidance below is written for rejections under the September 15 release. For an earlier rejection, use the details supplied with that decision or contact Support. Use the code you received; do not substitute another code because its title looks similar.
Existing codes with updated guidance
| Code | September 15 meaning or correction |
|---|---|
| 30448 | Correct the age-restricted declaration; actual age-gate failures remain separate. |
| 30475 | Messaging consent is bundled with another agreement; mandatory service consent remains 30505. |
| 30493 | Correct missing, inaccessible, or incomplete Terms of Service. Privacy Policy issues are separate under 30536. |
| 30501 / 30502 | Use 30501 for a supplied invalid/unverifiable token and 30502 for a missing required Campaign Verify token. The FEC/state committee ID is separately identified by 30541. |
| 30530 | Correct a legal-entity mismatch; do not read this as a generic request for registration documents. |
What should I do first?
- Open the rejected verification request and read the error code and full rejection details.
- Find the code below and review its linked error page. A request may require more than one correction.
- Correct the actual information or messaging process. Update the website, consent flow, documents, and message samples where applicable so they agree.
- Provide evidence showing the complete corrected flow and submit the request for review where resubmission is available. If the option is unavailable, contact Support with the verification details.
Review the Toll-Free Verification Onboarding Guide for the complete submission requirements and examples.
Can I correct and resubmit?
For the Toll-Free denial reasons in this article, corrected or misclassified submissions can be resubmitted for review. Resubmission does not authorize prohibited messaging. If the actual content or use case is prohibited, you must not continue that messaging or change only its description to obtain approval. If you believe the classification is incorrect, provide evidence explaining the error.
Cancellation and account/profile errors have their own next steps. Follow the applicable row and the status of your request.
When your request is eligible for editing, correct it promptly. The existing review process gives you seven days to amend a rejected submission while retaining its review priority. After that period, the submission expires and loses priority; you can still provide corrections for a new review.
Common distinctions that prevent repeat rejection
- CTA versus Terms: A disclosure in your Terms of Service does not replace a disclosure required where the customer gives consent. CTA name, rates, and support errors are 30568, 30569, and 30570; the corresponding Terms errors are 30557, 30562, and 30560.
- Missing versus inaccessible evidence: 30543 concerns a missing live link where that method requires one. 30509 concerns an inaccessible supplied opt-in URL. Use the evidence accepted for your actual opt-in method.
- Missing versus noncompliant opt-out: 30547 means CTA opt-out instructions are absent. 30539 means instructions are present but do not meet requirements.
- Declaration versus age gate: 30448 concerns the age-restricted declaration. 30512 concerns the actual gate, and 30529 concerns the alcohol-specific gate requirement.
- Consent versus other agreements: 30475 concerns consent bundled with another agreement; 30505 concerns mandatory messaging consent to obtain a service.
Find your error code
Search this article for the exact number. The tables summarize the correction; select the linked code for its complete conditions and requirements. A different related code does not automatically replace the code returned for your request.
Submission status and profile checks
| Error code | What it means | What to correct or check |
|---|---|---|
| 30437 | Submission Editing Timed Out | Correct the requested information and resubmit. An expired submission no longer retains its review priority. |
| 30440 | Toll Free verification rejection - Unknown Error | Read the rejection details and contact Support if the reason is unclear. Include the verification identifier and the full error message. |
| 30447 | Number not provisioned to your Organization | Reach out to the porting department to make sure the phone number is properly provisioned and resubmit the Toll-Free Number |
| 30451 | Toll-Free phone number verification unable to process - address invalid | Correct the invalid address in the associated customer profile and retry the affected request. |
| 30452 | Toll-Free phone number verification unable to process - email invalid | Correct the invalid email in the associated customer profile and retry the affected request. |
| 30481 | Submission canceled at your request | The submission was canceled at your request. Contact Support if the cancellation was unintended; cancellation is not a content-denial eligibility decision. |
Business identity, website, and use case
| Error code | What it means | What to correct or check |
|---|---|---|
| 30445 | Business Information Could Not Be Verified - Contact, Email, Address, or URL Is Invalid | Please update the information so it matches (business name, corporate website and email domain). Any mismatch on the information or confusing details can cause this denial. |
| 30472 | Business Registration Details Are Missing or Invalid | Provide a valid Business Registration Number that can be verified. Ensure all required fields (Entity Type, Business Registration Type, and Issuing Country) are accurately completed. Confirm that the submitted details align with official business records. |
| 30473 | Invalid or Inaccessible Website URL | Ensure the URL is correctly spelled and properly formatted. Provide a website with an active and accessible domain. |
| 30474 | End Business Details Must Be Accurate and Complete | ISVs must register each client through an individual submission with a dedicated Toll-Free number (no shared numbers). All submitted business details, message content, and opt-in branding must belong directly to the end-client, not the ISV. |
| 30478 | Toll-Free Number Cannot Be Shared Across Multiple Businesses | Assign a different Toll-Free number for each business |
| 30479 | Additional Information Requested - Insufficient Justification for 5+ Numbers | Please provide a comprehensive justification in the additional information field for requiring more than five numbers for a single business. If requesting multiple Toll-Free Numbers (TFNs) for various branches, include the specific details for each branch utilizing a TFN. This is not required if all numbers operate from a single business location. Ensure this distinction is clearly stated in your justification, as maintaining accurate business records is mandatory. |
| 30482 | Business contact email cannot be verified as associated with the business | Use an official business-domain email where available. A free-provider address may be considered if its association with the business can be verified; provide the supporting evidence. |
| 30483 | Contact Name Must Belong to a Business Representative | Provide the full first and last name of an authorized business representative. Ensure that the person listed holds an official role in the business. |
| 30484 | Business Name Must Match Official Records | Update the business name to match the name displayed on the website or other official documentation. Update DBA field and provide additional supporting documents if the business operates under multiple names. |
| 30487 | Charitable Organization Must Be 501(c)(3) and Provide Valid Accreditation URL for donation solicitation | Ensure the organization is a registered 501(c)(3) nonprofit. Provide a valid accreditation URL from a recognized nonprofit accreditation source (e.g., BBB Wise Giving Alliance, Charity Navigator, GuideStar). Verify that all submitted details match official records. |
| 30488 | Doing Business As (DBA) Name Must Be Accurately Provided | If the business operates under a DBA name, update the DBA field with the correct trade name. |
| 30489 | Website Must Be Established and Active | Submit a fully developed/functional website with clear business information, services offered, and contact details |
| 30490 | Social Platform Must Be Established and Active | Submit a more established social media account or a functional business website. Ensure the account includes posts, business information, and activity that establish legitimacy. |
| 30491 | Website Is Password Protected or Requires Login | Provide a publicly accessible website that allows verification of business information. If the website cannot be made public for security reasons, submit a screenshot displaying the necessary business details. |
| 30492 | Business website URL must display branding | Submit a URL that includes the business name and provides clear branding. Ensure the website displays the company name, logo, or other identifiable |
| 30494 | Independent Software Vendor (ISV) or Reseller Name Must Be Provided | Update the ISV/Reseller field with the correct details |
| 30495 | Projected Message Volume Exceeds Use Case Limits | Provide a detailed justification for the requested volume, including the target audience, frequency of messages, and type of content being sent. |
| 30496 | Use Case and Use Case Summary Inconsistent | Ensure that every messaging type included in the Use Case field is described in the use case summary If more than one use case was selected (promotional and informational) include a brief description for each type of messaging |
| 30527 | Business Registration Number Is Missing or Invalid | Please provide a valid Business Registration Number that can be verified Ensure the business name and Business Registration Number align character-by-character with the official business documentation to avoid mismatches. If the Business Registration Number provided is accurate, please provide an official document that certifies a business’s legal registration and authorization to operate within a specific jurisdiction. The official document must include the business’s name, registration number, and date of incorporation. If the Business Registration Number is for a political candidate and/or organization, please be sure that it matches the number on file with Campaign Verify. |
| 30530 | Entity Misclassification (Legal Entity Type Mismatch) | Please provide valid business registration information matching your official legal entity type, or update your entity selection to match your corporate records. |
| 30915 | BRN Validation Failure: Invalid Sole Proprietorship Classification | Please resubmit with correct legal details matching your actual corporate registration records. |
Consent, opt-in evidence, and messaging details
| Error code | What it means | What to correct or check |
|---|---|---|
| 30446 | Marketing Messages Require Express Written Consent | Update the opt-in process to require users to provide explicit written consent for marketing messages. Clearly label the opt-in as related to marketing messages and include language stating the user is agreeing to receive promotional communications. |
| 30448 | Age-gated program not identified in submission | Correct the age-restricted classification in the verification submission, including AgeGatedContent when using the API. An actual missing or inadequate gate is covered by 30512; an alcohol-specific gate failure is 30529. |
| 30475 | Messaging consent is bundled with other agreements | Collect messaging consent separately from other agreements. Accepting Terms, a privacy policy, or an account agreement must not also enroll the customer in messaging. Mandatory service consent is a separate 30505 issue. |
| 30476 | Opt-in - No opt-in provided | Please provide the opt-in URL or attach the image to the submission. |
| 30477 | Opt-In Consent Cannot Be Reused or Shared Across Programs | Ensure that consent is collected directly by the end business from the users they will contact. Clearly specify the business collecting the consent and the messaging purpose in the opt-in process. |
| 30486 | HELP Keyword Response Must Meet Compliance Requirements | Configure the automatic HELP reply with your business/brand name, a working support contact, a rates disclosure, and opt-out instructions. Provide the corrected response for review. |
| 30498 | Opt-In Workflow Must Match the Submission Details | Update the Opt-in Workflow description or the opt-in provided for accuracy and consistency Ensure that the described opt-in workflow matches the opt-in provided |
| 30499 | Message Content Does Not Align with Use Case or is Incomplete | Update the production message content to accurately reflect the approved use case Ensure all required message details are included and complete (e.g., Brand/Business Name) |
| 30501 | Political messaging: Campaign Verify token is invalid or unverifiable | Check that the supplied Campaign Verify token is active, matches the political entity and business registration details, and was issued for Toll-Free messaging. A missing required token is 30502. |
| 30502 | Political messaging must provide a Campaign Verify token | Provide the missing required Toll-Free Campaign Verify token for the political entity. A supplied invalid or mismatched token is 30501. |
| 30503 | Confirmation Message Missing Required Details | Please update the opt-in confirmation message to include the following elements: Program name or product description Customer care contact info (e.g., phone number, HELP command) Opt-out instructions (e.g., 'Reply STOP to opt out') Message Frequency (e.g. Recurring or Msg freq may vary) Pricing statement (e.g., 'Msg & Data rates may apply') |
| 30504 | Single Opt-In for Multiple Use Cases Is Not Allowed | Provide separate opt-ins for each use case (e.g., promotional, informational). Clearly describe the purpose of each opt-in and the type of messages users will receive. |
| 30505 | Agreeing to Receive Messages Must Be Optional | Update forms to ensure users can complete their desired action without opting in to receive messages. Clearly indicate that messaging consent is optional and unrelated to the primary action. If using a checkbox to collect consent, the disclosure text must explicitly tie consent to checking the box, rather than secondary actions like submitting the form, entering a phone number, or clicking a button |
| 30506 | Opt-Ins Must Clearly Reflect the End Business | Submit an opt-in that shows the end business’s branding and language, explicitly indicating the user is opting in to messages from the end business, not the ISV |
| 30507 | Opt-In Does Not Match the Use Case | Ensure the opt-in explicitly matches the use case described in the submission (e.g., “This opt-in is for account updates only” for an informational use case) Update the opt-in text or submission details to align with the intended use case |
| 30508 | Opt-In Checkbox is Pre-selected | Remove all pre-selected options from your opt-in forms. Require users to actively select or confirm their consent (e.g., checking a box, typing “Yes”). |
| 30509 | Opt-In URL Not Accessible | Provide a working, publicly accessible URL to the opt-in evidence. For an accepted authenticated or offline consent method, supply hosted evidence that reviewers can access without credentials. |
| 30510 | Opt-In Example Must Be Complete, Branded, and Legible | Submit a complete opt-in example that includes all text, buttons, branding (e.g., company name or logo). If consent is collected ia webform it must have a phone number field Ensure the opt-in clearly identifies the business collecting consent. |
| 30511 | Verbal Consent Script Must Be Provided for Approval | Submit a script or simulated conversation showing the exact language used for obtaining verbal consent. Include instructions for how users can opt-out after providing consent. |
| 30512 | Age Gate Not Present or Does Not Meet Requirements | Implement a robust age gate that verifies users meet the required age. Acceptable methods include: Requiring users to enter a date of birth (MM/DD/YYYY) before accessing content. Using a third-party age verification service. Resubmit once a compliant age gate is in place. |
| 30513 | Opt-in language is missing, unclear, or buried in other agreements | Update the opt-in form to include clear, unambiguous language where users explicitly agree to receive SMS communications. Do not bury the texting consent inside general Terms of Service or Privacy Policies. It needs to be a separate, standalone statement. |
| 30515 | Opt-in relies on organizational or government exemption. Valid Opt-in is required for all toll-free submissions | Provide evidence of valid opt-in for the actual messaging use case. Do not rely on an organizational or government exemption in place of consent. |
| 30516 | Double Opt-in Required for Intended Use Case | Set up a two-step confirmation process. Once a user gives the initial agreement to receive SMS, A double opt-in SMS must be sent asking them to reply with a specific keyword (like "YES" or "START") to confirm their consent before any actual campaign messages are sent. |
| 30517 | Shopping Cart Reminder Programs Must Comply with Opt-In, Privacy, and Messaging Standards | To ensure compliance please ensure your shopping cart reminder message program complies with the following requirements: Mandatory Double Opt-In: Requires a text-based double opt-in confirmation before sending reminders. Tracking Disclosures: State in your Terms/Privacy Policy how you link or identify a consumer's telephone number to an abandoned shopping cart (e.g., cookies, plugins). CTA & Terms Updates: Include shopping cart reminders explicitly in your Call-to-Action (CTA) and terms. Send Limits & Window: Limit to exactly one reminder per unique abandoned cart, sent strictly within 48 hours |
| 30518 | Call-to-Action Missing Required Disclosures | Please update the CTA details to include the following mandatory disclosures: Business name Message purpose/type: Marketing, promotional, 2FA Message frequency disclosure for recurring programs: "Message frequency varies" Pricing disclaimer: “message and data rates may apply” Opt-Out Instructions: "Reply STOP to opt out"- Help instructions "Reply HELP for help" Terms of Service (ToS): A direct hyperlink Privacy Policy: A direct hyperlink |
| 30531 | Toll-Free verification rejection - HELP keyword response must meet requirements | Review and correct the automatic HELP reply using the requirements on the linked error page. Use the code actually returned in your rejection; a related HELP error may appear as 30486. |
Terms of Service and Privacy Policy
| Error code | What it means | What to correct or check |
|---|---|---|
| 30493 | Terms of Service URL Is Missing, Inaccessible, or Lacks Content | Ensure a valid, working URL to the website's Terms of Service is provided. The page must be fully accessible to the public and must contain the appropriate SMS disclosures regarding rates, frequency, and opt-out commands before the submission can be re-evaluated. |
| 30519 | Providing an active privacy policy URL is required | CTA Inclusion: Include an accessible Privacy Policy link in your Call-to-Action (CTA) disclosures. Data Usage: Disclose what data is collected and how it is used. No Third-Party Sharing: Explicitly state that mobile data and opt-in consent will not be shared with third parties for marketing. Cart Tracking: If using shopping cart reminders, detail how web sessions and cart states are tracked. |
| 30520 | Privacy Policy Mentions Sharing of Personal Data with 3rd parties for marketing purposes | Update the privacy policy to include a clause associated with the business's messaging program that excludes the sharing of text messaging opt in data such as: "All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties." |
| 30521 | Opt-In Data Cannot Be Shared, Transferred, Rented, or Sold to Third Parties | Remove all language that allows sharing opt-in data with third parties. Update the policy to include the following disclosure (or similar): “The above excludes text messaging originator opt-in data and consent; this information will not be shared with any third parties.” |
| 30522 | The terms and conditions details are missing/ incomplete/not accessible | Ensure the terms and conditions include the following elements: Program or business Name. . Message Frequency: "Message frequency may vary" for recurring programs Product Description Customer contact Info: Accessible customer care contact information (such as an email address, phone number, or HELP keyword instructions). Opt-Out Information: Clear cancel or opt-out instructions (such as the STOP keyword), "Message and data rates may apply" disclosure: Carrier Liability Disclosure: State that Wireless carriers are not liable for delayed or undelivered messages Proximity of Legal Links: Direct text links labeled explicitly as Terms of Service and Privacy Policy must be placed within close proximity of the Call-to-Action (CTA)/opt-in section. Hiding these links inside separate pop-up windows, dropdowns, or far away from the phone collection field is not permitted. Ensure that the link is publicly accessible and active |
Content, URL, and risk reviews
| Error code | What it means | What to correct or check |
|---|---|---|
| 30441 | SHAFT Violation – Sexually Explicit or Inappropriate Content Is Prohibited | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30442 | High Risk - Known Spam Campaign | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30443 | Disallowed Content - Loan Marketing | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30444 | High Risk - Submission Contains Fraudulent or Misleading Content | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30449 | Toll Free verification rejection - URL issues in sample message | Correct the sample-message URL issue identified in the rejection, including obscured sender identity, misleading destinations, or an inappropriate domain. A shortener-only failure may be identified separately by 30525. |
| 30455 | SHAFT Violation – Hate Speech, Violence, or Offensive Content Is Prohibited | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30456 | SHAFT Violation - Alcohol Promotions | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30457 | SHAFT Violation - Firearms, Fireworks, and Explosives Content Is Prohibited | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30458 | SHAFT Violation - Tobacco and Vape Messaging Must Comply with Legal Restrictions | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30459 | Disallowed Content – Cannabis, CBD, or Other Illegal Substances | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30460 | Disallowed Content - Third-Party Debt Collection | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30461 | Disallowed Content - Gambling or Betting | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30462 | Disallowed Content - Sweepstakes or Contests | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30463 | Disallowed Content - Stock Alerts | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30464 | Disallowed Content - Cryptocurrency | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30465 | Disallowed Content - Risk Investment Opportunities | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30466 | Disallowed Content - Debt Reduction or Debt Consolidation | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30467 | Disallowed Content -Credit Repair | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30468 | Disallowed Content – Third-Party Lead Generation or Multi-Level Marketing | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30469 | Disallowed Content – Prescription Drugs or Controlled Substances | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30470 | High Risk - Submission Contains Deceptive Marketing Practices | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30471 | High Risk - Non-Secured URLs (http://) Are Not Allowed | Provide a secure URL that uses encryption (https://) |
| 30480 | High Risk - Known Phishing Campaign | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30523 | High Risk - Submission Flagged for High-Risk Domain Reputation | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30524 | High Risk - Submission Flagged for Potential Fraud Risk | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30525 | High Risk - Public URL Shorteners Are Not Allowed; Use a Branded URL | Replace public shorteners with a branded URL or a privately owned branded short domain that identifies your business. |
| 30526 | High Risk - Submission Flagged for High-Risk Domain Issues | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30528 | Disallowed Content - Non-Federally Compliant Use Case | Do not continue the rejected prohibited or high-risk messaging. Correct the underlying issue where it can be corrected, or provide evidence if the submission was misclassified. See the linked code for the specific restriction; resubmission does not permit prohibited content. |
| 30529 | SHAFT Violation – Alcohol Message Content Without a 21+ Robust Age Gate | Implement a robust 21+ gate for an otherwise permitted alcohol-related use case and provide evidence. A simple yes/no age confirmation is insufficient. |
New shared error codes from September 15, 2026
These codes use the same rejection meaning for Toll-Free Verification and A2P 10DLC. Follow the correction for the code you received. The shared number does not mean that every program has the same resubmission procedure.
| Error code | What it means | What to correct or check |
|---|---|---|
| 30497 | Use case summary is incomplete or unrelated to the messaging | Explain who sends the messages, who receives them, what the messages contain, and why recipients receive them. Include details for each selected use case. |
| 30532 | Personal use cases are not supported | Personal messaging is unsupported. If the description is inaccurate, correct it to reflect your actual business messaging and provide matching evidence; do not simply relabel personal traffic. |
| 30533 | Person-to-person (P2P) use cases are not supported | Person-to-person messaging is unsupported by this registration program. Correct an inaccurate description only when the actual messaging is application-to-person business messaging. |
| 30534 | Testing use case is missing business or program details | Provide complete business information and describe the testing program, intended recipients, and supporting evidence. Identify the internal testing audience and confirm there are no external recipients. |
| 30535 | Viral messaging is missing required compliance disclosures | Document a one-time, consumer-initiated flow with prior recipient consent, individually selected recipients, sender identity, purpose, and opt-out instructions. Include the required CTA disclosures; do not use bulk selection or referral incentives. See the linked code for the complete requirements. |
| 30536 | Privacy policy URL is missing, inaccessible, or empty | Provide an active, publicly accessible Privacy Policy URL containing the policy text and required disclosures. A missing Terms of Service URL is a separate issue. |
| 30537 | Business model does not match the messaging use case | Align the actual messaging program, business model, website, and registration details. |
| 30538 | A message sample is missing for a selected use case | Provide a distinct, representative message sample for every selected use case. |
| 30539 | Call-to-Action opt-out instructions are present but noncompliant | Replace present but noncompliant CTA opt-out instructions with valid keyword instructions, such as “Reply STOP to opt out.” Entirely missing instructions are covered by 30547. |
| 30540 | Double opt-in confirmation message is required | Provide the required double opt-in confirmation message, including the brand/program, rates disclosure, HELP instructions, and opt-out instructions. |
| 30541 | Political campaign is missing an FEC or state committee ID | Provide the FEC committee ID or applicable state-level equivalent for the political organization. This is separate from a Campaign Verify token. |
| 30542 | Political messaging must use the Political use case category | Select the Political use case where applicable, align the description and samples, and provide the required program-specific political verification details. |
| 30543 | Live opt-in link not provided | For an opt-in method that requires a live website link, provide the direct active landing-page URL. Other accepted methods must supply the evidence required for that method and program. A supplied inaccessible TFV URL is a separate 30509 issue. |
| 30544 | Call-to-Action does not state the message purpose | State the purpose and type of messages in the Call-to-Action (CTA), such as appointment reminders or marketing offers. |
| 30545 | Call-to-Action does not state message frequency | State message frequency in the CTA, using wording that matches the program, such as “Message frequency varies” or “One message per request.” |
| 30546 | Deadline to correct the opt-in process has expired | Complete the changes requested during the previous review and provide evidence of the corrected opt-in. This code concerns an expired remediation deadline, not an independent determination that subscriber consent expired. |
| 30547 | Call-to-Action is missing opt-out instructions | Add missing opt-out instructions to the CTA, such as “Reply STOP to opt out.” Present but noncompliant instructions are covered by 30539. |
| 30548 | Charitable program does not separate consent for donation requests | Collect separate, optional consent for donation solicitations and informational messages. Show that subscribers can receive informational updates without agreeing to donation requests. |
| 30549 | No Terms of Service link found in the opt-in flow | Place a visible, accessible Terms of Service link in or immediately next to the CTA. |
| 30550 | No Privacy Policy link found in the opt-in flow | Place a visible, accessible Privacy Policy link in or immediately next to the CTA. |
| 30551 | Consent does not specify SMS or text messaging | State explicitly that consent covers SMS or text messages. |
| 30552 | Opt-in is not customer-facing | Provide the customer-facing consent flow. An internal admin setting or a staff-selected CRM checkbox alone does not demonstrate the customer’s consent. |
| 30553 | SMS is forced for two-factor authentication | Provide an alternative to SMS for completing authentication, such as email, so customers are not forced to enroll in SMS. |
| 30554 | Charitable donations collected insecurely over SMS | Direct donors to a secure external HTTPS donation page. Do not collect, authorize, or complete donations through text-based payment responses. |
| 30555 | First message sent without documented prior consent | Provide evidence that the customer actively consented before the first message was sent. |
| 30556 | SMS consent is bundled with other communication channels | Allow customers to choose SMS independently of email, voice, or other communication channels. |
| 30557 | Terms of Service missing business or program name | Identify the sending business or program in the Terms of Service. A name missing specifically from the CTA is covered by 30568. |
| 30558 | Terms of Service missing message frequency disclosure | State the message frequency in the Terms of Service, matching the actual program. |
| 30559 | Terms of Service missing product description | Describe the messaging product or program and the types of messages in the Terms of Service. |
| 30560 | Terms of Service missing customer support information | Add a working customer-support contact to the Terms of Service. Missing CTA support instructions are covered by 30570. |
| 30561 | Terms of Service missing opt-out information | Add clear opt-out instructions to the Terms of Service, including an appropriate opt-out keyword such as STOP. |
| 30562 | Terms of Service missing message and data rates disclosure | Include “Message and data rates may apply” in the Terms of Service. A rates disclosure missing from the CTA is covered by 30569. |
| 30563 | Terms of Service missing carrier liability disclosure | State in the Terms of Service that wireless carriers are not liable for delayed or undelivered messages. |
| 30564 | Terms of Service and Privacy Policy links not near opt-in | Place clearly labeled Terms of Service and Privacy Policy links close to the CTA or opt-in section. |
| 30565 | Promotional messaging for prescription drugs or GLP-1 products is not permitted | Promotional messaging for prescription drugs or GLP-1 products is not permitted. For an otherwise permitted business and use case, remove promotional content, provide evidence of the actual informational messaging, and include the required age statement in the Terms. This exception does not permit an otherwise prohibited business or controlled-substance use case. |
| 30566 | Academic Fraud and Cheating Services Are Prohibited | Academic fraud and cheating-service messaging is prohibited. If the rejection misclassifies your business, provide evidence for a review; do not submit the same prohibited service under a different description. |
| 30567 | Phishing and Simulated Phishing Messages Are Prohibited | Phishing and simulated phishing messages are prohibited. If you believe the classification is incorrect, provide evidence for review. |
| 30568 | Call-to-Action is missing the business or brand name | Name the sender in the CTA and match the registered business or brand. Example element: “Receive order updates from Acme.” This is not a complete CTA. A name missing from Terms is covered by 30557. |
| 30569 | Call-to-Action is missing the message and data rates disclosure | Add the exact disclosure “Message and data rates may apply” where consumers consent. This is one CTA element, not a complete CTA. Terms disclosures are separately covered by 30562. |
| 30570 | Call-to-Action is missing customer support instructions | Add CTA support instructions using HELP, such as “Reply HELP for help.” This is one CTA element, not a complete CTA. Terms support is covered by 30560; Toll-Free automated HELP-response requirements are covered by 30486. |
What if I believe the rejection is incorrect?
Contact Twilio Support with your business name, Toll-Free number or verification identifier, the error code, and evidence explaining why the rejection is incorrect. Include the original ticket number if you have one and use the subject “Toll-Free Verification Rejection Appeal for [business name or number].”
A pending correction or appeal does not verify the number. Review its verification status before attempting to send messages.
Additional resources
If your returned code is not listed here, open its Twilio error-code reference or contact Support. Do not replace it with a similar code from this article.