The Workflow Library

Library / Sales ops / sales-ops-006

Auto-unenroll from sequence when contact replies to a sequence email

Sales opsContactSales Hub ProfessionalSimple~20 min to buildFull spec

Outcome. A contact who replies stops receiving further sequence steps automatically, and the rep gets a heads-up to answer personally instead of letting a canned step go out on top of a live conversation.

Workflow map Enrollment, branches and actions at a glance sales-ops-006
flowchart TD
    A[Reply date changes while actively enrolled] --> B[Unenroll from sequence]
    B --> C[Set Sequence exit reason = Replied]
    C --> D[Notify contact owner to reply personally]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it to add a rep notification and a logged exit reason on top of the reply signal, not just to stop the sequence.
  • UseUse it when several teams share reporting on why contacts leave sequences and need one consistent Sequence exit reason value across workflows.
  • SkipDo not build this if your sequences already have "automatically unenroll when replied" turned on in the sequence's own enrollment settings and nobody needs an extra notification. Check that native toggle first, it may be all you need.
  • SkipDo not rely on this alone to detect genuine engagement. A one-line "please remove me" reply still counts as a reply and still unenrolls the contact.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.3 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the sales ops pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.