界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
数据与研究 · SKILL.md

customer-ops-specialist

customer-ops-specialist

【数据与研究】Manage customer operations across success, support, and revenue operations. Cover customer onboarding, health scoring, renewal management, ticket triage, SLA management, knowledge base development, billing operations, dunning, refunds, and customer metrics. Triggers on "customer onboarding", "support ticket triage", "billing inquiry", "churn analysis…

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: customer-ops-specialist description: | Manage customer operations across success, support, and revenue operations. Cover customer onboarding, health scoring, renewal management, ticket triage, SLA management, knowledge base development, billing operations, dunning, refunds, and customer metrics. Triggers on "customer onboarding", "support ticket triage", "billing inquiry", "churn analysis", "health score", "SLA management", "dunning process", "customer success playbook", "renewal management", "CSAT review", or "customer ops". Exec/VIP and public community escalation program: community-executive-escalations-program-manager. Monetization product (pricing, paywalls): product-management-monetization.

Customer Operations Specialist

Overview

Manage customer operations across success, support, and revenue operations. This skill covers customer onboarding, health scoring, renewal management, ticket triage, SLA management, knowledge base development, billing operations, dunning, refunds, and customer metrics.

Features

  • Customer onboarding playbook with milestone tracking
  • Health score framework with leading indicators and risk signals
  • Renewal management workflow with expansion opportunity identification
  • Ticket triage and SLA management with escalation paths
  • Billing operations: dunning sequences, refund processing, subscription changes
  • Customer metrics: CSAT, NPS, NRR, GRR, churn rate, time-to-resolution

Usage

  1. Identify the user's customer ops need (onboarding, support, billing, or metrics)
  2. Follow the corresponding workflow below
  3. Produce structured outputs: onboarding checklists, health scorecards, renewal playbooks, or billing SOPs

Examples

  • User: "Design a customer onboarding flow" Agent: Runs Customer Onboarding workflow, produces 30-60-90 day plan with milestones, success criteria, and handoff points

  • User: "Set up a health score" Agent: Runs Health Scoring workflow, defines leading indicators (product usage, support tickets, NPS), creates scoring model with risk thresholds

  • User: "Handle a billing dispute" Agent: Runs Billing Operations workflow, investigates charge, applies refund policy, documents resolution, updates customer record

When to Use

  • Design or run customer onboarding, health scoring, and renewal playbooks
  • Triage support tickets, SLAs, escalations, and knowledge-base updates
  • Handle billing, dunning, refunds, and subscription change operations
  • Review CSAT, churn, NRR, and other customer-facing operational metrics

When NOT to Use

  • ASC 606 revenue recognition, deferred revenue, or audit-ready close → use senior-revenue-accountant
  • Data pipeline incidents or warehouse platform operations → use data-system-ops-lead or data-manager
  • Product requirements or process documentation for internal systems → use business-analyst
  • Public API or developer documentation → use tech-writer-researcher
  • Deal desk, order forms, signature routing, CRM close process → use deal-operations-administrator
  • Employee HR onboarding, offboarding, HRIS → use people-operations-specialist
  • Technical debugging, repro, engineering escalation → use support-engineer
  • Product how-to, configuration help, support macros → use product-support-specialist

Core Workflows

1. Customer Onboarding & Success

Onboarding checklist:

  1. Pre-engagement

    • Welcome email with next steps
    • Account setup and provisioning
    • Introductory call scheduled
    • Technical requirements confirmed
  2. Activation (first 30 days)

    • Core feature walkthrough
    • Data migration/import completed
    • Integrations configured
    • First value milestone achieved
  3. Adoption (30-90 days)

    • Advanced feature training
    • Use case expansion
    • Regular check-in cadence established
    • Success metrics baseline set

Health scoring:

DimensionWeightGreenYellowRed
Product usage30%Daily activeWeekly<Monthly
Feature adoption25%>80% core features50-80%<50%
Support tickets15%<2/month2-5/month>5/month
NPS/CSAT15%>5030-50<30
Engagement15%ResponsiveDelayedGhosted

2. Support & Issue Resolution

Ticket triage:

PriorityResponseResolutionExamples
P1 (Critical)15 min4 hoursSystem down, data loss, security
P2 (High)1 hour24 hoursMajor feature broken, workaround exists
P3 (Normal)4 hours72 hoursMinor bug, feature question
P4 (Low)24 hours7 daysCosmetic, enhancement request

Resolution workflow:

  1. Acknowledge and set expectations
  2. Gather context (logs, screenshots, reproduction steps)
  3. Reproduce internally
  4. Resolve or escalate to engineering
  5. Verify fix with customer
  6. Document in knowledge base
  7. Close with CSAT survey

3. Revenue Operations

Billing workflow:

  • Invoice generation and delivery
  • Payment processing and reconciliation
  • Dunning (failed payment recovery)
  • Refund and credit processing
  • Subscription changes (upgrade/downgrade/cancel)

4. Metrics & Continuous Improvement

Weekly review:

  • Ticket volume and trend
  • First response time vs SLA
  • Resolution time vs SLA
  • CSAT score
  • Top categories and emerging issues

Monthly review:

  • Churn rate and reasons
  • Expansion revenue
  • NRR (Net Revenue Retention)
  • Health score distribution
  • Knowledge base article effectiveness
我的收藏