# Weiyu Zeng — 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 | 13m 45s | MBE7000 | CONNECTIVITY | — | — | --- ## Scorecard | Dimension | This Week | Calls Reviewed | |---|---|---| | Accuracy | 2.40 | 5 | | Protocol | 1.60 | 5 | | Communication | 2.00 | 5 | | Overall | 2.44 | 5 | *Scores reflect a small sample (5 calls). Overall range: 1.4 – 3.0.* --- ## This Week's Coverage ### Models Supported | Model | Calls | Avg Score | |---|---|---| | MBE7000 | 2 | 2.20 | | MX5300 | 1 | 3.00 | | MX4200 | 1 | 1.80 | | LN11011202 | 1 | 3.00 | Lower scores on MX4200 calls suggest a need for deeper familiarity with this model's troubleshooting flows. ### Problem Categories | Category | Calls | Avg Score | Focus Area? | |---|---|---|---| | CONNECTIVITY | 2 | 2.20 | ✓ | | SETUP | 2 | 3.00 | | | HARDWARE | 1 | 1.80 | ✓ | **Connectivity** and **Hardware** categories show lower average scores and merit focused attention. The single **HARDWARE** call (MX4200 mesh node) had significant accuracy and protocol gaps, indicating a need for stronger diagnostic frameworks in hardware-related cases. --- ## What Went Well ### High accuracy on complex setup > Agent correctly identified printer only supports 2.4 GHz and focused troubleshooting on that band; guided customer to check both SSIDs and confirmed they were visible and distinct. [#LTS00130991](https://linksys.happyfox.com/staff/ticket/130991/) ### Good communication under distress The agent maintained a polite and professional tone throughout the call with the MX4200 customer, allowing the customer to speak and avoiding talking over them, even when the customer expressed frustration about hardware failure assumptions. --- ## Growth Opportunities ### Low accuracy across multiple calls Several calls suffered from technical inaccuracies that undermined customer confidence and resolution progress. For example: > Agent provided incorrect reset duration (20-30s) for MX4200; KB specifies ~10s. Also invented undocumented 'rescue mode' power-cycling procedure. [#LTS00130999](https://linksys.happyfox.com/staff/ticket/130999/) **What better looks like:** - Always verify reset durations against the official KB before advising customers. - Avoid inventing procedures; if uncertain, acknowledge the gap and offer to check documentation or escalate. ### Protocol compliance gaps Calls frequently ended without clear next steps, documentation, or verification of resolution. For instance: > Agent incorrectly stated solid white LED on MX6200 means node is already meshed; KB states solid white = powered on only, not meshed. Failed to offer valid pairing method (5-press, Pair button, factory reset). [#LTS00131376](https://linksys.happyfox.com/staff/ticket/131376/) **What better looks like:** - Use a consistent call closure script: confirm next steps, document outcomes, and schedule follow-up if needed. - Always verify the customer’s ability to perform requested actions before ending the call. --- ## Next Week's Focus 1. **Verify technical details before advising** — cross-check reset durations, LED meanings, and terminology against KB articles for every device type. 2. **Implement a closure checklist** — confirm next steps, document serial numbers, and schedule callbacks when resolution isn’t fully verified. 3. **Practice concise, accurate terminology** — replace “5Gbps/6Gbps” with “5 GHz/6 GHz” and use band-specific language when discussing Wi‑Fi. 4. **Build confidence with hardware diagnostics** — ask targeted diagnostic questions before assuming hardware failure (e.g., LED patterns, app behavior, Ethernet tests). --- ## Technical Accuracy ### **Improvement** > Agent provided incorrect reset duration (20-30s) for MX4200; KB specifies ~10s. Also invented undocumented 'rescue mode' power-cycling procedure. [#LTS00130999](https://linksys.happyfox.com/staff/ticket/130999/) ### **Improvement** > Agent incorrectly stated solid white LED on MX6200 means node is already meshed; KB states solid white = powered on only, not meshed. Failed to offer valid pairing method (5-press, Pair button, factory reset). [#LTS00131376](https://linksys.happyfox.com/staff/ticket/131376/) ### **Improvement** > Agent used incorrect technical terminology: '5Gbps' and '6Gbps' instead of '5 GHz' and '6 GHz' when discussing Wi-Fi bands on MBE7000. [#LTS00131376](https://linksys.happyfox.com/staff/ticket/131376/) ### **Improvement** > Agent provided vague channel-changing guidance (select between 1-6 or 6-11) without tying to printer requirements or verifying router model/access. [#LTS00130991](https://linksys.happyfox.com/staff/ticket/130991/) ### **Strength** > Agent correctly identified printer only supports 2.4 GHz and focused troubleshooting on that band; guided customer to check both SSIDs and confirmed they were visible and distinct. [#LTS00130991](https://linksys.happyfox.com/staff/ticket/130991/) --- ## Coaching Moments ### **Improvement** > Agent provided vague channel-changing guidance (select between 1-6 or 6-11) without tying to printer requirements or verifying router model/access. [#LTS00130991](https://linksys.happyfox.com/staff/ticket/130991/) *Note: Instructions for changing the 2.4 GHz channel were unclear and not specific to the printer’s needs. Always confirm the router model, verify access to the admin interface, and tie channel changes to the device’s capabilities.* --- ## Escalation Lessons: What L2 Did No escalated cases were recorded this week. The two lowest-scoring calls (MX4200 and MX6200) were unresolved but not formally escalated. Had they been escalated, Level 2 would likely have focused on: - **MX4200:** Verifying warranty status, confirming exact LED behavior, and guiding a proper 10‑second factory reset rather than the incorrect 20‑30 second procedure used. - **MX6200:** Providing accurate pairing instructions (5‑press Cognitive Mesh reset, Pair button, or web UI) and validating router access before proceeding. **L1 learning points for next time:** 1. Collect model, serial number, and firmware version upfront for any hardware issue. 2. Reference the exact KB section for LED states and reset procedures before advising customers. 3. Offer at least two valid pairing/recovery paths and confirm the customer can access them before closing the call. --- ## Coach Appendix *Highest-signal trend:* Repeated technical inaccuracies (reset durations, LED interpretation, Wi‑Fi terminology) and inconsistent call closure led to low accuracy and protocol scores. Focus next week on verifying KB details for every device before advising and implementing a structured closure checklist to ensure documented next steps and follow‑up where needed.* --- ## This Week's Calls | Case | Date | Score | Direction | Product | Category | Outcome | |---|---|---|---|---|---|---| | [#LTS00130991](https://linksys.happyfox.com/staff/ticket/130991/) | 2026-05-27 01:00:09+00:00 | 3.0 | INBOUND | LN11011202 | SETUP | Pending | | [#LTS00130999](https://linksys.happyfox.com/staff/ticket/130999/) | 2026-05-27 03:32:55+00:00 | 1.8 | INBOUND | MX4200 | HARDWARE | Callback set | | [#LTS00131375](https://linksys.happyfox.com/staff/ticket/131375/) | 2026-05-29 07:02:07+00:00 | 3.0 | INBOUND | MX5300 | SETUP | None – call ended without resolution, case creation, or clear next step | | [#LTS00131376](https://linksys.happyfox.com/staff/ticket/131376/) | 2026-05-29 07:17:09+00:00 | 3.0 | INBOUND | MBE7000 | CONNECTIVITY | ✓ Likely resolved | | [#LTS00131376](https://linksys.happyfox.com/staff/ticket/131376/) | 2026-05-29 07:55:59+00:00 | 1.4 | INBOUND | MBE7000 | CONNECTIVITY | None provided; call ended without resolution, escalation, or follow-up |