# Xiangjie Zhang — Coaching Report ## Week of 2026-05-25 – 2026-05-31 --- ## At a Glance | Calls Handled | Avg Handle Time | Top Product | Top Problem | Cases Documented | Cases Escalated | |---|---|---|---|---|---| | 5 | 12m 1s | MX5300 | CONNECTIVITY | — | — | --- ## Scorecard | Dimension | This Week | Calls Reviewed | |---|---|---| | Accuracy | 3.00 | 4 | | Protocol | 2.00 | 5 | | Communication | 2.25 | 4 | | Overall | 2.55 | 5 | *Scores reflect 4 calls with complete QA data (overall range: 1.2–3.0).* --- ## This Week's Coverage ### Models Supported | Model | Calls | Avg Score | |---|---|---| | MX5300 | 3 | 2.40 | Lower scores on MX5300 calls suggest a need for deeper familiarity with this model's troubleshooting flows, especially around connectivity and LED interpretation. ### Problem Categories | Category | Calls | Avg Score | Focus Area? | |---|---|---|---| | CONNECTIVITY | 3 | 2.10 | ✓ | | NO TROUBLESHOOTING NEEDED | 1 | 3.00 | | | ACCESS | 1 | 3.00 | | **Connectivity** is the clear focus area this week. The lower average score (2.1) points to gaps in handling complex connectivity scenarios—particularly around WAN validation, LED state interpretation, and reset procedures. --- ## What Went Well ### Technical accuracy on straightforward cases You maintained solid accuracy (score 4) on two calls where the issue was either clearly defined or fell into a known troubleshooting path: > **[#LTS00131168](https://linksys.happyfox.com/staff/ticket/131168/)** > *"Delete and reinstall the Linksys app. If the issue persists, call back for additional troubleshooting..."* ### Clear identification of product and issue You consistently identified the product model early in calls, which is essential for targeted troubleshooting: > **[#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/)** > *"MX5300, it cannot connect to the internet."* ### Valid first-step suggestions When faced with app instability, you correctly recommended deleting and reinstalling the app—a textbook first-line action aligned with KB guidance. --- ## Growth Opportunities ### Validate modem/WAN connectivity before proceeding In connectivity calls, skipping a quick check of the modem’s WAN link (e.g., checking its lights or asking the customer to confirm internet service is active) can lead to misdirected troubleshooting. **Good looks like:** after identifying the product, always ask, *"Is your modem showing a solid green/wifi-connected light?"* or *"Can you confirm your internet service is active with your ISP?"* before moving to router-level steps. > **[#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/)** > *No verification of modem/WAN status was performed.* ### Standardize MX5300 reset instructions The MX5300 reset procedure requires ~10 seconds of holding the reset button, not the 20 seconds you instructed. This discrepancy can prolong issue resolution. **Good looks like:** *"Hold the reset button for about 10 seconds until the LED blinks three times, then release."* Always cross-check reset times against the latest KB article before instructing customers. > **[#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/)** > *Incorrect reset duration (20 seconds) provided.* --- ## Next Week's Focus 1. **Add a WAN/modem check to every connectivity call** – make it the first question after identifying the product. 2. **Review MX5300 reset and LED guidance** – memorize the 10‑second reset and correct LED meanings (purple = pairing/transient, not readiness). 3. **Document every call** – even if you can’t resolve it, create a HappyFox ticket to capture details for follow‑up or escalation. 4. **Use the router’s web UI early** – when app‑based troubleshooting fails, guide customers to `http://myrouter.local` for direct diagnostics (firmware version, connected devices, node status). --- ## Technical Accuracy ### **Improvement** > *Agent gave incorrect reset duration (20 seconds instead of ~10 seconds) for MX5300 - contradicts KB guidance* [#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/) ### **Improvement** > *Agent misinterpreted LED colors - claimed purple light means readiness, but MX5300 purple indicates pairing mode or transient state* [#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/) ### **Improvement** > *Agent failed to verify modem/WAN connectivity - critical first step for Internet/WAN Setup issues not performed* [#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/) ### **Improvement** > *Provided contradictory information about compatible Mesh models (VLAB vs. 'white cylindrical' only) creating customer confusion* [#LTS00130823](https://linksys.happyfox.com/staff/ticket/130823/) ### **Improvement** > *No router-side diagnostics performed (web UI login, firmware check, node connectivity verification) despite customer reporting persistent app crashes and zero device visibility* [#LTS00131168](https://linksys.happyfox.com/staff/ticket/131168/) --- ## Coaching Moments ### **Improvement** > *"All three are red lights."* Agent misinterpreted LED colors – claimed purple light means readiness, but MX5300 purple indicates pairing mode or transient state. This misinterpretation can delay proper diagnosis. [#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/) ### **Improvement** > *"Hold the reset button for 20 seconds..."* Provided incorrect reset duration for MX5300 (should be ~10 seconds). This can prolong issue resolution and frustrate customers. [#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/) --- ## Escalation Lessons: What L2 Did *No escalation learning data was available this week. All calls were handled at Level 1 without handoff to engineering or escalation queues.* --- ## Coach Appendix *Internal note: This week’s data shows a critical need to reinforce WAN validation and MX5300-specific troubleshooting. The agent’s accuracy drops sharply on connectivity calls where modem status isn’t confirmed first. Focus next coaching on building a repeatable “WAN check” habit and memorizing MX5300 reset/LED guidance.* --- ## This Week's Calls | Case | Date | Score | Direction | Product | Category | Outcome | |---|---|---|---|---|---|---| | [#LTS00130823](https://linksys.happyfox.com/staff/ticket/130823/) | 2026-05-26 | 3.00 | INBOUND | MX5300 | NO TROUBLESHOOTING NEEDED | Abandoned or vague | | [#LTS00131001](https://linksys.happyfox.com/staff/ticket/131001/) | 2026-05-27 | — | INBOUND | MX2000 | CONNECTIVITY | — | | [#LTS00131168](https://linksys.happyfox.com/staff/ticket/131168/) | 2026-05-28 | 3.00 | INBOUND | MBE7000 | ACCESS | Callback set | | [#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/) | 2026-05-28 | 3.00 | INBOUND | MX5300 | CONNECTIVITY | Abandoned or vague | | [#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/) | 2026-05-28 | 1.20 | INBOUND | MX5300 | CONNECTIVITY | Abandoned or vague |