Cadence exit conditions

An exit condition tells a cadence when a contact must leave automated outreach because the contact's state changed. Base each condition on the event that changes the route, then assign a clear destination: human follow-up, suppression, another sequence, or a clean end. Silence is one possible ending. Replies and suppression events can end a cold email sequence, while meetings and referrals can end a cadence.^{1, 2}

Define entry before exit

An exit rule depends on what the cadence was allowed to do. Set the entry population and problem before the stop, then judge each status change against that purpose.

A sequence should answer one bounded prospecting question and keep its enrollment population, trigger, problem, proof, and next action coherent.^{3, 4}

Write a one-page sequence contract with the eligible person, verified address, approved outreach basis, exclusions, trigger and as-of time, problem hypothesis, evidence, CTA, sender, message jobs, progression, stop and pause rules, suppression authority, experiment, metrics, review date, rollback owner, and retained evidence.⁵ Eligibility evidence should explain why the person may enter now using IDs, role, trigger, source, or date.⁶

Run the stop check before the next send

Before each queued send and whenever a new event enters the record, check the contact's status. The record should show what changed, why the cadence stopped, and where the contact goes next.

Exit criteria are conditions that contacts or accounts must match to leave a sequence at any point.⁷ Run this check in the same order every time:

Stage	What you are trying to learn	Example question
Reply	whether a live response has changed the route	Has the contact replied?
Suppression	whether the record now blocks further outreach	Has the record acquired a stop event?
Outcome	whether the intended result has happened or the contact should route elsewhere	Has the intended outcome occurred?
End condition	whether the planned run has reached its boundary	Has the run reached its planned end?
Continue	whether the next planned step still fits	Does the next step still answer the sequence question?

You can optionally set an end condition to stop the run after a specific number of sends or on a certain date.⁸

Route replies to a person

Automation should yield control as soon as the contact answers. Decide this route before launch so a live response does not wait for another scheduled message.

Reply handling determines whether a contact finishes the sequence or continues to the next step.⁹ For most sales scenarios, finish the sequence so manual follow-up takes over after the response.¹⁰ Include replies to emails outside the cadence if the stop rule covers any reply, since auto-removal can cover any email.¹¹

Specify reply handling, out-of-office messages, and delivery failures in the plan. Keep the destination visible in the record so the next person can see whether the contact needs a response, suppression, or another route.

Let silence reach the planned end

No inbound event leaves the record ambiguous, so give the run a planned ending. Keep the cadence open for the planned follow-up, then close it with a no-engagement outcome.

Use a planned window, such as 10 to 14 touches over 30 days across email, phone, and LinkedIn.¹² A sequence exists to catch the moment the first message missed.¹³ No engagement after the final touch can be an exit condition.²

Treat silence separately from rejection. Before the planned end, leave the contact in the active run. At the planned end, record the no-engagement state and remove the contact from further sends.

Route status changes

Stopping is complete only when the record receives a destination. Give each stop state its own route so a conversation, a suppression event, and an invalid record do not collapse into the same finished label.

When a condition is met, the contact can exit successfully, exit unsuccessfully, or move to the next sequence stage.¹⁴ Stop on an opt-out, delivery failure, ownership change, or disqualifying fact.¹ Keep meeting and referral outcomes separate from suppression so later review can show whether the cadence produced a conversation or became invalid.

What not to do

These mistakes can turn a sound stop rule into premature abandonment or unwanted follow-up. Check for them during the cadence review.

• Do not treat a sequence as a fixed number of emails or as permission to keep sending until someone responds.¹⁵
• Do not close a contact as uninterested after a silent email when the prospect may simply be busy.^{16, 17}
• Spread touches across channels; sending 14 emails on one channel is obnoxious.¹⁸
• Do not mix industries, roles, problems, and offers in a sequence when you need useful diagnosis.¹⁹
• Do not leave reply, out-of-office, and bounce handling unspecified in the plan.²⁰