Why is GoHighLevel still sending follow-ups after a customer replies?

Short answer: GoHighLevel keeps sending follow-ups after a reply because the workflow that sends them is not set to stop on response, or because the contact is enrolled in a second workflow you forgot about. Find the workflow that sent the message from its enrollment history, turn on Stop on Response in every follow-up workflow, and add one reply handler workflow that removes the contact from everything else. Test it with a real reply before you trust it.

First, find the workflow that actually sent the message

Do not change anything yet. Open the conversation, note the exact time of the unwanted message, then check the enrollment history of the workflows that could have sent it. You are looking for the contact's name with a step that ran at that time.

This matters because the answer is rarely the workflow you built last week. It is usually an older sequence, a form-submission workflow from a previous agency, or a missed-call text back that also runs a follow-up. If you inherited the account, expect two or three workflows that all text new leads. A Reddit thread from this week makes the same point: check which workflow sent them before you touch settings.

Write down every workflow that shows the contact. If it is more than one, you have found the real problem, and the fixes below are about that.

The causes, in the order we check them

Most accounts we open have the first two at once. One workflow has the setting off, and another one nobody remembered is doing the sending.

How to set Stop on Response properly

Stop on Response lives in the workflow's settings, not in the individual steps. When it is on, a reply from the contact removes them from that workflow, so remaining wait steps and messages do not fire. Because it is a per-workflow setting, you have to check it in every workflow that sends follow-ups. Make a short list and tick each one off.

Then test it the boring way. Enroll your own mobile number, let the first message arrive, reply from your phone, and watch the enrollment history. Do the same for email if the sequence uses email. If the contact leaves the workflow after the reply, the setting works on that channel.

Do not skip the test. A setting that looks right and a setting that behaves right are different things, and the first time you find out should not be a customer who says "I already answered you."

Add one reply handler so overlapping workflows stop together

Per-workflow settings fall apart as an account grows. The fix we install is a single workflow whose only job is to deal with replies.

1. Create a workflow with the Customer Replied trigger.
2. First action: add a tag such as Replied.
3. Second action: Remove from Workflow, once for each follow-up sequence the contact might be in.
4. Then move the opportunity to a stage like Engaged and assign a task or send an internal notification to the person who should answer.

Now a reply does three things at once. It stops the sequences, flags the contact, and puts a human on it. If you later build a new follow-up workflow, adding it to the handler's removal list is a ten-second job. This is the same pattern we use in the speed to lead system and in quote follow-up for contractors, where the whole point is that automation hands off to a person the moment the customer speaks.

Add an If/Else check in front of long sequences

If a sequence runs over several days, put an If/Else step before each message that asks whether the contact has the Replied tag. If yes, end the path. If no, send. It looks redundant next to Stop on Response, and that is the point: it covers the gap between a reply landing and the removal action finishing, and it protects you if someone later turns the setting off.

Keep the logic readable. One tag, one condition, same name everywhere. We have seen accounts with 242 tags where nobody could say which one meant "this person answered," which is how this problem comes back. If your tag list is already tangled, see the notes in our audit checklist.

When the message is not really a follow-up problem

Two cases look similar and are not. If the same message went out twice at once, you have a duplicate send, not a missed reply, and why GoHighLevel sends duplicate text messages covers it. If the workflow log says it ran fine but the wrong content went out, read why a workflow can say it worked and still send the wrong message.

The third case is the serious one. If the contact replied STOP and still got a message, check whether the contact is marked Do Not Disturb for SMS, then find the workflow that sent it and fix it the same day. Opt-outs sit under TCPA rules enforced through the FCC, and carriers watch for them too. This is practical guidance and not legal advice.

What we would do first

We would open every workflow that texts or emails a lead, list which ones have Stop on Response off, and map which contacts sit in more than one sequence. Then we would build the reply handler and test it with a real phone. On an account with dozens of overlapping workflows, that mapping is most of the work, and it is what our GoHighLevel account audit, starting at $497, is built for. If you only have two or three workflows, you can do the steps above yourself in an afternoon.

Yaakov (Koby) Oranski, Founder and CEO of Yotomations

Certified GoHighLevel Admin and Partner. Koby designs CRM migrations, two-way integrations, billing systems and AI agents for service businesses, and writes from the engagements described on this site.

Published 2026-10-21