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.
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]

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 reasonvalue 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.
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.




