Module 5 · Chapter 4

Conditional logic and branching

8 min read

A linear sequence sends every prospect the same emails in the same order regardless of how they interact with your messages. That is a missed opportunity. Conditional logic lets your sequences adapt in real time based on what the prospect does — or does not do. The result is smarter, more relevant outreach that feels less like a campaign and more like a conversation.

In this chapter, you will learn how to set up branching paths for the most common prospect behaviors, when conditional logic genuinely improves performance versus when it adds unnecessary complexity, and how to design smart sequences that run on autopilot.

What is conditional logic in sequences?

Conditional logic is an if-then framework applied to your outreach sequence. Instead of "send email 2 three days after email 1 no matter what," you create rules like "if prospect opened email 1 but did not reply, send email 2A. If prospect did not open email 1, send email 2B with a different subject line."

This simple concept has a profound impact on performance because it allows you to tailor your next action based on the signal the prospect just gave you. An open without a reply is a very different signal than no open at all. A link click without a reply means something different again. Conditional logic lets you respond to each signal appropriately.

The five core conditions to build around

Most outreach platforms support a core set of conditions. Here is how to think about each one and what actions to take.

1. Opened but did not reply

This is the most common and useful condition. The prospect saw your email, read at least part of it, but did not take action. This is a warm signal. They are aware of you and interested enough to open, but something — timing, relevance, or a weak CTA — stopped them from responding.

Best actions:

  • Follow up sooner than you normally would (2 days instead of 3-4)
  • Keep the same thread — they already engaged with the conversation
  • Try a different CTA. If you asked for a call, try offering a resource instead
  • Add a social touch the same day they opened — they are already thinking about you

Watch out

Open tracking is not perfect. Email clients that pre-fetch images, privacy tools, and corporate firewalls can trigger false opens. Use open data as a directional signal, not a certainty. Never reference the fact that you know they opened your email — it feels invasive.

2. Did not open

If the email was not opened, the problem is almost certainly the subject line or the send timing. The content of the email is irrelevant if it was never seen.

Best actions:

  • Resend with a completely different subject line
  • Try a different send time (morning if you originally sent afternoon, or vice versa)
  • Start a new thread instead of replying in the same one
  • If available, try sending from a different sender address within your team

3. Clicked a link

A link click is one of the strongest intent signals you can get from outreach. The prospect not only opened your email but actively engaged with the content enough to click through. This person is interested — they just have not committed to a reply yet.

Best actions:

  • Follow up within 24 hours while interest is hot
  • Reference the content they clicked on: "Saw you checked out the case study — any questions I can answer?"
  • Move them to a faster cadence or flag them for a phone call
  • Offer a related, deeper piece of content as a natural next step

Key insight

Prospects who click links are 4-5x more likely to eventually convert than those who only open. Treat every link click as a priority follow-up — but never say "I saw you clicked the link." Instead, naturally bring up the content: "Hope the case study was helpful. Happy to walk you through the specifics if you're interested."

4. Replied with a negative response

Negative replies come in many flavors. "Not interested," "wrong person," "bad timing," and "unsubscribe me" all require different responses.

Branch handling:

  • "Not interested": Remove from sequence, send a brief polite reply, mark in CRM. Do not argue or try to re-pitch.
  • "Wrong person": Thank them, ask for a referral to the right contact, and remove them from the sequence.
  • "Bad timing": This is actually a positive signal. Ask when would be better, set a reminder, and move them to a timed re-engagement queue.
  • "Unsubscribe" or any opt-out: Remove immediately. This is both a legal requirement and common decency.

5. Replied with a positive response

When a prospect replies positively, the sequence should immediately pause or end. The worst thing you can do is send an automated follow-up after someone has already agreed to meet. Positive replies should trigger:

  • Automatic sequence pause
  • Notification to the account owner for manual follow-up
  • CRM record update (lead status change, task creation)
  • If available, automatic calendar link or meeting scheduler

Designing branching paths

When you combine multiple conditions, you create branching paths — different journeys through your sequence based on prospect behavior. The key is to keep branching manageable. Overly complex sequences are impossible to maintain and difficult to analyze.

The recommended approach: two-branch simplicity

For most teams, the ideal branching structure has two paths at each decision point: the engaged path and the unengaged path. Here is what this looks like in practice:

After email 1 (wait 3 days):

  • If opened: Send email 2A (same thread, reference previous context, new CTA)
  • If not opened: Send email 2B (new thread, new subject line, same core offer)

After email 2 (wait 4-5 days):

  • If opened or clicked: Send email 3A (social proof, faster follow-up)
  • If not opened: Send email 3B (completely different angle, possibly different sender)

This two-branch approach doubles your chances of finding a message that resonates without creating an unmanageable web of conditions.

Watch out

More branches does not mean better performance. Every branch you create is a branch you need to write copy for, monitor, and optimize. Start with simple two-branch logic. Only add complexity when you have data showing it improves results.

Setting up smart sequences in practice

Here is a step-by-step process for building a conditional sequence:

  • Step 1: Map your linear sequence first. Write the default path as if no branching existed. This is your baseline.
  • Step 2: Identify the highest-impact decision points. Usually this is after email 1 and after email 3. These are the moments where engagement data is most actionable.
  • Step 3: Write the alternate branch. For each decision point, write the variant email. The unengaged branch should try a different approach; the engaged branch should accelerate.
  • Step 4: Set your exit conditions. Define exactly what removes someone from the sequence: positive reply, negative reply, bounce, opt-out, or sequence completion.
  • Step 5: Test with a small batch. Run the conditional sequence with 50-100 prospects before scaling. Verify that branches trigger correctly and exit conditions work as expected.

Advanced conditions worth exploring

Once you are comfortable with basic open/click/reply conditions, you can explore more sophisticated triggers:

  • Website visit: If your platform tracks website visitors, you can trigger a follow-up when a prospect visits your pricing or product page after receiving an email.
  • Multiple opens: A prospect who opens the same email three or more times is showing strong interest. Flag them for immediate follow-up or a phone call.
  • Forwarded email: Some platforms can detect when an email is forwarded to a colleague. This is a strong buying signal — it means your email is being shared internally.
  • Time-based conditions: "If prospect has not opened within 48 hours of delivery" is more precise than "3 days after send" because it accounts for delivery timing.

When conditional logic is not worth it

Conditional logic is powerful, but it is not always the right call. Skip it in these situations:

  • Small list sizes: If you are sending to fewer than 200 prospects, the branches will have too few people in each path to draw meaningful conclusions.
  • Early in your outreach journey: Get your linear sequence working first. Adding branches to a fundamentally broken sequence just creates more broken paths.
  • When you lack the time to maintain it: Every branch needs copy, monitoring, and optimization. If your team is stretched thin, a well-written linear sequence will outperform a neglected conditional one.
"Start linear. Add conditions based on data, not assumptions. Every branch you add is a hypothesis — validate it before building on top of it."

Conditional logic transforms sequences from static email chains into dynamic, responsive outreach systems. Master the basics — open, click, reply conditions — and you will see meaningful improvements in both reply rates and reply quality. In the next chapter, we will cover how to systematically test and optimize every element of your sequences through A/B testing.