Support Playbook Builder

When support depends on individual talent, quality is unpredictable. The brilliant agent leaves; the careful one leaves; the new hire writes responses that sound nothing like the brand. The Support Playbook Builder converts the founder's instinct into a system anyone on the team can run. Not a script — a flexible template with variants, escalation rules, and the voice guide that holds it all together.

The voice guide leads every playbook because that's the layer most teams skip. "Be professional and helpful" is not a voice guide. Three specific "we always" behaviours and three specific "we never" behaviours give the team something to check their drafts against — the difference between consistency and rigidity. Naming what you refuse to do ("we never say 'unfortunately, our policy states...'") is often more useful than naming what you do.

Each scenario ships with three emotional variants — standard, frustrated, angry. The same billing question from a calm customer and an angry one requires different openings, and a single template across both is the fastest way to make a frustrated customer angry. The skill writes the standard response first, then layers acknowledgment and personal touch for the variants. Customisation brackets [Name], [specific finding], [their plan] mark every spot where personalisation is required before sending — a template sent without them is worse than no template.

Escalation triggers are defined per scenario, not in a generic appendix. The billing-scenario escalation rule names a specific threshold ("refunds over £500 or any chargeback"). The bug-report rule names a specific condition ("data loss, security issue, or affects more than 5 customers"). Generic escalation rules get ignored under pressure; specific ones get followed because the agent doesn't have to think.

The playbook is treated as a living document by design. Every output includes the maintenance routine — monthly review, flag templates that produced escalations, add scenarios when new features ship, retire scenarios that have aged out. A playbook written once and never updated is worse than no playbook because it creates the illusion of a system while quietly going stale. The skill ships the document AND the upkeep schedule. For solo founders or two-person teams, it simplifies to five scenarios with one template each plus a triage rule — heavyweight playbooks aimed at three-person teams create more friction than they remove at that scale.