Step-by-Step Guide
How to Automate WhatsApp Follow-Up in GoHighLevel
This guide assumes your WhatsApp Business API is already connected inside GoHighLevel — if it isn't yet, start with my guide on sending GoHighLevel leads to WhatsApp for the WABA setup and template approval first. What's below is the part that comes after: how to actually design a multi-touch WhatsApp follow-up sequence inside the workflow builder — the cadence, the wait steps, the reply branching, and the rule that trips up almost everyone who skips it.
On This Page
How to Design the Sequence
Six steps, in the order I actually build them — from mapping the cadence on paper to watching a real test contact move through every branch.
Map the touches and the gaps between them, before touching the workflow builder
WhatsApp is a higher-intimacy channel than email, so a good follow-up sequence usually runs fewer touches, spaced tighter, than an email drip would. A workable starting cadence: an immediate first message, a second touch a few hours later the same day if there's no reply, then touches at roughly day 1, day 3, and day 7, tapering off after that. Sketch this on paper — trigger, touch 1, gap, touch 2, gap, touch 3 — before you open GoHighLevel's workflow builder, so the build is just translating a decision you've already made instead of making it live inside the canvas.
Decide which touches need a Template and which can be free-form
This is the single most important design decision in the whole sequence, and it has to be made touch-by-touch, not once for the whole workflow. If the contact hasn't messaged you back, every touch has to be an approved Meta template. The moment they reply, a 24-hour customer service window opens and later touches inside that window can be free-form session messages instead. Template setup and approval itself isn't covered here — see my guide on how to send GoHighLevel leads to WhatsApp for that groundwork; this step is about deciding, touch by touch, which one your sequence needs.
Use a Wait step to create the gap, not a fixed calendar date
Between each touch, add a Wait action set to pause for a duration rather than a specific date, so the timing is relative to when the contact entered the sequence, not a shared clock. GoHighLevel's Wait action also supports pausing until an event — most usefully here, until the contact replies on WhatsApp, with an optional timeout so the sequence still advances automatically if nobody responds. That event-based option is what makes the next step possible.
Branch on whether they replied, using If/Else or the window-check condition
After a Wait-for-reply step, add an If/Else action that checks whether the contact actually responded — off a reply-received condition, an inbound-message event, or a tag your workflow sets on their first reply. Contacts who replied should branch into a different path than contacts who stayed silent: a warmer, free-form-style path for the repliers, and the next scheduled template touch for everyone else. If you're using GoHighLevel's WhatsApp template reply buttons, note that WhatsApp V2 can auto-generate a branch per button response, which handles a chunk of this branching for you without a manual If/Else.
Stop the sequence from re-firing on someone who already responded
The most common WhatsApp automation complaint isn't a missed message — it's a contact who replied on Tuesday still getting Thursday's scheduled follow-up as if nothing happened. Guard against it two ways: tag the contact the moment they reply (something like whatsapp-replied) and add that tag as an exit or re-entry-suppression condition on the workflow itself, and put an If/Else check at the top of every later touch that skips the send if the reply-tag is already present. Belt and suspenders here is worth it — a sequence that double-messages a warm lead looks worse than one that's slightly slow.
Test all three paths before it touches a real contact
Run a test contact through three scenarios: one that never replies (confirm it falls back to template touches on schedule and stops after the last one), one that replies immediately (confirm it branches into the free-form path and the later template touches don't fire), and one that replies late, after touch 3 but before touch 4 (confirm the re-trigger guard catches it). Watch the execution log for each run, not just the end state — a branch that looks right in the builder can still route or send wrong until you've watched a message actually land.
The 24-Hour Window: Template vs. Free-Form
Every branch decision in a WhatsApp sequence comes back to one thing: whether a 24-hour customer service window is currently open with that contact. It opens the moment they send you a message, stays open for 24 hours from their last inbound message, and resets if they message again before it closes. Inside that window, you can send free-form (session) messages — ordinary text, no pre-approval needed. Outside it, only an approved Meta template (Utility, Marketing, or Authentication) can reach them.
For sequence design, that means the window state has to gate every touch, not just the first one. A contact who replied on day 1 has an open window for the next 24 hours — a day-2 touch sent while it's still open can be free-form, but if they go quiet and you don't catch up with them until day 5, that touch is back to template-only. GoHighLevel's WhatsApp Customer Service Window Check condition exists specifically to test this before each send, which is the cleanest way to build it rather than assuming the window state from an earlier branch still holds.
One more thing worth designing around now rather than discovering later: Meta has announced that starting October 1, 2026, free-form service messages sent inside the window — along with utility templates sent inside the window — move to per-message billing, at the same rate as a utility template in that country, with no volume discount. Until now those in-window sends have largely been treated as the "free" option compared to templates. The window still determines what you're allowed to send; it just stops being a way to avoid a per-message cost once that date passes, so factor it into your cost estimate for a high-volume sequence rather than assuming in-window messages are free by default.
Common Mistakes & Gotchas
The four things I see break a WhatsApp follow-up sequence after it's already live, usually a few days after someone builds it and stops watching the execution log.
Sending free-form after the window has already closed
A reply on Monday doesn't keep the window open all week — it closes 24 hours after their last inbound message. A sequence that checks for a reply once, early on, and then sends free-form for every touch after that will start failing silently once the window lapses. Re-check the window state before each free-form send, not just once at the start of the branch.
One tag doing the job of two
It's tempting to reuse a general 'replied' tag from another channel to gate the WhatsApp sequence. Give the WhatsApp reply its own tag. A contact who replied to an email but never opened WhatsApp isn't the same signal, and conflating them either suppresses touches that should still send or lets duplicate touches through.
No re-entry guard on the trigger itself
If the sequence can be re-triggered by the same event that started it the first time — a tag re-applied, a pipeline stage revisited — a contact who already finished the sequence once can restart it from touch one. Scope the trigger with a condition that excludes contacts who already carry the sequence's completion or reply tag.
Treating every template the same
Utility, marketing, and authentication templates are reviewed and categorized differently by Meta, and a template that reads as promotional inside what you declared a utility template gets rejected. If a later touch in the sequence is meant to nudge toward a booking or offer, expect it to need marketing-category approval, not the lighter utility review your first touch may have sailed through.
Frequently Asked Questions
For WhatsApp specifically, fewer and tighter-spaced than an email sequence — typically 3-5 touches across the first week, front-loaded (same day, next day) and tapering off after that. WhatsApp is a channel people expect to be personal and low-volume; a sequence that behaves like an email drip on WhatsApp reads as spammy faster than the same cadence would on email.
Want This Built and Tested for You Instead?
Everything above is buildable yourself inside GoHighLevel with enough patience for the execution log — I'd rather you actually ship it than not. If you'd rather not spend that time on window checks and branch testing, this is exactly what I build for clients: full WhatsApp automation sequences and the wider GoHighLevel automation it plugs into, tested against real reply scenarios before it goes live for your leads.
- 7+ years building CRM and WhatsApp automation for businesses worldwide
- 100,000+ leads delivered through systems built the same way this guide describes
- One real estate automation system alone responsible for 50,000+ of those leads
Ready to Automate Your WhatsApp Follow-Up?
Fastest way to start: message me directly on WhatsApp with what your current sequence (or lack of one) looks like. Or send the details below and I'll get back to you.