How to Use GHL Conditional Workflow Branches to Send the Right Follow-Up to Every Lead

Most GHL workflows I audit treat every lead identically — same email, same delay, same CTA, regardless of whether someone booked a call, just browsed a price page, or went cold three weeks ago. Conditional branches fix that. Here's how to build them properly in under an hour.

The Problem: One-Size-Fits-All Follow-Up Kills Conversions

When you build a GHL workflow without conditions, you're making a silent assumption: every lead is in the same situation. They're not. The person who watched your entire webinar and visited your checkout page is in a completely different headspace than someone who downloaded a lead magnet and hasn't opened an email since. Sending them the same follow-up doesn't just underperform — it actively damages trust. The hot lead gets a generic nurture email when they needed a direct call invite. The cold lead gets a hard pitch when they needed warming up first.

I've built automation systems for over 150 coaches at Systrify, and this is the single most common mistake I see in GHL setups: technically working workflows that are strategically wrong because they treat segmentation as optional. It isn't. Conditional branches are how you turn a broadcast into a conversation.

What GHL Conditional Branches Actually Are (and When to Use Each Type)

GoHighLevel gives you two main tools for branching logic inside a workflow: If/Else conditions and Wait + condition checks. They solve different problems.

If/Else branches split a contact's path the moment they hit that step, based on data that already exists — a tag they carry, a custom field value, which pipeline stage they're in, or whether they've opened a previous email. Use these when you want to diverge based on what you already know about the lead right now.

Wait + condition checks pause the workflow and then evaluate a condition after a delay — "wait 2 days, then check if they booked a call." Use these when you need to wait for the lead to do something (or not do something) before deciding the next message. This is the right tool for post-send checks: "did they open the email? If yes, send the case study. If no, send a different subject line."

Most coaches only know about If/Else. Both together are where the real power is.

Step-by-Step: Building Your First Conditional Branch in GHL

Here's how to build a lead follow-up workflow that splits based on whether someone has booked a call or not. This takes about 45 minutes the first time.

• Step 1 — Create the workflow trigger. Go to Automation → Workflows → New Workflow. Set your trigger — for this example, use "Contact Tag Added" and set the tag to whatever fires when a lead opts into your lead magnet or fills your contact form. Name the workflow clearly: "New Lead — Post Opt-In."
• Step 2 — Add your first action. Add a "Send Email" action — your standard welcome email. Keep it warm, no hard pitch. Give it a 10-minute delay from the trigger so it doesn't land instantly.
• Step 3 — Add a Wait step. After the welcome email, add a "Wait" step set to 48 hours. This gives the lead time to book a call or engage before you decide the next move.
• Step 4 — Add an If/Else branch. After the wait, click the "+" and select "If/Else." Set the condition to: Contact → Tag → Contains → "booked-call" (or whatever tag your calendar booking fires). This creates two paths: YES (they booked) and NO (they didn't).
• Step 5 — Build the YES path. Under the YES branch, add a brief confirmation email: "Looking forward to our call — here's what to prepare." Keep it short. Add a calendar reminder SMS 24 hours before the call using a "Send SMS" action with the appointment time merge tag.
• Step 6 — Build the NO path. Under the NO branch, add a "Send Email" action with a different angle — a case study, a client result, or a "still thinking it over?" message. Do NOT send the same email again. Two days later, add another If/Else checking the same tag. If they still haven't booked, send one final SMS: "Hey [First Name], still happy to chat — here's a direct link." If they have booked by now, end the workflow.
• Step 7 — Add a Remove from Workflow action at the end of both branches so contacts don't get stuck in limbo. Also add a "Remove Tag" action to clean up any in-progress tags you used.

Test the workflow by enrolling a test contact manually. Assign and remove the "booked-call" tag manually to walk both branches and confirm the emails fire correctly and the conditions evaluate as expected.

Three Conditional Branch Setups Worth Stealing Right Now

Beyond the basic booked/not-booked split, here are three conditional setups I install for almost every client at Systrify:

1. Open rate branch. Send an email, wait 24 hours, then add an If/Else checking "Email Opened = True." If yes: follow up with content that goes deeper on the topic. If no: resend with a completely different subject line (GHL lets you use the same email body). This alone typically lifts overall open rates by 15–25% because you're not abandoning people who just missed the first send.

2. Pipeline stage branch. When a contact hasn't moved in 7 days, fire a re-engagement workflow. At the branch point, check their current pipeline stage. If they're in "Proposal Sent" — send a follow-up specifically about the proposal. If they're in "Discovery Booked" — send a reminder about the call. If they're in "New Lead" — send a case study. One workflow, three targeted messages, zero manual work.

3. Custom field branch. When leads opt in, capture one qualifying question — business type, revenue, team size, whatever matters for your offer. Then branch your entire nurture based on that field. A coach whose answer is "solopreneur under £5k/month" gets a different sequence than one who answered "agency, 10+ clients." The messages can be nearly identical in structure but personalised in specifics — and that specificity is what makes people feel seen rather than marketed to.