Customer Onboarding Playbook

30-day milestones from contract signing to first successful task — chronological trigger conditions, intervention actions, measurement metrics.

Trigger condition

Activates immediately after contract signing (subscription or enterprise contract). Free / Lite tier self-signup users use the simplified version (see “self-serve onboarding version” at the end).

Roles and responsibilities

RolePrimary responsibility
Customer Success (CSM)Full-process owner; at least 1 customer touch per week for 30 days
SalesHand off CSM in week one after signing; only re-engage on expansion opportunities
SupportHandle tickets; proactively reach out only when assigned by CSM
EngineeringEngaged only when escalated by CSM, for customer-specific integration or customization

30-day milestones

30-day onboarding timeline Four phases scaled to actual duration · each ends with a measurement gate Handoff kickoff signed Activation Seed FST ≥ 70% Habit formation 7-day return ≥ 60% · workflows ≥ 2 Expansion review Success: Yes / No / Partial Day 0 Day 3 Day 10 Day 20 Day 30 Phase widths proportional to duration · CSM-owned throughout · escalate on FST coverage < 50%

Days 0-3: handoff and alignment

Operational steps:

  1. Sales holds handoff meeting within 24 hours of signing, introduces CSM to customer primary contact
  2. CSM holds kickoff meeting within 48 hours, confirming:
    • Primary workflows (top 3 task types the customer wants agent to handle)
    • Internal primary users (5-15 seed users)
    • Success criteria (the customer’s own definition of “successful onboarding by day 30”, not the CSM’s recommendation)
  3. CSM delivers within 72 hours:
    • Account provisioning confirmation
    • Seed user access configuration
    • Week-one onboarding plan (including recommended first-task list)

Completion criterion: customer primary contact confirms kickoff meeting notes by Day 3.

Days 4-10: seed user activation

Operational steps:

  1. CSM monitors first-task initiation for every seed user
  2. If a user has not initiated a task 48 hours after signup, CSM reaches out directly (email + 1-on-1 short call)
  3. If a user’s first task fails, within 24 hours CSM:
    • Analyzes failure cause (task difficulty, agent completion rate history, HITL trigger reason)
    • Recommends alternative tasks for this user
    • Escalates to engineering if the failure pattern recurs, to evaluate if it’s a product issue

Measurement metric: FST (First Successful Task) coverage for seed users ≥ 70% by Day 10.

Escalation path: when FST coverage < 50%, CSM lead engages; when < 30%, escalate to VP Customer Success + engineering lead.

Days 11-20: habit formation

Operational steps:

  1. Monitor seed users’ 7-day return rate and task diversity (workflow count)
  2. For non-returning users (no second submission within 7 days after FST):
    • Push task recommendations related to the first task type
    • If still not returning, CSM directly asks about usage barriers
  3. For returned users with workflow count stuck at 1:
    • Introduce 2-3 examples of adjacent workflows
    • Do not push aggressively — the largest churn cause in agent products is “failed after being pushed the wrong workflow”

Measurement metric: seed users’ 7-day return rate ≥ 60% by Day 20; per-user workflow count ≥ 2.

Days 21-30: seed expansion & success criteria review

Operational steps:

  1. Review Day 0’s success criteria with customer primary contact, comparing to current state
  2. If met:
    • Initiate expansion beyond seed users (other departments, other workflows)
    • Coordinate with sales for 60/90-day expansion opportunity assessment
  3. If not met:
    • Analyze gap: product quality / user education / wrong workflow selection
    • Develop 30-day remediation plan with assigned owner
  4. Collect customer usage feedback and route to product team

Measurement metric: customer primary contact’s explicit answer to “was onboarding successful?” by Day 30 (do not let customer answer vaguely “okay” — push for Yes / No / Partial).

Self-serve onboarding version (Free / Lite)

No full-process CSM engagement; product automation handles it:

  • Signup triggers onboarding email sequence (Day 0, 3, 7, 14, 21, 30)
  • Monitor same metrics; trigger in-app recommendations rather than human contact
  • Key thresholds relaxed: seed-user FST coverage monitored at ≥ 50%
  • Human engagement only when user contacts support or hits tier cap

Critical things not to do

  • Days 0-3: do not discuss expansion or upsell — customer just signed; they need product value delivery, not more sales conversation
  • Do not let support replace CSM — support handles specific issues; CSM ensures overall success; conflating roles makes customer success reactive instead of managed
  • Do not use a generic onboarding email sequence in place of targeted outreach — different seed users of the same customer have different activation cadences; mass mail loses specificity
  • Do not avoid failure in the Day 30 review — customers will pay vendors who openly acknowledge problems and present remediation plans; avoidance only delays churn to Day 90

Cross-section connections

Was this page helpful?
Edit on GitHub