Solution guide · SMS & compliance

GoHighLevel SMS error 30034: why your number is “unregistered” and how to fix it

GoHighLevel SMS error 30034 means your 10DLC number is not linked to an approved A2P campaign. Find the cause, link the number and get texts delivered.

GoHighLevel SMS error 30034: why your number is “unregistered” and how to fix it — guide thumbnail

Key takeaways

  • Error 30034 means a US text was sent from a +1 10DLC number that is not linked to an approved A2P 10DLC campaign, so the carrier network blocked it before it reached the phone.
  • An approved campaign does not register your numbers by itself: each number has to be linked to the campaign and show the green A2P Verified label under Settings → Phone System → Phone Numbers.
  • A Sole Proprietor brand allows one campaign and one phone number, so a second local number in the same sub-account fails with 30034 even when the first is approved.
  • After linking, allow up to 24 hours for carriers to activate the number; error 30035 during that window means the number is still being configured, not rejected.
  • Blocked 30034 messages are still billed by Twilio, so pause the workflows or campaigns sending from the number until it is verified.

GoHighLevel SMS error 30034 means your text was blocked because it came from a US local (10DLC) number that is not associated with an approved A2P 10DLC campaign. The message, the contact and HighLevel itself are all fine. The carriers simply refuse traffic from numbers they have no registration for, and they have done so for every unregistered 10DLC number since 2023.

The fix is nearly always one of four things: the number was never linked to your approved campaign, the brand or campaign is not approved yet, a Sole Proprietor brand has more than one number, or the carriers have not finished activating a number you linked recently. Below I show how to tell which one you have and the exact steps for each. It is the same check I run when I handle A2P 10DLC registration for clients.

What error 30034 means in GoHighLevel

HighLevel’s error dictionary lists 30034 as “Message from an Unregistered Number”: a +1 10DLC number that is not associated with an approved A2P campaign. Twilio’s error page adds that submitting a campaign is only one of several registration steps. The number has to be fully registered to an approved campaign under your brand before it can text US phones.

Three points save a lot of confusion:

  • It is a registration error, not a content error. Rewriting the message changes nothing. (If the code is 30007, the content is the problem; see my 30007 guide.)
  • It only affects US 10DLC numbers. Toll-free numbers use a separate verification process and fail with 30032 when unverified.
  • Blocked messages still cost money. Twilio says its messaging rates apply even to blocked messages, although no carrier fines are charged.
InfographicClear error 30034in five steps
  1. 1Confirm the error codeHover the failed text in Conversations.
  2. 2Check brand and campaignBoth must say Approved in Trust Center.
  3. 3Link every numberLook for the green A2P Verified label.
  4. 4Fix Sole Proprietor limitsOne number per Sole Prop campaign.
  5. 5Wait, then test onceAllow up to 24 hours for carriers.
Source: HighLevel Support Portal; Twilio Docsscalewithhunaid.com

Step 1: confirm it really is 30034

Open Conversations, find the failed text and hover over the red error to see the code. Several registration codes look alike, and each has a different fix:

Code What it means What to do
30034 10DLC number not linked to an approved A2P campaign Link the number, or finish registration (this guide)
30035 Number is linked but still being configured Wait up to 24 hours; don’t remove and re-add it
30033 A2P campaign suspended Fix the campaign issue, then resubmit
30032 Toll-free number not verified Toll-free verification
30007 Carrier filtered the content Fix the message and consent

Sources: HighLevel’s SMS error guide, Twilio 30034 and Twilio 30035.

Step 2: check the brand and campaign are approved

A number can only be linked to a campaign that is already approved, and a campaign can only exist under an approved brand.

Fix:

  1. Go to Settings → Phone System → Trust Center, then Brands and Campaigns.
  2. Check the brand status. If it is rejected or missing, register it first. HighLevel says the legal name and EIN must match IRS records exactly (your CP-575 or 147C letter), and my brand rejection guide walks through each rejection reason.
  3. Check the campaign status. If it is pending, nothing else will clear 30034 until it is approved. If it is rejected, use my A2P campaign rejected guide to fix the website, opt-in and sample messages before you resubmit.
  4. Note whether the brand is Standard or Sole Proprietor. It decides Step 4.

This is the cause I find most often. The campaign was approved weeks ago, but the number sending the texts was bought later, or was never attached. HighLevel is clear that approval does not link numbers automatically: each number needs its own link.

Fix (as of November 2026):

  1. Go to Settings → Phone System → Phone Numbers.
  2. Find the number that sent the failed text. A registered number shows a green A2P Verified label under it; an unregistered one doesn’t.
  3. Click the three-dot menu on the right of that number.
  4. Choose Select A2P campaign to Link.
  5. Pick your approved campaign from the list and confirm.
  6. Check that the green A2P Verified label now shows under the number.
  7. Repeat for every local number in the sub-account that sends texts, including numbers used only by workflows.

