Revenue Operations 18 min read

Customer Success Playbook Template: 5 Core Plays for Every CS Team

A complete customer success playbook template with onboarding, expansion, at-risk, renewal, and churn plays — including trigger tables, health score thresholds, and EBR structure.

Siddharth Gangal

A customer success playbook is only as good as its triggers. Most CS teams have playbooks — they just have the wrong ones: documents that describe ideal behavior rather than prescribing specific actions in response to specific signals. The result is CSMs who know what good looks like in theory but revert to instinct when a customer shows up in the red.

This template gives you the structural foundation that platforms like Gainsight, Totango, and ChurnZero are built around — five core plays, each with a defined trigger condition, action sequence, owner, and success metric. It's designed for VP CS leaders building repeatable programs, CSMs who need consistent playbooks they'll actually use, and COOs who want CS operating as a revenue function, not a support org.

What Makes a CS Playbook Work (and What Makes It Collect Dust)

Research consistently points to the same pattern: CS teams using structured, platform-enforced playbooks report net revenue retention above 100% at significantly higher rates than those relying on informal processes. Totango's SuccessBLOC model — pre-built, modular programs for Onboarding, Adoption, and Renewal Risk — became popular precisely because it removed the "how do we start?" friction. Gainsight's CTA (Call to Action) framework operates on the same principle: every signal above a threshold produces a task, not a suggestion.

Playbooks fail when they're written once and never operationalized into the tools your CSMs live in. They also fail when trigger conditions are too vague ("customer seems unhappy") or too narrow ("NPS below 3 after Q4 survey"). The plays below are calibrated to signal types you can monitor continuously, not just at scheduled touchpoints.

Health Score Foundation: Know What You're Reacting To

Every play in this template is triggered against health score bands or behavioral signals. Before building plays, align your team on a composite health score model with four primary inputs.

Health Score Components

Signal Category Inputs Suggested Weight
Product Usage Login frequency, feature adoption breadth, session duration, workflow completion rate 35%
Relationship Signals Executive sponsor engagement, CSM meeting cadence, NPS/CSAT scores 25%
Support Health Open ticket count, escalation frequency, days-to-resolution trend 20%
Commercial Signals Renewal date proximity, contract utilization, overage vs. usage gap 20%

Threshold Bands

  • Green (75–100): Standard engagement cadence. Monitor for expansion signals.
  • Yellow (50–74): Increased monitoring. CSM proactive outreach within 5 business days.
  • Red (25–49): At-risk protocol. Manager notified. Intervention play activated within 48 hours.
  • Critical (<25): Executive save play. Cross-functional war room. Escalation to VP CS within 24 hours.

ChurnZero's AI-augmented health scoring builds on this by adding behavioral decay signals — not just current usage but the rate of change. A customer at 68 who has dropped 15 points in 30 days is more at-risk than one sitting at a steady 55.

Play 1: Onboarding Play

Objective: Get the customer to defined first value (time-to-value) within 30–45 days of contract signature. Establish product habits before the honeymoon period expires.

Trigger Conditions

Trigger Threshold Priority
Contract signed Automatic on Day 0 Standard
License utilization below target <50% in first 30 days Elevated
Weekly active users declining Two consecutive weeks of decline during onboarding High
Core feature not activated Primary workflow not touched by Day 21 High
No executive sponsor confirmed Day 14 with no sponsor identified Elevated

Action Sequence

  1. Day 1 — Kickoff call (CSM): Confirm stakeholders, document success criteria, agree on milestone dates. Deliver shared onboarding plan in writing.
  2. Day 3 — Technical setup confirmed (Implementation/CSM): Integrations active, data flowing, key users provisioned. Verify against pre-defined technical checklist.
  3. Day 14 — Adoption check-in (CSM): Review usage data. If primary workflow not yet activated, escalate to onboarding support or solutions consultant.
  4. Day 21 — First value milestone (CSM + Champion): Formally confirm first value achieved against agreed success criteria. Document and share internally.
  5. Day 30 — Onboarding close (CSM): Transition to standard success plan. Confirm EBR scheduled. Hand off to steady-state cadence.

Owner and Metrics

  • Primary owner: Assigned CSM
  • Escalation: CSM Manager if Day 21 milestone missed
  • Success metrics: Time-to-first-value ≤30 days, license utilization ≥60% by Day 45, onboarding NPS ≥40

Play 2: Expansion Play

Objective: Identify and convert expansion opportunities in accounts showing adoption depth or new use-case signals. Expansion is a CS motion, not just a sales motion.

