1Calls
1.10Avg Score
—Avg Handle Time
1Documented
0Escalated
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 1.1 | 1 |
| Technical Accuracy | 1.0 | 1 |
| Protocol | 2.0 | 1 |
| Communication | 1.0 | 1 |
Main focus: Incorrect technical guidance
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 | — | 1.1 | 1.0 | 2.0 | 1.0 |
By Problem Category
| Category | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Focus? |
|---|---|---|---|---|---|---|---|
| SETUP | 1 | — | 1.1 | 1.0 | 2.0 | 1.0 | ✓ |
What You Did Well
- Accurate device identification1 of 1 callsCollected the correct model number (MX-5500) and serial number from the customer ([01:00]).Why this matters: Ensures accurate troubleshooting and support processing
- Initial setup guidance1 of 1 callsAttempted to guide the customer through initial node placement and LED observation.Why this matters: Provides structured first-step support for new installations
Growth Focus
- Incorrect technical guidance1 of 1 callsAdvised using the 5-press method as a node-addition step ([08:00], [17:00]), which is an escalation procedure, not a pairing method (per universal_5press_models.md). Incorrectly stated the router admin password can be used to log into the Linksys app ([04:00]); the app uses a separate cloud account.Why this matters: Led to customer confusion, potential incorrect setup attempts, and wasted time on invalid credentialsExample: In call #LTS00074243, agent instructed customer to perform 5-press reset during node addition and told them to use router password for app loginWhat better looks like: Use 5-press reset only for factory resets or escalation procedures; clarify that Linksys app requires a separate cloud account
- Unverified closure1 of 1 callsDeclared the setup complete ([24:00]) without verifying the new node was successfully added or functioning.Why this matters: Risk of unresolved issues leading to callbacks or repeated support contactsExample: In call #LTS00074243, agent ended the call with 'setup complete' without confirming node functionalityWhat better looks like: Verify node addition success through customer confirmation of LED states or network connectivity before closing
Callback Flags
No callback chains detected.
Documentation Accuracy
No documentation mismatches detected this week.
Practice Plan
- Step 1Before closing any call where the issue is not confirmed fixed, ask the customer to test the fix on the call and confirm it works.Why: Prevents unresolved issues that lead to callbacks and repeated support contactsThis week: #LTS00074243
- Step 2Only use the 5-press reset method for factory resets or escalation procedures, never as a standard node-addition step.Why: Avoids providing incorrect technical guidance that can break customer setupsThis week: #LTS00074243
- Step 3Clarify that the Linksys app requires a separate cloud account, not the router admin password, for login.Why: Prevents customer login failures and wasted time on invalid credentialsThis week: #LTS00074243
Escalation Lessons
No escalated case learning this week.
Evidence Calls
| Case | Date | Score | V2 | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00074243 | 2026-06-17 | 1.1 A 1P 2C 1 | — | MX5500 | SETUP | Customer left to test setup independently; no further action or follow-up scheduled by agent. |