Operations Playbook

An effective Operations Playbook has seven components: (1) Trigger Condition — the specific event or signal that activates this playbook (not a vague situation, but a precise measurable condition: "Account health score drops below 50 for accounts with ACV > $10k"). (2) Objective — what successful execution of the playbook achieves (prevent the at-risk account from churning and improve their health score to above 60 within 60 days). (3) Owner — which role is responsible for executing the playbook (the CSM assigned to the account). (4) Steps — numbered, explicit actions in chronological order, with each step specifying: what action to take, what system to take it in, what the expected outcome is, and when to advance to the next step. (5) Templates — message templates, email drafts, call agendas, or slide templates used in each step, embedded directly in the playbook for immediate use. (6) Escalation Criteria — conditions under which the standard playbook should be escalated to the manager or a different team. (7) Measurement — how success of the playbook is tracked (health score change, renewal outcome, NPS change).

Support Ops playbooks: Ticket Escalation Playbook (when and how to escalate to Tier 2, Tier 3, Engineering, or Security); Mass Incident Communication Playbook (template-driven response workflow for product outages affecting many customers); Enterprise Complaint Playbook (handling executive-level complaints that require immediate response and cross-functional coordination); New Agent Onboarding Playbook (30/60/90 day structured onboarding program for new support hires). CS Ops playbooks: At-Risk Account Playbook (triggered by health score drop); New Customer Onboarding Playbook (60-day structured program for new accounts); Expansion Opportunity Playbook (triggered by usage signals indicating readiness for upsell); Renewal Playbook (triggered 90 days before contract end); Champion Departure Playbook (triggered when the primary point of contact leaves the customer account); Executive Escalation Playbook (handling executive-level complaints or escalation requests from enterprise accounts).

Playbooks expire faster than most organizations realize. Every product update, pricing change, team restructure, or support tool configuration change can make playbook steps inaccurate — and agents executing stale playbooks may take incorrect actions with customer impact. Maintenance discipline: assign every playbook an owner (the person responsible for keeping it current) and a review trigger (review on: product release cadence, ticket theme changes, team process changes, and at minimum annually). Build a Playbook Registry — a central index of all active playbooks with: owner, last reviewed date, trigger condition, and a 1-sentence description. Flag playbooks not reviewed in > 90 days as "stale" in the registry. When reviewing tickets that involved unusual escalations or edge cases, proactively check whether an existing playbook should be updated to cover the new scenario. Product Ops conducts a quarterly Playbook Audit, reviewing all playbooks in the registry for accuracy and identifying gaps where common situations are not yet covered.