Trigger Conditions

Trigger Threshold Priority
License utilization high >85% of licensed seats active for 30+ days High — expansion-ready
Feature limit approaching Usage within 15% of plan limit High — upgrade signal
New department or team identified Champion mentions new team in any interaction Elevated
High NPS + strong adoption NPS ≥8, health score green for 60+ days Standard — advocacy + expansion
Successful EBR with positive sentiment Post-EBR survey score ≥4/5 Elevated

Action Sequence

  1. Signal identified (CSM): Log expansion opportunity in CRM. Tag account with expansion flag. Notify Account Executive within 1 business day.
  2. Qualification call (CSM + AE): Confirm budget authority, timeline, and scope. Is this a seat expansion, tier upgrade, or new module?
  3. Value narrative (CSM): Build ROI summary from current usage data — active users, workflows run, time saved, revenue influenced. This is the business case for expansion, not a pitch deck.
  4. Expansion proposal (AE): Present commercial terms. CSM stays involved as the value anchor throughout negotiation.
  5. Close and onboard expanded scope (CSM): New users or features get a condensed onboarding sequence. Update success plan and health score inputs.

Owner and Metrics

  • Primary owner: CSM (source), AE (close)
  • Success metrics: Net Revenue Retention (NRR), expansion pipeline generated by CS, expansion close rate, time from signal to proposal

Play 3: At-Risk Play

Objective: Intercept accounts showing declining health signals before they reach churn intent. Speed is the variable that determines outcome here — most at-risk interventions that succeed happen within the first 72 hours of signal detection.

Trigger Conditions

Trigger Threshold Escalation Level
Health score drop Score falls to Red (<50) or drops 15+ points in 30 days CSM + Manager
Product disengagement No logins from key users for 14+ days CSM
Unresolved escalation Support ticket open 7+ days, no resolution path CSM + Support Lead
Champion departure Internal sponsor leaves or changes role CSM + AE + Manager
Negative CSAT or NPS CSAT <3/5 or NPS detractor (0–6) CSM + Manager
Competitor mention Any mention of competitive evaluation in call or email CSM + AE + Manager

Action Sequence

  1. Within 24 hours — Risk assessment (CSM): Pull account health history. Identify root cause category: adoption gap, relationship issue, product gap, or external event. Do not contact the customer until you know what you're solving.
  2. Within 48 hours — Manager briefing: Escalate risk to CS Manager with root cause hypothesis and proposed response. Align on who contacts the customer and what the ask is.
  3. Within 72 hours — Executive outreach (CSM or VP CS): Personal outreach from a senior stakeholder. Do not send an automated email sequence. The message: "We've noticed X, we want to make it right, here's what we're prepared to do."
  4. Recovery plan (CSM): Deliver a written recovery plan within 5 business days of first intervention. Include specific milestones, owners, and a defined re-assessment date.
  5. 30-day check (Manager): Review health score trajectory. If score has not improved, escalate to executive save play or begin churn protocol.

Escalation Workflow

If the at-risk play does not produce health score improvement within 30 days, trigger the following escalation ladder:

  1. VP CS personal call to executive sponsor
  2. Product leadership involvement if root cause is a product gap
  3. Custom success plan with executive co-signature
  4. If no resolution path by Day 45, begin churn play

Owner and Metrics

  • Primary owner: CSM (execution), CS Manager (oversight)
  • Success metrics: At-risk-to-recovered rate, time from signal to first intervention, health score trend at 30/60/90 days post-intervention

Play 4: Renewal Play

Objective: Secure renewal at or above current ARR, address retention risks proactively, and identify expansion opportunities before the contract end date. The renewal conversation should never be the first time a customer hears that their contract is expiring.

Trigger Conditions

Trigger Timing Action
Standard renewal flag 90 days before renewal date CSM initiates renewal health review
At-risk renewal flag 120 days before (if health is Yellow or Red) Accelerated intervention; AE engaged immediately
Champion departure during renewal window Any point in 90-day window Escalate to VP CS; re-map stakeholders immediately
Price objection signaled Any point in 90-day window Build ROI case; loop in AE for commercial discussion