What fixed looks like: every sending number on the Phone Numbers page shows A2P Verified, and the Trust Center shows the brand and campaign as approved.

Step 4: Sole Proprietor brands allow one number only

If the brand is Sole Proprietor, the limit is strict. Twilio’s Sole Proprietor FAQ allows one campaign per brand and one phone number per campaign, and HighLevel warns that a Sole Proprietor sub-account with two or more local numbers can hit 30034 even when one number was approved. Twilio’s troubleshooting page confirms the extra numbers simply stay “Unregistered”.

Fix — option A, keep Sole Proprietor:

  1. Decide which single number the business texts from. Usually it is the one on the website and Google Business Profile.
  2. Make sure that number is the one linked to the campaign and shows A2P Verified.
  3. Change every workflow SMS step, bulk send and missed-call text back to send from that number only.
  4. Use any other numbers for calls only, or release them.

Fix — option B, move to a Standard brand:

  1. Check you qualify. HighLevel says a business with an EIN must register as a Standard brand, and Sole Proprietor is not available to businesses with two or more employees.
  2. In Trust Center, register a new Standard (or Low Volume Standard) brand with the legal name and EIN exactly as the IRS has them. HighLevel notes EINs issued in the last 15 days may be rejected.
  3. Submit a campaign under the new brand that matches what you actually send. HighLevel’s rejection reasons article confirms that the fix for the wrong registration type is to register again as Standard or Low Volume.
  4. When the campaign is approved, link each number as in Step 3.

HighLevel does not document an in-place conversion from Sole Proprietor to Standard, so ask HighLevel Support how the old brand and campaign are handled before you register the new one.

A Standard brand also lifts the daily cap that Sole Proprietor brands live with:

ChartT-Mobile daily message limit by A2P 10DLC registration type
  • Sole Proprietor1000 msgs/day
  • Low-Volume Standard2000 msgs/day
  • Standard, Trust 25–4910000 msgs/day
  • Standard, Trust 75–100200000 msgs/day

Message segments per day to T-Mobile subscribers. Standard limits depend on the brand’s Trust Score and are shared across the EIN.

Source: Twilio Help Center, T-Mobile Daily Message Limits for A2P 10DLC (2026)

Sole Proprietor is still the cheaper route if one number is enough. Twilio lists a $4.50 one-time Sole Proprietor brand fee (as of August 2025), a $15 campaign vetting fee and a $2 monthly campaign fee. Your HighLevel agency may bill these differently, so check your own LC Phone pricing.

Step 5: wait for carrier activation, then test once

Linking is not instant. HighLevel says it can take up to 24 hours for a number to be fully registered and activated with the carriers, and Twilio notes that each number must then be approved by the individual US carriers, which can take several days when request volumes are high.

Fix:

  1. After linking, wait 24 hours before sending anything from the number.
  2. Send one test text to a mobile on a different carrier from your own.
  3. If it fails with 30035, the number is still being configured. Twilio says not to remove and re-add it, because that restarts registration and delays activation further.
  4. If it still fails with 30034 after 24 hours, and the number shows A2P Verified, contact HighLevel Support with the number, the campaign name and two or three failed message examples.
  5. Once the test arrives, unpause your workflows and campaigns.

Catch the next 30034 automatically

Error 30034 often appears when someone buys a new number months later and forgets to link it. A small workflow tells you the same day.

Fix — build the alert:

  1. Go to Automation → Workflows → Create Workflow.
  2. Add the trigger Messaging Error – SMS and a filter on Error Code for 30034, as described in HighLevel’s trigger article.
  3. Add Add Tag sms-unregistered-number, then Internal Notification to the account owner with the contact name.
  4. If the contact has an email address, add Send Email so the message still reaches them.
  5. Don’t add an automatic SMS resend. HighLevel advises against blindly resending failed texts, and a resend from the same number fails again.
  6. Publish the workflow.
InfographicWhy 30034keeps coming back

Keeps failing

  • Avoid: New number never linked
  • Avoid: Two numbers on Sole Prop
  • Avoid: Re-adding a pending number
  • Avoid: Workflows still sending
  • Avoid: EIN business as Sole Prop

Stays verified

  • Do: Link every new number
  • Do: One number per Sole Prop
  • Do: Wait 24 hours, then test
  • Do: Pause sends until verified
  • Do: Standard brand with EIN
Source: HighLevel Support Portal; Twilio Docsscalewithhunaid.com

