Use case · Follow-up and nurture
Follow-up sequences that stop the moment someone says stop
Most leads need more than one touch, and most teams forget the third one. We build follow-up and nurture sequences across email, WhatsApp and SMS that record consent per channel, check it before every message, pause when a person replies and honour an opt-out on every channel at once. Bought lists never go in.
At a glance
- What it takes on
- Capture consent per channel
- Run the sequence
- Draft answers to replies
- Pause on real engagement
- Connects to
- Your CRM
- Your email sending service
- WhatsApp Business Platform
- Twilio
- n8n, Make or custom code
- OpenAI, Anthropic Claude or Google Gemini
- Typical rollout
- Week 1 → Weeks 5–6See the plan
The problem
Where the work gets stuck today
Follow-up is where pipelines leak. A lead asks for a quote, gets one reply and then nothing, because the rep moved on. Automated sequences often run blind instead: they email someone who already booked a call, message people on WhatsApp who only gave an email, and carry on after an unsubscribe because each tool keeps its own list.
That is a deliverability problem and a legal one. Mailbox providers watch complaint rates, WhatsApp limits businesses that users block or report, and consumer-protection rules in most markets require a working opt-out that is honoured promptly.
| Failure | Why it happens | The gate that prevents it |
|---|---|---|
| Messages after a reply | The sequence never reads the inbox or the CRM | Any reply or booked meeting pauses the sequence |
| The wrong channel | Consent stored as one yes or no for everything | Consent recorded per channel, with source and time |
| Opt-outs ignored elsewhere | Each tool keeps its own suppression list | One suppression list checked before every send |
| Messages at night | No quiet hours or time zones | Sending windows in the contact’s local time |
| Cold lists | Bought or scraped contacts loaded into the tool | Only contacts with recorded consent can enter |
Task catalog
What the system takes on
Task 01
Capture consent per channel
Forms, chats and calls record what the person agreed to (email, WhatsApp, SMS or none), with the wording they saw, the source and the time. That record decides which channels a sequence may use.
Task 02
Run the sequence
Steps follow rules you approve: what to send, on which channel, after how long and when to skip. Personal details come from the enquiry and the CRM, inside templates you signed off.
Task 03
Draft answers to replies
When a lead replies with a question, the assistant drafts an answer from approved content for the owner, or answers directly on topics you allow. The sequence pauses either way.
Task 04
Pause on real engagement
A reply, a booked meeting, a purchase or an open support ticket pauses or ends the sequence, so nobody gets a reminder for a call they already booked.
Task 05
Honour opt-outs everywhere
An unsubscribe click, a STOP reply or a request to a person adds the contact to one suppression list that every channel checks, followed by a single confirmation.
Task 06
Report each step
Every contact’s history shows each message, the consent that allowed it and why the sequence stopped. A weekly report shows replies, opt-outs and complaints per step, so weak steps get rewritten.
Step trace
One run, step by step
Day 0 · Enquiry
Quote request, consent recorded
Website form: the visitor ticks email updates and leaves WhatsApp unticked. Consent is saved with the form wording, the page and the time.Day 0 · Email
The quote, plus one question
Sent inside the sending window, with the unsubscribe link and your postal address.Day 2 · Consent gate
WhatsApp nudge skipped
The sequence has a WhatsApp step, but there is no WhatsApp opt-in on record, so the step is skipped and logged.Day 3 · Email
A short follow-up with an explainer
Checked first against the suppression list and the CRM: no reply, no meeting, still subscribed.Day 5 · Reply
The lead asks about delivery times
The sequence pauses. The assistant drafts an answer from approved content and the owner sends it.Branch · Opt-out
If the lead had replied “stop”
Added to the suppression list for every channel at once, one confirmation sent, sequence ended. No later step can send.Day 12 · Last step
No booking yet: one final check-in
Resumed by the owner after the thread went quiet. Afterwards the contact moves to the monthly newsletter they opted into.
Read the trace as text (Sample data)
- Day 0Website formStepQuote request submitted. Consent: email yes, WhatsApp not given. Stored with the form wording and time.
- Day 0SequencerDoneFirst email sent inside the sending window, with unsubscribe link and postal address.
- Day 2Consent gateCheckWhatsApp nudge skipped: no WhatsApp opt-in on record.
- Day 3Suppression checkDoneNot suppressed, no reply, no meeting booked. Second email sent.
- Day 5Inbox watcherStepReply detected. Sequence paused and the reply routed to the owner.
- Day 5AssistantApprovalAnswer drafted from approved delivery content, waiting for the owner.
- Day 12OwnerStepSequence resumed for one final check-in; the contact then moves to the newsletter they opted into.
Consent gates
What each channel checks before a message goes out
| Channel | Before every send | When someone opts out | Public guidance |
|---|---|---|---|
| Consent or a documented relationship on record, not suppressed, inside the sending window. Every message carries a working unsubscribe link and your postal address. | Suppressed on every channel at once. The FTC guide sets the outer limit: honour opt-outs within 10 business days, keep the mechanism working for at least 30 days after sending, and never charge or add steps to opt out. | FTC CAN-SPAM compliance guide | |
| Bulk email to Gmail | One-click unsubscribe headers on marketing messages, an authenticated sending domain and a watched complaint rate. | One-click requests write to the same suppression list. | Gmail email sender guidelines |
| An opt-in that names your business. Once the customer service window has closed, only templates approved in advance. | A STOP reply or a block suppresses the contact; no further templates are sent. | Meta: opt-in and service-window documentation | |
| SMS and voice | Consent recorded for the number and the market, and quiet hours in local time. | STOP and similar replies suppress the number on every channel. | Checked per market with your compliance owner |
Bought, rented or scraped lists never enter a sequence. Addresses of people who opted out are never sold or shared, and the suppression list outlives every campaign.
Public sources for the gates
- CAN-SPAM Act: A Compliance Guide for Business (opens in a new tab) · Federal Trade Commission · accessed
- Email sender guidelines (opens in a new tab) · Gmail Help, Google · accessed
- Get opt-in for WhatsApp (opens in a new tab) · Meta for Developers · accessed
- Service messages and the customer service window (opens in a new tab) · Meta for Developers · accessed
Systems involved
What it connects to
- Your CRM
- Lead source, owner, stage and consent fields, read and updated through its API.
- Your email sending service
- Sends from your authenticated domain; unsubscribe and bounce events flow back to the suppression list.
- WhatsApp Business Platform
- Template and service messages on a number registered to your business.
- Twilio
- SMS and voice steps where you use them, on your own account.
- n8n, Make or custom code
- Schedules steps, runs the consent and suppression checks, logs every send.
- OpenAI, Anthropic Claude or Google Gemini
- Fills approved templates and drafts replies, on accounts in your name.
Guardrails
- No contact enters a sequence without recorded consent or a relationship you have documented. No bought, rented or scraped lists.
- Consent is checked per channel before every message, not once when the sequence starts.
- One suppression list covers email, WhatsApp, SMS and voice. An opt-out anywhere stops everything.
- Sending windows follow the contact’s local time, with quiet hours you set.
- AI personalisation stays inside approved templates and facts from the enquiry or the CRM. It cannot invent offers, prices or deadlines.
- Opt-out and complaint rates are watched per step, and a step that spikes is paused for review.
Human checkpoint
A named owner approves every template and every change to the sequence rules before it goes live, and answers the replies the assistant may not handle. Pricing questions, complaints and anything that might be a request to stop go to a person, and when in doubt the system treats a message as an opt-out. A monthly review checks a sample of consent records against the forms that collected them.
What we plan for
Typical targets
Typical target
None, by design
Messages sent after an opt-out
Basis: Every send checks the shared suppression list first, and opt-outs from any channel write to that same list
Typical target
90–100%
Eligible leads that get every planned step
Basis: Scheduled steps replace manual reminders; leads who replied, booked, opted out or lack consent are not eligible
Typical target
Minutes, not days
Time to pause after a reply
Basis: Inbox and CRM events trigger the pause; tools that only support polling add their polling interval
Rollout
Week by week
Week 1
Map today’s follow-up, forms and consent wording, and check a sample of contacts for the consent actually on record.
Weeks 2–3
Consent capture fixed on forms and chat, suppression lists unified, and the first sequence built from templates you approve.
Week 4
The sequence runs for a small share of new leads. Replies, pauses and opt-outs tested end to end, including STOP on WhatsApp and SMS.
Weeks 5–6
All new leads enrolled, a second sequence for older leads who opted in, and the weekly step report handed over.
FAQ
Frequently asked questions
Can we upload our old contact list and start a sequence?
Only the contacts with consent on record, or a relationship you can document, such as past customers where your market allows it. We check where the list came from first. Bought, rented or scraped lists are out of scope, because they damage deliverability for every message you send afterwards.
What counts as an opt-out?
An unsubscribe click, a STOP or similar reply on WhatsApp or SMS, a block, or a person asking your team to stop in any words. Clear cases are applied automatically; unclear ones go to a person, and when in doubt the system treats the message as an opt-out.
Can follow-ups go out on WhatsApp if the lead only gave us an email?
No. WhatsApp needs its own opt-in naming your business, so the sequence skips WhatsApp steps for that lead and logs why. Your form or chat can offer WhatsApp updates as a separate choice, and once a lead ticks it, later steps may use it.
How many messages should a nurture sequence send?
Fewer than most tools suggest. We start with a short sequence over a few weeks and watch replies, opt-outs and complaints per step. A step that earns complaints is cut or rewritten; leads who finish move to a quieter list they opted into.
Does the AI write each follow-up from scratch?
No. You approve a template for every step, and the model fills in details from the enquiry and the CRM, such as the product asked about or the city. It cannot invent offers, prices or deadlines, and its output is checked against the approved template before sending.
Will the sequence stop if the lead books a call through our calendar?
Yes, as long as the booking tool updates the CRM or sends a webhook, which most do. A booking, a reply, a purchase or an open support ticket pauses or ends the sequence.
Who is responsible for following marketing rules?
You remain the sender, so your compliance owner signs off the consent wording, templates and sending rules. We design the gates to the public guidance on this page, keep the records that show who agreed to what and when, and flag anything that needs a legal view in your market.
Next step
Have a workflow in mind? Let’s scope it together.
Book a free 30-minute strategy call. Bring one process you want to automate and we will talk through scope, integrations and a sensible first step.
Free 30-minute call · no commitment