Action Sequence

  1. Day −90: Renewal health audit (CSM): Score current health, document open risks, review usage against licensed capacity, and confirm executive sponsor is still active and engaged.
  2. Day −75: Renewal kickoff call (CSM + Champion): Frame the renewal as a value conversation, not an administrative task. Present usage summary and outcomes achieved. Surface any concerns early.
  3. Day −60: Risk remediation (CSM): If any red flags identified at Day −75 call, activate at-risk play in parallel with renewal motion. Do not proceed to commercial negotiation with unresolved relationship issues.
  4. Day −45: Commercial terms (AE): Deliver renewal proposal. CSM supports with value documentation. Address objections with data, not discounts alone.
  5. Day −30: Executive alignment (VP CS or AE): If not yet signed, escalate to executive-to-executive contact. Flag internally as renewal at risk.
  6. Day −14: Close deadline (AE + CSM): Final push. Escalate to VP CS if close is uncertain. Internal alert to CS leadership.

Owner and Metrics

  • Primary owner: CSM (health), AE (commercial)
  • Success metrics: Gross Revenue Retention (GRR), renewal rate by segment/tier, time from renewal initiation to signature, expansion at renewal rate

Play 5: Churn Play

Objective: When cancellation is confirmed or highly likely, execute a structured wind-down that preserves the relationship, captures learnings, and creates conditions for future re-engagement. Not every customer can be saved — but every churn can be learned from.

Trigger Conditions

Trigger Signal Urgency
Cancellation notice received Formal written notice or CRM cancellation flag Immediate
Non-response to renewal outreach No engagement after 3 outreach attempts in Day −30 window High
Confirmed competitive switch Customer confirms migration to competitor Immediate
At-risk play failed Health score not improved at 45-day check High

Action Sequence

  1. Within 24 hours — Internal notification (CSM): Flag churn to CS Manager, AE, and RevOps. Update CRM with cancellation reason (primary and secondary). This data drives root cause analysis.
  2. Win-back assessment (CS Manager): Is there a viable save path? If root cause is product gap, support failure, or pricing — document a potential counter-offer. If root cause is budget elimination, company shutdown, or strategic pivot — proceed to structured offboarding. Do not invest resources in a save with no viable path.
  3. Executive outreach if warranted (VP CS): For accounts above $25K ARR or strategic logos, personal VP-level outreach before accepting churn. One call — clear ask, specific offer, definitive response expected.
  4. Offboarding protocol (CSM): If churn proceeds: confirm data export process, introduce customer to any self-serve documentation, close out open support tickets, and confirm cancellation date per contract terms.
  5. Exit interview (CSM or CS Manager): Request a 20-minute call or async survey within 2 weeks of cancellation. Three core questions: What was the primary reason? What would have changed the outcome? What would need to be true for you to consider us again?
  6. Win-back flag (CRM): Set a 6-month re-engagement flag. Assign to AE or expansion CSM. Churned customers who had a positive offboarding experience re-buy at measurably higher rates than those who left on bad terms.

Owner and Metrics

  • Primary owner: CSM (execution), CS Manager (save assessment)
  • Success metrics: Churn reason categorization accuracy, exit interview completion rate, win-back rate at 6/12 months, save rate for at-risk interventions that reached churn play

EBR Structure: The Anchor for Every Play

Executive Business Reviews are not standalone events — they're the scheduled mechanism that generates data for every play above. A well-run EBR surfaces expansion signals, confirms health, identifies at-risk conditions, and begins the renewal motion. A poorly run EBR is a slide deck nobody asked for.

EBR Cadence by Segment

  • Enterprise (>$50K ARR): Quarterly EBR, in-person or live video
  • Mid-market ($10K–$50K ARR): Semi-annual EBR, video + async follow-up
  • SMB (<$10K ARR): Annual EBR or digital equivalent (data summary email + async Q&A)

Standard EBR Agenda

  1. Business context review (10 min): What has changed for the customer's business since the last EBR? New priorities, org changes, growth or contraction?
  2. Value delivered (15 min): Usage metrics, outcomes achieved, ROI tied to agreed success criteria. Present data the customer doesn't already have — not a recap of their own dashboard.
  3. Open issues and risks (10 min): Transparent review of any unresolved support issues, adoption gaps, or product gaps. Come with status and resolution timeline, not apologies.
  4. Roadmap alignment (10 min): What is coming from product that addresses their stated needs? What needs to be on your internal roadmap to serve them?
  5. Mutual commitments (5 min): Specific, named action items with owners and dates on both sides. The EBR is not complete until mutual commitments are documented.

Response Time Standards by Tier

Playbooks are only as effective as the speed at which they're executed. These benchmarks reflect 2026 B2B SaaS standards for CS-led engagement:

