Your weekly coaching path
Coach as a hybrid queue owner with both frontline and escalation responsibilities.
Snapshot
Calls handled: 56 | Average score: 2.28 | Main focus: Incorrect technical instructions
Progress Since Last Week
No prior-week comparison available yet.
What You Did Well
- Clear and accurate technical guidance: Provided correct local admin URLs: http://myrouter.local and http://[REDACTED_PHONE] at [25:00] (per KB).
- Persistence in troubleshooting: Persisted through a complex mesh issue and did not abandon the customer despite multiple setbacks.
Main Growth Area
- Incorrect technical instructions: Incorrect reset duration (25 seconds) for WHW03; correct is 10 seconds per KB.
- Failure to verify warranty status before offering paid support: Processed payment for paid support without confirming warranty eligibility or collecting serial number.
Practice Plan
No items available.
Evidence Calls
| Case | Date | Score | Product | Category | Outcome |
|---|---|---|---|---|---|
| #GI00127699 | 2026-06-01 12:58:56+00:00 | 1.5 | GENERAL INQUIRY | Call terminated; no resolution provided. | |
| #GI00131690 | 2026-06-01 20:17:32+00:00 | 3.5 | EA7300 | CONNECTIVITY | Advised that the EA7300 is End-of-Life and recommended upgrading to a newer Linksys router for better performance. |
| #LTS00131700 | 2026-06-01 20:37:05+00:00 | 1.8 | WHW03 | CONNECTIVITY | Directed customer to support.linksys.com and offered paid connect service; no configuration completed or validated. |
| #LTS00131709 | 2026-06-01 21:19:47+00:00 | 2.8 | WHW03 | CONNECTIVITY | Directed customer to support.linksys.com and promised email with setup instructions. |
| #LTS00131713 | 2026-06-01 21:41:25+00:00 | 2.8 | EA8300 | CONNECTIVITY | Customer resolved issue independently; agent did not verify fix or provide correct self-help resources. |
| #LTS00101564 | 2026-06-01 22:28:55+00:00 | 2.4 | MX2000 | CONNECTIVITY | Customer will call back to purchase Paid Connect service for further assistance. |
| #GI00131724 | 2026-06-01 22:40:56+00:00 | 1 | Unclassified | not_fixed | |
| #LTS00131728 | 2026-06-01 22:55:06+00:00 | 1 | WHW03 | CONNECTIVITY | not_fixed |
| #LTS00131730 | 2026-06-01 22:59:14+00:00 | 1.6 | E5400 | SETUP | Directed customer to support.linksys.com for self‑service articles; offered paid $15 Connect service if they choose. |
| #LTS00131728 | 2026-06-01 23:45:30+00:00 | 1.1 | WHW03 | CONNECTIVITY | Agent promised to call back without specifying time or method; no valid next step was confirmed. |
| #LTS00131728 | 2026-06-02 00:10:02+00:00 | 1.6 | WHW03 | CONNECTIVITY | Identified hardware fault on one child node; advised replacement may be needed, but no formal RMA, escalation, or self-help path was provided. |
| #GI00131741 | 2026-06-02 01:04:57+00:00 | 3 | MX6203 | GENERAL INQUIRY | Agent confirmed technical feasibility; customer will attempt setup independently and may call back if issues arise. |
| #LTS00131743 | 2026-06-02 01:10:33+00:00 | 2.8 | MX6200 | CONNECTIVITY | Router appears online after power cycle; advised customer to consider purchasing an MX series node for better coverage. |
| #LTS00131753 | 2026-06-02 02:27:44+00:00 | 3.4 | MR8300 | CONNECTIVITY | Customer directed to support.linksys.com for self-service troubleshooting articles. |
| #TE00131905 | 2026-06-02 20:14:50+00:00 | 1.4 | WHW03 | SETUP | Escalated to Level 2 for advanced troubleshooting including possible firmware reflash; customer to be contacted within 2–3 hours. |
| #LTS00131955 | 2026-06-02 22:12:19+00:00 | 1 | E1200 | ACCESS | None; agent incorrectly declared router end-of-life and suggested replacement without verification. |
| #GI00131931 | 2026-06-02 22:21:14+00:00 | 2.8 | ACCESS | Factory reset and re-configure the router using default credentials. | |
| #LTS00131938 | 2026-06-02 22:43:00+00:00 | 1.8 | MX2000 | CONNECTIVITY | Customer to contact Spectrum to resolve modem-level internet issue; agent will follow up the next day. |
| #LTS00083162 | 2026-06-02 23:29:18+00:00 | 1.4 | MX4200 | CONFIGURATION | Node displayed solid green, but agent provided no verification steps and closed under incorrect brand (TP-Link). |
| #LTS00131953 | 2026-06-03 00:11:51+00:00 | 2.8 | MR6350 | CONFIGURATION | Customer will use the online support article to attempt band separation; no further action required by agent. |
| #LTS00131955 | 2026-06-03 00:18:57+00:00 | 1.3 | E1200 | ACCESS | Customer directed to invalid URL for self-help; no password recovery method provided. |
| #LTS00131955 | 2026-06-03 00:31:05+00:00 | 2.8 | E1200 | ACCESS | Customer instructed to log into the router’s web UI to view or change the Wi-Fi password; no further action taken. |
| #LTS00131966 | 2026-06-03 01:27:27+00:00 | 1.3 | EA5800 | CONNECTIVITY | No resolution achieved. Agent provided invalid URL (support.linkedin.com) and did not confirm internet restoration. |
| #LTS00002343 | 2026-06-03 01:32:49+00:00 | 1.8 | MX6200 | SETUP | Advised that the observed UI glitch should self-correct; instructed customer to monitor node status with no further action or escalation path provided. |
| #LTS00132116 | 2026-06-03 20:02:02+00:00 | 2.8 | MX4200 | SETUP | Agent will email KB articles on resetting the admin password and adding child nodes. |
| #LTS00132130 | 2026-06-03 21:49:54+00:00 | 4 | MX8500 | ACCESS | Access router UI via http://192.168.15.1/ui/local/dynamic/index.html using HTTP and Edge browser; login successful. |
| #LTS00132132 | 2026-06-03 22:14:41+00:00 | 2.8 | VLP01 | CONNECTIVITY | Directed customer to support.linksys.com for self‑service guidance. |
| #LTS00098739 | 2026-06-03 22:24:34+00:00 | 2.8 | WHW03 | CONNECTIVITY | Nodes paired successfully; Wi-Fi network operational. |
| #LTS00132147 | 2026-06-03 23:13:48+00:00 | 1 | EA7250 | ACCESS | None. |
| #LTS00132147 | 2026-06-03 23:41:54+00:00 | 1 | EA7250 | ACCESS | None |
| #LTS00132147 | 2026-06-03 23:47:52+00:00 | 2.8 | EA7250 | ACCESS | Use http://myrouter.local or http://192.168.1.1 with admin password 'admin'; if login still fails, perform a factory reset. |
| #LTS00132148 | 2026-06-04 00:00:54+00:00 | 2.9 | CM3024 | CONNECTIVITY | Contact ISP for configuration changes or replace the modem with a supported model. |
| #LTS00131955 | 2026-06-04 00:22:58+00:00 | 1 | E1200 | ACCESS | Provided website link only; no functional resolution. |
| #LTS00058471 | 2026-06-04 00:33:03+00:00 | 1.4 | MX5500 | SETUP | No resolution. Customer directed to a misspelled URL and offered paid support, leading to call abandonment. |
| #TE00027382 | 2026-06-04 00:34:27+00:00 | 2.8 | MX6200 | SETUP | All nodes are now online; advise monitoring signal and repositioning if needed. |
| #LTS00132307 | 2026-06-04 20:07:38+00:00 | 1.4 | E7350 | SETUP | Customer reported admin page opened after trying URLs, but agent did not confirm or assist with further setup. |
| #LTS00096076 | 2026-06-04 21:26:23+00:00 | 2 | MX4200 | CONNECTIVITY | Most nodes showed connected status (green/blue) by end of call, but one remained unstable. No definitive resolution confirmed. No follow-up or escalation scheduled. |
| #LTS00132332 | 2026-06-04 22:59:03+00:00 | 1.7 | WHW03 | CONNECTIVITY | Agent concluded node was connected based on incorrect LED interpretation; no actual resolution or further steps provided. |
| #LTS00112384 | 2026-06-04 23:52:23+00:00 | 2.2 | EA7450 | SETUP | Customer to manage router locally using provided URLs and change WAN type to DHCP after modem replacement. No path provided to correct email address. |
| #LTS00132342 | 2026-06-05 00:22:06+00:00 | 2.8 | E5400 | CONNECTIVITY | Internet restored after reset and Wi‑Fi re‑configuration. |
| #LTS00132348 | 2026-06-05 00:57:54+00:00 | 2.8 | PAP2T | SETUP | Advised to consult support.linksys.com for legacy products and consider a newer model; no technical fix provided. |
| #GI00127132 | 2026-06-05 01:13:34+00:00 | 2.8 | WHW03 | SETUP | All nodes are now solid blue and admin UI is accessible; customer can complete bridge-mode configuration and place nodes. |
| #LTS00132350 | 2026-06-05 01:27:40+00:00 | 2.8 | EA6100 | CONNECTIVITY | Provided support website and offered paid support; customer declined and plans to replace router. |
| #LTS00132352 | 2026-06-05 01:43:00+00:00 | 2.8 | WHW03 | CONNECTIVITY | Internet restored; router and at least one node are operational. |
| #LTS00132447 | 2026-06-05 18:12:34+00:00 | 2.8 | WHW01 | SETUP | Agent will email a link to a video showing how to reset and re-add the nodes. |
| #LTS00131968 | 2026-06-05 18:25:16+00:00 | 3.3 | MX4200 | NO TROUBLESHOOTING NEEDED | Access router locally via http://myrouter.local; monitor for any further issues. |
| #LTS00132453 | 2026-06-05 18:46:54+00:00 | 2.8 | MX5300 | CONNECTIVITY | Network restored; advise replacement of original parent node with faulty WAN port. |
| #GI00132479 | 2026-06-05 20:58:26+00:00 | 2.2 | MR7340 | SETUP | No concrete resolution; advised to research further on support.linksys.com. |
| #LTS00132485 | 2026-06-05 21:43:46+00:00 | 2.8 | MX4200 | CONNECTIVITY | Router reset and Wi-Fi re-configuration restored internet; child nodes re-joined the mesh. |
| #LTS00132495 | 2026-06-05 22:33:06+00:00 | 2.2 | E4200 | CONNECTIVITY | Customer to try wired connection and access 192.168.1.1; no confirmation of success or follow-up scheduled. |
| #LTS00132500 | 2026-06-05 23:02:02+00:00 | 2.8 | MX4000 | SETUP | Nodes paired and Wi-Fi reconfigured; internet appears functional but not confirmed. Advised on parental controls. |
| #LTS00121778 | 2026-06-05 23:29:18+00:00 | 1.7 | MX4200 | CONNECTIVITY | No resolution achieved; further troubleshooting required (correct reset timing, proper pairing method, WAN verification). |
| #LTS00132506 | 2026-06-06 00:14:15+00:00 | 3.1 | WHW01 | SETUP | Directed customer to support.linksys.com and offered paid-connect service; no troubleshooting performed. |
| #LTS00121778 | 2026-06-06 00:26:13+00:00 | 4 | MX4200 | CONNECTIVITY | Issue resolved; network operational. |
| #LTS00132507 | 2026-06-06 00:30:50+00:00 | 2.8 | WHW03 | CONNECTIVITY | Offered self-help article link and paid support; customer declined. |
| #TE00132127 | 2026-06-06 00:53:04+00:00 | 1.8 | MX6200 | CONFIGURATION | Callback promised but not arranged; agent later stated support was closed and no technician available. No valid next step confirmed. |