A sequence is a plan for what happens next, not permission to keep sending indefinitely. Every follow-up should have a purpose, and every recipient should have a clear path out of the sequence.
Give each step a different job.
Use the introduction to establish relevance. A later message can add a specific product detail or clarify who should own the conversation. Repeating “just checking in” without new context creates work for the recipient. Agree on timing around the recipient’s business hours and your team’s response capacity.
Define the stops before execution.
Plan to stop or review queued messages after a meaningful reply, an opt-out, a hard bounce, a booking or an existing active opportunity. A referral needs a new contact decision; an out-of-office reply needs a review of timing. Neither should be blindly treated as positive interest.
Confirm what your connected system supports.
This worksheet describes an operating plan, not a claim that every rule is available in your workspace. Verify configured scheduling, suppression and pause controls before live execution. Keep an owner for exceptions and inspect the run history when an action fails instead of repeatedly retrying an uncertain send.
IN PRACTICE
Write the exception path first.
Send follow-ups until the prospect responds.
Use a finite set of steps. Review replies and stop conditions before each one. Pause uncertain delivery outcomes for inspection.
An ending protects the clarity of the sequence. Exception handling also prevents the next planned message from contradicting a real conversation.
| Event | Operating decision to define |
|---|---|
| Opt-out or hard bounce | Stop eligible queued outreach and record the reason. |
| Referral or out-of-office | Review contact ownership or timing. |
| Uncertain send result | Inspect history before retrying. |
Take one planned follow-up and imagine a reply arriving one minute before it runs. Write down how the team or configured system would detect the reply, stop the queued message and assign the next action. Verify those controls before live execution.
A worksheet for your team.
Use this as a starting point. Replace the fields with verified information about your own business.
Audience and mission: Step 1: purpose and message Step 2: purpose, delay and eligibility Final step and ending: Recipient time zone and business hours: Reply handling: Opt-out, bounce and booking stop rules: Referral and out-of-office review: Supported controls verified by: Exception owner:
Before you move on.
- Every step adds useful context.
- Timing and ownership are explicit.
- Replies and opt-outs have defined handling.
- The sequence ends instead of looping.
Editorial guidance for planning and review. Examples are illustrative. Confirm your workspace’s available controls and configuration before live execution.