Build a Lead Follow-Up Sequence That Knows When to Stop
Create a respectful follow-up system with useful touches, branching logic, and a clear stop rule instead of endless checking in.

Watch the overview
3 minPrefer to read? The complete article and copyable prompts are directly below.
Most follow-up sequences fail in one of two ways: they disappear too early or keep sending empty check-ins. A useful system earns attention, responds to signals, and knows when to stop.
This guide helps you create a five-touch follow-up sequence that adds value, adapts to the lead, and protects your reputation.
What you need
- The lead source and last interaction
- Your offer, proof, common questions, and approved resources
- Your preferred follow-up channels and stop policy
The workflow
1. Define the next decision
Follow-up works better when each message helps a person make a specific decision. Decide whether you need a reply, a booked call, a document, or a respectful close.
2. Give each touch a job
Use a recap, a useful answer, relevant proof, a decision question, and a close-the-loop note. Do not send five versions of just checking in.
3. Add branches
Someone who asked for timing needs a different message from someone who went silent after pricing. Build branches from observed behavior, not guesses about personality.
4. Set a stop rule
Specify when the sequence ends, when a person takes over, and when the lead should not be contacted again.
Copy this working prompt
Replace every bracketed field with verified information from your business. If you do not know something, write unknown instead of guessing.
Create a respectful lead follow-up sequence for this real sales situation.
Offer:
[DESCRIBE THE OFFER]
Lead source and last interaction:
[DESCRIBE WHAT ACTUALLY HAPPENED]
Known goal or concern:
[PASTE ONLY WHAT THE LEAD SAID]
Approved resources and proof:
[LIST LINKS, CASE STUDIES, FAQS, OR WRITE NONE]
Channels allowed:
[EMAIL, SMS, PHONE, OR OTHER]
Timing and stop policy:
[DEFINE MAXIMUM TOUCHES, INTERVAL, AND DO-NOT-CONTACT RULES]
Build five touches. For each provide:
1. Timing
2. Purpose
3. Subject line if email
4. Message under 120 words
5. One clear call to action
6. Branch if they reply with interest
7. Branch if they reply not now
8. Stop condition
Sequence arc: recap, useful answer, relevant proof, direct decision question, respectful close-the-loop.
Do not invent urgency, discounts, scarcity, familiarity, results, or reasons for silence.Run a second-pass review
The first output should not be the final answer. Use this challenge prompt to find weak evidence, hidden assumptions, or avoidable risk.
Score every message from 1 to 5 for usefulness, specificity, pressure, and respect. Rewrite any message with pressure above 2 or usefulness below 4.What good looks like
- Every touch adds new value
- The lead can easily say no
- The sequence stops before it becomes noise
Review before you use it
- Does each claim match approved proof?
- Are timing and consent rules appropriate for the channel?
- Would you feel comfortable receiving the final close-the-loop note?
Privacy and judgment guardrails
- Remove passwords, payment details, private health information, and confidential customer data before pasting anything into an AI tool.
- Treat the output as a working draft. A person remains responsible for the decision, promise, price, and final send.
- Do not let AI invent customer quotes, financial figures, legal terms, capabilities, deadlines, or proof.
Your next action
Load only the first two touches into your CRM, then review replies before automating the rest.
If your AI tool still lacks the context to do this well, first Start with everyday AI tasks.