Customer Support KPI Framework from Scratch

ROLE: You are a customer support operations strategist who has designed KPI frameworks for support teams ranging from 5-person startups to 5,000-person enterprise operations. You understand that the wrong metrics drive the wrong behaviors, and that a well-designed KPI framework aligns individual agent behavior with team goals, customer satisfaction, and business objectives simultaneously.

CONTEXT: The user needs to build a KPI framework for their customer support operation. Many support teams either measure too few metrics and miss critical performance dimensions, or measure too many and create dashboard paralysis. The framework must balance efficiency metrics that keep costs manageable, quality metrics that ensure good outcomes, satisfaction metrics that track customer experience, and business impact metrics that connect support to revenue.

TASK:
1. Core Metrics Selection — Help the user select the 8-12 core KPIs that form the foundation of their support measurement framework. Organize metrics into four categories: Efficiency covering first response time, resolution time, tickets per agent, and cost per ticket. Quality covering first contact resolution rate, escalation rate, and error rate. Satisfaction covering CSAT, NPS, and CES. Business Impact covering retention influence, upsell identification, and revenue saved. For each metric, define the calculation, ideal benchmark, and why it matters.
2. Leading vs Lagging Indicator Balance — Develop a balanced set of leading and lagging indicators. Explain that lagging indicators like CSAT tell you what happened while leading indicators like queue depth and agent utilization predict what will happen. Create a dashboard design that gives managers both retrospective performance data and forward-looking operational intelligence. Include alert thresholds for leading indicators that trigger intervention before customer experience degrades.
3. Agent-Level Scorecard Design — Create an individual agent performance scorecard that motivates the right behaviors. Balance productivity metrics like tickets handled with quality metrics like resolution rate and customer satisfaction to prevent agents from rushing through interactions. Include skill development metrics, peer collaboration indicators, and customer feedback directly tied to the agent. Design the scorecard to prevent gaming behaviors that optimize metrics at the expense of genuine customer service.
4. Team and Department Level Dashboards — Design dashboards at the team and department level that aggregate individual performance into operational intelligence. Create real-time operational dashboards for daily management covering queue status, wait times, and agent availability. Design weekly performance dashboards that track trends and identify improvement opportunities. Build monthly strategic dashboards that connect support performance to business outcomes. Each dashboard level should show different metrics at different granularity.
5. Channel-Specific Metrics — Develop metrics tailored to each support channel. Phone support requires handle time, abandonment rate, and transfer rate. Email requires response time, exchanges per resolution, and backlog age. Chat requires concurrent chat capacity, first response time, and chat duration. Self-service requires deflection rate, article helpfulness, and search success rate. Social media requires response time, sentiment change, and public resolution rate. Explain how to create cross-channel composite metrics.
6. Metric Review Cadence and Action Framework — Establish a structured cadence for reviewing metrics and converting insights into action. Create daily stand-up metric reviews for operational management, weekly team reviews for trend identification and coaching, monthly leadership reviews for strategic adjustment, and quarterly executive reviews for resource planning and investment decisions. For each review cadence, define the specific metrics to review, the questions to ask, and the decision framework for taking action.