The Workflow Library

Library / Customer onboarding / customer-onboarding-019

Stuck-in-stage onboarding ticket alert

Customer onboardingTicketService Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. An onboarding ticket that has not moved out of a working stage after a set number of business days notifies the CS manager, catching onboardings that quietly stopped progressing.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-019
flowchart TD
    A[Ticket enters a watched working stage] --> B[Set Stage Entered Date]
    B --> C[Delay 5 business days]
    C --> D{Still in same watched stage?}
    D -->|Yes| E[Alert CS manager]
    E --> F[Create check-in task]
    D -->|No| G[End, ticket moved on]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when onboarding runs as a ticket through pipeline stages (see customer-onboarding-011) and a ticket can sit in one stage for a long time with nobody noticing.
  • UseUse it alongside, not instead of, customer-onboarding-012 (overdue ticket by due date), the two catch different failure modes, one is a missed date, the other is a stalled stage.
  • SkipDo not use it on a pipeline where every stage naturally takes weeks (long enterprise rollouts), the fixed delay below will false-alarm constantly, raise the delay or use the Wait until variant instead.
  • SkipDo not use it on Completed or Closed stages, exclude them from the watched-stage list.
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.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 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.