Riskbot: Comprehensive Partnership Health Assessment

Gather input data sources including:

- Client call transcripts from check-ins or unscheduled calls (Client Call Transcripts-Extract from Zoom)

- Email and other communication logs between CPM and client (Email and Other relevant communication with client)

- XP and CPM coaching logs (XP coaching log with CPM-copy and paste from SI)

- XP attendance and disciplinary records if applicable

- Other relevant partnership information (Other details that should matter)

Record key metadata such as Kick-off Call Date (Kick of Call Date) and reason for partnership audit (Trigger for Partnership Audit).

Summarize the current state of the partnership, addressing client engagement, sentiment over time, XP performance trends, and external business or financial factors.

Analyze data across risk categories and identify early warning signs with supporting quotes and sources:

- XP Performance & Reliability Risks: client dissatisfaction, unresolved performance issues, attendance or behavior concerns

- Commitment & Engagement Risks: client disengagement signs, communication hesitations, unclear expectations reported by XP

- Business & Financial Stability Risks: budget concerns, refunds or billing adjustments requested (automatic red flag)

- Escalation & Trust Issues: unresolved frustrations, trust breakdowns, repeated coaching interventions

Categorize the partnership risk level: No Risk, Low Risk, Medium Risk, or High Risk based on findings, noting that refund/credit requests are high risk.

Facilitate CPM and SOM discussion to validate the partnership health assessment using key questions about client sentiment, engagement, coaching effectiveness, financial stability, and escalation history.

Recommend actions such as expectation alignment, direct client feedback, XP development plans, financial retention strategies, and crisis interventions if needed.

Identify possible churn reasons using churn definitions and categories including matching issues, XP performance, client business state, internal process breakdowns, and other common causes.

Assign an AI Analysis Churn Tag with rationale based on the comprehensive findings.