3Calls
1.87Avg Score
29m 18sAvg Handle Time
3Documented
1Escalated
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 1.87 | 3 |
| Technical Accuracy | 2.67 | 3 |
| Protocol | 1.0 | 3 |
| Communication | 1.33 | 3 |
Main focus: Device Information Collection
V2 Rubric (Shadow Grading)
V2 overall: 59.78% across 2 v2-scored calls this week
| Category | Week Average |
|---|---|
| Resolution | 2.81 |
| Technical Accuracy | 2.5 |
| Communication | 3.12 |
| Customer Ownership | 3.57 |
| Escalation Judgment | 5.0 |
| Customer Experience | 1.61 |
- Successful Resolution: 1
- Unresolved: 1
Where Did the Time Go
By Product Family
| Family | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Note |
|---|---|---|---|---|---|---|---|
| MX | 1 | 51m 34s | 2.8 | 2.0 | 1.0 | 2.0 | Outlier: 1.8x weekly median handle time |
| RE | 1 | 7m 01s | 1.8 | 5.0 | 1.0 | 1.0 | |
| E | 1 | — | 1.0 | 1.0 | 1.0 | 1.0 |
By Problem Category
| Category | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Focus? |
|---|---|---|---|---|---|---|---|
| ACCESS | 1 | — | 1.0 | 1.0 | 1.0 | 1.0 | ✓ |
| CONNECTIVITY | 1 | 51m 34s | 2.8 | 2.0 | 1.0 | 2.0 | |
| SETUP | 1 | 7m 01s | 1.8 | 5.0 | 1.0 | 1.0 | ✓ |
What You Did Well
- Technical Resolution Success1 of 3 callsSuccessfully restored Wi-Fi connectivity on both a Windows 10 PC and Roku Stick using KB-aligned methods, confirming resolution via YouTube and Netflix access.Why this matters: Ensures customers can immediately resume essential internet use, reducing repeat calls and improving satisfaction.
- Escalation Coordination1 of 3 callsCorrectly identified the case had been escalated to Level 2 and attempted to connect the customer with the assigned technician, maintaining case continuity.Why this matters: Prevents case duplication and ensures seamless handoff to specialists, improving resolution efficiency.
Growth Focus
- Device Information Collection3 of 3 callsFailed to collect critical device details (model, serial number) in 3 of 3 calls, violating protocol and impeding warranty validation and troubleshooting.Why this matters: Missing device data delays resolution, prevents warranty claims, and forces repeat calls when details are later required.Example: In #LTS00116112, the agent did not obtain the router model despite the customer mentioning 'Elop WR occasional', leading to unsupported LED interpretation.What better looks like: Always confirm and document product model and serial number within the first 30 seconds of the call, using KB-guided questions.
- Technical Instruction Accuracy2 of 3 callsProvided incorrect reset instructions ('hold reset button until solid blue') contradicting KB guidance, and omitted key troubleshooting steps like WAN cable checks.Why this matters: Incorrect guidance leads to failed resolutions, customer frustration, and potential misdiagnosis of hardware issues.Example: In #LTS00133667, the agent instructed 'hold reset button until solid blue' instead of the KB-specified 15-second factory reset, causing unnecessary repetition.What better looks like: Follow KB reset procedures exactly (e.g., 15-second hold for factory reset) and verify WAN cable status before node resets.
Callback Flags
No callback chains detected.
Documentation Accuracy
No documentation mismatches detected this week.
Practice Plan
- Step 1Always confirm and document product model and serial number within the first 30 seconds of every call.Why: Missing device data prevents proper troubleshooting, warranty validation, and efficient escalation.This week: #LTS00116112
- Step 2Follow KB reset procedures exactly, using specified hold times (e.g., 15 seconds for factory reset) instead of visual cues like 'solid blue'.Why: Incorrect instructions cause failed resolutions and repeat calls.This week: #LTS00133667
- Step 3When escalating, verify prior case details, update notes with all troubleshooting performed, and confirm next steps with the customer.Why: Prevents case duplication and ensures continuity for Level 2 support.This week: #TE00134119
Escalation Lessons
#TE00134119 — RE6400
Status: pending_with_level_2_or_followup · Category: SETUP
What happened on the call: Awaiting callback from Level 2 technician (currently on break).
Why it escalated: L1 determined issue required Level 2 intervention due to unresolved warranty setup and customer frustration after prior unsuccessful handling.
What L2 did:
- Reviewed ticket and determined need for callback due to customer unavailability during storm.
- Endorsed ticket for prioritization on Monday at 10:00 AM Eastern Time.
- Contacted customer to schedule callback and confirm device readiness.
L1 learning points:
- Always collect serial number and verify warranty status before escalation.
- Document all customer-provided troubleshooting steps and outcomes in HappyFox.
- When Level 2 is unavailable, provide clear callback expectations and alternative support paths.
Evidence Calls
| Case | Date | Score | V2 | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00116112 | 2026-06-17 | 1 A 1P 1C 1 | — | E5350 | ACCESS | Ticket opened; customer instructed to call back for 'damage test'. |
| #LTS00133667INBOUND | 2026-06-17 | 2.8 A 2P 1C 2 | 91.9% Meets / Exceeds | MX2000 | CONNECTIVITY | Internet access restored on PC and Roku; customer advised to reconnect other devices using same Wi-Fi credentials and avoid unnecessary resets. |
| #TE00134119INBOUND | 2026-06-19 | 1.8 A 5P 1C 1 | 27.7% Needs Improvement | RE6400 | SETUP | Awaiting callback from Level 2 technician (currently on break). |