The A2P 10DLC rejection code index for GoHighLevel (2026)

In GoHighLevel, every A2P 10DLC rejection comes back as a numeric Twilio error code, and the code tells you both what tripped and whether you can fix it. This index lists all of them: the code, its verbatim Twilio label, the exact Trust Center field it points to, and whether resubmitting will work.

Last verified: 2026-07-22 against Twilio’s full error dictionary. That sweep pulled every documented code in the 30880 to 30972 range (85 of them) and each code’s own page, which is how the 30910 to 30937 policy codes below joined this index. This page is a living reference. When Twilio adds or relabels a code, the row and the date change with it.

How to read a GHL rejection

GoHighLevel runs A2P registration on Twilio underneath, so a rejection in Trust Center arrives as a Twilio error code in the 308xx or 309xx range. Each code maps to one of three outcomes:

• Fixable. Correct the named field and resubmit. Resubmitting a rejected campaign is free, per GHL’s Help Center; the cost is the wait (1 to 3 days for Sole Prop, 3 to 15 days for Standard).
• Formatting near-fix. The rejected campaign cannot be resubmitted, but the cause is a URL choice, not a prohibited activity. Fix the URL and register a clean new campaign.
• Terminal. The business activity itself is ineligible for 10DLC. No rewrite clears it; the realistic path is toll-free messaging.

And a handful of codes are none of the three: they are pipeline statuses, not rejections at all. Those get their own table below.

Where the rejection reason lives in Trust Center

To read the rejection itself, go to Settings → Phone System → Trust Center, open Brands & Campaigns, then select the Campaigns tab. Each rejected campaign carries a View required fixes link. Per GHL’s Understanding A2P Campaign Rejection Reasons & Required Fixes article, that link opens four fields: Error code, Rejection category (a plain-language label for the violation), What it means, and Correction needed. The value in that first field is the code to look up below.

The full explanation of each cause, with example copy and the field-by-field fix, lives in the narrative pillar, Every TCR rejection reason in GoHighLevel, explained. This page is the lookup layer: find your code, get the field and the verdict, then jump to the pillar for the walk-through.

One structural fact worth knowing before you start: the review stops at the first problem it finds and reports only that one. Your submission may have more issues waiting behind the cited code. Fix the whole thing, not just the line in the email.

Fixable codes (correct the field, resubmit free)

These are the procedural rejections. The field named is the GHL Trust Center field where the fix goes.

The policy and consent codes (30900 to 30937)

These arrived alongside the granular content range and cover submission policy, consent structure, and identity matching. Unlike the 30940s, nearly every one is fixable: correct the named field (or re-scope the use case) and resubmit. Labels are verbatim from Twilio’s dictionary.

30933 and 30934 are the codes behind the Privacy Policy URL and Terms & Conditions URL fields that became required in GHL’s Campaign Details, the change we covered when it landed. 30913 is the two-separate-checkboxes rule wearing its own number.

Website verification codes

The reviewer visits your website. If it cannot be verified, these fire. They are website fixes, not copy fixes.

Statuses, not rejections

Four codes in this range are pipeline states. Nothing in your copy caused them and no copy change clears them.

Terminal content codes (broad)

These predate the granular range and are still active. A content rejection may surface as one of these or as a specific 30940 to 30964 code below.

The March 23, 2026 granular codes (30940–30964)

On March 23, 2026, GoHighLevel and The Campaign Registry rolled out per-reason content codes in the 30940 to 30964 range. Per GHL’s Understanding A2P campaign rejection reasons and required fixes article, the granular codes “provide more precise rejection reasons compared to previous general codes.”

Two things to hold onto. They are additive, not a rename: the broad codes above are still live, so treat this as a crosswalk. And almost every one is terminal, because the code keys off your declared business activity and website, not the wording of a single message. A wellness brand that gets 30940, deletes “CBD” from its samples, and resubmits gets 30940 again. Each label below is quoted verbatim from its own page in Twilio’s error dictionary.

Prohibited business activity or content (30940–30952):

SHAFT content (30953–30958):

High-risk or deceptive (30959–30964):

The last two are the only easy escapes. Twilio still marks the rejected campaign not eligible for resubmission, but the cause is a formatting choice. 30963 fires on public link shorteners like bit.ly or tinyurl, so swap to a branded or dedicated domain. 30964 fires on non-secure http links, so switch to https. Correct the URL, register a clean new campaign, and you are through.

Per-code fixes for the ones you can actually fix

The terminal codes have no fix on this platform. These do. Each links to the full walk-through in the pillar.

30909, message flow or CTA incomplete

The most common opt-in and consent rejection. It fires when consent collection is not documented at the opt-in URL you submitted, or a required CTA disclosure element is missing. Fix the opt-in form itself: two separate unchecked consent checkboxes, the mandatory disclosures, and links to your Privacy Policy and Terms of Service on the form. See the opt-in and consent pillar for the full CTA disclosure list.

