The Workflow Library

Library / Lead nurturing / lead-nurturing-021

Closed-lost (non-customer) contact re-engagement nurture

Lead nurturingContactMarketing Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. A contact whose deal closed lost gets left alone for a fixed cooldown, then receives one re-engagement email checking whether anything has changed, instead of either being nurtured immediately after a loss or forgotten entirely.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-021
flowchart TD
    A[Deal closed lost, contact not a customer] --> B[Set cooldown_until = +90 days]
    B --> C[Delay until cooldown_until]
    C --> D{Any open deal now?}
    D -- No --> E[Send: checking back in email]
    E --> F[Set closed_lost_reengaged = true]
    D -- Yes --> G[No action]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse once deals in the account reliably move to a Closed Lost stage and that stage change is trackable on the associated contact.
  • UseUse it for a genuine loss (budget, timing, chose a competitor), where circumstances plausibly change later. This is not for disqualified or bad-fit contacts, see lead-nurturing-041 for that pattern.
  • SkipDo not use it immediately after a loss. The cooldown exists because reaching out right away after a "no" reads as tone-deaf; give it real time.
  • SkipDo not enroll a contact who has an open deal on a different associated record. Check that no other active opportunity exists before starting the cooldown clock.
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.5 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 lead nurturing 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.