Stopping a sequence changes its state. A sequence moves an eligible prospect through planned message jobs until a reply, opt-out, delivery failure, ownership change, disqualifying fact, or final stop condition changes the path.1 The record should determine whether a contact stays in automation, pauses for review, hands off, or reaches re-entry.
Silence deserves its own branch. The first message may be buried, read at a bad time, or forgotten.2 Silence can leave the prospect undecided.3 A sequence exists to reach the prospect at a moment the first message missed.4 Decide what each response means before deciding whether automation continues.
Set the stop policy before enrollment
Write the exit rules before the messages. Every contact needs a path into the sequence, a reason to stay, and a clear reason to leave.
A sequence should answer one bounded prospecting question.5 Keep the enrollment population, trigger, problem, proof, and next action coherent.6
Before launch, freeze the sender domain or mailbox, legal entity, owner, platform, CRM source, list source and date, jurisdictions or subscriber types, suppression sources, segment, trigger, message versions, send window, threading, reply and OOO handling, bounce rules, experiment assignment, and observation window.7
Set a time boundary alongside the event rules. For inbound leads, use up to ten days; for outbound target accounts, use up to twelve days.8 A separate multi-channel design uses ten to fourteen touches over thirty days across email, phone, and LinkedIn.9 Choose the policy that matches the motion and write it down before enrollment. Do not blend the time boundary into an open-ended send plan.
Apply hard stops immediately
After a reply, meeting, open opportunity, or opt-out, treat a higher-priority state as present, keep the CRM and conversation owner current, hand control to the owner or compliance rule, and immediately stop overlapping automated outreach.10 Make the handoff visible in the record before another task can fire.
Positive replies stop the sequence and route to a human; referrals trigger re-prospecting of the named contact; objections escalate to a rep; unsubscribes suppress the contact and update the CRM.11
Make the stop reason specific enough for another person to tell whether to follow up, suppress, or recycle the record. A stop without an owner or disposition leaves the same contact exposed to another automated path.
Branch on meaning
A reply needs a disposition before the next action is scheduled. The response meaning determines whether automation finishes, pauses, or continues.
Result branch conditions let scripts handle different outcomes when an action executes.12 Reply action can finish the sequence or continue to the next step when a contact responds.13 For most sales scenarios, finishing the sequence lets the user take over manually after the response.14
For a non-actionable reply such as "Thanks," pause the lead, review the context, and resume later only if the original reason still fits.15 This gives a vague response a review path without treating it like a buying signal.
For a no-answer branch, start with the biggest problem, move to the next problem if needed, then ask for a response if neither worked.16 Keep each message focused on the current problem and make the next branch earn its place.
Let silence reach a clean stop
A no reply gives you less information than a reply, so give it a planned path and a final boundary.
Only a small share of any list is actively in a buying cycle in a given month.17 At the final boundary, close the sequence and record the reason. The workflow ends at its final stop condition even when no response arrives.18
Spread planned touches across channels when the motion calls for it. Spreading fourteen touches across channels creates more touchpoints and doubles the email reply rate.19 When you send a bubble-up email, reply to the previous email in the thread.20
Read silence as a timing problem to investigate while keeping the final boundary in force. If the original trigger or problem has changed, close the current sequence and use the new state to decide what happens next.
Re-enter only on a trigger
A return path is a new eligibility decision. Store the reason the contact left, the condition that permits return, and the message context needed for the return.
Soft disqualifications should enter a recycle pool with an explicit re-entry trigger such as a date, funding event, or new contact at the account.21 An example re-entry pattern brings a prospect back after ninety days or places the prospect in a different sequence.22
At the trigger, recheck the record before enrollment. Test the original bounded question again and choose the step that matches the new context. A contact who returns because of a new signal should receive a path built for that signal, with the old stop reason preserved for anyone reviewing the record.
What not to do
These errors turn a controlled exit policy into noise or accidental re-entry.
- Do not mix industries, roles, problems, and offers in one sequence, because that prevents useful diagnosis.23
- Do not send fourteen emails on one channel; that is obnoxious.24
- Sell one thing at a time. Selling everything in one email creates long emails that get deleted.25
- Do not treat deliverability as a sequence setting or put legal review there; deliverability is a separate prerequisite and legal review belongs with the compliance guide.26