41Calls
2.29Avg Score
18m 10sAvg Handle Time
30Documented
5Escalated
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.29 | 41 |
| Technical Accuracy | 2.46 | 41 |
| Protocol | 1.68 | 41 |
| Communication | 2.17 | 41 |
Main focus: LED Interpretation & Call Control
V2 Rubric (Shadow Grading)
V2 overall: 40.9% across 31 v2-scored calls this week7 auto-zeros
| Category | Week Average |
|---|---|
| Resolution | 1.68 |
| Technical Accuracy | 2.06 |
| Communication | 2.3 |
| Customer Ownership | 3.11 |
| Escalation Judgment | 4.09 |
| Customer Experience | 1.85 |
- Unresolved: 17
- Successful Resolution: 6
- Appropriate Escalation: 4
- Partial Resolution: 4
Where Did the Time Go
By Product Family
| Family | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Note |
|---|---|---|---|---|---|---|---|
| LN | 1 | 67m 39s | 1.4 | 1.0 | 1.0 | 2.0 | Outlier: 5.7x weekly median handle time |
| MX | 12 | 28m 33s | 2.43 | 2.75 | 2.0 | 2.33 | Outlier: 2.4x weekly median handle time |
| RE | 2 | 26m 04s | 1.4 | 2.5 | 1.0 | 2.0 | Outlier: 2.2x weekly median handle time |
| MR | 5 | 14m 15s | 2.0 | 2.4 | 1.4 | 1.8 | |
| EA | 7 | 11m 55s | 2.17 | 2.29 | 1.29 | 1.86 | |
| WHW | 5 | 11m 55s | 2.62 | 1.6 | 2.2 | 2.6 | |
| OTHER | 2 | 10m 18s | 2.75 | 3.0 | 1.5 | 2.0 | |
| SPN | 2 | 8m 05s | 2.65 | 4.0 | 2.0 | 2.5 | |
| WRT | 1 | 4m 53s | 1.0 | 1.0 | 1.0 | 1.0 |
By Problem Category
| Category | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Focus? |
|---|---|---|---|---|---|---|---|
| CONNECTIVITY | 12 | 28m 50s | 2.08 | 1.92 | 1.83 | 2.17 | ✓ |
| CONFIGURATION | 9 | 25m 40s | 2.44 | 2.22 | 2.11 | 2.33 | |
| HARDWARE | 6 | 31m 05s | 1.95 | 1.67 | 1.5 | 2.0 | ✓ |
What You Did Well
- Warranty & Resolution Clarity3 of 30 callsConsistently set proper warranty expectations and offered appropriate paid-support options for out-of-warranty devices, while collecting necessary device identifiers before troubleshooting and guiding customers to functional resolutions despite technical missteps. Exemplified in calls #LTS00133408, #TE00133469, and #LTS00133582.Why this matters: Ensures customers understand support boundaries and feel supported, reducing frustration and repeat calls.
- Correct Mesh Procedures2 of 30 callsAccurately applied factory reset and 5-press pairing methods for MX series devices, restoring connectivity in multiple cases. Demonstrated in calls #TE00133469 and #LTS00133582.Why this matters: Restores customer confidence and network functionality efficiently.
Growth Focus
- LED Interpretation & Call Control8 of 30 callsRepeatedly misidentified solid blue LEDs as 'green' and provided inconsistent node placement guidance (2–3 ft vs. 10 ft), causing confusion. Calls suffered from excessive silences, repeated clarification requests, and lack of concise summaries. Appeared in 8 of 30 calls, notably #LTS00133408 and #TE00133469.Why this matters: Miscommunication about LED states can lead to incorrect troubleshooting and customer frustration; poor call control increases handle time and reduces efficiency.Example: In #LTS00133408, agent called solid blue 'green,' contradicting KB documentation and delaying resolution.What better looks like: Use exact KB terminology for LED states (solid blue = online) and provide clear, step-by-step instructions with consistent placement guidance.
- Password & Stability Verification2 of 30 callsFailed to verify router admin password access before directing customers to web UI, leading to confusion when recovery keys were requested. Did not confirm long-term node stability or internet connectivity after re-pairing, closing calls prematurely. Seen in #TE00133469 and #LTS00133650.Why this matters: Skipping password verification can cause login failures; not confirming stability risks callbacks due to unresolved issues.Example: In #TE00133469, admin password creation failed with error 2-2-9-8, but the agent did not troubleshoot or escalate.What better looks like: Verify password access upfront and confirm node stability and internet connectivity post-repair 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 and callbacks by ensuring the customer validates the solution before hanging up.
- Step 2Always verify router admin password access before directing customers to the web UI, and provide the correct local access URL (http://[REDACTED_PHONE] or http://myrouter.local).Why: Avoids login failures and confusion caused by incorrect instructions or inaccessible interfaces.This week: #TE00133469
- Step 3Use exact KB terminology for LED states (e.g., solid blue = online) and provide consistent node placement guidance.Why: Ensures accurate troubleshooting and reduces miscommunication that delays resolution.This week: #LTS00133408
- Step 4Collect and verify product model, serial number, and warranty status at the start of every call.Why: Enables proper diagnostics, appropriate support offerings, and efficient case management.This week: #LTS00133967
Escalation Lessons
#TE00133469 — MX4200
Status: pending_with_level_2_or_followup · Category: CONNECTIVITY
What happened on the call: Escalated to Level-2 technical team; callback scheduled in 2–3 hours.
Why it escalated: Level 1 was unable to resolve the MX4200 child node disconnection despite multiple resets and re-pairing attempts; admin password creation failed, indicating potential firmware or configuration issues beyond L1 scope.
What L2 did:
- Claimed ticket TE00133469 from the TE queue.
- Diagnosed firmware mismatch causing child node instability.
- Performed firmware update on parent and child nodes.
- Re-paired nodes using correct 5-press method.
- Verified solid blue LEDs and internet connectivity.
L1 learning points:
- Always verify admin password access before directing customers to the web UI.
- Confirm long-term node stability and internet connectivity after re-pairing before closing the call.
- Use exact KB terminology for LED states (solid blue = online).
#TE00133650 — LGS352MPC
Status: resolved · Category: NO TROUBLESHOOTING NEEDED
What happened on the call: Callback from Level 2 with specific transceiver part numbers and purchase links.
Why it escalated: Customer requested specific purchase links for compatible SFP transceivers for an LGS352MPC switch, a request beyond L1 scope.
What L2 did:
- Provided direct purchase links for compatible 10GBase-T copper transceiver modules.
- Confirmed module compatibility with LGS352MPC model.
- Scheduled callback to ensure customer received links and could proceed with purchase.
L1 learning points:
- When customers request specific part numbers or purchase links, escalate to L2 for accurate product information.
- Confirm customer understanding of compatible module types before escalation.
#TE00011507 — MX6200
Status: resolved · Category: CONNECTIVITY
What happened on the call: Escalated to Level 2; callback scheduled; ticket #11507 created.
#LTS00133935 — LN1600
Status: resolved · Category: SETUP
What happened on the call: Recommended hardware replacement; provided case number LTS-01000750 for follow-up
#TE00134119 — RE6400
Status: pending_with_level_2_or_followup · Category: SETUP
What happened on the call: Callback scheduled for next day at 10 am; receipt requested for warranty verification. No technical resolution achieved.
Evidence Calls
| Case | Date | Score | V2 | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00133408INBOUND | 2026-06-15 | 2.8 A 2P 2C 2 | 68.8% Needs Improvement | MX2000 | CONNECTIVITY | All nodes restored to solid blue, internet connectivity confirmed. |
| 8ac5c448-68d8-11f1-af69-42010a623f91INBOUND | 2026-06-15 | 2.8 A 4P 3C 3 | 96.2% Meets / Exceeds | MX4200 | CONNECTIVITY | Node temporarily stabilized to solid blue after reset and re-pairing, but admin password creation failed with error 2-2-9-8. Customer advised to observe node stability. No further steps provided. |
| #LTS00133444INBOUND | 2026-06-15 | 2.6 A 4P 2C 2 | 48.5% Needs Improvement | MX2000 | CONFIGURATION | Callback scheduled for further troubleshooting of persistent Wi-Fi disconnects. |
| #LTS00133444INBOUND | 2026-06-15 | 1.8 A 5P 1C 2 | — | MX2000 | CONFIGURATION | Agent stated technician would call back in ~2 minutes; no case created, no callback number confirmed, no follow-up documented. |
| #TE00133469INBOUND | 2026-06-15 | 2 A 1P 2C 2 | 71.7% Developing | MX4200 | CONNECTIVITY | Escalated to Level-2 technical team; callback scheduled in 2–3 hours. |
| #LTS00133479INBOUND | 2026-06-15 | 1.8 A 5P 1C 1 | — | MR9000 | SETUP | Agent requested phone number for callback; no further action taken or guidance provided. |
| #LTS00133479INBOUND | 2026-06-15 | 2.8 A 1P 2C 2 | 43.1% Needs Improvement | MR9000 | SETUP | Agent offered $15 paid support or email with troubleshooting steps. Customer chose email option. |
| #LTS00133488INBOUND | 2026-06-15 | 2.8 A 1P 1C 2 | 0.0% Needs Improvement | EA7200 | SETUP | Perform hard reset, wait for reboot, then log in with default password; if still unsuccessful, consider paid support or arrange follow-up. |
| #LTS00133488OUTBOUND | 2026-06-15 | 3.2 A 4P 2C 2 | 77.1% Developing | EA7200 | SETUP | Internet connectivity confirmed on both devices; customer advised that Wi-Fi is now functional. |
| #LTS00133582INBOUND | 2026-06-16 | 3.1 A 3P 3C 3 | 87.5% Meets / Exceeds | MX2000 | SETUP | All nodes now show solid blue; Wi-Fi renamed to 'Guru' and functional; issue resolved. |
| b40e3146-6996-11f1-b93f-42010a623f91INBOUND | 2026-06-16 | 2.8 A 2P 2C 3 | — | SETUP | Customer will obtain Ethernet cable and call back for further assistance. | |
| #GI00133609INBOUND | 2026-06-16 | 1 A 1P 1C 1 | — | WRT3200ACM | CONFIGURATION | Customer to log into router web interface and configure guest network password; verify security status. |
| ba4ba1c2-69a2-11f1-b913-42010a623f91INBOUND | 2026-06-16 | 1.1 A 1P 1C 2 | 0.0% Needs Improvement | ACCESS | No resolution; customer declined factory reset. Next step: provide customer with KB article linksys_now_login_admin.md for recovery key method. | |
| #LTS00133626INBOUND | 2026-06-16 | 1.1 A 1P 1C 2 | — | MR8300 | SETUP | Incorrect URL provided; no valid resolution path given. |
| #TE00133650INBOUND | 2026-06-16 | 2.7 A 5P 2C 2 | 57.5% Needs Improvement | LGS352MPC | NO TROUBLESHOOTING NEEDED | Callback from Level 2 with specific transceiver part numbers and purchase links. |
| #GI00126444 | 2026-06-17 | 2.6 A 4P 1C 3 | — | SPNM62 | HARDWARE | Callback scheduled for midnight Hong Kong time to continue investigation. |
| #LTS00133749INBOUND | 2026-06-17 | 2.8 A 1P 1C 2 | 0.0% Needs Improvement | VLP01 | CONNECTIVITY | Agent will email the customer generic instructions for adding a child node; no confirmation of fix or valid troubleshooting performed. |
| 226ad696-6a58-11f1-8eee-42010a623f91INBOUND | 2026-06-17 | 1.8 A 1P 2C 2 | 48.5% Needs Improvement | MR7350 | CONFIGURATION | Customer advised to contact Comporium ISP; follow-up with Linksys recommended for proper AP-mode setup. |
| #LTS00133738INBOUND | 2026-06-17 | 3.3 A 3P 3C 3 | 81.0% Developing | WHW03 | ACCESS | Admin password reset, Wi-Fi SSID and password renamed; customer confirmed changes are working. |
| #LTS00133757INBOUND | 2026-06-17 | 2.7 A 4P 3C 2 | 59.9% Needs Improvement | SPNM60CF | ACCESS | No resolution achieved. Recommend power-cycling router, trying a different browser/device, checking firmware status, or escalating to senior technician for further troubleshooting. |
| #LTS00133743INBOUND | 2026-06-17 | 2.5 A 2P 2C 3 | — | WHW03 | NO TROUBLESHOOTING NEEDED | Customer was given incorrect instructions for adding child nodes; issue not operationally resolved. Follow-up required for correct guidance via 5-press method or Network Map/Add Node. |
| #LTS00133743INBOUND | 2026-06-17 | 2.8 A 1P 2C 3 | 45.6% Needs Improvement | WHW03 | NO TROUBLESHOOTING NEEDED | Agent provided self-help steps with critical inaccuracies and did not verify success. Customer still sees old SSID and has not confirmed node connectivity. |
| #LTS00133776INBOUND | 2026-06-17 | 3.2 A 5P 2C 2 | 0.0% Needs Improvement | EA8300 | ACCESS | Customer instructed to perform factory reset using the reset button to restore default admin password ('admin') and default Wi-Fi credentials (from label). Agent offered to email instructions or provide paid support. |
| #LTS00133786INBOUND | 2026-06-17 | 2.8 A 2P 2C 2 | 82.8% Developing | MX6200 | CONNECTIVITY | Advised customer to run a wired speed test to verify ISP speed and monitor node status; no further action taken during call. |
| #TE00011507INBOUND | 2026-06-17 | 1.8 A 1P 2C 2 | 43.3% Needs Improvement | MX6200 | CONNECTIVITY | Escalated to Level 2; callback scheduled; ticket #11507 created. |
| #LTS00133811INBOUND | 2026-06-17 | 2.8 A 3P 2C 2 | 0.0% Needs Improvement | MX5500 | CONNECTIVITY | Agent will send an email with generic Wi-Fi troubleshooting steps. |
| #LTS00133817INBOUND | 2026-06-17 | 2.5 A 4P 1C 2 | 67.6% Needs Improvement | MR7350 | SETUP | Customer to contact ISP regarding modem status; agent offered paid-support if further assistance is needed and will follow up if the customer calls back. |
| #LTS00133811 | 2026-06-17 | 2.4 A 3P 2C 3 | — | MX5500 | CONNECTIVITY | Customer to verify modem connection with ISP (Starry); agent will call back in one hour to continue troubleshooting. |
| #LTS00133825INBOUND | 2026-06-17 | 2.8 A 1P 2C 2 | 13.2% Needs Improvement | WHW03 | HARDWARE | Sent a step-by-step troubleshooting guide via email. |
| #LTS00133935INBOUND | 2026-06-18 | 1.4 A 1P 1C 2 | 18.5% Needs Improvement | LN1600 | SETUP | Recommended hardware replacement; provided case number LTS-01000750 for follow-up |
| #LTS00133951INBOUND | 2026-06-18 | 1.1 A 1P 1C 2 | 0.0% Needs Improvement | EA6900 | CONNECTIVITY | Advised purchase of new MX6200 router; no troubleshooting or alternative paths offered. |
| #LTS00133958INBOUND | 2026-06-18 | 1.8 A 4P 1C 3 | 34.6% Needs Improvement | RE6300 | SETUP | Promised email with self-help steps; no technical fix confirmed. |
| #GI00133967INBOUND | 2026-06-18 | 1.1 A 1P 1C 2 | 17.5% Needs Improvement | EA7500 | SETUP | Customer advised to buy a new router; no technical fix applied or validated. |
| #LTS00133394INBOUND | 2026-06-19 | 1 A 1P 1C 1 | — | EA9500 | ACCESS | None – call ended without any action. |
| #LTS00134036INBOUND | 2026-06-19 | 1.7 A 1P 2C 2 | 0.0% Needs Improvement | WHW03 | SETUP | Agent offered paid support but provided no valid setup guidance or correct resources. |
| 3126e8a2-6c09-11f1-991f-42010a660053OUTBOUND | 2026-06-19 | 1.6 A 1P 1C 2 | 47.1% Needs Improvement | MX6200 | HARDWARE | Agent concluded hardware fault and offered replacement (discontinued) or pro-rated refund; promised to follow up after internal discussion. |
| #LTS00133696INBOUND | 2026-06-19 | 2.7 A 4P 2C 3 | 37.9% Needs Improvement | MX4200 | CONFIGURATION | Customer to call back using ticket LTS00133696 to schedule paid-support session. No technical steps taken during this call. |
| #LTS00134112INBOUND | 2026-06-19 | 2.8 A 3P 1C 2 | 24.8% Needs Improvement | EA8500 | CONNECTIVITY | Suggested purchasing a newer router or performing a full reset; no further action taken. |
| #TE00134119INBOUND | 2026-06-19 | 1 A 1P 1C 1 | 54.2% Needs Improvement | RE6400 | SETUP | Callback scheduled for next day at 10 am; receipt requested for warranty verification. No technical resolution achieved. |
| b57fcbc2-6c19-11f1-9063-42010a62006fINBOUND | 2026-06-19 | 3.5 A 5P 2C 3 | 41.0% Needs Improvement | SETUP | Customer will test internet connectivity directly at the AT&T modem. If no connection, contact AT&T for service repair. If connection succeeds, contact Linksys for further support. | |
| #GI00134028INBOUND | 2026-06-19 | 2.8 A 3P 2C 2 | — | SETUP | Customer advised to contact their Internet Service Provider to troubleshoot the modem. |