Common mistakes to avoid

  • Rewriting the message. 30034 is about the number, not the words.
  • Assuming approval covers every number. Check the A2P Verified label on each one.
  • Adding numbers to a Sole Proprietor campaign. Only one will ever register.
  • Removing and re-adding a pending number. It restarts registration.
  • Leaving workflows running. Blocked texts are still billed and still miss the lead.

Get your texts delivered again

Error 30034 is fixed once every sending number is linked to an approved campaign under the right brand type, and a day has passed for carrier activation. If you’d rather hand it over, I handle brand, campaign and number linking as part of A2P 10DLC registration, and I fix the rest of the sending setup in email and SMS deliverability. Moving numbers from another provider? Read my number port rejected guide first, because a ported number needs linking too.

Hunaid Zia

Hunaid Zia

GoHighLevel Expert, Developer & Automation Specialist

I have built GoHighLevel systems, AI agents and websites for 50+ businesses since 2020, and written this guide from that work. Questions about your own setup? Book a free call.

References

  1. 30034: US A2P 10DLC — Message from an Unregistered Number — Twilio
  2. 30035: US A2P 10DLC — Message from a number still being configured — Twilio
  3. Troubleshooting A2P Phone Number registration issues — Twilio
  4. Shutdown of Unregistered 10DLC Messaging — Twilio Help Center
  5. A2P 10DLC Sole Proprietor Brands FAQ — Twilio Help Center
  6. Pricing and Fees for A2P 10DLC Service — Twilio Help Center
  7. T-Mobile Daily Message Limits for Long Code Messaging with A2P 10DLC — Twilio Help Center
  8. Error 30034: Linking a Phone Number to an Approved A2P Campaign — HighLevel Support Portal
  9. LC Phone System: Error Codes and Warning Dictionary — HighLevel Support Portal
  10. Understanding Common SMS Delivery Errors in HighLevel — HighLevel Support Portal
  11. A2P Brand Registration Guide for 10DLC in HighLevel — HighLevel Support Portal
  12. US Phone Number Registrations: Summary and FAQs — HighLevel Support Portal
  13. Campaign Rejection Reasons and Resolutions — HighLevel Support Portal
  14. Workflow Trigger — Messaging Error Code — SMS — HighLevel Support Portal

FAQ

Quick answers.

The questions people ask most about gohighlevel sms error 30034.

Ask me directly

It means the text came from a US 10DLC (local) number that is not associated with an approved A2P 10DLC campaign, so it was blocked. HighLevel’s error dictionary calls it “Message from an Unregistered Number”. The fix is in your A2P registration and number linking, not in the message wording.

Approval covers the campaign, not every number in the account. Each number has to be linked to the approved campaign separately, and only linked numbers show the green A2P Verified label. A number you bought after the approval, or one that was never linked, still fails with 30034.

HighLevel says it can take up to 24 hours for a number to be fully registered and activated with the mobile carriers. Twilio adds that individual numbers must be approved by each carrier after the campaign is approved, which can take several days when volumes are high. Send one test after a day before you change anything else.

No. Twilio and HighLevel both limit a Sole Proprietor brand to one campaign and one phone number on that campaign. Any extra local number in the same sub-account stays unregistered and fails with 30034. If you need more numbers, register a Standard brand, which requires an EIN.

Error 30034 means the number is not registered to an approved campaign at all. Error 30035 means registration is in progress and the number is still being configured with carrier partners. Twilio says to allow up to 24 hours for 30035 and not to remove and re-add the number, because that restarts registration.

No. Toll-free numbers do not use A2P campaign linking; they go through toll-free verification instead. An unverified toll-free number fails with error 30032, which has a different fix.

Twilio says its messaging rates still apply to blocked messages, although no per-message carrier fines are charged. Every workflow step that keeps texting from an unregistered number therefore costs money and reaches nobody, so pause those sends until the number is verified.

Not from the 10DLC number: US carriers have fully blocked unregistered 10DLC traffic since 2023. Twilio suggests a sender that is not part of A2P 10DLC, such as a verified toll-free number, if you must text before registration finishes. Email or a phone call is the simplest stop-gap for urgent messages.

The block itself is a registration failure, not a spam signal, and Twilio says no carrier fines are charged for it. The real damage is missed messages: reminders, missed-call text backs and lead replies that never arrive. Fix it quickly and set up an alert so you hear about the next one.

Rather have it fixed?

I can do thisfor you.

If you would rather not work through this yourself, tell me what is going on and I will fix it — usually faster than reading the guide twice.

Spots fill fast — most weeks I take on two new builds.

Chat with Hunaid Zia on WhatsApp (+92 340 422 2101), opens in a new tab