architecture

Customer Success AI Agents

AI agents for customer success: account health monitoring, QBR preparation, renewal sequencing, and onboarding automation. Includes off-the-shelf options, custom build approaches, and training examples.

Overview

CS roles focus on retention, expansion, and health monitoring. High-frequency tasks include account prep, health checks, renewal outreach, QBR preparation, and risk identification.

Efficiency Potential: 5-7 hrs/week at Adoptive tier

Agent Summary

Agent Efficiency Target Complexity Priority
2 hrs β†’ 15 min/day Medium High
3 hrs β†’ 30 min Medium High
80% automated Medium High
40% time reduction Medium Medium

Account Health Monitor

Problem Statement

CSMs manage 30-80 accounts. They can't manually check usage data, support tickets, NPS, and engagement signals for every account every week. At-risk accounts slip through until it's too late.

Efficiency Target: 2 hrs/day manual checking β†’ 15 min reviewing AI-prioritized list

Off-the-Shelf Options

Tool Capability Pricing
Gainsight Health scores, playbooks Enterprise
ChurnZero Usage tracking, health Mid-market
Totango Customer journey, health $249+/mo
Vitally Product analytics, health $150+/mo

Custom Build Approach

Data Sources:

  • Product usage (events, logins, feature adoption)
  • Support tickets (volume, sentiment, resolution)
  • NPS/CSAT scores
  • Billing (payment issues, downgrades)
  • Engagement (email opens, meeting attendance)
  • Contract data (renewal date, terms)

Health Score Model:

HEALTH SCORE = weighted average of:

Usage Score (30%)
β”œβ”€β”€ Login frequency vs. baseline
β”œβ”€β”€ Feature adoption breadth
β”œβ”€β”€ Power user ratio
└── Usage trend (growing/flat/declining)

Support Score (20%)
β”œβ”€β”€ Ticket volume vs. baseline
β”œβ”€β”€ Ticket sentiment
β”œβ”€β”€ Resolution satisfaction
└── Escalation frequency

Engagement Score (25%)
β”œβ”€β”€ CSM meeting attendance
β”œβ”€β”€ Email response rate
β”œβ”€β”€ Training participation
└── Community involvement

Outcome Score (25%)
β”œβ”€β”€ Stated ROI achievement
β”œβ”€β”€ Reference-ability
β”œβ”€β”€ Expansion conversations
└── Executive sponsor strength

Training Example: Daily Risk Digest

Generate a prioritized risk digest for CSM review.

TODAY'S DATE: {{date}}
CSM: {{csm_name}}
PORTFOLIO: {{account_count}} accounts

ACCOUNT DATA:
{{account_health_data_json}}

For each account flagged as at-risk or trending down, provide:

## Daily Risk Digest

### Immediate Action Required (Red)
[Accounts with health score drop >15 points in 7 days OR critical signals]

**{{Account Name}}** | Health: {{score}} ({{trend}})
- Primary signal: [what triggered the flag]
- Risk level: [churn risk: high/medium]
- Days to renewal: {{days}}
- Recommended action: [specific next step]
- Suggested outreach: [1-2 sentence message to send]

### Monitor Closely (Yellow)
[Accounts with concerning signals but not critical]

### Positive Signals (Green)
[Accounts showing expansion or advocacy signals]

### Portfolio Summary
- Red accounts: X
- Yellow accounts: X
- Accounts with renewal in 30 days: X
- Suggested focus today: [top 3 priorities]

Architecture Pattern

Uses Pattern: Agent Chaining & Orchestration for risk-based response:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Health Score    │────►│ Risk Level      │────►│ Response        β”‚
β”‚ Calculator      β”‚     β”‚ Router          β”‚     β”‚ Generator       β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                               β”‚
              β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
              β–Ό                β–Ό                β–Ό
       [Red: Urgent]    [Yellow: Watch]  [Green: Expand]

QBR Prep Generator

Problem Statement

QBR prep takes 2-4 hours per account. CSMs pull data from multiple systems, create slides, and try to tell a coherent story. Most QBRs end up generic.

Efficiency Target: 3 hrs β†’ 30 min per QBR prep

Off-the-Shelf Options

Tool Capability Pricing
Gainsight QBR templates, data pull Enterprise
Matik Automated presentations Mid-market
Klipfolio Dashboard generation $99+/mo

Training Example: QBR Narrative

Generate a QBR narrative and talking points.

ACCOUNT: {{account_name}}
QUARTER: {{quarter}}
CSM: {{csm_name}}

DATA INPUTS:
- Usage Metrics: {{usage_data}}
- Support History: {{support_summary}}
- Goals from Last QBR: {{previous_goals}}
- ROI Metrics: {{roi_data}}
- Stakeholder Map: {{stakeholders}}
- Upcoming Renewal: {{renewal_date}}

GENERATE:

## {{account_name}} QBR Prep

