The Workflow Library

Library / Customer onboarding / customer-onboarding-012

Overdue onboarding ticket alert to CS manager

Customer onboardingTicketService Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. An onboarding ticket that has been open for longer than a set number of days without reaching Completed sends a single alert to the CS manager, catching stalled onboarding before the customer notices.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-012
flowchart TD
    A[Ticket created in Onboarding pipeline] --> B[Delay 30 days]
    B --> C{Stage = Completed?}
    C -->|Yes| D[End, no alert]
    C -->|No| E[Notify CS manager: overdue]
    E --> F[Set Overdue Alert Sent = true]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it once the Onboarding pipeline (customer-onboarding-005) is live and the team has a rough sense of how long onboarding normally takes.
  • UseUse it as a blunt, portfolio-wide safety net, not a substitute for customer-onboarding-011's stage-by-stage notifications, which react to specific transitions rather than elapsed time.
  • SkipDo not use it if onboarding length varies too much across deal types for one fixed threshold to mean anything, segment the workflow by deal size or product first, or use the date-property variant below.
  • SkipDo not use it if the team already reviews an "onboarding tickets by age" list view daily, this fiche adds automation on top of a habit that might already work.
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.5 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.