The Workflow Library

Library / Customer onboarding / customer-onboarding-034

Deal reopened during onboarding triggers escalation

Customer onboardingDealSales Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. If a deal that already closed won gets moved back to an open stage while its onboarding is still active, sales and CS both get an immediate alert instead of finding out weeks later.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-034
flowchart TD
    A[Deal stage moves to an open stage, Onboarding Start Date known] --> B[Increment Onboarding Reopen Count]
    B --> C[Notify Onboarding Owner and Deal owner]
    C --> D[Create same-day review task]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when a reopened closed-won deal usually signals a real problem during onboarding: a cancellation threat, a contract correction, or a chargeback, not routine data cleanup.
  • UseUse it as a safety net on top of customer-onboarding-001 and customer-onboarding-011, it does not replace either.
  • SkipDo not use it if reps in your portal routinely reopen and reclose deals for administrative reasons (fixing a wrong amount, a typo), you will get alert fatigue, exclude that pattern in your enrollment filters or retrain the team to use a note instead of reopening.
  • SkipDo not use it once onboarding is marked complete, a reopened deal after go-live is a renewal or churn signal, see the renewal-expansion category instead.
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.4 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.3 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 customer onboarding 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.