Customer success teams manage complex portfolios of accounts — tracking health, driving adoption, preventing churn, and identifying expansion. AI helps CS teams work more accounts at higher quality by automating routine analysis and accelerating communication preparation.

1. Health Score Analysis

Building a Customer Health Score

Prompt: Help me design a customer health score model for our B2B SaaS product.

Company context:
- Product: Project management software
- Average ARR per customer: $24,000
- Typical contract: Annual
- Core feature: Task management, reporting, integrations
- Customer types: Marketing teams, product teams, operations teams

Available data signals:
- Login frequency (daily/weekly/monthly/none)
- Feature adoption (tasks created, reports run, integrations active)
- User count vs. licensed seats (expansion/contraction indicator)
- Support ticket volume and severity
- NPS scores (collected quarterly)
- Contract data: Days to renewal, ARR, expansions/contractions
- Marketing engagement: Email open rates, webinar attendance

Design:
1. Health score framework (what dimensions matter most and why)
2. Weighting recommendation for each signal
3. Thresholds for Red/Yellow/Green status
4. How to handle missing data (some signals not available for all customers)
5. Alert triggers for CS team intervention
6. Score recalculation frequency recommendation

Interpreting Health Patterns

Prompt: Analyze these account health signals and recommend CS actions.

Account: MegaCorp Inc
ARR: $48,000 | Renewal: 87 days
Contract: 25 seats purchased

Current signals:
- Active users last 30 days: 9 of 25 (36%) — was 18 of 25 (72%) 90 days ago
- Feature adoption score: 42/100 (down from 68 last quarter)
- Support tickets: 3 open, 2 medium severity (integration issues)
- Last login (economic buyer/main contact): 45 days ago
- NPS: Last score was 6 (collected 6 months ago, not re-surveyed)
- Executive sponsor: Left company 60 days ago (CSM note)

