Contacts getting the same text twice, texts from two different numbers, or a whole list blasted at once. The four causes and the fix for each.
Short answer: duplicate texts in GoHighLevel come from one of four places: two workflows that trigger on the same event, a contact that re-enters a workflow after a tag or stage change, a paused workflow that is republished and releases everyone waiting inside it at once, or a Yelp or Facebook conversation that is also mirrored into SMS. Texts from two different numbers are a fifth, related problem: the workflow sends from the default number instead of the number the customer used. Each has a specific fix below.
The most common cause in accounts that have grown over time. A "new lead" workflow was built in March, another in June, both fire on the same form submission or pipeline stage, and both send a welcome text. The fix is to map every trigger in the account to every workflow that uses it, then consolidate. In a 160-workflow account this is where most duplicates live.
Tag added, tag removed, tag added again by a different automation, and the contact re-enters a workflow that has "allow re-entry" on. Set re-entry off unless it is deliberately needed, and use a single source of truth for the tag that triggers it.
A drip workflow with a seven-day wait step holds hundreds of contacts. Someone pauses it for a holiday, then republishes. Every contact advances at once and the whole list gets the next message in the same minute. Before editing a live drip, drain it: stop new entries, let existing contacts finish, or clone the workflow and point the trigger at the clone. GoHighLevel does not have a true holiday pause for a drip, so plan for it in the design.
Yelp and Facebook conversation providers deliver a message once as a Yelp or Facebook message and, if a workflow or conversation AI replies through SMS, the contact sees a second copy. Configure the AI and follow-up workflows to reply on the originating channel, and do not attach an SMS sequence to a lead that arrived without a phone number.
A customer calls your tracking number for a Yelp campaign, then gets a text from your default number, then a callback from a third. Continuity breaks and people assume spam. Store the inbound number on the contact at first touch, and set every send step to use that number. For multi-location or multi-source businesses, number pools by source keep this consistent.
A "hot agent" tag was supposed to exclude contacts from the drip, but they kept getting texted. Tag conditions evaluate only at the step where they sit; if the contact is already past it, or a parallel workflow has no filter, the send happens. Put exclusion conditions on the trigger and in every workflow that can send.
Export the workflow list, note every trigger, and group by trigger. Anything with two or more workflows is a suspect. Then check re-entry settings and any workflow edited in the last 30 days that has wait steps. That is the core of the GoHighLevel audit we run, and it is why we ask for read-only access before quoting a fix.
The workflow was paused or edited and republished while contacts were sitting in a wait step. On republish, every contact advanced to the next action at the same time. Drain or disable the workflow for existing contacts before republishing, or use a workflow version with a fresh trigger.
The workflow is using the sub-account default number. Set the workflow's from number to the contact's assigned number, use number pools tied to lead source, or store the inbound number on the contact and reference it in the send step.
Tag conditions inside a workflow only evaluate at the step where they sit. If the contact was already past that step, or a second workflow has no filter, the text still goes out. Move the filter to the trigger and audit every workflow that shares the trigger.
Book a 30-minute call. We look at the account live and tell you what is broken, what we would fix first and what it would cost.
No pitch deck. We look at your current setup and tell you what we would do and what it would cost.Need more than GoHighLevel? Yotomations, our parent company, also builds AI agents, custom software and websites.
