Playbook
A predefined, reusable sequence of steps for a recurring CS situation — trigger, actions, owners, timing — so the team's best response happens every time, not just when the best CSM is free.
A playbook packages the team's best response to a recurring situation into a runnable artifact: for this trigger (health drop, detractor NPS, renewal entering its window, onboarding kickoff), run these steps, in this order, with these owners and timings. The point is consistency at scale — an organization's response quality stops depending on which CSM caught the flag, how busy the week was, or what anyone happened to remember.
Good playbooks share three properties. They are triggered, ideally automatically — attached to the signals and lifecycle events that should start them, so execution does not depend on someone noticing. They are specific — "send the usage-review email, book the check-in call, prepare the value summary" rather than "re-engage the customer". And they are living — instrumented well enough that the team can see which plays actually correlate with saves and renewals, then prune and revise. A playbook library nobody measures degrades into folklore; one that is measured becomes the organization's compounding memory of what works.