--- name: helpdesk-ticketing description: Manage helpdesk operations including ticket creation, prioritization, routing, resolution tracking, SLA management, and customer communication. Use when setting up helpdesk workflows, managing ticket queues, tracking SLA performance, handling escalations, or optimizing ticket resolution. Triggers on phrases like "helpdesk", "ticket management", "ticket routing", "SLA tracking", "first call resolution", "ticket escalation", "knowledge base", "self-service". --- # Helpdesk & Ticketing Operations Deliver efficient customer support through structured ticketing workflows and SLA-driven resolution processes. ## Workflow ### 1. Ticket Intake & Creation 1. **Multi-channel intake**: - Web portal: structured form submission with category and priority selection - Email: auto-convert emails to tickets via email parsing - Phone: agent-created tickets with call notes and recordings - Chat: live chat conversion to tickets for follow-up - Social media: social channel monitoring and ticket creation - API integration: automated ticket creation from monitoring systems 2. **Ticket information capture**: - Required fields: subject, description, category, requested priority - Auto-enrichment: customer data, account tier, contract status, history - Attachments and screenshots capture - Initial triage: product/service, environment, urgency indicators - Spam and duplicate detection 3. **Duplicate and related ticket detection**: - Subject and description similarity matching - Same issue across multiple customers (outage detection) - Merge related tickets under master ticket - Notify affected customers of master ticket status - Track duplicate rate as quality metric ### 2. Ticket Classification & Prioritization 1. **Category and subcategory assignment**: - Automated category assignment based on keywords and customer input - Agent override for miscategorized tickets - Category hierarchy: IT → Hardware → Laptop; Sales → Order → Billing - Category analytics for resource planning and knowledge gaps - Regular category structure review and optimization 2. **Priority and severity assignment**: - Auto-prioritization based on: customer tier, SLA, issue impact - Severity matrix: impact × urgency → P1 through P4 - P1: critical business impact, immediate response required - P2: significant impact, workaround not available - P3: moderate impact, workaround available - P4: low impact, informational request 3. **SLA assignment and tracking**: - SLA targets by priority level and customer tier - First response time SLA (e.g., P1: 15 min, P2: 1 hour, P3: 4 hours, P4: 24 hours) - Resolution time SLA (e.g., P1: 4 hours, P2: 8 hours, P3: 24 hours, P4: 72 hours) - SLA pause conditions: awaiting customer, awaiting vendor, blocked by dependency - SLA breach alerts and escalation ### 3. Ticket Routing & Assignment 1. **Routing strategy**: - Skill-based routing: assign to agents with relevant expertise - Round-robin: distribute evenly within skill group - Load-balanced: consider current queue and agent workload - VIP/enterprise customers: dedicated routing to senior agents - Geographic routing for language/timezone alignment 2. **Automated assignment rules**: - Category → team mapping (hardware → IT ops, billing → finance team) - Keyword-based routing (product name, error message, technical term) - Customer account tier routing (enterprise → premium support) - Escalation path definition (L1 → L2 → L3 → engineering/vendor) - Auto-assignment with agent override capability 3. **Queue management**: - Separate queues by category, priority, and team - Queue capacity monitoring and alerting - Overflow routing when primary queue overwhelmed - Priority queue jumping for P1 tickets - Cross-team queue sharing for capacity balancing ### 4. Ticket Resolution & Fulfillment 1. **Resolution process**: - Knowledge base lookup before resolution attempt - Standard operating procedures (SOP) execution - Customer communication at each significant step - Internal collaboration (agent notes vs customer-visible comments) - Resolution verification with customer 2. **First Contact Resolution (FCR)**: - Track FCR rate by agent, team, and category - Empower agents with resolution authority (refund thresholds, replacements) - Quick resolution tools and templates - FCR training and coaching - Target: >70% FCR rate 3. **Escalation management**: - Escalation triggers: SLA breach, customer request, technical complexity, agent discretion - Formal escalation process with notification to both levels - Escalation justification documentation - Escalation callback time commitment (within 30 minutes) - Escalation resolution and root cause tracking 4. **Customer communication standards**: - Acknowledge receipt within SLA timeframe - Provide regular status updates (minimum every 4 hours for P1/P2) - Use clear, non-technical language - Set expectations for next update timing - Resolution confirmation and satisfaction survey trigger ### 5. Post-Resolution & Continuous Improvement 1. **Ticket closure and feedback**: - Customer satisfaction survey (CSAT) upon resolution - Net Promoter Score (NPS) periodic survey - Resolution confirmation and feedback invitation - Reopen process if issue recurs within 7 days - Closure reason coding for analysis 2. **Knowledge management**: - Resolution documentation in knowledge base - Public KB articles from common resolutions - Internal KB for complex technical resolutions - KB article rating and effectiveness tracking - Regular KB review and content refresh 3. **Performance measurement**: - Volume metrics: tickets by category, priority, source - Efficiency metrics: handle time, resolution time, FCR rate - Quality metrics: CSAT, NPS, SLA compliance, first contact quality - Agent metrics: productivity, quality scores, customer feedback - Trend analysis: volume trends, category shifts, seasonal patterns ## Templates & Frameworks ### Ticket Priority Matrix ``` TICKET PRIORITY MATRIX ======================= IMPACT → | Minor (1 user) | Moderate (team) | Major (department) | Critical (organization) | | | | Urgency ↓| | | | Immediate| P2 | P1 | P1 | P1 High | P3 | P2 | P1 | P1 Medium | P4 | P3 | P2 | P2 Low | P4 | P4 | P3 | P3 SLA TARGETS: P1: First response 15 min | Resolution 4 hours P2: First response 1 hour | Resolution 8 hours P3: First response 4 hours | Resolution 24 hours P4: First response 24 hours | Resolution 72 hours ESCALATION THRESHOLDS: P1: Auto-escalate at 30 min (response) / 2 hours (resolution) P2: Auto-escalate at 2 hours (response) / 4 hours (resolution) P3: Auto-escalate at 8 hours (response) / 12 hours (resolution) P4: Auto-escalate at 48 hours (response) / 5 days (resolution) ``` ### Helpdesk Performance Report ``` HELPDESK PERFORMANCE — April 2025 =================================== VOLUME METRICS: Total tickets: 2,347 By channel: Portal: 1,234 (53%), Email: 612 (26%), Phone: 347 (15%), Chat: 154 (7%) By priority: P1: 23 (1%), P2: 94 (4%), P3: 563 (24%), P4: 1,667 (71%) By status: Resolved: 2,134 (91%), Open: 156 (7%), Escalated: 42 (2%) EFFICIENCY METRICS: Avg first response time: 1.8 hours (target: <2 hours ✓) Avg resolution time: 14.2 hours (target: <16 hours ✓) First Contact Resolution: 68% (target: >65% ✓) Tickets per agent/day: 24.7 SLA compliance: 94.3% (target: >90% ✓) QUALITY METRICS: CSAT score: 4.4/5.0 (target: >4.0 ✓) NPS: 52 (target: >40 ✓) Reopen rate: 3.2% (target: <5% ✓) Escalation rate: 8.7% (target: <10% ✓) TOP CATEGORIES: 1. Account Access: 423 tickets (18%) 2. Technical Issues: 389 tickets (17%) 3. Billing/Invoicing: 298 tickets (13%) 4. Product Questions: 267 tickets (11%) 5. Feature Requests: 198 tickets (8%) KNOWLEDGE BASE IMPACT: KB articles published: 23 new KB-assisted resolutions: 34% of total Self-service resolution rate: 28% ``` ## Integration Points - ITSM platforms (ServiceNow, Zendesk, Freshservice, Jira Service Management): Ticket management - CRM platforms (Salesforce, HubSpot): Customer data enrichment, account context - Knowledge base platforms (Confluence, Guru, Document360): Resolution guidance - Monitoring systems: Automated ticket creation from alerts - Communication tools (Slack, Teams): Agent collaboration and customer communication - VoIP/telephony (Twilio, RingCentral): Phone integration, call recording - Chat platforms (Intercom, LiveChat): Live chat integration - Survey tools (Qualtrics, Medallia): CSAT and NPS collection - BI/reporting tools (Tableau, Power BI): Performance analytics ## Edge Cases - **Ticket volume surge** (outage, product launch, holiday): Activate surge staffing; implement automated acknowledgments; triage and batch similar tickets; extend SLAs with customer communication - **Multi-language support**: Language detection and routing; multilingual agent team; translation tools for initial triage; multilingual knowledge base - **VIP/enterprise customer escalation**: Dedicated VIP queue; named account manager as point of contact; premium SLA; executive escalation path - **Cross-team dependency resolution**: Dependency tracking between tickets; regular coordination meetings; shared resolution timelines; unified customer communication - **Recurring ticket patterns**: Trigger problem management investigation; create permanent fix; update knowledge base; monitor resolution effectiveness ## Output ### Helpdesk Operations Dashboard ``` HELPDESK OPS — Real-Time ========================== CURRENT QUEUE: Open tickets: 198 P1 (critical): 2 🔴 P2 (high): 8 ⚠ P3 (medium): 47 P4 (low): 141 AGENT STATUS: Active agents: 23/28 On call: 18 In meeting/training: 5 On break: 2 Offline: 3 SLA STATUS: At risk (< 25% time remaining): 7 tickets Breached (last 24h): 3 tickets SLA compliance rate: 96.1% Avg time in queue: 22 minutes TODAY'S PERFORMANCE: Tickets resolved: 187 Avg resolution time: 12.4 hours FCR rate: 71% CSAT (today): 4.5/5.0 Escalations: 4 KNOWLEDGE BASE: KB-assisted resolutions today: 67 (36%) Top referenced articles: Access Reset, Password Policy, Billing FAQ Articles needing update: 3 TREND ALERTS: ⚠ Ticket volume 23% above average — investigating root cause ⚠ Category "Login Issues" spike — possible system issue ✓ SLA compliance trending up (94% → 96%) ```