# 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 | 4 | | Communication | 2.25 | 4 | | Overall | 2.55 | 4 | *4 calls reviewed; score range: 1.2 – 3.0* --- ## This Week's Coverage ### Models Supported | Model | Calls | Avg Score | |---|---|---| | MX5300 | 3 | 2.40 | | MBE7000 | 1 | 3.00 | | MX2000 | 1 | — | Lower scores on MX5300 calls suggest a need to reinforce product-specific troubleshooting steps and documentation practices. ### Problem Categories | Category | Calls | Avg Score | Focus Area? | |---|---|---|---| | CONNECTIVITY | 3 | 2.07 | ✓ | | ACCESS | 1 | 3.00 | | | NO TROUBLESHOOTING NEEDED | 1 | 3.00 | | **Connectivity** shows the lowest average score (2.07). The pattern suggests challenges in diagnosing and resolving Internet/WAN Setup issues — particularly around modem verification, reset procedures, and LED interpretation. Focus here will improve overall effectiveness. --- ## What Went Well ### Accurate model identification and guidance > **Correctly identified the product model (MX5300) and confirmed it can act as the primary router due to superior performance, providing accurate guidance.** [#LTS00130823](https://linksys.happyfox.com/staff/ticket/130823/) This demonstrates strong product knowledge and the ability to deliver clear, actionable advice — even when the customer’s question is nuanced. ### Valid first-line troubleshooting step > **Suggested a valid first-line troubleshooting step (delete and reinstall app) that aligns with KB guidance for app instability.** [#LTS00131168](https://linksys.happyfox.com/staff/ticket/131168/) Offering a textbook-aligned solution shows you’re grounded in best practices and can apply them to real customer scenarios. --- ## Growth Opportunities ### Incomplete case documentation The system shows **no HappyFox cases were created** despite collecting customer details and indicating intent to document. Good documentation protects the customer and creates a clear audit trail. **What better looks like:** After confirming customer information (name, email, product details), **immediately create a HappyFox ticket** and reference its number in all subsequent communication. This ensures continuity if the customer calls back or if escalation is needed later. ### Inconsistent technical guidance Several calls contained **inaccurate or incomplete technical instructions**, especially around reset durations and LED interpretation, which led to confusion and unresolved issues. **What better looks like:** - **Verify reset times** against the official KB before instructing customers (e.g., MX series resets are ~10 seconds, not 20). - **Confirm modem/WAN connectivity** as a first step in any Internet/WAN Setup issue — ask about modem lights and perform a simple ping test if the customer is comfortable. - **Interpret LEDs accurately** using product-specific guides (e.g., MX5300 purple means pairing mode, not readiness). --- ## Next Week's Focus 1. **Create a HappyFox ticket on every call** where you collect customer contact details or discuss troubleshooting steps. Reference the ticket number before closing the call. 2. **Standardize reset instructions**: When guiding a reset, pull the exact duration from the KB and confirm the customer executed it correctly before moving forward. 3. **Add modem/WAN verification** to your opening troubleshooting branch for connectivity issues — ask “Are the modem lights solid?” and offer a quick connectivity test if appropriate. 4. **Use product-specific LED guides**: Keep a quick reference handy for common MX and Velop LED meanings to avoid misinterpretation. --- ## Technical Accuracy ### **Improvement** > Incorrect reset time for MX5300 (20 seconds instead of ~10 seconds), leading to potential customer confusion and unresolved issue. [#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/) **Note:** Reset times are a critical detail. Always cross-check the official KB before instructing customers — a 10-second reset is the correct MX series procedure. This misstep created unnecessary complexity and left the issue unresolved. ### **Improvement** > Failed to verify modem/WAN connectivity, a critical first step in Internet/WAN Setup issues, leading to incomplete troubleshooting. [#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/) **Note:** Skipping modem verification risks misdiagnosing the root cause. A quick “Are the modem lights solid?” or guiding the customer through a simple ping test can save time and prevent looping. ### **Improvement** > No case number created or referenced, no KB article cited, and no follow-up plan established despite open questions about Mesh compatibility. [#LTS00130823](https://linksys.happyfox.com/staff/ticket/130823/) **Note:** Documenting the interaction protects the customer and creates a roadmap for future contact. Always create a ticket when you gather contact info or discuss troubleshooting. ### **Strength** > Correctly identified the product model (MX5300) and confirmed it can act as the primary router due to superior performance, providing accurate guidance. [#LTS00130823](https://linksys.happyfox.com/staff/ticket/130823/) **Note:** Spot-on product knowledge and clear guidance — a great example of how to answer a nuanced compatibility question. --- ## Coaching Moments ### **Improvement** > **“If your 5350 is the main router, then it's the MX2000, 4200, 5500 models I just mentioned. There are also some older ones, and the really old ones probably can't be sold anymore. Or, our new models…”** **Note:** This created confusion by mixing VLAB series compatibility with a vague “white cylindrical” statement. Better guidance would have been: “For Mesh, stick with the VLAB series (MX2000, MX4200, MX5500). The MX5300 can serve as the primary router because it’s the most powerful node.” ### **Improvement** > **“All three are red lights.”** **Note:** Misinterpreting MX5300 LED states (claiming red means readiness) is inaccurate — red indicates a problem. The agent should have asked about modem lights first and explained that solid green/white means readiness, while red signals an issue needing reset or modem verification. --- ## Escalation Lessons: What L2 Did No escalated cases were logged this week, and the HappyFox activity shows **0 cases escalated**. This suggests opportunities to improve early identification of complex issues before they become repeat contacts. When customers mention account/billing triggers (e.g., unpaid ISP bills) or persistent unresolved symptoms, consider documenting as a potential escalation candidate even if the call ends without a formal handoff. --- ## Coach Appendix *Highest-signal trend:* **Technical inaccuracy in reset procedures and LED interpretation** contributed to all unresolved MX5300 connectivity calls. Pairing this with inconsistent case documentation created a cycle of repeat contacts. Next coaching should focus on standardized verification steps (modem/WAN check, exact reset times) and disciplined ticket creation to break this pattern. --- ## This Week's Calls | Case | Date | Score | Direction | Product | Category | Outcome | |---|---|---|---|---|---|---| | [#LTS00130823](https://linksys.happyfox.com/staff/ticket/130823/) | 2026-05-26 05:54 | 3.0 | INBOUND | MX5300 | NO TROUBLESHOOTING NEEDED | — | | [#LTS00131001](https://linksys.happyfox.com/staff/ticket/131001/) | 2026-05-27 05:43 | — | INBOUND | MX2000 | CONNECTIVITY | — | | [#LTS00131168](https://linksys.happyfox.com/staff/ticket/131168/) | 2026-05-28 02:51 | 3.0 | INBOUND | MBE7000 | ACCESS | ✓ Likely resolved | | [#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/) | 2026-05-28 06:25 | 3.0 | INBOUND | MX5300 | CONNECTIVITY | — | | [#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/) | 2026-05-28 06:30 | 1.2 | INBOUND | MX5300 | CONNECTIVITY | — |