### Executive Summary (for busy execs)
[3 bullets: what's working, what needs attention, recommended focus]

### Value Delivered This Quarter
| Goal | Target | Actual | Status |
|------|--------|--------|--------|
[Map to goals from last QBR]

### Usage & Adoption Story
[Narrative connecting usage data to business value]
- Highlight: [biggest win]
- Opportunity: [underutilized capability]

### Health Indicators
[Honest assessment with data]

### Recommended Next Quarter Goals
1. [Specific, measurable]
2. [Connected to their business priorities]
3. [Sets up expansion conversation if appropriate]

### Expansion/Upsell Opportunity
[If appropriate based on health and usage patterns]
- Opportunity: [what]
- Why now: [trigger]
- Suggested approach: [how to position]

### Talking Points for {{exec_sponsor_name}}
[Tailored to their priorities and communication style]

Architecture Pattern

Uses Pattern: Knowledge Architecture (RAG vs Semantic vs Fine-Tuning) for full account context:

# Load full account context (semantic approach)
account_context = f"""
## Account: {account.name}
### CRM Data
{account.crm_export}
### Usage Metrics (Last 90 Days)
{account.usage_summary}
### Support Tickets
{account.support_tickets}
### Previous QBR Notes
{account.last_qbr}
"""

Renewal Outreach Sequencer

Problem Statement

Renewals require multiple touchpoints over 90+ days. CSMs often start too late, miss touches, or send generic messages. Result: surprises at renewal time.

Efficiency Target: Automate 80% of renewal sequence; CSM focuses on strategic conversations

Sequence Structure

Day -90: Health check email (auto-generated, CSM reviews)
Day -75: Value summary + ROI data share
Day -60: Renewal preview + any changes
Day -45: Exec sponsor touchpoint
Day -30: Contract review meeting
Day -14: Final terms
Day -7:  Signature follow-up
Day 0:   Renewal

Training Example: Renewal Email

Generate a renewal sequence email.

ACCOUNT: {{account_name}}
CONTACT: {{contact_name}}, {{contact_title}}
RENEWAL DATE: {{renewal_date}}
DAYS TO RENEWAL: {{days_remaining}}
SEQUENCE STAGE: {{stage}} (e.g., "Day -90 Health Check")

ACCOUNT CONTEXT:
- Health Score: {{health_score}}
- Key Wins This Year: {{wins}}
- Open Issues: {{issues}}
- Contract Value: {{contract_value}}
- Proposed Change: {{proposed_change}} (if any)

GENERATE:

Subject: [specific to stage and account]

Body:
[Stage-appropriate content]
- Day -90: Focus on value delivered, set up renewal conversation
- Day -60: Preview renewal terms, surface any concerns
- Day -30: Drive toward contract review meeting
- Day -7: Create urgency without pressure

CTA: [Clear, single action]

---

CSM NOTES:
- Key talking point if they respond: [based on context]
- Escalation trigger: [what response should prompt intervention]

Onboarding Copilot

Problem Statement

Onboarding is critical but repetitive. CSMs run similar playbooks with customization. Customers get lost, miss steps, or don't achieve time-to-value quickly.

Efficiency Target: 40% reduction in CSM time per onboarding; 25% faster time-to-value

Training Example: Onboarding Status

Generate an onboarding status update.

CUSTOMER: {{customer_name}}
ONBOARDING START: {{start_date}}
TARGET GO-LIVE: {{go_live_date}}
CSM: {{csm_name}}

ONBOARDING CHECKLIST STATUS:
{{checklist_data}}

RECENT ACTIVITY:
{{activity_log}}

BLOCKERS/ISSUES:
{{blockers}}

GENERATE TWO VERSIONS:

## Internal Status (for CSM manager/team)

### Onboarding Health: [Green/Yellow/Red]
- Days in onboarding: X of Y planned
- Checklist completion: X%
- On track for go-live: [Yes/At Risk/No]

### Blockers & Risks
[What's slowing things down; who needs to act]

---

## Customer-Facing Update

Subject: {{customer_name}} Onboarding Update - Week {{week_number}}

[Professional, concise summary]
- Progress this week
- What's coming next
- Any items needing their attention

Chains

Health β†’ Response Chain

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Scheduled       │────►│ Health Score    │────►│ Router          β”‚
β”‚ Daily Check     β”‚     β”‚ Calculator      β”‚     β”‚ (Risk Level)    β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                                       β”‚
                        β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                        β–Ό                              β–Ό                              β–Ό
                 β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”              β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”              β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                 β”‚ Red Path    β”‚              β”‚ Yellow Path β”‚              β”‚ Green Path  β”‚
                 β”‚ Urgent      β”‚              β”‚ Proactive   β”‚              β”‚ Expansion   β”‚
                 β”‚ Outreach    β”‚              β”‚ Check-in    β”‚              β”‚ Opportunity β”‚
                 β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜              β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜              β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

See Pattern: Agent Chaining & Orchestration for implementation.

Renewal Orchestration Chain

Day -90              Day -60              Day -30              Day 0
   β”‚                    β”‚                    β”‚                    β”‚
   β–Ό                    β–Ό                    β–Ό                    β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”        β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”        β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”        β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Health   │───────►│ Value    │───────►│ Contract │───────►│ Close    β”‚
β”‚ Check    β”‚        β”‚ Summary  β”‚        β”‚ Review   β”‚        β”‚ Sequence β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜        β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜        β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜        β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Uses Pattern: Memory & State Management for account persistence.