Optimize Support Ticket Workflows

This skill provides expertise in designing, implementing, and optimizing support ticket workflows for customer success operations, covering the complete ticket lifecycle from creation through resolution - routing logic, escalation procedures, SLA management, and automation strategies. It works from a ticket classification framework covering a priority matrix (Critical/High/Medium/Low based on impact vs urgency), a category taxonomy (Technical, Billing, Account, Product, Integration), a three-level complexity score (Level 1 FAQ, Level 2 Technical, Level 3 Engineering), and channel integration (Email, Chat, Phone, Self-Service, API).

Use this when designing or auditing a support ticket workflow: routing rules, multi-tier escalation policies, SLA targets by priority and customer tier, automated ticket assignment, or proactive outreach triggers based on customer health signals.

Not needed for handling an individual support ticket in isolation, or for teams without a formal ticketing system where routing, SLA, and escalation logic would actually be configured.

Given a description of a support operation's structure (priority levels, customer tiers, categories, channels), it produces concrete, implementation-ready artifacts: routing rule definitions, escalation matrices, SLA target tables, assignment logic, and quality-metric queries, illustrated with runnable examples across YAML, JSON, Python, JavaScript, and SQL.

routing_rules:
  - condition: "priority == 'critical' AND category == 'technical'"
    action: "assign_to_senior_engineer"
    notify: "manager_escalation"
    sla_target: "15_minutes"
  
  - condition: "customer_tier == 'enterprise' AND business_hours == true"
    action: "assign_to_dedicated_csm"
    sla_target: "1_hour"
  
  - condition: "category == 'billing' AND amount > 10000"
    action: "assign_to_billing_specialist"
    cc: "account_manager"
    sla_target: "4_hours"

Response-time targets are defined per priority/tier pair (critical+enterprise: 15-minute first response, 240-minute resolution; critical+professional: 30/480; high+enterprise: 60/480; high+professional: 120/720; medium: 240/1440; low: 480/2880), with an SLA breach-risk calculation and automated breach warnings at 50%, 75%, and 90% of target time. Automation covers smart ticket assignment (skill-based routing, customer-history-aware priority boosting, workload balancing), auto-responses, knowledge-base article suggestions, duplicate-ticket detection, and sentiment analysis to flag negative sentiment for priority handling. A proactive outreach trigger evaluates customer health signals - usage decline, error spikes, low feature adoption, upcoming contract renewal - and opens a health-check ticket when two or more risk factors are present. Continuous improvement runs through weekly ticket retrospectives, post-resolution customer feedback loops, converting frequent issues into self-service knowledge-base articles, and A/B testing workflow variations.

Customer success and support operations leads designing or refining ticket routing, escalation, and SLA policies, and engineers building the automation - assignment logic, breach-risk scoring, proactive outreach - that enforces those policies.