Onboarding stage duration / stalled-onboarding alert

Outcome. When a portal tracks onboarding as its own dedicated deal pipeline rather than a ticket pipeline, a deal that sits in one working stage too long alerts the onboarding owner instead of quietly stalling.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-035

flowchart TD
    A[Deal enters watched Onboarding pipeline stage] --> B[Set Onboarding Stage Entered Date]
    B --> C[Delay 7 business days]
    C --> D{Still in same watched stage?}
    D -->|Yes| E[Alert Onboarding Owner]
    E --> F[Create check-in task]
    D -->|No| G[End, deal moved on]

When to use it, when not to

• UseUse it when onboarding lives in a separate "Onboarding" deal pipeline (a second pipeline on the deal object, distinct from the sales pipeline), with its own stages such as Kickoff, Implementation, Training, Live.
• UseUse it if you prefer keeping onboarding on the deal object instead of creating a ticket, for example when your team is small and does not want to manage a second object.
• SkipDo not use it if onboarding already runs through a ticket pipeline, use the ticket version of this pattern in customer-onboarding-019 instead, the two do the same job on different objects.
• SkipDo not use it on a stage that legitimately takes a long time by design (a multi-month enterprise implementation stage), the fixed delay below will false-alarm, raise the delay or use the Wait until variant.