29Calls
2.31Avg Score
19m 26sAvg Handle Time
25Documented
1Escalated
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.31 | 29 |
| Technical Accuracy | 2.52 | 29 |
| Protocol | 1.83 | 29 |
| Communication | 2.45 | 29 |
Main focus: Inconsistent Troubleshooting
V2 Rubric (Shadow Grading)
V2 overall: 35.26% across 27 v2-scored calls this week3 auto-zeros
| Category | Week Average |
|---|---|
| Resolution | 1.28 |
| Technical Accuracy | 1.45 |
| Communication | 2.55 |
| Customer Ownership | 2.35 |
| Escalation Judgment | 1.67 |
| Customer Experience | 1.92 |
- Unresolved: 18
- Partial Resolution: 4
- Successful Resolution: 4
- Appropriate Escalation: 1
Where Did the Time Go
By Product Family
| Family | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Note |
|---|---|---|---|---|---|---|---|
| WHW | 6 | 28m 42s | 2.37 | 2.83 | 1.67 | 2.5 | Outlier: 2.1x weekly median handle time |
| MX | 9 | 22m 11s | 2.18 | 2.44 | 2.0 | 2.67 | Outlier: 1.6x weekly median handle time |
| MR | 3 | 20m 05s | 2.3 | 2.0 | 1.33 | 2.33 | |
| RE | 2 | 13m 50s | 2.2 | 2.5 | 2.0 | 2.5 | |
| OTHER | 1 | 11m 41s | 1.4 | 1.0 | 1.0 | 3.0 | |
| E | 2 | 10m 54s | 2.8 | 3.0 | 2.5 | 2.5 | |
| EA | 5 | 10m 12s | 2.44 | 2.2 | 1.6 | 1.8 |
By Problem Category
| Category | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Focus? |
|---|---|---|---|---|---|---|---|
| CONNECTIVITY | 12 | — | 2.3 | 2.1 | 1.8 | 2.2 | ✓ |
| SETUP | 8 | — | 2.7 | 2.4 | 2.1 | 2.5 | |
| NO TROUBLESHOOTING NEEDED | 3 | — | 2.1 | 1.7 | 1.3 | 2.0 | ✓ |
What You Did Well
- Accurate Device Identification12 of 25 callsCorrectly identified E7350 as end-of-life and out of warranty per KB guidance across multiple calls (e.g., #LTS00135135, #LTS00135139).Why this matters: Ensures customers receive appropriate support options and avoids misinformation about warranty coverage.
- Clear Paid Support Communication8 of 25 callsClearly communicated paid Connect service options without coercion when devices were out of warranty (e.g., #LTS00135165, #LTS00135310).Why this matters: Maintains transparency and helps customers make informed decisions about support.
Growth Focus
- Inconsistent Troubleshooting9 of 25 callsFailed to perform basic diagnostics (power cycle, LED check, modem test) before concluding issues were hardware-related, leading to unresolved cases (e.g., #LTS00135135, #LTS00135194).Why this matters: Increases risk of repeat calls and customer frustration due to unresolved issues.Example: In #LTS00135135, no troubleshooting was performed despite Wi-Fi outage; only a paid service email was offered.What better looks like: Always perform power cycle, check LED status, and test with Ethernet cable before concluding hardware failure.
- Miscommunication of Policies5 of 25 callsIncorrectly stated that out-of-warranty devices receive no free support, contradicting KB which allows basic triage (e.g., #LTS00135139, #LTS00135194).Why this matters: Violates Linksys policy and risks customer trust and compliance issues.Example: In #LTS00135139, claimed 'no free support for out-of-warranty devices' despite KB requiring basic troubleshooting.What better looks like: Always offer basic triage and self-help resources for out-of-warranty devices per universal_escalation_guide.md.
Callback Flags
No callback chains detected.
Documentation Accuracy
#LTS00135209HIGH
Grader saw: Agent incorrectly advised that the dim LED is normal and told customer to monitor the device. No actual resolution or valid next step provided.
Agent documented: **Issue Description: ** LED Changed **Model Number**: **Serial Number:** 41P410M13849101 **Warranty Start Date: ** Apr 14, 2026 **Notes:** Calling about the Linksys extender that he bought, it's two months old LED changed from a solid blue it turned dim Educated customer and advised it’s fine As long as there is no issues with the connectivity Customer acknowledged EOC
Grader marked issue unresolved due to no validation, while documentation claims 'EOC' (End of Call) with no resolution steps.
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 and reduces repeat calls due to incomplete problem resolution.
- Step 2Always verify WAN connectivity and perform a power cycle before concluding a device is faulty.Why: Skips critical diagnostics and leads to incorrect hardware failure conclusions.This week: #LTS00135135
- Step 3Review and memorize KB policies for out-of-warranty device support to avoid miscommunication.Why: Ensures compliance with Linksys policy and maintains customer trust.This week: #LTS00135139
Escalation Lessons
#TE00135683 — MX6200
Status: resolved · Category: CONNECTIVITY
What happened on the call: Escalated to Level‑2 technical support for further investigation.
Why it escalated: Customer reported MX6200 with no internet; L1 agent performed incorrect 5-press attempts and provided invalid URLs.
What L2 did:
- Verified WAN connectivity via direct PC test
- Corrected LED state interpretation (solid blue = online)
- Provided accurate access URL (myrouter.local)
- Escalated for advanced WAN diagnostics
L1 learning points:
- Always verify WAN connectivity before assuming hardware failure
- MX6200 uses myrouter.local, not myrouter.info
- Solid blue LED indicates online/healthy state per KB
Evidence Calls
| Case | Date | Score | V2 | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00135135INBOUND | 2026-06-29 | 2.8 A 4P 3C 2 | 26.4% Needs Improvement | E7350 | CONNECTIVITY | Advise factory reset and reconfiguration; offer to email user guide; inform of paid support option. |
| #LTS00135139INBOUND | 2026-06-29 | 2.8 A 2P 1C 2 | 12.5% Needs Improvement | MR20EC | CONNECTIVITY | Offered paid support; customer declined. No further action taken. |
| #LTS00135165INBOUND | 2026-06-29 | 2.8 A 3P 1C 2 | 0.0% Needs Improvement | EA7200 | CONNECTIVITY | Offered paid Connect service ($15) and suggested purchasing a new router from Amazon, Best Buy, or Linksys. No technical fix provided. |
| #LTS00135194INBOUND | 2026-06-29 | 1.3 A 1P 1C 2 | 3.8% Needs Improvement | MR20EC | NO TROUBLESHOOTING NEEDED | No resolution achieved. Customer was given incorrect information and no actionable next steps. |
| #LTS00135209INBOUND | 2026-06-29 | 1.1 A 1P 1C 2 | 0.0% Needs Improvement | RE7350 | NO TROUBLESHOOTING NEEDED | Agent incorrectly advised that the dim LED is normal and told customer to monitor the device. No actual resolution or valid next step provided. |
| #LTS00135310INBOUND | 2026-06-30 | 3 A 4P 2C 4 | 34.4% Needs Improvement | WHW01 | SETUP | Agent will email step-by-step troubleshooting instructions and offered $15 paid-support if needed. |
| #GI00135335INBOUND | 2026-06-30 | 2.8 A 5P 3C 3 | 21.2% Needs Improvement | GENERAL INQUIRY | Customer will call back with serial number; no technical solution was implemented during this call. | |
| #LTS00135340INBOUND | 2026-06-30 | 1.8 A 1P 1C 2 | 42.5% Needs Improvement | WHW01 | SETUP | Agent provided reset instructions and offered paid support but no confirmed fix; customer advised to retry setup and may call back. |
| #LTS00135360INBOUND | 2026-06-30 | 1.3 A 1P 1C 2 | 3.8% Needs Improvement | MX6200 | CONFIGURATION | No resolution achieved. Further troubleshooting required: verify modem status, reboot modem, check WAN IP, run speed test at modem, and consider escalation if issue persists. |
| #LTS00135360INBOUND | 2026-06-30 | 4 A 5P 4C 3 | 68.4% Needs Improvement | MX6200 | CONFIGURATION | Guest network SSID now visible on phone; issue resolved. |
| #LTS00135488INBOUND | 2026-07-01 | 2.8 A 2P 2C 3 | 94.2% Meets / Exceeds | MX4200 | CONNECTIVITY | Node re-paired and functioning (solid blue). No further steps required. |
| #LTS00135506INBOUND | 2026-07-01 | 2.6 A 4P 3C 4 | 54.9% Needs Improvement | MX2000 | SETUP | Agent incorrectly assumed the Wi-Fi was extended and closed the call without confirming functionality or providing further steps. |
| #LTS00135511INBOUND | 2026-07-01 | 2.8 A 4P 2C 3 | 7.5% Needs Improvement | WHW03 | CONNECTIVITY | Agent will send an email with information; no technical fix was applied. |
| #LTS00135522INBOUND | 2026-07-01 | 2.8 A 1P 2C 2 | 40.4% Needs Improvement | EA7300 | CONNECTIVITY | Agent offered to email generic troubleshooting steps and suggested using the Linksys AI chat; customer accepted the email option. |
| #LTS00135528INBOUND | 2026-07-01 | 2.8 A 1P 2C 2 | 21.5% Needs Improvement | EA6350 | CONNECTIVITY | Suggested upgrading to a newer router; no configuration or troubleshooting steps were completed. |
| #LTS00135541INBOUND | 2026-07-01 | 3.3 A 4P 3C 3 | 63.3% Needs Improvement | RE6300 | SETUP | Agent will email the RE6300 V2 user guide and instructed the customer to reset the extender and use WPS or LAN-cable setup. |
| #LTS00135660INBOUND | 2026-07-02 | 1.4 A 1P 1C 3 | 64.8% Needs Improvement | VLP01 | CONNECTIVITY | Agent recommended purchasing a new router and will email the user guide for a reset. |
| #LTS00131580INBOUND | 2026-07-02 | 2.8 A 4P 1C 3 | 19.2% Needs Improvement | WHW01 | CONNECTIVITY | Customer to verify ISP service and, if needed, contact ISP; agent will email the router user guide; paid-support option offered. |
| #TE00135683INBOUND | 2026-07-02 | 1.8 A 1P 2C 3 | 55.1% Needs Improvement | MX6200 | CONNECTIVITY | Escalated to Level‑2 technical support for further investigation. |
| #LTS00113665INBOUND | 2026-07-02 | 2.8 A 3P 3C 2 | 84.3% Developing | WHW03 | SETUP | Router re‑configured and online; no further action needed. |
| #LTS00094640 | 2026-07-03 | 1.8 A 4P 1C 1 | — | EA8300 | CONNECTIVITY | Agent promised to send an email later; no resolution or concrete next steps provided. |
| #LTS00135793INBOUND | 2026-07-03 | 2 A 2P 2C 2 | 2.4% Needs Improvement | EA9500 | CONNECTIVITY | Suggested customer consider purchasing a new router; no technical troubleshooting or self-help guidance provided. |
| #LTS00135805INBOUND | 2026-07-03 | 1 A 1P 1C 1 | 0.0% Needs Improvement | WHW03 | SETUP | Offered paid PayConnect support; no troubleshooting performed. Call ended without clear next steps. |
| #LTS00135810INBOUND | 2026-07-03 | 2.4 A 3P 3C 2 | 47.6% Needs Improvement | MX6200 | SETUP | Wait up to 24 hours for the nodes to fully join; then re-check the app. If still missing, reopen case. |
| #LTS00135810OUTBOUND | 2026-07-03 | 1.1 A 1P 1C 2 | 3.8% Needs Improvement | MX6200 | SETUP | No valid resolution provided. Customer left with nodes offline and no actionable next steps. |
| #LTS00135810OUTBOUND | 2026-07-03 | 1.8 A 1P 1C 2 | 73.8% Developing | MX6200 | SETUP | Advised to try downstairs node; no confirmed fix or valid next step. |
| #LTS00135810OUTBOUND | 2026-07-03 | 1.8 A 4P 1C 3 | — | MX6200 | SETUP | Monitor node for 24 hours; case escalated for further investigation. |
| #LTS00077794INBOUND | 2026-07-03 | 2.8 A 2P 2C 3 | 53.1% Needs Improvement | E2500 | ACCESS | Customer will attempt factory reset or web UI access and call back if unsuccessful. |
| #LTS00135849INBOUND | 2026-07-03 | 2.8 A 3P 2C 3 | 53.3% Needs Improvement | MR8300 | CONNECTIVITY | Customer to power-cycle equipment, re-test speed, and follow up if problem persists. |