Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More
3 contributions to GoHighLevel w/ Robb Bailey
Using a shared tag so follow-ups don't collide
Two workflows messaging the same lead on the same day is a quick way to look careless. A simple fix is a shared tag, such as "in-follow-up", applied at the start of each sequence and checked with a condition before any message goes out. Remove it when the sequence ends or the lead replies. Have you ever had two workflows message the same contact at once?
1 like • 3d
@Liton Sarker Naming each view after the question it answers is a good rule, I'm keeping that. On shared vs personal: in HighLevel smart lists are created per user, so by default only the person who made one sees it. I'd keep the working views personal and share the few the whole team relies on (Contacts > Smart Lists > ⋮ > Manage Smart List > share icon). One catch from the same doc: smart lists don't carry over in snapshots, so they have to be rebuilt in each new account. https://help.gohighlevel.com/support/solutions/articles/48001062094-how-to-create-manage-smart-lists
1 like • 2d
@Liton Sarker Good call on the TEAM- prefix. I'd keep that list short and written down where the team already looks (SOP or handover doc): view name, what it's for, and who owns it. Anything not on the list is personal and safe to change. Do you revisit that list when someone new joins the team?
Custom fields in GHL: the quiet upgrade most accounts skip
Most GoHighLevel accounts run on name, phone and email, and nothing else. Adding two or three custom fields, like what the lead wants, their budget range and how they found you, makes every later step smarter. Workflows can branch on them, reports can group by them, and your team stops asking the same questions twice. What custom field do you wish you'd added sooner?
1 like • 21d
A dropdown for service interest, because it lets one If/Else in the workflow send each lead down the right follow-up instead of building a separate workflow per service. Second one for me is a date field for last human contact, so a reactivation workflow can skip anyone your team talked to recently. Keep them as dropdowns instead of free text or the branching gets messy fast.
The AI needs to know when I took over the conversation
One thing we're putting into our AI messaging workflow is tracking who is handling the conversation. If I jump in and reply personally, the worker should pause on that thread until I hand it back. Otherwise it can write a perfectly reasonable follow-up without accounting for what I just told the person. Think about telling someone you'll check something for them, then having an automated message ask if they're ready to book. Now they're responding to two different conversations from the same business. That's why I'm treating the handoff as part of the workflow, alongside the reply itself. Before it says anything, it needs to know whether it's even its turn.
1 like • 22d
In GHL you can do this with a workflow that triggers when a user sends a manual outbound message, adds a 'human active' tag, and pulls the contact out of the AI workflow. Make the bot's first step check for that tag, and clear it when you hand the thread back or after a few quiet days so nothing sits dead.
1-3 of 3
John Carlo Caintic
1
1 point to level up
@john-carlo-caintic-5309
I build GHL systems that agencies can white-label: AI receptionists that answer and book 24/7, lead qualification, and quote follow-up.

Active 2d ago
Joined Oct 26, 2026
Butuan City, Phillipines
Powered by