Outcome. Every account that churns is queued for a win-back nurture automatically, with an owner review step in between, instead of falling off the radar the day the account is marked lost.
Workflow map
Enrollment, branches and actions at a glance
renewal-expansion-017
flowchart TD
A[Customer Status = Churned, sequence status Not started] --> B[Set sequence status = Queued]
B --> C[Add primary contact to Win-back Queue list]
C --> D[Create task for account owner]
D --> E[Wait 30 days]
E --> F{Sequence status still Queued?}
F -->|Yes| G[No action, nurture continues]
F -->|No| H[Exit, status changed elsewhere]
When to use it, when not to
- UseUse it as the detection and queueing layer for churned accounts: it flags the company, notifies the account owner, and hands the account's primary contact to a win-back nurture.
- UseUse it when churned accounts are currently a manual list somebody remembers to build once a quarter.
- SkipDo not treat this fiche as the nurture emails themselves. The actual multi-touch win-back content is a separate, contact-based marketing email nurture triggered by list membership; this fiche builds the company-side signal and queue, not the send sequence.
- SkipDo not use it on accounts that churned for reasons that make re-contact inappropriate (contract dispute, non-payment write-off). Exclude those explicitly.
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.5 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.6 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
or the renewal and expansion 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.
