2Calls
2.60Avg Score
—Avg Handle Time
2Documented
0Escalated
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.6 | 2 |
| Technical Accuracy | 3.0 | 2 |
| Protocol | 2.5 | 2 |
| Communication | 2.5 | 2 |
Main focus: Inaccurate 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 | — | 2.8 | 2.0 | 3.0 | 3.0 | |
| WHW | 1 | — | 2.4 | 4.0 | 2.0 | 2.0 |
By Problem Category
| Category | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Focus? |
|---|---|---|---|---|---|---|---|
| SETUP | 1 | — | 2.8 | 2.0 | 3.0 | 3.0 | |
| CONNECTIVITY | 1 | — | 2.4 | 4.0 | 2.0 | 2.0 | ✓ |
What You Did Well
- Correct mesh pairing procedure1 of 2 callsCorrectly used the 5-press method for pairing the child node on an MX5500, which is valid per KB documentation, ensuring proper mesh setup.Why this matters: Ensures customer can successfully complete mesh configuration without further issues.
- Effective information gathering1 of 2 callsCollected essential product information (model, serial, email) and guided the customer through web UI and network diagnostics (ping), establishing a foundation for troubleshooting.Why this matters: Helps identify issues faster and reduces repeat questions.
Growth Focus
- Inaccurate technical guidance1 of 2 callsProvided wrong router IP address and conflicting password policies for MX5500, which could prevent customers from accessing the device or configuring it correctly. Occurred in 1 of 2 calls (#LTS00134380).Why this matters: Leads to customer frustration, potential security risks, and repeat calls.Example: Told customer the router IP was [REDACTED_PHONE] and that passwords needed 10 characters with uppercase and special characters, contradicting MX5500 specifications.What better looks like: Verify correct IP address in KB before stating it; clearly state password requirements as 8+ characters with optional special characters for MX5500.
- Inefficient call control1 of 2 callsExcessive repetition and lack of concise next-step plan led to prolonged call and unresolved issue in WHW03 connectivity case (#LTS00134917).Why this matters: Wastes customer and agent time, risks unresolved issues, and may lead to callbacks.Example: Repeatedly asked for confirmations and ended call without confirming fix, recommending replacement without verification.What better looks like: Summarize steps clearly, confirm fix before closing, and provide explicit next steps if issue persists.
Callback Flags
No callback chains detected.
Documentation Accuracy
No documentation mismatches detected this week.
Practice Plan
- Step 1Before providing any router IP address, verify it against the official KB for the specific model to ensure accuracy.Why: Preventing access issues and customer confusion.This week: #LTS00134380
- Step 2When explaining password requirements, state the exact criteria from the device documentation (e.g., 'MX5500 requires 8+ characters, no special characters needed') and confirm understanding.Why: Avoids misconfiguration and security risks.This week: #LTS00134380
- Step 3After performing troubleshooting steps, summarize the outcome clearly and confirm resolution with the customer before closing the call.Why: Ensures issues are truly resolved and reduces callbacks.This week: #LTS00134917
Escalation Lessons
No escalated case learning this week.
Evidence Calls
| Case | Date | Score | V2 | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00134380 | 2026-06-23 | 2.8 A 2P 3C 3 | — | MX5500 | SETUP | Mesh network fully set up, internet confirmed, both nodes visible in app. |
| #LTS00134917 | 2026-06-26 | 2.4 A 4P 2C 2 | — | WHW03 | CONNECTIVITY | Factory reset the Linksys router and re‑configure; if issue persists, consider replacement. |