Playbook · Sequencing
When to break sequence: signal-triggered exits
Most sequences run on autopilot until they end. The 6 signal triggers that should force an immediate exit from the sequence (and what to send instead) — including the one signal that 90% of teams miss because their sequencer can't detect it.
01The play
Summary
Most sequences run on autopilot until they end. The 6 signal triggers that should force an immediate exit from the sequence (and what to send instead) — including the one signal that 90% of teams miss because their sequencer can't detect it.
02Expected outcome
Outcome: Signal-aware sequence exits improve positive-reply rate by 40-60% because every send is contextual.
Success metric: Zero instances of a sequence touch landing AFTER a major signal change at the account.
03Anti-patterns · do not run this when
- Do not exit a sequence on a low-confidence signal — it has to be verified
- Do not exit + immediately re-pitch — give the signal 3-5 days to settle
- Do not exit silently — log the exit reason so the next motion has context
Playbook entry · ships as-of {date('M Y')}. Operator-written, no theory inflation. If you've run this play and the numbers don't match yours — or the rhythm needs a tweak — write to [email protected] and we'll revise.
Signal-anchored outbound, no theater
Run this play on every account in your CRM.
Connect a CRM. Mama detects the trigger, scores the fit, and drafts the first message in the rhythm above. Free up to 100 accounts. No card.