If your A2P 10DLC Campaign registration request is rejected for eligible reasons, you need to correct and resubmit your request. For a full list of eligible rejection reasons see below. If eligible, you can re-submit your Campaign registration after correcting the identified content violation by deleting and resubmitting the campaign.
Common Rejection Reasons
As of February 2026 we are seeing a high volume of rejections related to the following reasons.
| 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.
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.
|
| 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
If the opt-in process is behind authentication, provide screenshots instead
|
| 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.
|
Rejection types eligible for resubmission 🔗
Each of the below rejection codes are eligible for resubmission. To resolve these issues, please take the corrective action(s) outlined in the table below, and then re-submit your Campaign registration request with the updated information.
| Error Code | Rejection category | Rejection reason | Correction needed |
|---|---|---|---|
| 30886 | Invalid Campaign Description | Campaign description does not thoroughly explain the purpose of the campaign or description does not match the use case. | Verify that the campaign description is accurate and detailed. If you are an ISV registering a direct offering to your customers, please indicate that in the campaign description. Resubmit campaign for review. |
| 30893 | Invalid Sample Message Use Case | Sample messages are either not provided, unclear, or content does not match the campaign use case. | Verify that sample messages are accurate and detailed. Sample messages should reflect actual messages to be sent under campaign and indicate templated fields with brackets. At least one of the sample messages needs to include your business name. Use case and campaign description need to match campaign description. |
| 30892 | Invalid Sample Message - Public URL Shorteners | Public URL shorteners are not accepted. The website URL included in the sample messages was either from a public URL shortener or is non-secured. | Remove public URL shorteners from sample messages. |
| 30891 | Invalid Website URL | Invalid URL was provided for registration. Websites need to be functioning. If this is a registration pre-launch, it needs to be indicated in campaign description. | Verify that provided websites are functioning or detail is provided if the registration is for a pre-launch website. |
| 30896 | Opt-in Error | Opt-in message workflow is not sufficient for campaign type and consent is required or opt-in is shared with 3rd parties. | Verify opt-in meets CTIA's guidelines. All methods of opt-in need to be listed. If opt-in is collected through a paper form or behind a login, please provide a hosted link to the image of opt-in. If opt-in occurs on a website, please provide a link to the website. The website needs to have a privacy policy and terms of service. Ensure opt-in is not shared with 3rd parties. |
| 30887 | Opt-out Error | Campaign indicated collecting and processing consumer Opt-Outs, but the workflow is unclear, missing opt-out keywords or opt-message. | Verify that opt-out workflow is accurate and update Message Flow (labeled as 'How do end-users consent to receive messages' while submitting) description with opt-out process.If opt-out is managed, add opt-out keywords and update opt-out message to to include acknowledgement of opt-out request, confirmation that no further messages will be sent, and brand name. |
| 30890 | Subscriber Help | HELP message reply does not contain brand name, phone number, or email address. | Verify that subscriber help message contains brand name, phone number, or email address. Message needs to guide customers on who them can contact after replying "help". |
| 30889 | Embedded Phone Number | Embedded phone number use is selected, but is not reflective in the sample message. | Verify embedded phone number selection is accurate. Update the Sample Messages with Embedded Phone Number or update Embedded Phone Number selection. |
| 30888 | Age Gate Not Present / Not Acceptable | Age gate is not present. | Verify and add a robust age gate to your website or opt-in policy. |
| 30881 | Invalid Brand Support Email | Support email is not associated with the brand. The brand support email was either invalid or associated with a public domain email. | Verify brand support email is valid and not associated with a public domain email. |
| 30894 | Invalid Brand Information | Campaign registration needs to be associated with the brand behind the campaign. If you are an ISV registering a direct offering, campaign description needs to indicate a direct offering. | Verify brand information is valid. |
| 30895 | Direct Lending - Campaign and Content Attribute Error | Campaign is for direct lending or loan arrangement and is missing content attribute indicating direct lending. | Verify direct lending or loan arrangement is selected for campaign registration. If the campaign is not related to direct lending or loan arrangement, please update the campaign description. |
| 30903 | Incorrect Sole Prop Brand Registration | Brand behind the campaign does not meet the small business Sole Proprietor (EIN) criteria set by TCR and mobile carriers. Campaign can not be registered with a Sole Proprietor use case. | Register the brand as a standard brand and register a standard or acceptable campaign use case that aligns with the registered brand’s classification. |
| 30907 | Website URL Validation Issue | Website URL does not match the campaign description or Brand information. | Confirm the website aligns with the registered Brand and Campaigns. |
| 30908 | Compliant Privacy Policy Required | A compliant privacy policy was not provided in the Message Flow or could not be located on the website. | Verify privacy policy is accessible to end-users and include a direct link to the privacy policy with the Message Flow. |
| 30909 | CTA Verification Issue | Call to Action with the campaign could not be verified. | Provide complete CTA information and all possible methods end-users consent to messaging. |
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 A2P 10DLC 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.
Warning Notice: Users who disagree with their rejection can Contact Support to request an appeal. In your request, please include the details of your appeal and the subject line "10DLC Campaign Appeal for (your business name or number)".
| Error Code | Rejection Category | Rejection reason |
|---|---|---|
| 30883 | Content Violation - SHAFT - Sex | Submission included content such as nudity, pornography, sex toys, or other adult content |
| 30883 | Content Violation - SHAFT - Hate | Submission included speech that is hateful, profanity, violent, incites violence, or similar speech |
| 30883 | Content Violation - SHAFT - Alcohol | |
| 30883 | Content Violation - SHAFT - Firearms | Submission included:Firearms, Ammo, Gun Ranges (Common for guns to be sold at Gun Ranges) |
| 30883 | Content Violation - SHAFT - Tobacco / Vape | Submission included products such as: Cigarettes, Cigars, Tobacco Products (Chew, etc), Vape, Vape Juice, or similar items |
| 30883 | Content Violation - SHAFT - Marijuana / CBD | Submission included products such as: Cannabis, Marijuana, CBD, THC, Hemp or similar items |
| 30884 | Spam/Phishing | Spam/Fraud team has flagged the number/business/traffic for spam or phishing. |
| 30885 | High Risk |
Spam/Fraud team has flagged the number/business/traffic for fraud or deceptive marketing. Privacy policy or Terms associated with the campaign may indicate that SMS opt-in consent or phone numbers are being shared with third parties or affiliates. |
| 30897 | Disallowed Content |
Submission included:disallowed content types, such as Loan Marketing, 3rd party debt collection, gambling, sweepstakes, stock alerts, cryptocurrency, risk investments, debt reduction, credit repair, 3rd party lead generation, federally illegal substances. Privacy policy or Terms associated with the campaign may indicate that SMS opt-in consent or phone numbers are being shared with third parties or affiliates. |
| 30882 | Terms & Conditions | Campaign does not meet Terms and Conditions. |
| 30898 | Excessive EIN | Same EIN is used for multiple brands. Only register minimum number of brands per EIN and do not resubmit until brand registration is updated. |
New Granular Error Codes
Starting March 23rd, new error codes will provide more precise rejection reasons compared to the previous general codes. Instead of receiving a broad code like 30883, 30885, or 30897, you’ll be given a code that specifically identifies the issue.
The general catch-all code 30883, which covers specific SHAFT categories—Sex, Hate, Alcohol, Firearms, and Tobacco—will now have distinct error codes. These content categories are restricted or prohibited under CTIA messaging guidelines. The restrictions are applicable to campaign descriptions, sample messages, website content, and any linked URLs.
Furthermore, there are specific high-risk and disallowed error codes that take the place of the general 30884/30885 codes, identifying particular risk categories.
| Error Code | Rejection Category | What It Means | Correction Needed |
|---|---|---|---|
| 30909 | Opt-In and Consent | Your Call-to-Action/Message Flow cannot be verified by reviewers | Provide complete CTA information and all methods end-users use to consent. If behind a login, provide hosted screenshots. |
| 30913 | Opt-In and Consent | Marketing consent must be collected separately from informational/transactional consent | Add separate consent for promotional messages. If you only send transactional messages, clarify this in your campaign description. |
| 30917 | Opt-In and Consent | You selected multiple opt-in methods but did not describe all of them | Update your opt-in workflow description to cover every method listed. |
| 30923 | Opt-In and Consent | Messaging consent is bundled into mandatory terms or agreements | Ensure opt-in is a separate, optional action. Consumers must be able to decline messaging and still use your service. |
| 30924 | Opt-In and Consent | Consent language is missing required disclosures (frequency, opt-out, rates) | Add all four: message type, frequency, "message and data rates may apply," and STOP instructions near the opt-in checkbox. |
| 30925 | Opt-In and Consent | Opt-in form is missing a checkbox, or the checkbox is pre-selected | Add an unchecked-by-default checkbox specifically for SMS consent. |
| 30931 | Opt-In and Consent | Opt-in form mechanics prevent consumers from declining messaging | Add an explicit skip option or unchecked checkbox. A single button must not grant all permissions including messaging. |
| 30932 | Opt-In and Consent | Privacy policy indicates opt-in data is shared with third parties for marketing | Update your privacy policy to explicitly state that mobile information will not be shared with third parties for marketing purposes. |
| 30919 | Website | Website lacks sufficient business information or messaging disclosure | Add: company name, description of services, contact information, privacy policy, and mention of your SMS messaging program. |
| 30920 | Website | Website is just a form (lead capture, sign-up) without business context | Add business context around your form: company name, what your business does, contact information. |
| 30921 | Website | Website requires a login -- reviewers cannot access it | Create a publicly accessible page describing your business and messaging program. |
| 30922 | Website | Website does not meet verification requirements (under construction, non-standard URL) | Provide a functioning, standard URL. If pre-launch, note this in campaign description and provide screenshots. |
| 30914 | Business Identity | Sole proprietor campaign content does not match registered name | Align campaign description, sample messages, and website with the sole proprietor name you registered. |
| 30915 | Business Identity | Registered as sole proprietor but using a corporate name (LLC, Inc.) | Re-register as a standard brand using your EIN and corporate information. |
| 30918 | Business Identity | DBA (Doing Business As) name does not match legal name on file | Update brand registration to include your DBA name before resubmitting. |
| 30926 | Business Identity | Campaign references multiple companies or brands | Register separate campaigns for each brand. Each brand needs its own campaign. |
| 30927 | Business Identity | Opt-in evidence shows a different company than the one registered | Ensure opt-in evidence (screenshots, URLs) shows the exact company name matching this campaign's brand registration. |
| 30971 | Business Identity | Contact email uses a personal domain (gmail, yahoo) instead of official business domain | Register and use a business email address (e.g., name@yourcompany.com). |
| 30972 | Business Identity | Contact person listed is not an authorized representative of the business | Update the contact to an authorized representative of the registered business. |
| 30910 | Use Case | Registration fields contain non-English language | Campaign registration fields must be in English. Provide English translations of sample messages alongside originals. |
| 30911 | Use Case | Same text was copy-pasted across multiple registration fields, or all sample messages are identical | Each field (description, sample messages, message flow) must contain unique content. Each sample message must be distinct. |
| 30912 | Use Case | Use case appears to be personal/P2P messaging, not A2P | Describe what software or platform triggers the messages and how it serves your customers. |
| 30916 | Use Case | Selected lead generation but described lead nurture (or vice versa) | Lead generation = initial outreach to acquire new leads. Lead nurture = ongoing engagement with existing leads. Choose the one that matches. |
| 30928 | Use Case | Social influencer/public figure communications are not a valid use case | Register as a business entity and frame your campaign around your business use case (e.g., e-commerce, event notifications). |
| 30929 | Use Case | Emergency alert notifications are not permitted through A2P 10DLC | Emergency alerts are not a valid A2P 10DLC use case. Contact support for alternatives. |
| 30930 | Use Case | Your brand has reached the 100-campaign limit | Deregister unused campaigns in the Twilio Console to free up capacity. |
| 30940 | Disallowed | Cannabis, CBD, marijuana, or illegal substances | |
| 30941 | Disallowed | Prescription drugs or controlled substances | |
| 30942 | Disallowed | Loan marketing (payday, auto title, personal loans) | |
| 30943 | Disallowed | Third-party debt collection | |
| 30944 | Disallowed | Gambling or betting | |
| 30945 | Disallowed | Sweepstakes or contests | |
| 30946 | Disallowed | Stock alerts or investment signals | |
| 30947 | Disallowed | Cryptocurrency trading or token promotions | |
| 30948 | Disallowed | High-risk investment opportunities (forex, binary options) | |
| 30949 | Disallowed | Debt reduction or consolidation services | |
| 30950 | Disallowed | Credit repair services | |
| 30951 | Disallowed | Third-party lead generation or multi-level marketing (MLM) | |
| 30952 | Disallowed | Non-federally compliant use case | |
| 30953 | SHAFT | Sex or adult content | |
| 30954 | SHAFT | Hate speech, violence, or offensive content | |
| 30955 | SHAFT | Alcohol promotions | |
| 30956 | SHAFT | Alcohol content without a robust 21+ age gate | |
| 30957 | SHAFT | Firearms, fireworks, or explosives | |
| 30958 | SHAFT | Tobacco or vape products | |
| 30959 | High Risk | Fraudulent or misleading content detected | |
| 30960 | High Risk | Campaign identified as a known phishing campaign | |
| 30961 | High Risk | Website or URL has a high-risk domain reputation | |
| 30962 | High Risk | Deceptive marketing practices (false urgency, bait-and-switch, fake endorsements) | |
| 30963 | High Risk | Campaign uses public URL shorteners (bit.ly, tinyurl, etc.) | |
| 30964 | High Risk | Campaign URLs use HTTP instead of HTTPS | |
| 30995 | Registration Issue | Your account has reached the maximum Messaging Services Phone Number limit | Reach out to Support |
My Campaign Use Case was rejected - What can I do? 🔗
If your Campaign registration request was rejected, your next steps will depend on the eligibility of the campaign.
1. If the campaign is ineligible: You may still 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.
2. If the campaign is rejected for specific issues that allow for resubmission: You can address these issues, make the necessary adjustments, and resubmit the campaign for approval.
To do this, you can edit a Campaign directly in the console or through the API.
You also have the option to delete (unregister) an A2P Campaign via the Console or API, and register a new one in its place as described in Deleting and Recreating a failed Campaign via Console.
Campaigns can also be recreated via API request. For more details see Troubleshooting Campaigns via the API.
Regardless of the reason for rejection, it is crucial that you fix any rejected campaigns promptly; otherwise, you will incur the TCR monthly fee. Deleting the rejected campaigns not only avoids unnecessary charges but also helps you maintain a clear record of your active and pending campaigns.
Additional Information
Who rejected my A2P 10DLC Campaign Registration?
Each campaign will incur a single vetting charge of $15. If your campaign gets rejected, you can edit it and resubmit, but without an extra vetting fee.
If the rejected campaign is deleted and recreated, a new $15 vetting fee will be applied.
If you believe that the campaign was rejected due to a mistake, please edit and add clarity to the campaign registration details and resubmit the campaign for review.
Comments
0 comments
Article is closed for comments.