# charm.awitan — Coaching Report ## Week of 2026-06-01 – 2026-06-07 --- ## At a Glance | Calls Handled | Avg Handle Time | Top Product | Top Problem | Cases Documented | Cases Escalated | | --- | --- | --- | --- | --- | --- | | 34 | 15m 23s | MX6200 | CONNECTIVITY | 34 | 3 | ## Scorecard | Dimension | This Week | Calls Reviewed | | --- | --- | --- | | Accuracy | 2.30 | 34 | | Protocol | 1.90 | 34 | | Communication | 2.20 | 34 | | Overall | 2.20 | 34 | ## Where Time Goes **Product Families** | Family | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Note | | --- | --- | --- | --- | --- | --- | --- | --- | | WHW | 7 | 28m 2s | 2.29 | 2.43 | 1.71 | 2.00 | Outlier: 2.4x weekly median handle time | | MX | 12 | 27m 41s | 1.88 | 1.75 | 1.75 | 2.17 | Outlier: 2.4x weekly median handle time | | SPN | 3 | 17m 56s | 3.03 | 3.67 | 2.67 | 2.33 | Outlier: 1.6x weekly median handle time | | MR | 4 | 16m 11s | 2.60 | 2.50 | 2.50 | 2.50 | | | EA | 6 | 11m 31s | 2.02 | 1.50 | 1.50 | 2.00 | | | MBE | 2 | 10m 16s | 2.00 | 2.50 | 1.50 | 2.50 | | | OTHER | 1 | 7m 30s | 1.00 | 1.00 | 1.00 | 1.00 | | | WRT | 1 | 6m 3s | 1.80 | 4.00 | 1.00 | 2.00 | | | E | 1 | 4m 47s | 2.90 | 5.00 | 2.00 | 2.00 | | **Key Observations** - WHW is the slowest family at 28m 2s; outlier: 2.4x weekly median handle time. - MX is the slowest family at 27m 41s; outlier: 2.4x weekly median handle time. **Problem Categories** | Category | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Focus Area? | | --- | --- | --- | --- | --- | --- | --- | --- | | CONNECTIVITY | 16 | 20m 56s | 2.00 | 2.10 | 1.80 | 2.10 | ✓ | | SETUP | 9 | 19m 15s | 2.20 | 2.30 | 2.10 | 2.40 | | | ACCESS | 5 | 13m 17s | 2.50 | 3.00 | 2.20 | 2.40 | | | CONFIGURATION | 3 | 11m 34s | 1.70 | 1.30 | 1.70 | 2.30 | ✓ | ## Week-over-Week Movement - Improve accuracy in technical guidance, especially for mesh node pairing and reset procedures. - Ensure consistent collection of product model and serial number at the start of each call. - Follow standard troubleshooting flows before escalating or offering paid support. ## What Went Well - **Accurate Model Identification and Serial Collection**: > Collected model number (SPNM60) and serial number accurately during call. [#LTS00132075](https://linksys.happyfox.com/staff/ticket/132075/) - **Effective Use of Local Web UI for Setup**: > Guided customer to use local web UI ([REDACTED_PHONE]) to complete router setup despite app failure. [#LTS00132075](https://linksys.happyfox.com/staff/ticket/132075/) --- ### Growth Opportunities - **Incorrect Technical Guidance on Router Access**: > Provided wrong admin URL ([REDACTED_PHONE]) instead of [REDACTED_PHONE] or myrouter.local, causing browser error and delayed resolution. [#LTS00131804](https://linksys.happyfox.com/staff/ticket/131804/) - **Failure to Perform Basic Troubleshooting**: > Skipped standard WAN troubleshooting steps (modem power-cycle, WAN LED check) despite clear connectivity issues. [#LTS00131693](https://linksys.happyfox.com/staff/ticket/131693/) [#LTS00131582](https://linksys.happyfox.com/staff/ticket/131582/) --- ### Next Week's Focus - **Improve Accuracy in Technical Guidance**: Ensure correct URLs and steps are provided, especially for router access and setup. - **Consistent Collection of Product Information**: Always collect model and serial numbers at the start of each call. - **Follow Standard Troubleshooting Flows**: Perform basic troubleshooting before escalating or offering paid support. - **Enhance Communication Clarity**: Provide clear and concise instructions to avoid confusion and improve customer experience. --- ### Technical Accuracy - **Improvement**: > Incorrectly applied 5-press pairing method to MX8500 series, which only supports Intelligent Mesh via app/web UI. This contradicts KB guidance for Velop MX models. [#LTS00131693](https://linksys.happyfox.com/staff/ticket/131693/) - **Improvement**: > Agent failed to clarify the topology requirement for fiber installations, which mandates an ONT between the wall and router. This could mislead the customer and result in setup failure. [#GI00131618](https://linksys.happyfox.com/staff/ticket/131618/) - **Improvement**: > Incorrect URL provided caused browser error and delayed resolution. This is a critical protocol error that undermines customer confidence. [#LTS00131804](https://linksys.happyfox.com/staff/ticket/131804/) - **Improvement**: > Incorrect reset procedure provided for MR20 model, which does not support 5-press reset. This could confuse the customer and delay resolution. [#LTS00131860](https://linksys.happyfox.com/staff/ticket/131860/) - **Strength**: > Accurately communicated the limitation of the Linksys app for EA9450 model, aligning with KB guidance. [#LTS00131624](https://linksys.happyfox.com/staff/ticket/131624/) --- ### Coaching Moments - **Improvement**: > Incorrectly applied 5-press pairing method to MX8500 series, which only supports Intelligent Mesh via app/web UI. This contradicts KB guidance for Velop MX models. > [#LTS00131693](https://linksys.happyfox.com/staff/ticket/131693/) - **Improvement**: > Agent failed to clarify the topology requirement for fiber installations, which mandates an ONT between the wall and router. This could mislead the customer and result in setup failure. > [#GI00131618](https://linksys.happyfox.com/staff/ticket/131618/) - **Improvement**: > Incorrect URL provided caused browser error and delayed resolution. This is a critical protocol error that undermines customer confidence. > [#LTS00131804](https://linksys.happyfox.com/staff/ticket/131804/) - **Improvement**: > Incorrect reset procedure provided for MR20 model, which does not support 5-press reset. This could confuse the customer and delay resolution. > [#LTS00131860](https://linksys.happyfox.com/staff/ticket/131860/) --- ### Escalation Lessons: What L2 Did ### [#TE00023348](https://linksys.happyfox.com/staff/ticket/23348/) — Resolved by Level 2 - **What L1 Saw**: MX6200_intermittent to no internet connection. Customer reported intermittent disconnects more than 10 times everyday, with the internet cutting out and the main node changing to red light. - **Why it Escalated**: The issue persisted despite initial troubleshooting, requiring advanced diagnostics and intervention. - **Related Call Chain**: This was a repeat contact involving multiple agents, indicating ongoing issues that were not fully resolved at Level 1. - **What L2 Did**: Level 2 performed advanced troubleshooting, including reviewing system information, attached working sysinfo, and conducted a callback to resolve the issue. - **Current State**: The case is resolved. - **L1 Learning Points**: - Collect detailed information on intermittent issues, including exact error messages and LED statuses. - Verify internet connectivity and perform basic troubleshooting before escalating. - Document all steps taken and communicate clearly with the customer to avoid repeat contacts. ### [#LTS00132222](https://linksys.happyfox.com/staff/ticket/132222/) — Resolved by Level 2 - **What L1 Saw**: No Internet Connection. Customer reported drastic changes in internet speed depending on the area, with some areas only getting 100mbps due to distance from the nodes. - **Why it Escalated**: The issue required advanced troubleshooting and potential hardware upgrades. - **Related Call Chain**: This was a repeat contact involving multiple agents, indicating ongoing issues that were not fully resolved at Level 1. - **What L2 Did**: Level 2 provided guidance on adding more nodes to improve signal strength and offered a complimentary inconvenience node. - **Current State**: The case is resolved. - **L1 Learning Points**: - Explain the impact of node distance and interference on internet speed. - Offer solutions such as adding more nodes to improve connectivity. - Clearly communicate support options and potential upgrades. ### [#TE00057780](https://linksys.happyfox.com/staff/ticket/57780/) — Resolved by Level 2 - **What L1 Saw**: Trouble accessing the app. Customer had issues with one child node disconnected and wanted to put the VPN on the mesh. - **Why it Escalated**: The issue required firmware updates and advanced troubleshooting. - **Related Call Chain**: This was a repeat contact involving multiple agents, indicating ongoing issues that were not fully resolved at Level 1. - **What L2 Did**: Level 2 provided a Beta firmware update and guided the customer through the update process. - **Current State**: The case is resolved. - **L1 Learning Points**: - Inform customers about the limitations of certain nodes regarding features like VPN. - Provide clear instructions for firmware updates and ensure customers understand the process. - Offer self-help resources and follow-up support as needed. --- ### Coach Appendix - **Highest-Signal Weekly Trend**: The week was dominated by connectivity and setup issues, particularly with MX and WHW product families. There is a need for improved accuracy in technical guidance and consistent collection of product information. - **Recurring Technical or Process Pattern**: Agents often skipped basic troubleshooting steps and provided incorrect technical guidance, leading to unresolved issues and customer frustration. Focus should be on adhering to standard troubleshooting flows and ensuring accurate information is provided. --- ### This Week's Calls | Case | Date | Score | Direction | Product | Category | Outcome | |---|---|---|---|---|---|---| | [#LTS00131582](https://linksys.happyfox.com/staff/ticket/131582/) | 2026-06-01 13:05:24+00:00 | 1.3 | INBOUND | MBE7000 | SETUP | No resolution confirmed. Call ended without operational closure or next step. | | [#LTS00131588](https://linksys.happyfox.com/staff/ticket/131588/) | 2026-06-01 13:11:38+00:00 | 3.0 | INBOUND | MR7500 | SETUP | ✓ Resolved | | [#LTS00131594](https://linksys.happyfox.com/staff/ticket/131594/) | 2026-06-01 13:29:45+00:00 | 3.0 | INBOUND | EA7450 | SETUP | ✓ Likely resolved | | [#LTS00131598](https://linksys.happyfox.com/staff/ticket/131598/) | 2026-06-01 14:05:11+00:00 | 2.6 | INBOUND | WHW03 | ACCESS | ↑ Escalated | | [#LTS00131609](https://linksys.happyfox.com/staff/ticket/131609/) | 2026-06-01 14:34:54+00:00 | 1.6 | INBOUND | EA6350 | CONNECTIVITY | No resolution confirmed. Email with self‑help may not resolve the issue. | | [#GI00131618](https://linksys.happyfox.com/staff/ticket/131618/) | 2026-06-01 15:02:45+00:00 | 1.4 | INBOUND | MX8500 | SETUP | No resolution achieved. Customer was told to reset the MX8500 and consult the general mesh setup article on Linksys.com/support. | | [#LTS00131624](https://linksys.happyfox.com/staff/ticket/131624/) | 2026-06-01 15:20:08+00:00 | 2.9 | INBOUND | E9450 | ACCESS | ✓ Likely resolved | | [#LTS00131573](https://linksys.happyfox.com/staff/ticket/131573/) | 2026-06-01 17:28:03+00:00 | 3.4 | INBOUND | SPNMX57CF | CONNECTIVITY | ✓ Likely resolved | | [#LTS00131682](https://linksys.happyfox.com/staff/ticket/131682/) | 2026-06-01 19:36:36+00:00 | 1.8 | INBOUND | WRT54G | CONFIGURATION | Perform factory reset using pinhole button for 10 seconds, then reconfigure router using default SSID and password printed on device label. | | [#LTS00131693](https://linksys.happyfox.com/staff/ticket/131693/) | 2026-06-01 19:55:41+00:00 | 1.6 | INBOUND | MX8500 | CONNECTIVITY | Verify WAN connectivity; if issue persists, perform proper factory reset and re-add node via web UI (http://myrouter.local or http://192.168.1.1). | | [#LTS00131804](https://linksys.happyfox.com/staff/ticket/131804/) | 2026-06-02 15:37:12+00:00 | 2.8 | INBOUND | WHW03 | CONNECTIVITY | Customer will operate with only the primary node; no further action required. | | [#LTS00131860](https://linksys.happyfox.com/staff/ticket/131860/) | 2026-06-02 16:53:21+00:00 | 1.8 | INBOUND | MR20EC | SETUP | Ticket created (LCS0013860); customer to have spouse power-cycle equipment and call back for further assistance. | | [#LTS00131873](https://linksys.happyfox.com/staff/ticket/131873/) | 2026-06-02 17:39:34+00:00 | 2.8 | INBOUND | MX4200 | SETUP | ✓ Resolved | | [#LTS00131903](https://linksys.happyfox.com/staff/ticket/131903/) | 2026-06-02 19:52:30+00:00 | 1.8 | INBOUND | MX4200 | HARDWARE | Advised customer to purchase a replacement node; no self-help resources or further troubleshooting offered. | | [#LTS00040167](https://linksys.happyfox.com/staff/ticket/40167/) | 2026-06-03 14:01:37+00:00 | 1.4 | INBOUND | MX6200 | SETUP | Customer will call back later; no resolution achieved. | | [#LTS00132043](https://linksys.happyfox.com/staff/ticket/132043/) | 2026-06-03 15:59:20+00:00 | 2.8 | INBOUND | WHW03 | CONNECTIVITY | ↑ Escalated | | [#LTS00132106](https://linksys.happyfox.com/staff/ticket/132106/) | 2026-06-03 19:16:08+00:00 | 2.8 | INBOUND | WHW03 | SETUP | Perform factory reset on all nodes, reconfigure mesh wirelessly using default SSID, then enable wired backhaul; follow emailed guide. | | [#LTS00132110](https://linksys.happyfox.com/staff/ticket/132110/) | 2026-06-03 19:41:08+00:00 | 1.3 | INBOUND | EA9500 | CONFIGURATION | None provided; promised email cannot be delivered due to incorrect address capture. | | [#LTS00044333](https://linksys.happyfox.com/staff/ticket/44333/) | 2026-06-05 19:02:10+00:00 | 1.4 | INBOUND | MX6200 | SETUP | Customer to attempt reset and bridge mode setup independently; agent did not confirm steps or provide follow-up resources. | | [#LTS00132423](https://linksys.happyfox.com/staff/ticket/132423/) | 2026-06-05 15:47:25+00:00 | 1.0 | INBOUND | WUSB6300 | NO TROUBLESHOOTING NEEDED | Agent stated device is end-of-life and no driver is available; no actionable next step provided. | | [#LTS00132429](https://linksys.happyfox.com/staff/ticket/132429/) | 2026-06-05 16:05:40+00:00 | 2.0 | INBOUND | WHW03 | ACCESS | Customer changed Wi-Fi name and password but still reported no internet. No further troubleshooting or escalation path provided. | | [#LTS00131838](https://linksys.happyfox.com/staff/ticket/131838/) | 2026-06-05 16:43:03+00:00 | 2.8 | INBOUND | MX5300 | CONFIGURATION | Reset the child node and retry pairing via the app. | | [#LTS00132452](https://linksys.happyfox.com/staff/ticket/132452/) | 2026-06-05 18:15:12+00:00 | 1.4 | INBOUND | SPNM62CF | CONNECTIVITY | Agent incorrectly advised contacting PlayStation support for port numbers; no router diagnostics or fixes performed. | | [#LTS00044333](https://linksys.happyfox.com/staff/ticket/44333/) | 2026-06-05 19:02:10+00:00 | 1.4 | INBOUND | MX6200 | SETUP | Customer to attempt reset and bridge mode setup independently; agent did not confirm steps or provide follow-up resources. | | [#TE00057780](https://linksys.happyfox.com/staff/ticket/57780/) | 2026-06-05 20:30:23+00:00 | 2.7 | INBOUND | MBE7000 | CONNECTIVITY | Agent promised a callback from Level 2 within 5–10 minutes. No further action taken. | | [#LTS00121874](https://linksys.happyfox.com/staff/ticket/121874/) | 2026-06-05 16:05:40+00:00 | 1.0 | INBOUND | WHW03 | CONFIGURATION | | | [#LTS00132423](https://linksys.happyfox.com/staff/ticket/132423/) | 2026-06-05 15:47:25+00:00 | 1.0 | INBOUND | WUSB6300 | NO TROUBLESHOOTING NEEDED | Agent stated device is end-of-life and no driver is available; no actionable next step provided. | | [#LTS00132429](https://linksys.happyfox.com/staff/ticket/132429/) | 2026-06-05 16:05:40+00:00 | 2.0 | INBOUND | WHW03 | ACCESS | Customer changed Wi-Fi name and password but still reported no internet. No further troubleshooting or escalation path provided. | | [#LTS00131838](https://linksys.happyfox.com/staff/ticket/131838/) | 2026-06-05 16:43:03+00:00 | 2.8 | INBOUND | MX5300 | CONFIGURATION | Reset the child node and retry pairing via the app. | | [#LTS00132452](https://linksys.happyfox.com/staff/ticket/132452/) | 2026-06-05 18:15:12+00:00 | 1.4 | INBOUND | SPNM62CF | CONNECTIVITY | Agent incorrectly advised contacting PlayStation support for port numbers; no router diagnostics or fixes performed. |