# 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 06s | 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 performance shows room for growth, especially in protocol adherence and technical accuracy.* --- ## This Week's Coverage ### Models Supported | Model | Calls | Avg Score | |---|---|---| | MBE7000 | 2 | 2.20 | | MX4200 | 1 | 1.80 | | MX5300 | 1 | 3.00 | | LN11011202 | 1 | 3.00 | **Key pattern:** Lower scores on MBE7000 and MX4200 calls suggest a need for deeper familiarity with Wi‑Fi 7 mesh troubleshooting and MX series reset procedures. ### Problem Categories | Category | Calls | Avg Score | Focus Area? | |---|---|---|---| | CONNECTIVITY | 2 | 2.20 | ✓ | | SETUP | 2 | 3.00 | | | HARDWARE | 1 | 1.80 | ✓ | **Connectivity and hardware categories** are driving the lower average scores. Focus on these areas will have the biggest impact on overall performance. --- ## What Went Well ### Accurate device identification and data collection > **Accurate serial number collection** > "Yes, 59A, yes, 10M, yes, yes, OK, good, that's all we need, we've noted it down, yes." *Collected critical identification data efficiently, which supports future troubleshooting and case documentation.* [#LTS00131376](https://linksys.happyfox.com/staff/ticket/131376/) ### Structured guidance for configuration changes > **Structured troubleshooting guidance** > "Guided customer to connect to router Wi‑Fi and access http://[REDACTED_PHONE]; entered router’s five-digit admin code; changed SSID naming to separate 2.4 GHz, 5 GHz, and 6 GHz networks; disabled Multi-Link Operation (MLO)." *Provided clear, step-by-step instructions that align with known resolution paths for Wi‑Fi 7 mesh instability.* [#LTS00131376](https://linksys.happyfox.com/staff/ticket/131376/) --- ## Growth Opportunities ### Technical accuracy in guidance > **Inaccurate terminology and guidance** > "Provided inaccurate technical terminology (e.g., '5Gbps', '6Gbps' instead of '5 GHz', '6 GHz') and misrepresented the reason for 6 GHz unavailability as a national policy/usage right issue..." *What good looks like:* Use precise frequency terminology (GHz, not Gbps). Explain regional regulatory or device capability limitations clearly, not as policy restrictions. Verify each step before moving forward. ### Verification before closure > **No verification of resolution** > "Did not verify the customer's internet connectivity after configuration changes... The agent never verified that the suggested changes restored internet connectivity before ending the call." *What good looks like:* After guiding configuration changes, always confirm the customer can now access the internet or achieve the desired outcome. If not, continue troubleshooting or schedule a follow‑up. --- ## Next Week's Focus 1. **Double-check terminology** — Before mentioning bandwidth speeds or frequencies, confirm you’re using the correct units (GHz for frequency, Mbps for speed). 2. **Verify each step** — After any configuration change, ask the customer to confirm the result (e.g., “Can you now see the internet icon?” or “Is the printer connecting now?”). 3. **Collect router model and access details early** — Ask for the router model and confirm the customer can access the admin interface before diving into specific steps. 4. **Use KB‑validated reset procedures** — For MX series devices, follow documented reset durations (~10 seconds) and avoid inventing undocumented “modes.” --- ## Technical Accuracy ### **Improvement** > *No transcript quote available* > Failed to verify customer access to router admin interface (password, URL) before providing channel-changing guidance. Instructions were vague and not tied to printer requirements. [#LTS00130991](https://linksys.happyfox.com/staff/ticket/130991/) ### **Improvement** > *No transcript quote available* > Advised incorrect reset duration (20–30s) for MX4200; KB specifies ~10s. Invented undocumented ‘rescue mode’ power-cycling procedure. No verification of resolution before closing call. [#LTS00130999](https://linksys.happyfox.com/staff/ticket/130999/) ### **Improvement** > *No transcript quote available* > Provided factually incorrect LED interpretation for MX6200: claimed solid white LED means node is already meshed, which contradicts KB guidance (solid white = powered on, not meshed). No valid pairing instructions were offered. [#LTS00131376](https://linksys.happyfox.com/staff/ticket/131376/) ### **Improvement** > *No transcript quote available* > No technical support, case creation, or escalation provided despite customer's urgent distress and mental health concerns. Repeated automated hold messages dominated the call. [#LTS00131375](https://linksys.happyfox.com/staff/ticket/131375/) --- ## Coaching Moments ### **Strength** > **Accurate serial number collection** > "Yes, 59A, yes, 10M, yes, yes, OK, good, that's all we need, we've noted it down, yes." *Collected critical identification data efficiently, which supports future troubleshooting and case documentation.* [#LTS00131376](https://linksys.happyfox.com/staff/ticket/131376/) ### **Improvement** > **Incomplete verification of resolution** > "Customer instructed to monitor the network for a few days after changes; no immediate verification of fix." *Did not confirm whether separating SSIDs and disabling MLO resolved the intermittent disconnect issue before closing the call.* [#LTS00131376](https://linksys.happyfox.com/staff/ticket/131376/) --- ## Escalation Lessons: What L2 Did *No escalated cases were recorded for this week. All cases were closed at Level 1, though several would benefit from escalation due to unresolved technical issues or customer distress.* --- ## Coach Appendix *This week’s most significant trend is inconsistent technical accuracy, especially around MX series reset procedures and Wi‑Fi 7 mesh configuration. Focus next week on verifying each step, using precise terminology, and confirming resolution before closing. The high-distress call (ticket #LTS00131375) highlights the need for empathy and escalation protocols when customers express severe urgency or mental health concerns.* --- ## 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.00 | INBOUND | LN11011202 | SETUP | Pending | | [#LTS00130999](https://linksys.happyfox.com/staff/ticket/130999/) | 2026-05-27 03:32:55+00:00 | 1.80 | INBOUND | MX4200 | HARDWARE | ↑ Escalated | | [#LTS00131375](https://linksys.happyfox.com/staff/ticket/131375/) | 2026-05-29 07:02:07+00:00 | 3.00 | INBOUND | MX5300 | SETUP | ⚠ Closed incorrectly | | [#LTS00131376](https://linksys.happyfox.com/staff/ticket/131376/) | 2026-05-29 07:17:09+00:00 | 3.00 | INBOUND | MBE7000 | CONNECTIVITY | ✓ Likely resolved | | [#LTS00131376](https://linksys.happyfox.com/staff/ticket/131376/) | 2026-05-29 07:55:59+00:00 | 1.40 | INBOUND | MBE7000 | CONNECTIVITY | — |