Account Tier Channel Acknowledgment SLA Resolution Target
Strategic (>$100K ARR) Slack / dedicated channel <15 minutes Same business day
Enterprise ($50K–$100K ARR) Email / Slack <1 hour 24 hours
Mid-market ($10K–$50K ARR) Email <4 hours 48 hours
SMB (<$10K ARR) Email / portal <8 hours 72 hours

Top-performing B2B SaaS teams achieve under one hour first response on email for enterprise accounts and under 15 minutes on shared Slack channels. These are not aspirational numbers — they are the floor at which strategic accounts set expectations.

Operationalizing This Template

A playbook template sitting in a document is a strategy. A playbook loaded into your CS platform and connected to real-time health signals is an operating system. The gap between the two is where most CS programs stall.

To activate this template:

  1. Map triggers to your data sources. Identify which systems (product analytics, CRM, support platform) produce each trigger signal. If a trigger has no data source, you cannot automate it.
  2. Build health score in your CS platform. Whether you use Gainsight, ChurnZero, Totango, or a lightweight tool like Planhat, the composite health score has to be calculated automatically — not filled in manually by CSMs.
  3. Create task templates for each play. Every play above should translate into a task template in your CS platform. When a trigger fires, the CSM should receive a pre-built task with context, not a blank prompt to figure it out.
  4. Establish review cadences. Plays need managers reviewing them. A weekly pipeline review of accounts in Yellow and Red health, a monthly churn postmortem, and a quarterly playbook audit to update thresholds based on what's working.
  5. Measure play effectiveness separately from account outcomes. A play can be executed correctly but still result in churn if the underlying problem is product fit. Track both play completion rates and outcome rates to distinguish execution problems from strategy problems.

Frequently asked questions

How many plays should a CS team maintain at any one time?

Most effective CS programs run five to eight active plays. The five plays in this template cover the full customer lifecycle. Teams that build more than eight typically find that play quality degrades — triggers become inconsistent and CSMs stop trusting the system. Start with these five, instrument them properly, and add plays only when you've identified a repeatable scenario that isn't covered.

Who owns the playbook — CS or RevOps?

CS leadership owns the content and execution standards. RevOps owns the instrumentation and measurement. In practice, this means CS leaders define the trigger thresholds and action sequences, while RevOps ensures those triggers are connected to real data in the CS platform and that outcome metrics are tracked accurately. Neither function can do this alone without the other breaking something important.

How often should playbook triggers and thresholds be updated?

At minimum, once per quarter. Health score thresholds that made sense at $2M ARR often need recalibration at $10M ARR because your customer mix changes. Expansion signal thresholds change as your product evolves. Schedule a quarterly playbook review as a standing agenda item for CS leadership, and build in an annual full audit that includes comparing play execution data against actual retention and expansion outcomes.

What is the right health score model for an early-stage CS team?

Start with fewer inputs, not more. An early-stage team with limited instrumentation is better served by a three-signal model — product usage, support health, and renewal proximity — than a ten-signal model with half the inputs filled in manually. The goal is a score CSMs trust and act on. A simple score calculated from clean data beats a sophisticated score calculated from partial data every time. Add signals as your data infrastructure matures.

How do you handle the at-risk play when the root cause is a product gap?

Separate the relationship intervention from the product resolution. The relationship intervention — the outreach, the recovery plan, the executive engagement — happens on the CS timeline (24–72 hours). The product resolution happens on the product team's roadmap timeline, which you cannot compress by urgency alone. Be direct with the customer about what you can commit to and what you cannot. Customers tolerate product gaps far better than they tolerate vague promises about those gaps being fixed.

What's the difference between an EBR and a QBR?

Terminology varies by company, but the meaningful distinction is audience and focus. A QBR (Quarterly Business Review) is often CSM-led, focused on product usage and operational metrics, with the customer's day-to-day team. An EBR (Executive Business Review) is VP CS or above-led, focused on business outcomes and strategic alignment, with the customer's executive sponsor. QBRs keep the program running. EBRs keep the relationship at the executive level where renewal and expansion decisions actually get made. Both are necessary; neither substitutes for the other.

How do you measure whether a CS playbook is actually working?

Three metrics tell you most of what you need to know: play completion rate (are CSMs executing the plays when triggered?), signal-to-outcome correlation (do accounts that receive early intervention have better health trajectories than those that don't?), and net revenue retention by segment (the ultimate output measure). If completion rate is low, you have an adoption problem — the plays are too complex or the triggers are not trusted. If correlation is weak, you have a strategy problem — the interventions don't match the root causes. Start with completion rate. You cannot measure effectiveness if plays aren't being run.