Outcome. A contact who books a meeting stops getting further sequence touches automatically, since continued cold outreach right after a booking looks out of touch and the sequence has already done its job.
flowchart TD
A[Meeting Scheduled while actively enrolled] --> B[Unenroll from sequence]
B --> C[Set Sequence exit reason = Meeting booked]
C --> D[Notify contact owner]

When to use it, when not to
- UseUse it when you want a logged exit reason and a rep notification, not just a stopped sequence.
- UseUse it as a safety net when the meeting was booked through a link that is not the same one the sequence's own native unenrollment trigger watches.
- SkipDo not build this if your sequence's own "unenroll when a meeting is booked" setting already covers the case and nobody needs an extra notification.
- SkipDo not use it for internal or test meetings booked against a contact's link by your own team; exclude those with a static list if they pollute results.
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.





