Support AI Skill

Support Operations Reporting

Design and maintain comprehensive support operations reports and dashboards that track team performance, identify trends, and drive data-informed decisions. Use when building support dashboards, creating executive reports, tracking support KPIs, performing monthly business reviews, or setting up automated reporting. Triggers on phrases like "support reporting", "operations dashboard", "support KPIs", "team performance report", "executive support report", "support metrics dashboard", "monthly support report", "support analytics", "support scorecard", "operations reporting".

Support Operations Reporting & Dashboards

Design and maintain comprehensive support operations reports and dashboards — transforming raw support data into actionable insights for daily management, weekly reviews, and executive reporting.

Workflow

Define reporting hierarchy: real-time (daily), weekly, monthly, quarterly.
Identify key metrics for each audience (agents, managers, executives).
Build dashboards with automated data pipelines.
Establish reporting cadence and distribution.
Conduct regular review meetings with data-driven action items.
Track metric trends and set improvement targets.
Refine reports based on stakeholder feedback.

Reporting Hierarchy

REPORTING CADENCE AND AUDIENCE
================================

Level 1 — Real-Time Dashboard (Daily, operational):
  Audience: Support agents, team leads
  ════════════════════════════════════════════════════════════════════════
  Metric                          | Current  | Target   | Status
  ════════════════════════════════════════════════════════════════════════
  Tickets in queue                | 45       | < 60     | ✅
  Open tickets (24h+)             | 23       | < 30     | ✅
  Avg response time               | 1.8h     | < 2h     | ✅
  Avg resolution time             | 14.2h    | < 16h    | ✅
  First response SLA breach       | 3%       | < 5%     | ✅
  Resolution SLA breach           | 8%       | < 10%    | ✅
  Tickets resolved today          | 38       | —        | —
  CSAT (today)                    | 4.4/5    | > 4.2    | ✅
  ════════════════════════════════════════════════════════════════════════

Level 2 — Weekly Report (Tactical, team review):
  Audience: Support managers, team leads
  ════════════════════════════════════════════════════════════════════════
  Volume Metrics:
    → Total tickets: 245 (vs 230 last week, +6.5%)
    → Tickets by channel: Email 35%, Chat 25%, Phone 15%, SMS 5%, Other 20%
    → Tickets by priority: P1 8%, P2 25%, P3 45%, P4 22%
  
  Performance Metrics:
    → First response time: 1.6 hours (improved from 1.8h last week)
    → Resolution time: 13.8 hours (improved from 14.2h)
    → First-contact resolution: 62% (target: 65%)
    → Re-contact rate: 18% (target: < 15%)
  
  Quality Metrics:
    → CSAT: 4.3/5.0 (improved from 4.2)
    → CES: 4.1/5.0 (stable)
    → QA score: 84% (improved from 82%)
  
  Agent Performance:
    → Tickets resolved per agent: 31 avg (range: 24–42)
    → Top performer: Sarah K. (42 tickets, 4.6 CSAT)
    → Needs support: Tom R. (24 tickets, 3.8 CSAT) → coaching scheduled
  
  Action Items:
    → Investigate P1 ticket increase (+12% this week)
    → Address re-contact rate (above target)
    → Coach Tom R. on resolution quality

Level 3 — Monthly Report (Strategic, leadership):
  Audience: VP of Support, CS leadership, executive team
  ════════════════════════════════════════════════════════════════════════
  Executive Summary:
    → Ticket volume: 1,050 (vs 1,020 last month, +2.9%)
    → Overall SLA compliance: 94% (target: 95%)
    → CSAT: 4.3/5.0 (+0.1 from last month)
    → Cost per ticket: $7.20 (-$0.30 from last month)
    → Team headcount: 18 agents (0 changes this month)
    → Attrition rate: 0% (0 departures)
  
  Trend Analysis:
    → Volume trend: +2.9% MoM, +15% YoY (aligned with customer growth)
    → CSAT trend: Improving (+0.1 MoM, +0.3 YoY)
    → Resolution time trend: Improving (-0.5h MoM, -2h YoY)
    → Cost per ticket trend: Improving (-$0.30 MoM, -$1.20 YoY)
  
  Challenges:
    → Re-contact rate above target (18% vs 15%)
    → P1 resolution time increasing (investigating root cause)
    → Knowledge base gaps identified (12 articles flagged for creation)
  
  Recommendations:
    → Hire 2 additional agents for Q2 growth
    → Invest in self-service to reduce volume
    → Address top re-contact drivers through agent training

Dashboard Design

SUPPORT DASHBOARD STRUCTURE
=============================

Dashboard 1 — Operations Overview (Executive):
  ════════════════════════════════════════════════════════════════════════
  Row 1: Volume & Capacity
    → Total tickets (month-to-date) | vs last month | vs last year
    → Tickets per day (line chart)
    → Queue depth (current) | vs average
    → Agent utilization rate
  
  Row 2: Service Level Performance
    → First response time (avg, median, 90th percentile)
    → Resolution time (avg, median, 90th percentile)
    → SLA compliance rate (overall + by priority)
    → SLA breach trend (last 30 days)
  
  Row 3: Customer Satisfaction
    → CSAT score (avg, trend, distribution)
    → CES score (avg, trend)
    → NPS score (if collected in support)
    → Deflection rate
  
  Row 4: Cost & Efficiency
    → Cost per ticket (trend)
    → Handle time by channel
    → First-contact resolution rate
    → Re-contact rate
  ════════════════════════════════════════════════════════════════════════

