GoHighLevel SMS Replies Not Showing Correctly: What to Check
When a contact replies to your GoHighLevel SMS and the reply does not appear where you expect, the message was usually received but attached to an unexpected contact or conversation. Before assuming the reply was lost, check how the inbound number is matched to a contact record and which conversation it lands in.
Table of Contents
- 01.Why a reply can be hard to find
- 02.What to check first
- 03.The reply attached to an unexpected contact
- 04.The reply is in a different conversation
- 05.Multiple contacts with the same number
- 06.User access and conversation visibility
- 07.The reply was not received by the expected number
- 08.How to find a missing SMS reply
Why a reply can be hard to find
An inbound SMS is matched to a contact based on the phone number it came from. If that number is not on the contact you expect, or if it exists on more than one contact, the reply can attach to a different record or a different conversation. The message is not lost. It is sitting somewhere you did not look. Finding it means understanding how GoHighLevel matches inbound numbers to contacts.
What to check first
- Confirm the phone number the contact replied from.
- Search for that number across your contacts.
- Check whether the number exists on more than one contact.
- Look at the conversation view for the number that received the reply.
- Confirm which assigned number the contact originally received the SMS on.
The reply attached to an unexpected contact
If the inbound number matches a different contact than the one you were working with, the reply shows up on that other record. This happens when a number is reused, when a contact was created from the inbound number alone or when two contacts share a similar number. Search the number across all contacts to find where the reply actually landed.
The reply is in a different conversation
GoHighLevel organizes SMS into conversations tied to contacts and numbers. A reply can land in a conversation you are not currently viewing, especially if the contact has more than one phone number or if the message came in on a different assigned number than the one you sent from. Open the conversation view for the correct assigned number to see the full thread.
Multiple contacts with the same number
When the same phone number exists on more than one contact, an inbound reply can attach to whichever record the system matches first. This is a duplicate contact problem as much as an SMS problem. Resolving it means cleaning up the duplicate records so the number lives on a single contact. Until the duplicates are merged, replies may continue to land on the wrong record.
User access and conversation visibility
Even when a reply is correctly attached, a user may not see it if they do not have access to the contact or the conversation. Permissions and team assignments can hide conversations from users who expect to see them. Confirm the user assigned to the contact has access to the conversation view where the reply landed.
The reply was not received by the expected number
If the contact replied to a different number than the one you sent from, or if the inbound number is not properly configured for SMS, the reply may not reach the conversation you expect. Confirm the assigned number the contact originally received the message on and check whether that number is set up to receive inbound SMS.
How to find a missing SMS reply
- 1.Note the exact phone number the contact replied from.
- 2.Search that number across all contacts to find the matching record.
- 3.If more than one contact has the number, that is the cause of the misdirected reply.
- 4.Open the conversation view for the assigned number that received the reply.
- 5.Confirm the user assigned to the contact has access to that conversation.
Frequently Asked Questions
Why are my GoHighLevel SMS replies not showing?
The reply was usually received but attached to an unexpected contact or conversation. This happens when the inbound number matches a different contact, exists on more than one contact or lands in a conversation you are not viewing. Search the number across all contacts to find where the reply actually went.
Why does a GoHighLevel SMS reply attach to the wrong contact?
Inbound SMS is matched by phone number. If the number exists on more than one contact or matches a different record than the one you expect, the reply lands there. Cleaning up duplicate contacts so each number lives on a single record prevents this.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
GoHighLevel SMS Not Sending: Common Workflow, Phone and Contact Issues
SMS failures in GoHighLevel usually come from phone number setup, carrier filtering, DND settings or workflow conditions. This guide covers what to check before you rebuild the workflow.
GoHighLevel Duplicate Contacts: Why They Happen and How to Keep CRM Data Clean
Duplicate contacts break follow-up, inflate reporting and confuse automation. This guide explains why duplicates appear in GoHighLevel and how to prevent them at the source.