# Xiao Ge Ji — 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 | |---|---|---|---|---|---| | 4 | 9m 50s | MX5300 | SETUP | — | — | --- ## Scorecard | Dimension | This Week | Calls Reviewed | |---|---|---| | Accuracy | 3.00 | 4 | | Protocol | 1.75 | 4 | | Communication | 2.00 | 4 | | Overall | 2.63 | 4 | *Scores reflect data from 4 calls reviewed this week (overall range: 1.5–3.0).* --- ## This Week's Coverage ### Models Supported | Model | Calls | Avg Score | |---|---|---| | MX5300 | 1 | 1.50 | | LN1400 | 1 | 3.00 | | MX4200 | 1 | 3.00 | | E8450 | 1 | 3.00 | **Pattern to note:** The single MX5300 call scored notably lower (1.5 overall), suggesting a need for additional practice with this model’s mesh diagnostics and customer education. ### Problem Categories | Category | Calls | Avg Score | Focus Area? | |---|---|---|---| | SETUP | 2 | 3.00 | | | NO TROUBLESHOOTING NEEDED | 1 | 1.50 | ✓ | | HARDWARE | 1 | 3.00 | | **SETUP calls** performed well overall, but the “NO TROUBLESHOOTING NEEDED” category (customer inquiry about mesh signal behavior) scored low. This pattern suggests an opportunity to strengthen proactive guidance and self-help pathways for non-technical product questions. --- ## What Went Well ### Proactive contact capture for callbacks > “We recommend that you call us again when you are near the product.” [#LTS00131006](https://linksys.happyfox.com/staff/ticket/131006/) *You set clear expectations for a follow-up call, ensuring the customer knows exactly when and how to reconnect for effective troubleshooting.* ### Accurate mesh topology advice > “What you mean is, you have two satellite units, A and B… adding a middle node can improve backhaul signal.” [#LTS00131167](https://linksys.happyfox.com/staff/ticket/131167/) *Your explanation aligned with Linksys knowledge base guidance for Velop mesh systems, providing the customer with a technically sound next step.* --- ## Growth Opportunities ### Collect essential product details before guidance **Current gap:** Critical information (model, serial number, warranty status) was missing in multiple calls, leading to generic advice and missed troubleshooting opportunities. **What good looks like:** - Verify the exact product model and serial number within the first 30 seconds of the call. - Confirm warranty status early to guide appropriate next steps (repair, replacement, or self-help). > “Do you have the product with you now? Possibly… Hmm. We need to look at that laptop. Do you have the product with you?” [#LTS00131006](https://linksys.happyfox.com/staff/ticket/131006/) **Next step:** Add a quick script check: “May I confirm the exact model number and serial number on the device?” before diving into troubleshooting. ### Use documented reset procedures and avoid non-standard steps **Current gap:** The EA8450 factory reset was performed incorrectly (20–30 second hold vs. KB-specified 10 seconds), and a complex unplug/replug sequence was introduced without KB backing. **What good looks like:** - Follow KB-documented reset times precisely. - Avoid inventing recovery steps; if standard methods fail, escalate or offer verified self-help resources. > “Attempted factory reset with 20-second hold… Attempted second factory reset with 30-second hold… Introduced non-standard recovery method involving repeated unplug/replug cycles.” [#LTS00131191](https://linksys.happyfox.com/staff/ticket/131191/) **Next step:** Reference the `universal_mesh_full_rebuild.md` KB article for reset durations and stick to published steps. --- ## Next Week's Focus 1. **Start every call with a product snapshot:** Model, serial, warranty status, and current LED state in the first 30 seconds. 2. **Reset durations from KB only:** Practice the 10-second reset for EA series and other model-specific timings. 3. **When signal or mesh questions arise:** Offer a concise self-help link or KB article before suggesting hardware purchases. 4. **Call control:** Reduce filler words (“yes, yes, okay”) and restate the issue clearly after active listening. --- ## Technical Accuracy ### **Improvement** > *Failed to collect essential product details (model/serial) before providing guidance, violating protocol for product-specific support.* [#LTS00131006](https://linksys.happyfox.com/staff/ticket/131006/) ### **Improvement** > *Incorrect factory-reset procedure (20–30s hold instead of 10s) for EA8450 model. KB specifies 10-second reset for EA series.* [#LTS00131191](https://linksys.happyfox.com/staff/ticket/131191/) ### **Improvement** > *Failed to verify warranty status or support eligibility before suggesting paid hardware purchase, critical for mesh performance issues.* [#LTS00131167](https://linksys.happyfox.com/staff/ticket/131167/) ### **Strength** > *Correctly confirmed that adding a middle node can improve backhaul signal in a mesh network, consistent with Linksys KB for Velop systems.* [#LTS00131167](https://linksys.happyfox.com/staff/ticket/131167/) --- ## Coaching Moments ### **Improvement** > “We may also need to check that laptop.” [#LTS00131006](https://linksys.happyfox.com/staff/ticket/131006/) *Shifting focus to a laptop the customer did not mention delayed troubleshooting and confused the customer. Pull the call back to the reported issue (TV Wi‑Fi detection) and gather router details first.* ### **Improvement** > “Customer will consider repositioning the satellite or purchasing an additional MX-5300 unit.” [#LTS00131167](https://linksys.happyfox.com/staff/ticket/131167/) *Suggesting a hardware purchase without first running diagnostics or offering self‑help resources misses an opportunity to resolve the issue at no cost to the customer. Offer signal-strength checks, admin‑UI access, or firmware updates before recommending new hardware.* ### **Improvement** > “This model is ATLAS-6 series. On the lights…” [#LTS00131174](https://linksys.happyfox.com/staff/ticket/131174/) *Excessive filler (“yes, yes, okay, okay”) and fragmented dialogue made it hard to pinpoint the real issue. Practice concise restatements: “I understand the Wi‑Fi network isn’t appearing and the device shows a red light. Let’s verify the exact model and LED behavior together.”* --- ## Escalation Lessons: What L2 Did *No escalations occurred this week, so there are no L2 resolution patterns to review. Focus remains on strengthening frontline diagnostics to avoid future escalations.* --- ## Coach Appendix *High-signal trend:* All four calls ended with callbacks or unresolved status, indicating a consistent gap in collecting product details and executing documented troubleshooting flows before setting next steps. Prioritizing model/serial capture and KB-aligned procedures will reduce callbacks and improve resolution rates. *No new transcript quotes introduced beyond those already surfaced in the main report.*