support-runbook-builder-cs
Agent: Head of Customer Success
L1 customer success leader reporting to the CBO (1x) responsible for CS strategy, SLA design, playbook creation, expansion motion, and training materials.
Department ethos: ideal-customer-success.md
Skill Description
Builds runbooks for the CS team covering common customer scenarios, resolution procedures, and escalation paths.
When to Use
- When the CS team handles recurring customer scenarios inconsistently and needs standardized procedures.
- When new CSMs are joining the team and need documented procedures to ramp quickly.
- When a new product feature or workflow introduces customer scenarios that the team has not encountered before.
Workflow
- Catalog Scenarios: Inventory common customer scenarios from support tickets, CS conversations, and team input. Categorize by frequency and severity. Deliverable: prioritized scenario catalog.
- Document Resolution Procedures: For each scenario, write step-by-step resolution instructions: diagnosis steps, resolution actions, customer communication templates, and verification that the issue is resolved. Deliverable: resolution procedure per scenario.
- Map Escalation Paths: For each scenario, define when and how to escalate -- triggers for escalation, escalation target (engineering, product, leadership), and required context to include. Deliverable: escalation path per scenario.
- Review with Team: Circulate draft runbooks to the CS team for feedback. Incorporate real-world nuances and edge cases from experienced CSMs. Deliverable: reviewed and validated runbooks.
- Publish and Maintain: Publish runbooks in an accessible location. Establish a process for updating runbooks when scenarios change or new scenarios emerge. Deliverable: published runbooks with maintenance cadence.
Anti-Patterns
- Static runbooks: Writing runbooks once and never updating them as the product evolves. Why: outdated procedures lead CSMs to follow wrong steps, making customer situations worse.
- Over-detailed procedures: Writing runbooks so detailed that they cannot adapt to scenario variations. Why: every customer situation has unique context; runbooks should provide decision frameworks, not scripts.
- Runbooks without escalation criteria: Documenting resolution steps but not when to stop troubleshooting and escalate. Why: CSMs without escalation guidance either escalate too early (wasting engineering time) or too late (harming the customer).
Output
On success: Produces a runbook library containing categorized scenarios, resolution procedures, escalation paths, and communication templates. Delivered to the CS team.
On failure: Report which scenarios could not be documented (insufficient historical data, no established resolution), what partial runbooks were created, and what additional input is needed.
Related Skills
1---2name: support-runbook-builder-cs3description: This skill builds runbooks for the CS team covering common customer scenarios and escalation paths. Use when asked to create CS runbooks, document escalation procedures, or standardize customer scenario handling. Also consider when CS team members handle the same scenario differently. Suggest when the user hires new CSMs without documented procedures.4---56# support-runbook-builder-cs78## Agent: Head of Customer Success910L1 customer success leader reporting to the CBO (1x) responsible for CS strategy, SLA design, playbook creation, expansion motion, and training materials.1112Department ethos: [ideal-customer-success.md](../../../../departments/customer-success/ideal-customer-success.md)1314## Skill Description1516Builds runbooks for the CS team covering common customer scenarios, resolution procedures, and escalation paths.1718## When to Use1920- When the CS team handles recurring customer scenarios inconsistently and needs standardized procedures.21- When new CSMs are joining the team and need documented procedures to ramp quickly.22- When a new product feature or workflow introduces customer scenarios that the team has not encountered before.2324## Workflow25261. **Catalog Scenarios**: Inventory common customer scenarios from support tickets, CS conversations, and team input. Categorize by frequency and severity. Deliverable: prioritized scenario catalog.272. **Document Resolution Procedures**: For each scenario, write step-by-step resolution instructions: diagnosis steps, resolution actions, customer communication templates, and verification that the issue is resolved. Deliverable: resolution procedure per scenario.283. **Map Escalation Paths**: For each scenario, define when and how to escalate -- triggers for escalation, escalation target (engineering, product, leadership), and required context to include. Deliverable: escalation path per scenario.294. **Review with Team**: Circulate draft runbooks to the CS team for feedback. Incorporate real-world nuances and edge cases from experienced CSMs. Deliverable: reviewed and validated runbooks.305. **Publish and Maintain**: Publish runbooks in an accessible location. Establish a process for updating runbooks when scenarios change or new scenarios emerge. Deliverable: published runbooks with maintenance cadence.3132## Anti-Patterns3334- **Static runbooks**: Writing runbooks once and never updating them as the product evolves. *Why*: outdated procedures lead CSMs to follow wrong steps, making customer situations worse.35- **Over-detailed procedures**: Writing runbooks so detailed that they cannot adapt to scenario variations. *Why*: every customer situation has unique context; runbooks should provide decision frameworks, not scripts.36- **Runbooks without escalation criteria**: Documenting resolution steps but not when to stop troubleshooting and escalate. *Why*: CSMs without escalation guidance either escalate too early (wasting engineering time) or too late (harming the customer).3738## Output3940**On success**: Produces a runbook library containing categorized scenarios, resolution procedures, escalation paths, and communication templates. Delivered to the CS team.4142**On failure**: Report which scenarios could not be documented (insufficient historical data, no established resolution), what partial runbooks were created, and what additional input is needed.4344## Related Skills4546- [`sla-definer-cs`](../sla-definer-cs/SKILL.md) -- SLAs define the escalation timing that runbooks must respect.47- [`training-material-creator-cs`](../training-material-creator-cs/SKILL.md) -- Training materials teach CSMs how to use the runbooks.48- [`cs-release-readiness`](../../../customer-success/cs-manager/cs-release-readiness/SKILL.md) -- New releases may require runbook updates for new scenarios.
mittuled