Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More
9 contributions to GoHighLevel w/ Robb Bailey
Using a conditional wait step instead of a fixed delay
A fixed delay sends the next message whether or not the contact has replied. Use a wait step that ends when the contact replies or a tag is added, with a timeout as the fallback. The workflow then reacts to what the contact actually does, and you stop following up with people who already answered. How do you handle replies mid-sequence?
0 likes • 22h
@Liton Sarker The timeout as a fallback is the part people forget, so it's good you called it out. When someone replies mid-sequence, I'd pause the follow-ups and give a person a task to answer it, and only restart the sequence if the reply was something like "not yet, check back next month", because a real question deserves a real answer before anything automated goes out again.
Reading the execution log: the fastest way to debug a workflow
When a workflow misbehaves, the execution log usually already knows why. Open it, find the contact that went wrong, and read it step by step: which trigger fired, which condition was checked and which branch the contact took. Most issues turn out to be a condition that's too broad or a wait step that's too short. What's the most common bug you find in the log?
1 like • 5d
@Liton Sarker Yes, a short one: trigger filters, re-entry, wait steps that run longer than expected, and whether the contact's phone or email is actually valid. Most double sends or missing messages turn out to be one of those four.
0 likes • 4d
@Liton Sarker It's worth doing. A one line note on the contact with the cause and the fix is plenty, and after a few weeks it's easy to see if the same workflow keeps showing up.
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?
0 likes • 10d
@Liton Sarker Simple fix that saves a lot of awkward moments. It's worth adding a weekly check for contacts who still carry the tag but aren't in any active sequence, since one failed step can leave it stuck and quietly block every message after that.
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 • 14d
@Liton Sarker Clear way to explain why this matters. One I'd add for service businesses is the quote amount saved as a number field, because then you can see how much money is sitting in quotes nobody has answered yet and follow up on the biggest ones first.
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 • 15d
@David Ramirez Treating the handoff as part of the workflow is a really smart way to look at it. One thing to watch is follow-ups that were already sitting in a wait step before you jumped in, so have each one check who owns the thread right before it sends, not just when it was scheduled.
1-9 of 9
Madonna Lapid
2
10 points to level up
@madonna-lapid-3070
Custom instant quoting systems for home service businesses. Customers get a real price in 60 seconds, with follow-up until they book.

Active 1h ago
Joined Oct 17, 2026
Calamba City, Laguna
Powered by