GoHighLevel SMS Not Sending? How to Find the Cause and Fix It

A text that does not arrive is one of the most common HighLevel problems, and one of the most expensive: missed-call text-backs, booking confirmations and lead follow-ups all depend on it. The good news is that the cause is usually one of six things, and the account tells you which if you know where to look.

Step 1: find out whether the text was sent at all

Everything else depends on this. Open the contact, go to their conversation and look for the message.

• The message is not there. HighLevel never tried to send it. The problem is upstream: the workflow did not fire, the contact took another branch, or the step was skipped. Open the workflow’s execution log for that contact and read the status on the SMS step. The guide on workflows not firing covers that path.
• The message is there, marked failed or undelivered. HighLevel tried to send it and something stopped it. Hover or click the status for the error detail, then work through the causes below.
• The message shows as delivered but the person says they got nothing. The carrier accepted it. The problem is likely on the handset: a blocked sender, a spam filter on the phone, poor signal or a wrong number that belongs to someone else.

Step 2: check the contact

Do Not Disturb

When a contact is on Do Not Disturb for SMS (or for all channels), texts to them are skipped. This often follows an opt-out reply such as STOP. Check the DND settings on the contact record. Only remove DND if the person has genuinely asked to receive texts again; DND is usually there for a reason.

Number format and landlines

A phone number needs to be in full international format, with the country code. A number saved as a local 10-digit string can fail, especially for contacts in other countries. Landlines cannot receive texts at all.

What to do:

1. Correct the number on the contact to full international format (for example +1 followed by the number for the US and Canada).
2. Fix the source. If a form collects numbers without a country code, add a country selector or make the format clear.
3. Send a test to a mobile number you own.

Step 3: check the account

Is there an active sending number?

SMS needs a phone number on the location, either through HighLevel’s phone system or a connected provider. If a number was released, never purchased, or is not set as the default, texts have nothing to send from. Check the location’s phone number settings, confirm a number is active, and set a default sender.

A2P 10DLC registration (US numbers)

If you text US numbers from a US 10-digit local number, carriers expect your brand and your messaging campaign to be registered and approved, with your sending number attached to that campaign. Pending, rejected or incomplete registration is one of the most common reasons texts fail or are filtered in the US.

Check three things in the account’s trust or A2P area:

1. Brand status: approved.
2. Campaign status: approved.
3. Number assignment: your sending number is attached to the approved campaign.

If registration was rejected, the A2P 10DLC rejection guide explains the usual reasons, and the A2P readiness checker helps before you resubmit. This is general information, not legal advice.

Carrier filtering of the content

Even registered traffic can be filtered if a message looks like spam. Common triggers include public link shorteners, aggressive urgency in capitals, and content that does not match the use case you registered. If one message template fails while others send, compare its wording and links with the ones that work.

Step 4: check the workflow step

If the message never appeared in Conversations, read the execution log on the workflow:

• Skipped because of DND: see above.
• Missing phone number: the contact has no number, or the number is in a different field from the one the step uses.
• The contact took the other branch of an If/Else condition, so the SMS on this path never ran.
• A wait step is still holding the contact.
• The workflow stopped early because of a goal or a stop-on-response setting.

A quick test routine

When you change something, test it the same way each time so you know what fixed it:

1. Create a test contact with your own mobile number in full international format.
2. Make sure it is not on DND.
3. Trigger the workflow (or send a manual text from Conversations first, which separates account problems from workflow problems).
4. Read the status on the message and the execution log on the workflow.

If a manual text works but the workflow text does not, the problem is in the workflow. If neither works, it is the number, the registration or the content.

When it is worth getting help

If texts still fail after these checks, especially with registration that has been rejected more than once or messages that fail only for some carriers, an expert review usually saves time. Repeated resubmissions can cost both time and fees. The GHL Troubleshooter collects your answers, and you can send them straight into a troubleshooting audit request.