15Calls
2.57Avg Score
29m 58sAvg Handle Time
14Documented
0Escalated
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.57 | 15 |
| Technical Accuracy | 3.0 | 15 |
| Protocol | 2.07 | 15 |
| Communication | 2.4 | 15 |
Main focus: Model/Serial collection
V2 Rubric (Shadow Grading)
V2 overall: 53.65% across 15 v2-scored calls this week2 auto-zeros
| Category | Week Average |
|---|---|
| Resolution | 2.38 |
| Technical Accuracy | 3.0 |
| Communication | 2.75 |
| Customer Ownership | 3.37 |
| Escalation Judgment | 1.4 |
| Customer Experience | 2.45 |
- Partial Resolution: 8
- Unresolved: 4
- Ownership Gap: 2
- Successful Resolution: 1
Where Did the Time Go
By Product Family
| Family | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Note |
|---|---|---|---|---|---|---|---|
| MX | 6 | 38m 01s | 2.48 | 3.67 | 2.0 | 2.17 | Outlier: 2.0x weekly median handle time |
| WHW | 5 | 33m 13s | 2.74 | 2.4 | 2.2 | 2.8 | Outlier: 1.7x weekly median handle time |
| SPN | 1 | 26m 48s | 1.8 | 1.0 | 2.0 | 3.0 | |
| OTHER | 1 | 12m 11s | 2.6 | 4.0 | 2.0 | 2.0 | |
| MR | 1 | 9m 09s | 2.8 | 3.0 | 2.0 | 2.0 | |
| E | 1 | 7m 04s | 2.8 | 3.0 | 2.0 | 2.0 |
By Problem Category
| Category | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Focus? |
|---|---|---|---|---|---|---|---|
| CONNECTIVITY | 10 | 30m 42s | 2.4 | 2.9 | 2.1 | 2.5 | ✓ |
| SETUP | 3 | 31m 03s | 2.43 | 2.33 | 2.33 | 2.67 | ✓ |
| HARDWARE | 1 | 9m 09s | 2.8 | 3.0 | 2.0 | 2.0 |
What You Did Well
- Accurate technical guidance8 of 14 callsProvided correct troubleshooting steps including power-cycle sequences, Ethernet cable reseat, and LED status interpretation across multiple calls (e.g., #LTS00135933 confirmed internet access via solid blue LED).Why this matters: Ensures customers receive reliable, KB-aligned instructions that resolve issues efficiently.
- Clear communication7 of 14 callsMaintained polite, patient tone and provided structured next steps, reducing customer frustration (e.g., #LTS00136508 guided relocation of node with clear expectations).Why this matters: Improves customer experience and adherence to prescribed actions.
Growth Focus
- Model/Serial collection9 of 14 callsFailed to capture product model and serial number early in calls despite customer providing them, leading to delayed or inaccurate troubleshooting (e.g., #LTS00135933 missed model/serial at [11:00]).Why this matters: Delays resolution and increases repeat calls due to missing critical hardware data.Example: In #LTS00135933, the agent did not record the WHW03 model or serial despite the customer stating it at timestamp 11:00, requiring later re-confirmation.What better looks like: Capture model and serial number within the first 2 minutes of the call, verify accuracy, and confirm warranty status.
- Technical accuracy6 of 14 callsProvided incorrect information about post-reset SSID behavior, default passwords, and URL access (e.g., claimed Linksys cloud account is discontinued in #LTS00136499).Why this matters: Incorrect guidance leads to unresolved issues, customer confusion, and potential security risks.Example: In #LTS00136499, the agent incorrectly stated the Linksys cloud account is discontinued and assumed default admin password was 'admin' for SPNMX42TS model.What better looks like: Reference KB articles for model-specific defaults and verify URL accessibility before instructing customers.
Callback Flags
No callback chains detected.
Documentation Accuracy
No documentation mismatches detected this week.
Practice Plan
- Step 1Capture product model and serial number within the first 2 minutes of every call and confirm warranty eligibility.Why: Missing hardware data delays diagnosis and increases repeat contacts.
- Step 2Before instructing any reset or reconfiguration, verify internet/WAN status by connecting a computer directly to the modem.Why: Prevents unnecessary steps and misdirected troubleshooting.This week: #LTS00136501
- Step 3Reference model-specific KB articles for default credentials, reset methods, and post-reset behavior before providing guidance.Why: Ensures technical accuracy and avoids misinformation.This week: #LTS00136499
Escalation Lessons
No escalated case learning this week.
Evidence Calls
| Case | Date | Score | V2 | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00135933INBOUND | 2026-07-06 | 3.6 A 4P 2C 3 | 92.2% Meets / Exceeds | WHW03 | CONNECTIVITY | Internet connectivity restored. Advised customer to repeat power-cycle and cable check if issue recurs. |
| #LTS00135939INBOUND | 2026-07-06 | 2.1 A 2P 3C 2 | 52.1% Needs Improvement | WHW01 | CONNECTIVITY | Customer instructed to try connecting to default SSID; no connectivity achieved. No further action scheduled. |
| #LTS00135749INBOUND | 2026-07-06 | 1.8 A 5P 1C 1 | 0.0% Needs Improvement | MX2000 | CONNECTIVITY | No resolution; agent did not provide any next steps. |
| #LTS00135939OUTBOUND | 2026-07-06 | 2.8 A 1P 2C 3 | 75.5% Developing | WHW01 | CONNECTIVITY | Issue not resolved; ticket created for follow-up. Recommend Level-2 escalation or replacement. Customer has ordered new router. |
| #LTS00135975INBOUND | 2026-07-06 | 2.6 A 4P 2C 2 | 44.5% Needs Improvement | WRE6102 | SETUP | Informed customer that firmware is not available due to end-of-support status. Offered to send user guide but no further action taken. |
| #LTS00135983INBOUND | 2026-07-06 | 3.2 A 5P 2C 2 | 79.4% Developing | MX6200 | CONNECTIVITY | Node paired successfully and is currently stable; monitor for 24 h and relocate if issue returns. |
| #LTS00136135INBOUND | 2026-07-07 | 2.4 A 3P 2C 3 | 41.0% Needs Improvement | WHW03 | CONNECTIVITY | Agent advised a wired speed test and cable check; no further configuration steps were provided. |
| #LTS00136150INBOUND | 2026-07-07 | 2.8 A 3P 2C 2 | 0.0% Needs Improvement | MR7350 | HARDWARE | Advised customer to purchase a new router as the current unit appears defective and is out of warranty. |
| #EOS00136154INBOUND | 2026-07-07 | 2.8 A 3P 2C 2 | 32.9% Needs Improvement | E900 | SETUP | Emailed reconfiguration guide; advised power-cycle/reset and suggested upgrading the router. |
| #LTS00136155INBOUND | 2026-07-07 | 2.8 A 2P 2C 3 | 38.9% Needs Improvement | WHW03 | CONNECTIVITY | Nodes now show solid green; internet works on upstairs device. Customer to relocate downstairs node and verify connectivity. |
| #LTS00136350INBOUND | 2026-07-08 | 2.8 A 3P 2C 3 | 72.6% Developing | MX6200 | CONNECTIVITY | Advised to leave the node near the parent for about an hour to allow a stable link, then relocate it. |
| #LTS00136499INBOUND | 2026-07-09 | 1.8 A 1P 2C 3 | 56.4% Needs Improvement | SPNMX42TS | CONNECTIVITY | Customer was instructed to add the node via the app after password reset; agent did not verify success. Follow-up needed to confirm internet connectivity and complete node pairing. |
| #LTS00136501INBOUND | 2026-07-09 | 2.8 A 3P 4C 3 | 73.4% Developing | MX6200 | CONNECTIVITY | Contact ISP technician to fix modem; call back to Linksys after ISP resolves the issue. Ticket LTS00136501 logged. |
| #LTS00136508INBOUND | 2026-07-09 | 3.3 A 5P 2C 3 | 75.1% Developing | MX4200 | CONNECTIVITY | Node returned to solid blue after relocation; customer advised to monitor and call back if issue recurs. |
| #LTS00136655INBOUND | 2026-07-10 | 1 A 1P 1C 1 | 70.8% Developing | MX6200 | SETUP | not_fixed |
Feedback
✓ Feedback submitted — thank you!