Onboarding Risk Agent

When an onboarding milestone slips, the agent starts from that missed date. The miss is the signal rather than the assumed cause, so the next steps work backwards through the plan to find where the delay began.

• Trigger: An onboarding milestone slips
• Starting point: The milestone that missed its planned date

Next, the agent pulls the full onboarding plan from the account, including every step and its planned date. This gives it the sequence of events it needs to work backwards from the missed milestone.

• Source: The onboarding plan on the account
• Include: Every onboarding step and its planned date

The agent then pulls who owns each step on the customer side and on your side. Matching named owners to the plan shows who was responsible for the first step that ran late.

• Include: The owner of every onboarding step
• Sides: Customer owners and internal owners

Working backwards from the missed milestone, the agent finds the earliest onboarding step that ran late. It names the step, who owned it, and how long it has been delayed, so Customer Success can focus on where the stall began rather than where it became visible.

Using the point where the delay began, the agent suggests the one thing that would move the onboarding forward now. It also names who needs to do it, giving Customer Success a specific next action instead of generic escalation advice.

Finally, the agent sends the findings to the customer success lead in Slack. The message shows where the delay began, who owned that step, how long it has been delayed, and the specific action that could get the onboarding back on track.

• Recipient: The customer success lead
• Channel: Slack
• Include: The delayed step, its owner, the length of the delay, the unblock action, and who needs to do it