2Calls
2.25Avg Score
—Avg Handle Time
0Documented
0Escalated
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.25 | 2 |
| Technical Accuracy | 3.5 | 2 |
| Protocol | 2.0 | 2 |
| Communication | 2.5 | 2 |
Main focus: Incomplete troubleshooting
V2 Rubric (Shadow Grading)
No v2 shadow-grading data available for this week.
Where Did the Time Go
By Product Family
| Family | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Note |
|---|---|---|---|---|---|---|---|
| MX | 1 | — | 2.7 | 4.0 | 2.0 | 3.0 |
By Problem Category
| Category | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Focus? |
|---|---|---|---|---|---|---|---|
| GENERAL INQUIRY | 1 | — | 1.8 | 3.0 | 2.0 | 2.0 | ✓ |
| NO TROUBLESHOOTING NEEDED | 1 | — | 2.7 | 4.0 | 2.0 | 3.0 |
What You Did Well
- Polite customer engagement1 of 2 callsAgent used customer's name and provided correct generic warranty information (three years) across call #LTS00135917.Why this matters: Builds trust and sets professional tone for customer interactions
- Accurate technical guidance1 of 2 callsProvided consistent Linksys app instructions for clearing offline devices with no KB contradictions in call #GI00136126.Why this matters: Delivers correct technical solutions without risking customer confusion
Growth Focus
- Incomplete troubleshooting1 of 2 callsFailed to perform basic troubleshooting (power cycle, LED check) or obtain serial number for warranty verification in call #LTS00135917, leaving issue unresolved.Why this matters: Increases callback risk and prevents accurate warranty assessmentExample: In #LTS00135917, agent confirmed blue LED but did not check firmware status or collect serial number, stating 'Our system doesn't store that information.'What better looks like: Always collect serial number for warranty cases and perform at least power cycle verification before closing
- Abrupt call closure1 of 2 callsEnded call #GI00136126 without verifying action success or providing next steps, despite customer still needing account status verification.Why this matters: Leaves customer without resolution path and increases repeat call likelihoodExample: In #GI00136126, after instructing to 'clear' devices, agent ended call abruptly with 'Okay, ma'am' without confirming resolution.What better looks like: Always verify action success and document next steps before closing unresolved issues
Callback Flags
No callback chains detected.
Documentation Accuracy
No documentation mismatches detected this week.
Practice Plan
- Step 1Always collect device serial number before discussing warranty status on any support callWhy: Prevents inability to verify coverage and reduces repeat calls for warranty validationThis week: #LTS00135917
- Step 2Verify customer confirms resolution before ending calls, especially after technical instructionsWhy: Ensures issue is actually solved and prevents unresolved problems from recurringThis week: #GI00136126
- Step 3Perform at least one basic troubleshooting step (power cycle/LED check) on all reported connectivity issuesWhy: Identifies simple fixes and prevents premature escalation
Escalation Lessons
No escalated case learning this week.
Evidence Calls
| Case | Date | Score | V2 | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00135917 | 2026-07-06 | 2.7 A 4P 2C 3 | — | MX5500 | NO TROUBLESHOOTING NEEDED | Agent will email customer within 24 hours with instructions for warranty verification and next steps. |
| #GI00136126 | 2026-07-07 | 1.8 A 3P 2C 2 | — | GENERAL INQUIRY | None – call ended without resolution or defined next steps. |
Feedback
✓ Feedback submitted — thank you!