Here’s a scenario you’ve probably lived. A lead fills out your form on Monday, gets your automated text, replies “Yes, Thursday works!” and then gets a text on Tuesday that says “Just checking in, have you had a chance to book a time?” That’s a smart-follow-up automation problem, and it makes your business look like it isn’t paying attention.
The fix is to build smart follow-up automations that react to what each person actually does. Two tools make that possible: wait steps and if/else branches. You don’t need any tech background to use them. If you can say “if this happens, do that,” you can build them.
The idea in plain English
A basic automation is a straight line: step 1, then step 2, then step 3. Everyone gets the same thing no matter what they do.
A smart automation has forks in the road. It waits for a bit, checks what happened, and then picks a path. A reply sends the lead down one path. Silence sends them down another. A booking takes them off the follow-up path entirely.

Wait steps: give people time to respond
A wait step simply pauses the automation. You can pause for a set amount of time (like 2 days) or until a specific event happens (like the lead booking an appointment or replying to a message).
The best use of a wait step is “wait until something happens, but only for so long.” For example: wait up to 2 days for the lead to book. If they book, move on. If 2 days pass and they haven’t, move to the next step. This one setting prevents most of the “why did I get that text?” problems.
If/else branches: choose the right path
An if/else branch checks a condition and sends the contact down one of two (or more) paths. Conditions can be anything your CRM knows about the contact. Common ones include:
- Did they reply to your message?
- Did they book an appointment?
- Do they have a certain tag (like “VIP” or “Existing Customer”)?
- Is a custom field filled in (like “Service Interested In”)?
- Did they open or click your last email?
Example: a smart new-lead follow-up
Let’s say you run a landscaping company and a homeowner submits your quote request form. Here is how a smart automation would handle it:
- Immediately: Send a text and email thanking them and offering a link to book a site visit.
- Wait up to 4 hours for a booking.
- Branch A – they booked: Add the tag “Visit Scheduled,” send a confirmation with what to expect, and end the follow-up.
- Branch B – they didn’t book: Send a friendly text from a real person: “Hi Marcus, this is Jen at Green Valley. Want me to hold a spot for you this week?”
- Wait up to 2 days for a reply or booking.
- Branch B1 – they replied: Stop the automation and create a task for you to continue the conversation personally.
- Branch B2 – still silence: Send a value-add email with a before-and-after photo gallery and a booking link.
Notice what this does. A person who replies never gets an automated message that ignores their reply. A person who goes quiet gets a gentle, useful nudge. That’s the difference between automation that feels robotic and automation that feels attentive.

Five rules for building branches that work
- Always end the automation when someone replies. This is the single biggest improvement you can make. Your replies should come from a human.
- Always end it when someone books. Confirmation and reminders are a separate automation.
- Use tags to mark where people are. Tags like “Quote Sent” and “Follow-Up Complete” make it easy to see where everyone stands. Our guide to tagging like a pro will help you keep these organized.
- Keep it to two or three branches. Complex trees are hard to maintain and harder to fix. If you need more, split the work into two separate automations.
- Add a “catch-all” path. Decide what happens if none of your conditions match. A blank path is where contacts go to disappear.
Test it before it goes live
Before you turn any branching automation on, add yourself as a test contact and walk through each path: reply, book, and do nothing. Check that the messages make sense in order and that the exit points work. If something doesn’t behave the way you expect, our 7-point checklist for automations that didn’t fire will help you find the cause without rebuilding from scratch.
Where to go from here
Once you’re comfortable with one branching automation, apply the same thinking to what you already have. Open your existing sequences and ask: “What happens if this person replies halfway through?” Our drip campaign mistakes post covers other common problems worth fixing at the same time. If you want more quick wins, here are 9 tiny automations that each take under 15 minutes, and a full nurture example in our guide to the 5-step lead nurture sequence.
Your next step
Open the follow-up automation you use most. Add one wait step that waits for a reply or booking, then add one branch that ends the automation if either happens. That 10-minute change will make every follow-up you send feel more personal.


0 Comments