To automate client follow-up, you build one branching workflow for each of the five moments deals actually die: new lead, post-call, proposal sent, ghosted, and post-job. Each workflow needs a trigger, a channel sequence (usually text first, then email), timing rules, and an exit condition so nobody gets messaged after they’ve replied. This guide gives you the blueprint for all five, plus the copy and cadence rules, whether you build them in Zapier, your CRM, or by describing them to an AI in one sentence.
Why do most deals die from silence, not rejection?
Run the math on your own pipeline and it gets uncomfortable fast:
- Firms that contact a lead within an hour are 7× more likely to qualify it than those that wait even sixty minutes longer (Harvard Business Review, Oldroyd et al.).
- The odds of qualifying a lead are roughly 21× higher when you respond within five minutes instead of thirty (InsideSales.com Lead Response Management study).
- 80% of sales take five or more follow-ups, but 44% of salespeople quit after one (Invesp).
- And when leads call instead of filling a form? A caller is far closer to buying than a form-filler, yet callers who hit voicemail rarely try again. They call the next result on Google.
Nobody loses these deals in a negotiation. They lose them in the gap between “lead came in” and “someone said something.” You’re not bad at sales, you’re busy, and follow-up is the first thing busyness eats. Which is exactly why it should be the first thing you automate.
What are the five follow-up moments — and what should fire at each?
Below, each moment gets a generic branching blueprint you can build in any tool. Then the shortcut: in Stack Space you open Workflows, hit “Generate with AI,” and describe the flow in plain English (“when a new lead comes in, text them within a minute, wait a day, email, then task me if no reply”), and the AI builds the whole branching flow. There are also six starter templates that map almost one-to-one onto these moments: missed-call text-back, new-lead nurture, speed-to-lead, overdue-invoice, review-after-win, and re-engage cold.
Moment 1 — New lead (the speed-to-lead window)
Trigger: form submitted, missed call, or new contact created.
Blueprint:
- Within 60 seconds: send a text. Not an email, a text. (This is the speed-to-lead and missed-call text-back templates.)
- Branch: did they reply?
- Yes → notify you immediately, create a task, stop the sequence.
- No → wait 2 hours, then send a short email restating what they asked for.
- Day 1: second text with a booking link.
- Day 3: email with one useful thing (a price range, a portfolio piece).
- No reply by day 5: move to the long-term nurture list, stop pestering.
Copy template (first text):
“Hi {first name} — this is Marcus from {agency}. Saw your note about {service}. Want me to send a quick quote, or is a 10-min call easier? Book here: {link}”
Moment 2 — Post-call
Trigger: call ended / call logged.
Blueprint:
- Within 10 minutes: recap text or email — what you heard, what happens next, one clear next step.
- Branch: was a next step booked on the call?
- Yes → confirmation, calendar invite, reminder 24h and 1h before.
- No → send your booking link, wait 2 days, nudge once.
The recap is the highest-leverage message in this whole article. It turns a conversation into a commitment while the call is still warm. If your calls are answered by a voice agent that transcribes them, the recap writes itself from the transcript, with no “wait, what did they say about budget?”
Moment 3 — Proposal sent
Trigger: proposal/estimate status changes to “sent.”
Blueprint:
- Day 0: email the proposal, text “Just sent it — 2-minute read.”
- Day 2: “Any questions on the {specific line item}?” (Specific beats “just checking in” every single time.)
- Day 5: offer a 15-minute walkthrough call.
- Day 10: the real deadline: “Planning our schedule for {month} — should I hold your spot?”
- Branch on open/click if your tool tracks it: opened 3+ times with no reply → notify you personally. That lead is deciding right now.
Moment 4 — Ghosted (the re-engage flow)
Trigger: no reply in 14+ days, deal still open.
Blueprint:
- Message 1: zero pressure, give them an out: “Totally fine if this got deprioritized — want me to close the file, or move it to next month?” (The “close the file” framing gets replies precisely because it’s easy to answer.)
- Wait 7 days. Message 2: send something of value, a relevant result or a new idea for their business. No ask.
- Wait 14 days. Message 3: the breakup: “Last note from me — door’s open whenever.” Then automatically tag them into a monthly nurture list.
- Exit rule: any reply anywhere kills the sequence and creates a task for you. Nothing torches trust like an automated nudge after a human reply.
Moment 5 — Post-job (reviews + winbacks)
Trigger: deal marked won / job completed / invoice paid.
Blueprint:
- Day 1: thank-you and review request by text with a direct link (the review-after-win template). One link, one tap. Every extra step halves your review rate.
- Branch: left a review → personal thank-you. Didn’t → one reminder at day 4, then stop.
- Day 30: “How’s everything holding up?”, the quiet upsell moment.
- Day 90–180 (service businesses): the winback: “Most clients refresh {service} around now — want me to pencil you in?”
Also in this bucket: the overdue-invoice flow. Trigger on invoice 3 days past due → friendly text → day 7 email with payment link → day 14 firmer note and task for you. Awkward for a human, effortless for a workflow, and it’s money you already earned.
What are the cadence rules that keep automation from feeling robotic?
- Text first, email second. Texts get read; email carries detail.
- Reply kills the robot. Every sequence exits the moment a human responds. This is the one non-negotiable rule.
- 3-2-1 pacing: roughly three touches in week one, two in week two, one in week three, then monthly nurture. Persistent, never frantic.
- Every message needs one specific thing: a question, a link, a deadline. “Just checking in” is a message that asks the lead to do your job.
- Business hours only for automated sends (8am–8pm local). A 3am “just following up!” reads exactly like what it is.
- Cap it. Five to seven touches per sequence, then park the lead in long-term nurture. The Invesp numbers say most people quit too early, but there is a too-late, and it starts around touch eight.
Should AI write and send the follow-ups too?
Sequences with fixed copy get you 80% of the value. The last 20% is responsiveness, and that’s where AI employees earn their keep: drafting the reply when a lead answers your 2am text-back, turning a call transcript into the recap email, chasing the invoice in a tone you approved. Stack Space includes a dedicated Follow-up AI employee for exactly this, and its workflows support AI actions (AI reply, AI phone call, qualify lead) inside any branch. We built it because we watched agency owners lose winnable deals to their own calendars. The full picture is in our guide to the best AI to run your business.
One honest caveat: automation amplifies whatever process you have. If your offer is fuzzy or your pipeline stages are fiction, automate after you fix that. A robot sending confusing messages faster is not progress.
FAQ
What’s the difference between follow-up automation and an email drip? A drip sends the same emails to everyone on a timer. Follow-up automation is branching and event-driven: it reacts to what the lead does (replied, booked, opened, went silent) and exits the moment a human takes over. Drips nurture audiences; follow-up automation closes individual deals.
How fast should I respond to a new lead? Under five minutes if humanly (or robotically) possible. The InsideSales.com data puts a five-minute response at roughly 21× the qualification odds of a thirty-minute one. This is the single strongest argument for automating the first touch: no human answers every lead in five minutes, every time, forever.
Won’t clients be annoyed by automated messages? They’re annoyed by irrelevant messages and by being messaged after they’ve replied. Trigger on real events, reference specifics, exit on reply, and cap the sequence. Done right, automated follow-up reads as “impressively on top of it,” not “mail merge.”
How many follow-ups is too many? Five to seven over about three weeks for an active deal, then monthly low-pressure nurture. The data (80% of sales need 5+ touches, per Invesp) says err on the side of more than feels comfortable, and the exit-on-reply rule keeps it civilized.
Do I need a developer to build these workflows? No. Visual builders handle all five blueprints, and in Stack Space you can skip the canvas entirely: describe the flow in a sentence and “Generate with AI” builds the branches, or start from the six templates and edit the copy.
Stack Space bakes these five blueprints into one CRM: a Follow-up AI employee (one of 17) drafts and sends the touches, and Neo, the AI brain, watches the pipeline so no reply goes unanswered and no sequence fires after one. Follow-up is where the pieces compound: the missed-call text-back play catches the lead, AI cold email fills the top of the funnel, and the boring 80% of agency ops runs itself while you sell.