Dashboard 2 — Agent Performance (Manager):
  ════════════════════════════════════════════════════════════════════════
  → Per-agent metrics table:
     Agent | Tickets | Avg Handle | CSAT | QA Score | FCR | Utilization
  → Leaderboard (top 5 performers)
  → At-risk agents (below targets in 2+ categories)
  → Trend charts: Team improvement over time
  → Workload distribution (are all agents equally loaded?)
  ════════════════════════════════════════════════════════════════════════

Dashboard 3 — Channel Analysis:
  ════════════════════════════════════════════════════════════════════════
  → Volume by channel (pie chart + trend)
  → Performance by channel (CSAT, handle time, resolution rate)
  → Cost by channel
  → Channel growth/decline trends
  → Recommended channel investments
  ════════════════════════════════════════════════════════════════════════

Dashboard 4 — Issue Analysis:
  ════════════════════════════════════════════════════════════════════════
  → Top 10 ticket categories (volume)
  → Top 10 ticket categories (handle time)
  → Emerging issues (new categories gaining volume)
  → Resolved issues (categories declining)
  → Root cause distribution
  ════════════════════════════════════════════════════════════════════════

Automated Reporting

AUTOMATED REPORT DISTRIBUTION
===============================

Report Schedule:
  ════════════════════════════════════════════════════════════════════════
  Report                    | Frequency | Recipients           | Delivery
  ════════════════════════════════════════════════════════════════════════
  Daily Operations          | Daily 9 AM | Team leads, managers | Slack + email
  Weekly Performance        | Monday     | Support manager      | Email + dashboard
  Monthly Executive Summary | 1st of month | VP, executives      | Email + PDF
  Quarterly Business Review | Quarterly  | Leadership, board    | Presentation
  Ad-hoc incident report    | As needed  | Management           | Slack + email
  ════════════════════════════════════════════════════════════════════════

Alert Configuration:
  ════════════════════════════════════════════════════════════════════════
  Alert Condition                       | Severity | Action
  ════════════════════════════════════════════════════════════════════════
  Queue exceeds 100 tickets             | High     | Slack alert + SMS to manager
  CSAT drops below 4.0                  | High     | Email to manager + Slack
  SLA breach rate > 15%                 | Critical | Immediate escalation
  Single agent tickets < 15/day         | Medium   | Manager notification
  P1 ticket unresolved > 4 hours        | Critical | Escalation to manager
  Spike in tickets (> 50% vs avg)       | High     | Manager alert + investigation
  ════════════════════════════════════════════════════════════════════════

Integration Points

Help Desk (Zendesk, Freshdesk, Intercom): Primary data source (ticket metrics, CSAT, handle times)
BI Platform (Tableau, Power BI, Looker, Metabase): Dashboard building, data visualization, automated reporting
Data Warehouse (Snowflake, BigQuery, Redshift): Data storage, ETL pipelines, metric computation
Communication (Slack, Teams): Report delivery, alert notifications, daily standup data
Email (SendGrid, Outlook): Scheduled report delivery
CRM (Salesforce, HubSpot): Customer context, account-level support metrics
Survey Tools (Qualtrics, Medallia): CSAT, CES, NPS data
HR Systems: Agent headcount, attrition, performance data
Finance Systems: Cost tracking, budget vs actual

Edge Cases

Data inconsistencies across tools: Help desk shows 1,000 tickets; dashboard shows 980
Root cause: Different counting methods (resolved vs closed, time zones, filters)
Standardize: Define metric definitions clearly; document in data dictionary
Single source: Designate one system as source of truth per metric
Reconciliation: Monthly data audit; investigate and resolve discrepancies
Communication: Tell stakeholders which number to trust and why

Report doesn't drive action: Leadership reads reports but nothing changes
Action items: Every report includes specific recommended actions
Follow-up: Previous month's action items tracked to completion
Meetings: Monthly review meeting focused on decisions, not just data review
Accountability: Assign owners to each action item with deadlines
Escalation: Unresolved issues escalated to leadership

Too many reports causing fatigue: Stakeholders overwhelmed with data
Prioritization: Executive gets 1-page summary; manager gets detailed report
Frequency: Right level of frequency for each audience (not daily for executives)
Self-service: Dashboard available for ad-hoc exploration (not everyone needs scheduled reports)
Feedback: Quarterly survey — "Are these reports useful? What do you need?"
Pruning: Eliminate reports nobody reads

Metric gaming: Agents optimize for metrics, not quality
Multi-metric view: Don't measure just volume; balance with CSAT and QA
Mystery shopping: Periodic quality checks outside normal metrics
Customer feedback: CSAT and CES as counterbalance to agent-driven metrics
Culture: Emphasize "help customers" over "hit numbers"
Manager oversight: Review individual tickets, not just aggregates

Disclaimer: All rights reserved by Circulos AI. These skills are specifically designed for Claude Code, Claude Cowork, Codex, and OpenClaw. When using or referencing any skill, please provide proper attribution to Circulos AI.