What is a customer onboarding playbook?
A customer onboarding playbook is a standardised guide defining how a CS team handles every new customer. It has 8 components: (1) Customer segmentation rules — which playbook applies to whom. (2) Default onboarding stages with entry/exit criteria. (3) Trigger plays — pre-defined responses to specific signals like silent accounts or blocked tasks. (4) Communication templates for each touchpoint. (5) Health score thresholds with response actions. (6) Escalation matrix. (7) Success metrics and targets. (8) Quarterly review cadence.
In this article
An onboarding playbook is distinct from a per-account plan. The plan is customised for each customer. The playbook defines the default approach that applies to all customers in a segment — and the pre-defined responses to specific events when they occur.
Component 1: Customer Segmentation Rules
Define which playbook applies to which customer. Most CS teams operate 2–3 playbooks: enterprise (complex, 90+ days), mid-market (standard 30 days), and SMB (automation-heavy, light touch). Define the criteria clearly — ACV, company size, integration complexity — so every CSM makes the same assignment decision.
Component 2: Default Onboarding Stages
For each stage, define entry criteria (what must be true before this stage starts), exit criteria (what must be true before moving on), and default tasks with owners. See our CS onboarding template for the task-level detail on each stage.
Component 3: Trigger Plays
Trigger plays are pre-defined responses to specific events. Document them so CSMs don't improvise:
- Silent account play: no client action for 10+ days → direct call, not email
- Blocked task play: task blocked 48+ hours → see our block protocols
- At-risk play: health score below threshold → immediate intervention
- Champion loss play: internal champion goes quiet or leaves → contact within 48 hours
- Go-live slip play: 5+ days past go-live date, below 60% completion → CS manager escalation
Component 4: Communication Templates
Define standard communications for each stage: welcome email, kickoff recap, weekly update, at-risk outreach, go-live celebration, 30-day post-go-live check-in. Don't leave these to individual CSM creativity. The full 10-email sequence is in our email sequence guide.
Component 5: Health Score Thresholds
Define what each range means and what it triggers: 70–100 healthy (monthly cadence), 40–69 monitor (weekly touchpoint), 0–39 critical (immediate intervention, escalate if no response in 48 hours). Match these to your health score formula. See our health score guide.
Component 6: Escalation Matrix
CSM handles routine issues. CS Manager handles blocks unresolved for 7+ days. VP CS handles accounts at renewal risk. Client side: project lead handles routine, their manager handles extended blocks, executive sponsor handles project failure risk. Get both sides defined upfront — in the kickoff, not in a crisis.
Component 7: Success Metrics and Targets
Define what the playbook is designed to achieve: completion rate target (85%+), TTV target (under 14 days), go-live rate on date (75%+), health score at Day 30 (70+). These are how you know whether the playbook is working. See our onboarding KPIs guide.
Component 8: Review and Update Cadence
A playbook that doesn't get updated becomes historical. Quarterly review: what metrics improved, which trigger plays fired most often, which communication templates have lowest response rates? Update based on what you learn. The best playbooks are living documents. For the broader CS playbook covering all lifecycle stages, see our complete CS playbook.
Frequently Asked Questions
Stop flying blind on your accounts.
Lyniro gives CS leaders real-time visibility into every account — with completion verified by the client, not your team.
Become a Founding Design Partner — Free