Outcome. A contact who has been enrolled in sequences too many times in a short window gets pulled out and flagged, instead of getting hit with yet another automated cadence while nobody notices the pattern.
Workflow map
Enrollment, branches and actions at a glance
sales-ops-047
flowchart TD
A[Sequence enrollment count reaches 3 in 90 days] --> B[Unenroll from sequence]
B --> C[Set Sequence exit reason = Other]
C --> D[Add to Do not sequence list]
D --> E[Notify contact owner]
When to use it, when not to
- UseUse it as an over-contacting guardrail when several workflows or reps can independently enroll the same contact into different sequences over time.
- UseUse it to protect contact experience and sender reputation, catching cases where a contact bounces between SDRs or gets re-qualified repeatedly.
- SkipDo not use it if you only ever run one sequence program with tight suppression rules already in place; this is a backstop for portals where multiple entry points into sequences exist.
- SkipDo not use it with a very low threshold; a contact legitimately re-engaging in different quarters (a returning prospect) should not be treated the same as one being spammed in a short window. Set the threshold and window to match real over-contacting, not normal sales cadence.
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.4 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 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
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.
