# weiyu.zeng@concentrix.com — 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 | |---|---|---|---|---|---| | 3 | 18m 12s | FGW5500 | HARDWARE | 3 | 2 | --- ## Scorecard | Dimension | This Week | Calls Reviewed | |---|---|---| | Accuracy | 2.00 | 3 | | Protocol | 2.00 | 3 | | Communication | 1.67 | 3 | | Overall | 2.63 | 3 | *Scores reflect 3 calls reviewed. Overall score range: 1.9 – 3.0.* --- ## This Week's Coverage ### Models Supported | Model | Calls | Avg Score | |---|---|---| | MX6200 | 1 | 1.90 | | FGW5500 | 1 | 3.00 | | MBE7000 | 1 | 3.00 | Lower scores on MX6200 calls suggest a need to reinforce correct reset procedures and troubleshooting flow for this model. ### Problem Categories | Category | Calls | Avg Score | Focus Area? | |---|---|---|---| | HARDWARE | 2 | 2.45 | ✓ | | SETUP | 1 | 3.00 | | **HARDWARE** calls show a lower average score (2.45). This pattern suggests a need for more structured hardware diagnostics and clearer communication around warranty processes. Focus on verifying WAN/SIM status, using precise reset durations, and confirming warranty eligibility before escalation. --- ## What Went Well ### Initiated valid warranty claims > Collected essential customer information (name, phone, email, serial number, purchase channel, and date). Initiated a valid warranty claim for hardware replacement, aligning with support protocol for in-warranty devices. [#LTS00131007](https://linksys.happyfox.com/staff/ticket/131007/) ### Clear communication of warranty process > Provided clear timeline: email with instructions within 5–10 minutes. [#LTS00131160](https://linksys.happyfox.com/staff/ticket/131160/) --- ## Growth Opportunities ### Incorrect reset guidance and technical inaccuracies The agent used an incorrect reset duration for MX6200 (20 seconds instead of the standard ~10 seconds) and introduced the non-existent term **“Nauta”**, which confused the customer and disrupted the troubleshooting flow. **What better looks like:** - Use the exact reset duration specified in KB articles (e.g., 10 seconds for MX6200). - Avoid using undefined or non-standard terms. - Confirm the customer understands each step before moving to the next. [#LTS00131160](https://linksys.happyfox.com/staff/ticket/131160/) ### Missed basic troubleshooting steps For the MBE7000 setup issue, the agent did not verify the correct admin URL (`http://myrouter.info`), skipped essential steps like power-cycling the modem/router, and failed to guide the customer through basic IP verification via the Linksys app or network settings. **What better looks like:** - Always verify the correct admin URL for the specific product (e.g., MBE7000 uses `http://myrouter.info`). - Follow a structured troubleshooting flow: power-cycle modem and router, check WAN cable, confirm physical connections, and verify LAN IP via app or network settings. - Provide self-help resources or KB articles when appropriate. [#LTS00131189](https://linksys.happyfox.com/staff/ticket/131189/) --- ## Next Week's Focus - **Practice precise reset instructions**: Memorize or reference KB articles for exact reset durations per model (e.g., 10 seconds for MX6200, 10–15 seconds for FGW5500). - **Adopt a structured troubleshooting flow**: For hardware issues, always verify WAN/SIM status, perform a modem power-cycle, and confirm physical connections before concluding a fault. - **Use product-specific admin URLs**: Commit to correct default URLs (e.g., `http://myrouter.info` for MBE7000) and confirm them early in setup calls. - **Enhance communication clarity**: Avoid jargon or undefined terms; paraphrase complex steps into simple, actionable instructions. --- ## Technical Accuracy ### **Improvement** Did not verify SIM card status or WAN connection for FGW5500, which are critical for 4G/5G routers. Reset duration instruction was ambiguous (10 seconds instead of 10-15 seconds). [#LTS00131007](https://linksys.happyfox.com/staff/ticket/131007/) ### **Improvement** Failed to identify correct admin URL for MBE7000 (should be http://myrouter.info, not [REDACTED_PHONE]). Skipped basic troubleshooting steps (power-cycle, LAN check, IP verification). [#LTS00131189](https://linksys.happyfox.com/staff/ticket/131189/) ### **Improvement** Incorrect reset duration for MX6200 (20s instead of ~10s). Used non-existent term 'Nauta' multiple times, creating confusion. [#LTS00131160](https://linksys.happyfox.com/staff/ticket/131160/) --- ## Escalation Lessons: What L2 Did ### [#LTS00131007](https://linksys.happyfox.com/staff/ticket/131007/) — Resolved by Level 2 - **What L1 saw:** Customer reported a red globe light (no signal) and poor Wi‑Fi performance on an FGW5500. After a reset showed flashing blue lights but no Wi‑Fi SSID, L1 concluded hardware failure and opened a warranty claim. - **Why it escalated:** The case was escalated because L1 did not verify WAN/SIM status, perform a modem power-cycle, or check firmware—critical steps for 4G/5G routers. - **What L2 did:** L2 likely reviewed WAN/SIM status, performed a full modem power-cycle, and confirmed hardware fault, leading to warranty claim approval. - **Current state:** Resolved via warranty replacement. - **L1 learning points:** 1. For 4G/5G routers like FGW5500, always verify SIM/WAN status and perform a modem power-cycle before concluding hardware failure. 2. Use the exact reset duration (10–15 seconds) and confirm the customer completes it fully. 3. Document all troubleshooting steps clearly to support escalation decisions. ### [#LTS00131160](https://linksys.happyfox.com/staff/ticket/131160/) — Resolved by Level 2 - **What L1 saw:** MX6200 Velop 6E was not broadcasting its Wi‑Fi SSID. L1 performed an incorrect 20‑second reset, repeated power cycles, and concluded hardware failure without verifying warranty or performing diagnostic checks. - **Why it escalated:** Escalation trigger was L1’s incorrect technical guidance (wrong reset duration, use of undefined term “Nauta”) and failure to follow standard troubleshooting flow. - **What L2 did:** L2 likely re-ran the correct ~10‑second reset, verified LED behavior, checked for firmware issues, and either repaired or confirmed hardware fault for replacement. - **Current state:** Resolved via warranty replacement. - **L1 learning points:** 1. Always use model-specific reset durations (e.g., ~10 seconds for MX6200). 2. Avoid undefined terms; use clear, standard language. 3. Follow a structured diagnostic flow: reset → power-cycle → firmware check → hardware verification before escalation. --- ## Coach Appendix **Highest-signal weekly trend:** All three calls involved hardware or setup issues where missing or inaccurate troubleshooting steps led to escalation. The recurring gaps include incorrect reset durations, failure to verify WAN/SIM status on 4G/5G devices, and overlooking basic connectivity checks (power-cycle, LAN verification). These patterns point to a need for reinforced protocol adherence and technical accuracy in hardware diagnostics. --- ## This Week's Calls | Case | Date | Score | Direction | Product | Category | Outcome | |---|---|---|---|---|---|---| | [#LTS00131007](https://linksys.happyfox.com/staff/ticket/131007/) | 2026-05-27 07:30:47+00:00 | 3.00 | INBOUND | FGW5500 | HARDWARE | ↑ Escalated | | [#LTS00131160](https://linksys.happyfox.com/staff/ticket/131160/) | 2026-05-28 02:08:02+00:00 | 1.90 | INBOUND | MX6200 | HARDWARE | ↑ Escalated | | [#LTS00131189](https://linksys.happyfox.com/staff/ticket/131189/) | 2026-05-28 06:51:08+00:00 | 3.00 | INBOUND | MBE7000 | SETUP | ↻ Callback set |