How to Fix GoHighLevel SMS Forwarding Issues

Start by separating SMS receipt from SMS forwarding

There are two different events in this process:

1. Inbound receipt: the connected GoHighLevel number receives the customer message and records it in Conversations.
2. Forwarding: GoHighLevel sends an alert or forwarded message to the configured user phone number.

If the message is visible in Conversations, the inbound route is working at least far enough to create a conversation record. Rechecking the sender’s phone or repeatedly testing the external carrier will not usually identify the forwarding failure. The next question is whether GoHighLevel knows who should receive the message and whether that user’s forwarding path is configured correctly.

Use a controlled test before changing settings

Before editing workflows or user profiles, create a simple test that can be repeated. Send a new SMS from a separate phone to the GoHighLevel number and record:

• The source phone number and destination GoHighLevel number.
• The approximate time the message was sent.
• Whether the message appeared in Conversations.
• Which user, if any, owns the conversation.
• Whether the forwarding phone received anything.

Use a fresh message for each test. Old conversations may retain previous ownership or automation outcomes, which makes them poor evidence for a configuration change.

Check the forwarding user and destination number

The first configuration check is the user who is expected to receive the forwarded SMS. Open the relevant user or staff profile in GoHighLevel and review the forwarding number and notification preferences. Menu names can vary by account version, so look for the staff, user, profile, or notification area rather than relying on one exact navigation path.

Verify the destination number

• Confirm that the number belongs to the intended recipient.
• Check the country code and regional format.
• Remove accidental spaces, duplicated digits, or copied punctuation.
• Confirm that the number is still active and can receive the relevant message type.

Save the profile before testing again. If the number was recently changed, do not assume that an unsaved or partially updated profile is being used by the forwarding process.

Verify the user’s notification choices

Review the user’s SMS, mobile, or conversation notification settings. The labels may differ, but the operational question is consistent: is this user opted in to receive the type of alert that should accompany an incoming conversation?

Do not treat every notification as equivalent. An in-app alert, email notification, and forwarded SMS may use different settings or delivery paths. Test the specific channel that is failing.

Confirm conversation ownership and assignment

Next, open a failed conversation and inspect its assigned user or owner. A common cause of inconsistent forwarding is that the message reaches GoHighLevel but is unassigned, assigned to the wrong person, or assigned after the expected notification event.

Compare the conversation owner with the user whose forwarding number you checked. If they do not match, correct the assignment or review the workflow that controls it.

Questions to ask while inspecting the conversation

• Is the conversation assigned to a specific user?
• Is that user the intended recipient of forwarded SMS?
• Does the assignment happen immediately or after another workflow action?
• Could a later automation be replacing the initial owner?
• Do different sources or phone numbers follow different assignment rules?

If the business expects one person to receive every incoming SMS, the routing rule should make that ownership explicit. If several people share responsibility, the workflow should define how assignment is distributed and what happens when no user is available.

Review workflows and routing logic

Open the workflows, triggers, or automation rules that respond to incoming conversations. Look for actions related to user assignment, tags, pipelines, contact ownership, or notifications. The goal is not to find every automation in the account. It is to identify the rule that determines the recipient for this particular message.

Use this sequence:

A workflow should represent a meaningful business decision, not just a collection of actions. If the system cannot clearly answer who owns an incoming message, forwarding will remain difficult to predict.

Check the connected phone number and provider path

If the user and assignment settings are correct, inspect the GoHighLevel phone configuration. Confirm that the number receiving the inbound SMS is still connected, active, and associated with the intended location or sub-account.

Also consider whether the number has another active configuration outside the expected GoHighLevel path. Legacy provider settings, old routing rules, or competing webhook arrangements can make responsibility unclear. The practical question is: which system is currently supposed to receive and process the inbound event?

Do not change provider settings casually. Record the current configuration first, then make one controlled change at a time. If the number shows an error, has recently been migrated, or behaves differently across message types, gather that evidence before reconnecting anything.

Use the result of each test to narrow the cause

After each change, compare the same checkpoints rather than relying only on whether the phone eventually rings. A useful diagnostic table can be represented by four states:

• Not visible in Conversations: investigate inbound number, contact handling, or provider receipt.
• Visible but unassigned: investigate routing and ownership logic.
• Assigned to the wrong user: investigate workflow conditions and competing assignment rules.
• Assigned correctly but not forwarded: investigate the user’s destination number, notification settings, provider connection, and account-level delivery.

This distinction prevents a common systems mistake: treating every failed notification as a phone-number problem when the actual failure is an ownership problem earlier in the process.

When to escalate the issue

Escalate to GoHighLevel or the relevant phone provider when the conversation is consistently received, assigned to the correct user, and configured with a valid destination, but forwarding still fails after controlled retests.

Include the sub-account or location, the connected phone number, the destination number, timestamps for failed tests, screenshots of the relevant settings, and the conversation assignment result. Avoid sending only a general description such as “SMS forwarding is broken.” The useful evidence is the point in the message path where the expected state stops occurring.

For broader CRM routing and ownership design, a CRM consulting approach can help clarify how conversations, users, workflows, and reporting should work together. GoHighLevel SMS forwarding is more reliable when its assignment logic reflects the real operating model rather than acting as an isolated notification workaround.

Design the workflow so forwarding is dependable

Once the immediate issue is fixed, document the intended operating rule. For example: “Every new inbound SMS is assigned to the support queue, then routed to the on-duty user, who has a verified forwarding number.” That statement is more useful than a vague instruction to “turn on forwarding” because it identifies the business owner, the sequence, and the exception path.

Keep ownership visible, define what happens when no user is available, and use a secondary alert only when it supports a clear response process. Adding more notifications or tools does not automatically create a better system. The workflow should make it clear who acts, by when, and how the team knows that the message was handled.

For organizations reviewing the wider relationship between CRM data, automation, and operational handoffs, ConsultEvo provides systems, CRM, automation and AI implementation services focused on process clarity before tooling.