The scoreboard, honestly: the hard targets, how often each one is actually looked at,
and the quiet human signals that never make it onto a dashboard.
First Contact Resolution (FCR)
The percentage of support tickets you resolve on the very first interaction with the user, without needing to escalate or follow up multiple times.
Target · >70% for common issuesIf you resolve 7 out of 10 'headset won't turn on' tickets during the initial call or chat, you're hitting the target. This shows you're efficient and knowledgeable.
Ticket Resolution Time (L1/L2)
The average time it takes you to resolve a support ticket from when it's opened to when it's closed, specifically for issues within your L1/L2 scope.
Target · <4 hours for L1, <8 hours for L2A user reports 'losing tracking' at 9 AM, and you've diagnosed it as a poor environment, guided them to a better spot, and closed the ticket by 1 PM. That's a 4-hour resolution.
Device Uptime & Availability
The percentage of assigned AR/VR devices (e.g., a pool of 20 headsets) that are fully functional and ready for use at any given time.
Target · Maintain 98% operational readiness for your assigned device poolIf you're responsible for 50 headsets, and only one is offline for maintenance or repair, you're at 98% uptime. This means proactive maintenance, not just reactive fixes.
Knowledge Base Contribution
The number of new or updated knowledge base articles you contribute, helping other users or junior technicians solve problems themselves.
Target · Author/update ≥2 high-impact articles per quarterYou notice a recurring issue with 'IPD mismatch' and create a clear, step-by-step guide with screenshots on how to adjust it. That's a valuable contribution.
User Satisfaction & Feedback
How happy our users are with your support, measured through post-resolution surveys and direct feedback. We're looking for comments that highlight your patience and clear communication.
- High scores on CSAT surveys (e.g., 4.5/5 average). Positive comments like 'The technician was incredibly patient and explained everything clearly,' or 'They fixed it quickly and made me feel heard.' We want to see users feeling genuinely helped, not just 'fixed'.
Proactive Issue Identification
Your ability to spot recurring problems or potential future issues before they become widespread, and then suggest ways to prevent them.
- You flag that 10% of Quest 3s from a specific batch are experiencing battery drain, even before a major wave of tickets comes in. You might propose a firmware rollback or a specific charging protocol to your Senior Technician. It's about thinking ahead, not just reacting.
Documentation Quality
The clarity, accuracy, and completeness of your ticket notes and any internal documentation you create. This helps everyone, including future you!
- Ticket notes are detailed enough that another technician could pick up the issue without asking you questions. Your troubleshooting steps are logical and easy to follow. We're looking for precision, not just volume.
Team Collaboration & Contribution
How well you work with the wider support team and other departments, sharing knowledge and helping out where needed.
- You regularly participate in team stand-ups, offering insights from your solved tickets. You're happy to help a junior colleague with a tricky problem. Other teams (like IT or Dev) give positive feedback about your interactions.