30932 and 30908, the Privacy Policy non-sharing clause

30932 fires when your Privacy Policy says opt-in data is shared with third parties for marketing, or omits the non-sharing statement. 30908 (“Compliant Privacy Policy Required”) is the same requirement when the policy is missing, cannot be verified, or leaves the clause out. The fix for both is the TCR non-sharing clause: state that mobile information will not be shared with third parties or affiliates for marketing or promotional purposes, and that sharing with support subcontractors such as customer service is permitted. The exact paragraph and where it goes are in the Privacy Policy and Terms of Service templates guide.

30903, incorrect Sole Prop registration

Your registration tier does not match your entity. You filed Sole Prop but the business has an EIN (should be Standard), or you filed Standard but the EIN cannot be verified. Re-register at the tier that matches reality. If you have no EIN, register Sole Prop and drop any LLC, Inc, or Corp suffix from the name. The Sole Proprietor guide covers the full walkthrough.

30886, invalid campaign description

The Use Case Description is generic or echoes the dropdown label. Name the actual message types the business sends. “Appointment reminders for property tours, listing alerts, and open-house follow-ups” passes where “various updates” does not.

30890, subscriber HELP inadequate

Your HELP reply lacks the brand name, a support contact, or clear assistance instructions. Add all three to the HELP auto-response and resubmit. The related 30936 fires on the same requirement when the HELP keyword response itself falls short.

30923, consent required for service use

The most misunderstood code in the range, because it regularly hits businesses doing something completely normal: requiring phone verification at signup. The error text names the trigger directly: consent to receive messages cannot be a required condition for “using your service, creating an account, or completing a transaction.”

Here is the part that trips people. Reviewers never see your app. They read your opt-in description and message_flow, and if those say “user agrees to receive SMS to sign up,” it reads as a gate whether the payload is a marketing blast or a one-time passcode. The fix is wording plus structure:

• For marketing and notification streams, make consent optional and separate from signup, and say so: “Consent is not a condition of purchase.”
• For user-requested verification codes (2FA, login, account recovery), drop the consent checkbox entirely. The user entering their number and tapping the button is the consent. A checkbox that gates a required code is required by definition, which manufactures the exact violation you are trying to clear.
• Describe the flow as a literal action with the URL: “User enters their number at [url] and taps Send verification code. One code is sent in direct response. No recurring or promotional messages.”
• Register strictly as 2FA if that is what the campaign is. Broader use cases invite the bundled-consent read.

Requiring phone verification to create an account is fine. Every bank does it. What cannot be required is standing consent to a message stream.

30913, 30924, 30925, and 30931, the rest of the consent cluster

Four codes, one theme: consent has to be a real, separate, active choice. 30913 fires when marketing and informational consent share a checkbox, so split them — it is common enough that we gave it its own write-up. 30924 fires when the consent disclosure is missing or does not cover what you send, so put the full disclosure at the point of opt-in. 30925 fires when the live form’s box is pre-checked, and reviewers check the actual form at your URL, not just your pasted copy. 30931 fires when there is no way to decline at all. If you fix one, check the other three while you are in there, because the review stops at the first problem it finds.

Brand rejections that arrive without a granular code

Not every rejection carries a 309xx number. Brand-side vetting failures (a legal name that does not match IRS records, a PO Box address, a DUNS number entered where an EIN belongs, a non-US entity) often come back as a plain “vetting failed” or “unverified” state. When brand problems do carry codes, they are 30881 (support email), 30894 (brand information mismatch), 30898 (excessive EIN), 30903 (Sole Prop tier), 30914 and 30915 (Sole Prop naming), 30918 (DBA mismatch), and the two contact codes 30971 (business email must use the official domain) and 30972 (contact must be an authorized business representative). The other brand causes, and their fixes, are numbered 1 through 10 in the rejection pillar.

If you want this in a form you can keep beside you

This page is organised by code, which is what you want when you have a number in front of you. If you would rather work from the wording of the email itself, the TCR Rejection Decoder is a free PDF that starts from the rejection message and walks to the field that caused it. For the underlying causes in full prose — all of them, with the fix for each — see every TCR rejection reason explained.

Where Easy A2P fits

Easy A2P reads your Trust Center copy before you submit and reports back what tripped a rule and how to fix it, across all ten Trust Center sections (Brand Registration, Campaign Description, both Sample Messages, Opt-In Flow Description, Opt-In Confirmation Message, both consent checkboxes, and the Privacy Policy and Terms of Service SMS sections). A Review (1 credit) gives you findings plus specific remediation guidance. When you want the rewritten copy handed to you paste-ready, Draft mode (2 credits) or Fix My Copy (1 credit) does that. We do not approve anything; the carriers and their review chain do that. We help you ship it clean the first time. Review your submission with 3 free credits.