HighLevel text error 30034 or 30007? What it means and how to check every sub-account

By SHAJ Studio. Checked against the HighLevel help center, the Twilio error pages and the Conversations and Phone System screens in October 2026.

The short answer

Error 30034 means the sending number in HighLevel (also called GoHighLevel or GHL) is not linked to an approved A2P 10DLC campaign. Error 30007 means a carrier or provider filtered the message. The causes and the fixes are different. Watchtower flags the sub-accounts where texts are rejected for missing A2P registration, across every sub-account, in one daily email.

What do errors 30034 and 30007 mean?

Error 30034. The sending number is not linked to an approved A2P 10DLC campaign. The usual causes are brand and campaign registration that is not finished, carrier activation that is still pending (it can take up to 24 hours after approval) and a Sole Proprietor campaign with more than one number, because that kind of campaign allows one.
Error 30007. The carrier or provider filtered the message for content, consent, links or spam signals.

The two errors have different causes and different fixes. A 30034 points at the registration of the sending number. A 30007 points at the message and who it was sent to.

Where does HighLevel show these errors?

In Conversations, a text that failed shows a red warning icon and a Try again link. Hover over the icon to see the error, for example "Error 30034 - Number not A2P compliant. Please register for A2P.", with a Learn More link to HighLevel's article for that code. That is one message and one sub-account at a time. Try again sends the same text again, which for a 30007 is likely to be filtered again.

For 30034 there is a second place to look. When a sub-account's A2P registration is incomplete or has failed, Settings, Phone System, Phone numbers shows a red banner pointing to the Trust Center tab. Like the messages, it is only visible inside that sub-account.

HighLevel also has a Messaging Error - SMS workflow trigger. It can filter by error code, so a workflow can tag the contact or alert your team for one code only. The error list in the trigger labels 30034 "A2P Registration Pending on Number" and 30007 "Carrier Violation". It is set up in each sub-account separately. The help article advises against using it to resend every failed text automatically.

How do I fix error 30034?

Check that the A2P brand and campaign are approved: Settings, Phone System, Trust Center, Brands and Campaigns. This also shows whether the registration is Standard or Sole Proprietor.
Go to Settings, Phone System, Phone numbers. Open the three-dot menu beside the local number and choose Select A2P campaign to Link, then pick the approved campaign. If that option is missing, the brand or campaign is not approved yet.
Back in the list, check that the number now shows the A2P Verified label. Approving a campaign does not link every number: repeat for each local number that sends texts.
After approval, allow up to 24 hours for carrier activation before you test again.
On a Sole Proprietor registration, keep one local number. That kind of registration allows one campaign and one number. A second local number can cause 30034 even when the first was approved.
Toll-free numbers are not linked this way. They need toll-free verification instead (see 30032 below).

How do I fix error 30007?

Read the text that failed and fix the content or consent issue before you send again.
Do not resend the same text. It is likely to be filtered again.
If your texts follow the rules and keep failing, collect three or more recent examples and contact HighLevel support.

What other text errors might I see?

The help article lists more codes than these. Six you are likely to meet:

30003. The number is unreachable or out of service.
30005. The recipient number is inactive or does not exist.
30006. The number is a landline or the carrier cannot be reached.
21610. The recipient opted out, for example by replying STOP.
30032. The toll-free number is not verified.
30033. The A2P 10DLC campaign is suspended.

How do I check every sub-account at once?

By hand, that means opening Conversations and hovering over each failed text, checking Settings, Phone System in each sub-account and setting up the trigger in each one. Watchtower does the reading for every sub-account.

Watchtower reads the carrier error on texts that fail in every sub-account. When a text is rejected for missing A2P registration (30034), it flags that sub-account in your next daily email and on the dashboard as a Critical finding. It does not look at the registration itself. It sees the rejection, so a sub-account is flagged after a text has failed.

The finding stays open until 7 days have passed with no new rejection and texts have gone through. If the sub-account sends nothing in those 7 days, the finding changes to a Warning that says Watchtower cannot confirm whether the problem was fixed.

Watchtower also flags a rising share of failed texts over 7 days, once a sub-account sends enough texts for the share to mean something. Texts rejected for 30034 are left out of that share. It is not split by error code, so Watchtower does not flag a 30007 by name. A 30007 counts only as one of the failed texts in that share.

Watchtower is read-only: it never sends, edits or deletes anything in a sub-account. All sub-accounts appear on one dashboard and in one morning email. See what the daily email looks like in the sample digest. Or read how Watchtower works.

See it on invented data

The sample shows the daily email and the dashboard for an invented agency. Every name and number is invented.

See a sample digest Install from the HighLevel Marketplace

Questions

What does error 30034 mean in HighLevel?

The sending number is not linked to an approved A2P 10DLC campaign. The registration may be unfinished, carrier activation may still be pending or a Sole Proprietor campaign may have more than one number. Finish the registration and link the number to the approved campaign.

What does error 30007 mean in HighLevel?

A carrier or provider filtered the message for content, consent, links or spam signals. Fix the content or consent issue before you send again and do not resend the same text.

How long after A2P approval can a text still fail with 30034?

The help article says to allow up to 24 hours after approval for carrier activation before you test again.

Where do I see the error code for a failed text in HighLevel?

Open the conversation and hover over the red warning icon beside the failed text. It shows the error code and a short explanation, with a Learn More link. For 30034, the sub-account's Phone System settings also show a registration banner.

Does Watchtower flag error 30007?

Not by name. Watchtower flags texts rejected for missing A2P registration (30034) as their own finding. A 30007 counts only as one of the failed texts in a sub-account's overall failure share, which is not split by error code.

Does Watchtower send or change texts?

No. Watchtower is read-only. It reports problems and never sends, edits or deletes anything in a sub-account.

Sources this page relies on

Watchtower checks every sub-account each day. Read about sub-account monitoring for HighLevel agencies.