Analyze:
1. Health trajectory (improving, stable, declining?)
2. Root cause hypothesis (what's likely driving the decline?)
3. Churn probability assessment
4. Recommended immediate actions (next 7 days)
5. 30-day recovery plan
6. Renewal risk assessment and recommended approach
7. Escalation triggers to involve leadership

2. QBR Preparation

QBR Agenda and Slides

Prompt: Help me prepare a QBR (Quarterly Business Review) for a key account.

Account: Acme Corp
ARR: $120,000 | Renewal: 4 months away
Attendees: VP Operations (our champion), CFO (economic buyer — new), 
           IT Director, 2 power users

Last QBR: 3 months ago (strong meeting, CFO was not there)
Account health: Yellow (usage down, but ROI measurable)

Key data points for this QBR:
- Time saved (based on usage): 1,400 hours/year (our ROI calculator)
- Cost savings vs. prior workflow: ~$78,000/year (at $56/hour average)
- Features they use: 8 of 15 available
- Features they don't use that would benefit them: Automation module, API
- Support: 2 tickets this quarter, both resolved quickly
- Their strategic goals (from last call): Improve team efficiency, reduce 
  software costs (new CFO mandate)

Create QBR structure:
1. Agenda (60-minute meeting)
2. Opening — hook for CFO (frame ROI first)
3. Usage summary — make the data visual and meaningful
4. ROI calculation — tie to their numbers
5. Feature expansion opportunity — 2 unrealized use cases
6. Roadmap preview — what's coming they'll care about
7. Success plan for next quarter — concrete goals
8. Renewal discussion framework

Also: 3 executive-ready slides (described, not designed)

QBR Follow-Up Email

Prompt: Write a QBR follow-up email to send within 24 hours.

Meeting outcome:
- CFO engaged positively on ROI data
- Agreed to explore automation module (potential $18K expansion)
- Requested: Technical assessment of API integration
- Renewal: CFO said "sounds good" — not signed yet
- Next steps agreed: 
  1. We send automation demo invite (this week)
  2. Their IT team connects with our solutions engineer (next week)
  3. Renewal paperwork sent by end of month

Write follow-up email that:
- Thanks attendees specifically (not generic)
- Summarizes decisions made and next steps with owners and dates
- Attaches/links: QBR slides, ROI summary PDF
- Creates accountability (next step clear for both sides)
- Opens the path for expansion without being pushy
- Sets up momentum for renewal

Subject line: 3 options

3. Churn Prevention

At-Risk Account Playbook

Prompt: Create an escalation playbook for at-risk accounts.

Context: B2B SaaS, $20-100K ARR accounts, 90-day renewal cycles
CS team: 6 CSMs, each managing 80-120 accounts
Current problem: Churn rate 18% annually (target: 10%)

Design a tiered escalation playbook:

Tier 1 (CSM-led intervention):
Trigger: Health score drops below 65, or any Red signal
- Day 1: CSM internal assessment (what's causing the decline?)
- Day 2: Proactive outreach (what to say, template)
- Day 5: If no response, second attempt + leadership notification
- Day 10: If unresponsive, escalate to Tier 2

Tier 2 (CSM + CS Manager):
Trigger: No response to Tier 1, or NPS < 5, or executive sponsor leaves
- Manager joins next call
- Internal root cause analysis (product issue? CS failure? external factors?)
- Recovery offer assessment (what can we offer? feature access, training, discount?)
- Executive engagement from our side

Tier 3 (Executive escalation):
Trigger: ARR > $50K at risk, or strategic account
- CRO or CEO involvement
- Executive to executive call
- Custom success plan

For each tier: Email templates, call scripts, offer options

Renewal Risk Conversation

Prompt: Write a script for a renewal risk conversation.

Situation: Account is 6 weeks from renewal. Health score is Red. 
Champion has not responded to 3 outreach attempts. Economic buyer 
sent a message saying "we're evaluating our software spend."

My goal: Save the renewal at full ARR if possible, understand if 
they're actually at risk, and not lose the account to a competitor.

Write a call script for when they finally pick up:

Opening (disarming, not defensive):
- Acknowledge their message
- Show I've done homework (what I know about their usage)
- Position this call as helping them, not saving the contract

Discovery questions:
- What's driving the software spend review?
- How has their use of our product been going?
- What would need to be different for this to be a clear yes?

Response frameworks for common objections:
- "We're not using it enough" → [response]
- "It's too expensive vs. alternatives" → [response]
- "Our team doesn't like it" → [response]
- "We're evaluating a competitor" → [response]

Close:
- Next step regardless of outcome
- When to walk away vs. fight

4. Customer Communication at Scale

Proactive Outreach Templates

Prompt: Create a proactive outreach email series for different customer segments.

Segment 1: New customers (30-day check-in)
Goal: Confirm they're set up, offer help, surface issues early

Segment 2: Customers approaching 60% through their contract
Goal: Remind them of features they haven't adopted, create momentum

Segment 3: Power users who haven't expanded to new features
Goal: Introduce relevant new capabilities, drive expansion

Segment 4: Dormant accounts (haven't logged in for 30+ days)
Goal: Re-engage, understand what happened, save the account

For each segment, create:
- Email subject line (3 options — test these)
- Body copy (150-200 words — short, high-value, clear CTA)
- Personalization variables [COMPANY_NAME], [FEATURE_UNUSED], etc.
- CTA: Specific and low-friction (book 15 min / watch 3-min video / reply to this email)

Renewal Negotiation Frameworks

Prompt: Help me prepare for a difficult renewal negotiation.

Situation: Customer wants 20% price reduction. Contract is $85,000.
They've had good ROI but are price-shopping a competitor.
The competitor is real — we know their pricing is 15% lower.

I have authority to: Discount up to 10% without approval
Above 10% discount: Requires VP approval (who I can get in 1 day)

Prepare:
1. Opening position (don't start by offering discount)
2. Value-based reframe (before any pricing conversation)
3. ROI reminder (help them do the math — is 15% savings worth the risk of switching?)
4. Bundle option (add something valuable instead of discounting)
5. Multi-year offer (lock them in with modest discount)
6. Counter to "we've decided to switch" (last-ditch offer)
7. When to let them go (some churns are okay)
8. Walk-away criteria

Call script for the conversation

5. CS Metrics and Reporting

Executive Dashboard

Prompt: Help me design a CS metrics dashboard for monthly executive review.

CS team: 6 CSMs, 480 total accounts, $12.4M total ARR managed

Metrics to report:
Retention:
- Gross revenue retention (GRR)
- Net revenue retention (NRR) 
- Logo churn rate
- ARR at risk (next 90 days by risk level)

Expansion:
- Expansion ARR generated this month
- Expansion pipeline (qualified opportunities in CS pipeline)
- Expansion win rate

Health:
- Health score distribution (Red/Yellow/Green by count and ARR)
- Health score trend (30-day change)
- NPS by cohort

Efficiency:
- Accounts per CSM
- ARR managed per CSM
- QBRs completed vs. planned
- Response time on inbound customer outreach

Design:
1. One-page executive summary format
2. Key numbers to headline (most important 4-5 metrics)
3. Trend indicators (arrows, red/green vs. last month)
4. Call-out box: "What's driving the numbers this month"
5. Actions we're taking on negative trends

AI in customer success works best as a force multiplier — enabling smaller CS teams to cover more accounts at higher quality through faster analysis, better-prepared conversations, and systematic early warning detection. The relationship and judgment elements of CS remain fundamentally human.