Customer Success Handbook
How Customer Success works at Prism, a white-label client reporting platform: the model it runs on, the procedures work moves through, the playbooks that fire when an account changes, and the artifacts used to run them.
The four sections follow a dependency chain — define the system, then how work flows into and out of it, then the responses that fire on a trigger, then the artifacts those responses call for.
The handbook documents the target model, not only what the software does today. Where the two differ, the page says so in a marked notice. Process running ahead of tooling is normal; naming it on the page is how the two stay honest about each other.
1. Operating Model
Vocabulary, structure, and how customers and health are modelled. 8 pages
2. Operating Procedures
How work flows into, through, and out of CS. 11 pages
- 2.1Sales → CS Handoff Standard
- 2.2Meeting Standards & Working Norms
- 2.3Operating Rhythm
- 2.4Account Prioritization Framework
- 2.5Cross-Functional Interfaces
- 2.6Renewal Forecasting
- 2.7Escalation Management
- 2.8Voice of Customer & Product Feedback
- 2.9Customer Education & Enablement
- 2.10Advocacy Program
- 2.11Exception Handling
3. Playbooks
Trigger-based responses, each with entry criteria, procedure, and exit criteria. 9 pages
4. Assets
The templates and kits the procedures and playbooks call for. 5 pages