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.
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]

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.
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.





