A2P 10DLC rejection codes explained, and how to fix each one.
Your campaign came back rejected with a code like 30909, 30908 or one of the newer 309xx codes. Here is every code Twilio lists, what it really means, and what to change before you resubmit.
By Akinbode Goodness, A2P 10DLC specialist with 150+ registrations · Updated November 15, 2026
The short version
Carrier reviewers compare four things: your brand details, your campaign description, your website and your sample messages. They must all describe the same business sending the same kind of texts to people who clearly agreed to get them. Almost every rejection code below is one of those four things not lining up. The rest are content carriers do not allow at all.
Most common codes: 30909 · 30908 · 30896 · 30924 · 30925 · 30886 · 30907 · 30897 · full list
Before you fix anything
- Open the campaign in your provider and copy the exact code and the reviewer's note
- Open your website on your phone and go through the form the way a stranger would
- Read your privacy policy, SMS Terms, campaign description and sample messages side by side
- Write down everything that does not match. Fix all of it, then edit and resubmit the same campaign once
Fixing only the field named in the rejection is the most common mistake. The next review then finds the next problem, and you lose another week.
Every rejection code at a glance
Twilio's list grouped by what you need to fix. Codes with a link have a full explanation further down.
Website problems
| Code | What it means |
|---|---|
| 30891 | Invalid website URL |
| 30907 | Website URL validation issue |
| 30919 | Not enough business or messaging info |
| 30920 | Website is only a form |
| 30921 | Website requires a login |
| 30922 | Website does not meet verification requirements |
Consent and opt in problems
| Code | What it means |
|---|---|
| 30896 | Opt in error |
| 30909 | Message flow or call to action incomplete |
| 30913 | Marketing and informational consent must be separate |
| 30917 | Every opt in method needs a description |
| 30923 | Consent required to use the service |
| 30924 | Consent language missing or not compliant |
| 30925 | Checkbox pre ticked or no active consent |
| 30927 | Opt in evidence for a different company |
| 30931 | Opt in must let people say no |
Privacy policy and terms
| Code | What it means |
|---|---|
| 30908 | Compliant privacy policy required |
| 30932 | Privacy policy must disclose third party sharing |
| 30933 | Privacy policy URL is required (API) |
| 30934 | Terms and Conditions URL is required (API) |
| 30882 | Terms and conditions do not meet review requirements |
Campaign details
| Code | What it means |
|---|---|
| 30886 | Invalid campaign description |
| 30887 | Opt out details unclear |
| 30889 | Embedded phone number not shown in samples |
| 30890 | Subscriber help not acceptable |
| 30892 | Public link shortener in samples |
| 30893 | Samples do not match the use case |
| 30910 | Campaign must be in English |
| 30911 | Duplicate text across fields |
| 30912 | Person to person texting is not A2P |
| 30916 | Lead generation and lead nurture mixed up |
| 30900 | Use case not eligible for this brand |
| 30930 | Brand already has 100 campaigns |
Brand and business details
| Code | What it means |
|---|---|
| 30881 | Invalid brand support email |
| 30894 | Invalid brand information |
| 30898 | Same EIN used for too many brands |
| 30903 | Brand does not qualify as sole proprietor |
| 30914 | Sole proprietor campaign name does not match |
| 30915 | Registered company filed as sole proprietor |
| 30918 | DBA name does not match the legal name |
| 30926 | Several companies in one campaign |
Content carriers do not allow
| Code | What it means |
|---|---|
| 30883 | Content violation |
| 30884 | Spam or phishing |
| 30885 | High risk |
| 30895 | Direct lending not declared |
| 30897 | Disallowed content |
| 30888 | Age gate missing |
| 30928 | Influencer or public figure use case |
| 30929 | Emergency alerts use case |
| 30940 to 30960 | Specific banned topics: cannabis and CBD, prescription drugs, loans, debt collection, gambling, sweepstakes, stock alerts, crypto, high risk investing, debt relief, credit repair, third party lead gen and MLM, adult content, hate speech, alcohol, firearms, tobacco and vape, fraud and phishing |
Process and status codes
| Code | What it means |
|---|---|
| 30880 | Rejected with no specific reason |
| 30899 | One or more carriers rejected the campaign |
| 30901 | Registration timed out |
| 30902 | Rejected in third party review |
| 30904 | Campaign not shared with Twilio |
| 30905 | Campaign still pending review |
| 30906 | Campaign rejected by Twilio's review partner |
The common codes, what they mean and the fix
Error 30886: Invalid campaign description
The description does not clearly say who is sending, who receives the texts and why. It is the most common rejection on rushed submissions.
How to fix it:
- Write it as one plain paragraph: business name, who the customers are, what the texts are for, and how they opted in
- Match the use case you picked. A "Customer Care" campaign whose description talks about promotions will fail
- If the brand name and the website name differ, add a line such as "Smith Roofing LLC, doing business as Peak Roofing"
- Agencies and platforms: describe your client's business, not your own
Error 30896: Opt in error
The reviewer cannot see how people agree to get texts. Usually the message flow is vague, one of several opt in methods is missing, or the opt in page is behind a login.
How to fix it:
- List every way people opt in: website form, text keyword, paper form, phone call
- Give the exact page URL of the form, not just the home page
- If the form is gated, in an app or on paper, upload a screenshot and give its public link
- Make sure the consent checkbox is optional and unchecked by default
Error 30897: Disallowed content
The use case falls into a category carriers do not allow, such as third party lead generation, loans, debt relief, credit repair, crypto, gambling or cannabis. Sometimes a normal business gets flagged because the wording makes it look like one.
How to fix it:
- Check that the business is not in a forbidden category. If it is, no rewrite will get it approved
- If it was flagged by mistake, rewrite the description and samples so they only cover texts to your own customers
- Remove words that suggest selling or sharing leads, such as "partners", "network" or "we connect you with"
- Lead gen agencies: register the texts your clients send to their own customers, under each client's brand
Error 30907: Website URL validation issue
The website does not match the brand, or tells a different story from the campaign. A footer name that differs from the legal name on the EIN letter is the classic case.
How to fix it:
- Make the legal name on the site match the IRS record (CP575 or 147C), or show the DBA clearly
- Make sure the site is live, loads on a phone and describes the business you registered
- Use the same domain in the website field, the samples and the email address
- Do not submit while the site is still "coming soon"
Error 30908: Compliant privacy policy required
The privacy policy is missing, hard to find, contradicts itself, or does not say that mobile numbers and consent are never shared for marketing.
How to fix it:
- Link the privacy policy in the footer and next to the consent checkbox
- Add an SMS section that says no mobile information will be shared with third parties or affiliates for marketing or promotional purposes
- Remove any line that says you share or sell customer data to partners
- Use one policy. Two different policies on the same site confuse the reviewer
Error 30909: Message flow or call to action incomplete
The reviewer cannot verify the consent step from what you wrote. This is the one I fix most often, and the cause is usually on the website, not in the text you typed.
How to fix it:
- The consent checkbox must sit on the form that collects the phone number. Two forms on one page with the box on the wrong one fails every time
- Under the box, show the brand name, message types, "Message frequency varies", "Msg and data rates may apply", HELP and STOP, and links to the Privacy Policy and SMS Terms
- No pre checked boxes and no consent hidden inside general terms
- In the message flow field, describe the exact steps a person takes, with the page URL
Error 30933: Privacy policy URL is required
A newer code. Since June 30, 2026 the privacy policy URL is a required field when a campaign is created through the Twilio API. This one is a missing field, not a policy problem.
How to fix it:
- Add your public privacy policy URL to the campaign registration and resubmit
- If you use a platform such as GoHighLevel, make sure its form has the privacy policy field filled
- If the policy is rejected after that, you are looking at a 30908 instead
Error 30919: Website lacks business or messaging info
The site does not tell the reviewer enough about who you are and why you text people. A one page site with a headline and a phone number is the usual cause.
How to fix it:
- Add a short About section, your services, the business address or service area, and a contact method
- Say on the site that customers can get texts from you, and what kind
- Make sure the business name on the site matches the brand you registered
Error 30920: Website is only a form
The URL you gave goes to a bare form or landing page with no business around it. Reviewers need to see a real business, not just a capture page.
How to fix it:
- Submit your main website, and give the form page separately in the message flow
- If you only have a funnel, add business details, a footer with your legal name, and Privacy Policy and Terms links
- Keep the funnel and the main site on the same brand name
Error 30921: Website requires a login
The reviewer hit a login screen, a password page or a members area, so they could not check anything.
How to fix it:
- Give a public URL for the website and for the opt in form
- If the opt in really happens inside an app or portal, host clear screenshots of it on a public page and link that
Error 30922: Website does not meet verification requirements
A catch all for a site that could not be verified: broken pages, a parked domain, a site under construction, or a site for a different business.
How to fix it:
- Open the URL on a phone in a private window and check it loads with no errors
- Remove coming soon pages and placeholder text
- Check the domain in the website field, the brand email and the sample messages all point to the same business
Error 30923: Consent cannot be required to use the service
Your form makes people agree to texts before they can submit, book or buy. Carriers want texting to be a choice, not a condition.
How to fix it:
- Make the SMS checkbox optional so the form still submits when it is left unticked
- Do not put SMS consent inside the general Terms checkbox
- Remove wording like "by submitting this form you agree to receive texts"
Error 30924: Consent language missing or not compliant
There is a checkbox, but the words next to it do not tell people what they are signing up for.
How to fix it:
- Name your business and the kind of texts, for example appointment reminders and follow up about your inquiry
- Add "Message frequency varies" and "Message and data rates may apply"
- Add "Reply STOP to opt out, HELP for help" and links to your Privacy Policy and SMS Terms
- Put the full text right next to the checkbox, not only in a linked document
Error 30925: Checkbox pre ticked or no active consent
The SMS checkbox is ticked by default, or there is no separate SMS checkbox at all.
How to fix it:
- Add a separate SMS checkbox that is unchecked when the page loads
- Keep it apart from the Terms or Privacy checkbox
- Check your form builder: some templates tick boxes by default
Error 30913: Marketing and informational consent must be separate
One checkbox covers both promotions and service texts. If you send marketing, carriers want a separate yes for it.
How to fix it:
- Use two optional checkboxes: one for service and account texts, one for marketing and offers
- Or register only the type of texts you really send and word the single box for that
Error 30931: Opt in must let people say no
People cannot finish the main action without agreeing to texts. Same idea as 30923, flagged on the whole workflow.
How to fix it:
- Test the form with the SMS box unticked. It must still submit and reach you
- Offer another way to be contacted, such as email or a phone call
Error 30932: Privacy policy must disclose third party sharing
Your privacy policy or form suggests phone numbers or consent may be shared with partners, affiliates or lead buyers.
How to fix it:
- Add: "No mobile information will be shared with third parties or affiliates for marketing or promotional purposes"
- Remove any general clause that lets you share or sell data to partners
- If you really do share leads, that use case is very likely not allowed on 10DLC
Error 30917: Every opt in method needs a full description
You ticked more than one way people opt in (website, keyword, paper form, phone) but only described one.
How to fix it:
- Describe each method step by step in the message flow, with a URL or screenshot link for each
- Untick any method you do not actually use
Error 30916: Lead generation and lead nurture mixed up
The use case, the description and the sample messages tell different stories about what you do with leads.
How to fix it:
- Pick one use case and make the description and every sample match it
- Nurturing your own inquiries is fine. Generating leads to pass to others is what carriers restrict
Error 30887: Opt out details unclear
The submission does not show how people stop texts.
How to fix it:
- Include "Reply STOP to opt out" in your consent text and at least one sample message
- Make sure your system really stops texts after STOP and sends one confirmation
Error 30890: Subscriber help not acceptable
Your HELP reply is missing or does not give real support details.
How to fix it:
- Make the HELP reply name your business and give a phone number or email for support
Error 30891: Invalid website URL
The website could not be reached or verified at all.
How to fix it:
- Check the URL for typos, https and redirects to another domain
- Make sure the site is live and not blocked by country filters
Error 30892: Sample message uses a public link shortener
A sample message contains a bit.ly style short link or a plain http link. Carriers distrust these.
How to fix it:
- Use full links on your own domain with https
- If you need short links, use a branded domain you own
Error 30893: Sample messages do not match the use case
You registered one use case but the samples read like another, for example a customer care campaign with promo samples.
How to fix it:
- Rewrite the samples so each one is clearly the type of text you registered
- Include your business name and opt out wording
Error 30911: Duplicate text across fields
The description, message flow and samples were copied from each other or from a template.
How to fix it:
- Write each field fresh. The description explains the program, the flow explains opt in, the samples are real texts
Error 30918: DBA name does not match the legal name
The name in the campaign is not the legal name on the brand, and the link between them is not shown.
How to fix it:
- Use the legal name, or write "Legal Name LLC, doing business as Trade Name" and show both on the website
Error 30894: Invalid brand information
The brand details do not match the business that is actually texting.
How to fix it:
- Agencies: register each client under the client's own brand, not the agency's
- Make the brand name, EIN, website and samples describe the same company
Error 30926: Several companies in one campaign
One campaign is being used for more than one business. Each business needs its own brand and campaign.
How to fix it:
- Split it: one brand and one campaign per business
Error 30927: Opt in evidence is for a different company
The form or screenshot you linked names a different company from the registered brand.
How to fix it:
- Link the opt in form that shows the registered business name in the consent text
Error 30934: Terms and Conditions URL is required
The companion to 30933. Since June 30, 2026 the terms URL is required when a campaign is created through the Twilio API.
How to fix it:
- Add a public SMS Terms or Terms and Conditions URL to the registration and resubmit
A real example
A plumbing lead generation agency had its campaign rejected under 30897 because it read like third party lead generation. I rewrote the description and sample messages so they only covered texts the agency sends to its own clients, and the resubmission was approved. A Squarespace clinic with repeated rejections passed once the double contact form and the privacy policy SMS section were fixed together. More examples are on the work page.
A quick checklist before you resubmit
- Legal name on the website matches the EIN letter, or the DBA is stated
- One form collects the phone number, with an optional, unchecked SMS consent box on that same form
- Consent text names the brand, message types, frequency, rates, HELP and STOP
- Separate boxes if you send both marketing and service texts
- Privacy Policy with an SMS section saying mobile data is never shared for marketing
- SMS Terms page linked from the form and the footer
- Description says who sends, who receives, why, and how they opted in
- Sample messages include the brand name and opt out language, and match the use case
Need the consent wording? Copy it from the A2P opt in and consent checkbox guide. New to all this? Start with What is A2P 10DLC, then the step by step registration guide. Already rejected and want it handled? See A2P campaign rejection fixes.
Code titles are from Twilio's public error list, checked November 15, 2026. Carriers add codes over time, so check your provider if you see one that is not here.
Things people usually ask
How long does an A2P campaign review take after resubmitting?
It varies. Many reviews come back in a few days, some take a couple of weeks. That is why it pays to fix everything before you resubmit instead of one item at a time.
Can a campaign be rejected for more than one reason?
Yes, and it is common. A site with no SMS section in the privacy policy usually also has a weak consent line, so it gets 30908 and 30909 or 30924 together. Fix the whole campaign, not just the code you were given.
Do these codes apply in GoHighLevel and other platforms?
Yes. The codes come from Twilio's campaign review, and GoHighLevel (LeadConnector) and many other platforms register through Twilio. Other providers use their own wording, but the causes are the same.
Should I edit the rejected campaign or create a new one?
Edit and resubmit the rejected campaign. Twilio says a brand new campaign starts a new vetting fee, while editing the rejected one keeps its history.
Which rejections cannot be fixed?
Codes for banned content, such as 30897 and 30940 to 30960, usually mean the business itself is not allowed on 10DLC. If your business was flagged by mistake, rewriting the description and samples can fix it. If it really is in a banned category, no rewrite will.
Is there a fee for resubmitting a rejected campaign?
Providers charge vetting fees, and some charge again on resubmission. Check your provider's current pricing. Getting it right the first time is the cheapest option.
Rejected again? Send me the code.
Send me your website and the rejection. I review it by hand for free and tell you exactly what to change.