# 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 | |---|---|---| | FGW5500 | 1 | 3.00 | | MX6200 | 1 | 1.90 | | MBE7000 | 1 | 3.00 | **Pattern Note:** The MX6200 call scored notably lower (1.9 overall), indicating a need for closer attention to troubleshooting flows and technical accuracy on this model. ### Problem Categories | Category | Calls | Avg Score | Focus Area? | |---|---|---|---| | HARDWARE | 2 | 2.45 | ✓ | | SETUP | 1 | 3.00 | | **HARDWARE (Avg 2.45)** The two hardware cases (FGW5500 and MX6200) show mixed results. The lower average suggests inconsistencies in diagnosing and resolving hardware faults—particularly around reset procedures, SIM/WAN verification, and clear escalation handoffs. --- ## What Went Well ### Correctly initiated warranty claims for hardware failures The agent efficiently gathered critical customer details (serial numbers, purchase information, contact data) and initiated valid warranty claims for both the FGW5500 and MX6200 cases, aligning with support protocols. > “Warranty claim opened for hardware replacement. Customer to email photos of device serial label and receipt. Replacement to be arranged after claim approval (1-2 business days).” [#LTS00131007](https://linksys.happyfox.com/staff/ticket/131007/) --- ## Growth Opportunities ### Inaccurate technical guidance and missed troubleshooting steps **What happened:** - **MX6200:** The agent used an incorrect 20‑second reset duration (should be ~10 seconds) and introduced a non‑existent term “Nauta,” confusing the customer. - **FGW5500:** Critical steps for 4G/5G routers—SIM/WAN verification and modem power‑cycle—were skipped. **What good looks like:** - Always verify reset durations against KB articles before instructing customers. - For 4G/5G routers, confirm SIM status and perform a modem power‑cycle as first‑line troubleshooting. - Avoid using unsupported terminology; stick to product‑specific language. > “Provided wrong 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/) ### Failure to provide the correct admin URL for MBE7000 **What happened:** The agent did not identify that the MBE7000’s admin interface uses `http://myrouter.info`, instructing the customer to use an incorrect IP address instead. Basic troubleshooting steps (power‑cycling, LAN checks) were also omitted. **What good looks like:** - Memorize or quickly reference model‑specific admin URLs (e.g., MBE7000 → `myrouter.info`). - Run a structured troubleshooting sequence: power‑cycle modem/router, verify LAN connection, confirm IP via Linksys app or network settings, then attempt UI access. > “Did not verify the correct admin URL for MBE7000 (should be http://myrouter.info, not [REDACTED_PHONE]). Skipped basic troubleshooting steps like power-cycling and LAN checks.” [#LTS00131189](https://linksys.happyfox.com/staff/ticket/131189/) --- ## Next Week's Focus 1. **Double‑check reset durations** against KB articles before guiding any customer through a factory reset. 2. **Add WAN/SIM verification** as a standard step for all 4G/5G routers (FGW, MX, MR series). 3. **Memorize or quickly pull up** model‑specific admin URLs (e.g., MBE7000 = `myrouter.info`, Velop = `myvelop.net`). 4. **Send self‑help resources** (KB articles, setup guides) during or immediately after the call when applicable—especially for setup‑related issues. --- ## Technical Accuracy ### **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/) ### **Improvement** Failed to verify WAN/SIM status or perform modem power-cycle for FGW5500, critical steps for 4G/5G routers. [#LTS00131007](https://linksys.happyfox.com/staff/ticket/131007/) ### **Improvement** Did not verify the correct admin URL for MBE7000 (should be http://myrouter.info, not [REDACTED_PHONE]). Skipped basic troubleshooting steps like power-cycling and LAN checks. [#LTS00131189](https://linksys.happyfox.com/staff/ticket/131189/) --- ## Escalation Lessons: What L2 Did ### [#LTS00131007](https://linksys.happyfox.com/staff/ticket/131007/) — Resolved by Level 2 | Aspect | Details | |---|---| | **What L1 saw** | Customer reported a red-globe (no signal) issue on an FGW5500. After a reset showed flashing blue lights but no Wi‑Fi, L1 concluded hardware failure. | | **Why it escalated** | The case was escalated because L1 skipped critical 4G/5G diagnostics (SIM/WAN verification, modem power‑cycle) and jumped straight to warranty claim. | | **What L2 did** | L2 likely reviewed the case, confirmed the need for hardware replacement, and guided the customer through the warranty claim process (photos of serial/label, receipt). No further technical steps were required because the hardware fault was clear. | | **Current state** | Resolved via warranty replacement. | | **L1 learning points** | 1. **Always verify SIM/WAN status** on 4G/5G routers before concluding hardware failure. 2. **Perform a modem power‑cycle** as a first step—it can resolve intermittent signal issues. 3. **Document all diagnostics** (LED behavior, reset outcome, SIM status) to provide a complete picture for escalation. | ### [#LTS00131160](https://linksys.happyfox.com/staff/ticket/131160/) — Resolved by Level 2 | Aspect | Details | |---|---| | **What L1 saw** | MX6200 Velop 6E wouldn’t broadcast its Wi‑Fi SSID. L1 performed an incorrect 20‑second reset, repeated power cycles, and ultimately concluded hardware failure. | | **Why it escalated** | Escalation occurred because L1 used inaccurate troubleshooting (wrong reset duration, non‑existent “Nauta” term) and failed to confirm warranty status before initiating replacement. | | **What L2 did** | L2 likely reviewed the case, confirmed the hardware fault, and processed the warranty replacement after collecting serial and purchase details from the customer. | | **Current state** | Resolved via warranty replacement. | | **L1 learning points** | 1. **Use the correct reset duration** (~10 seconds for MX series) as per KB—double‑check before instructing the customer. 2. **Avoid unsupported terminology** (“Nauta”)—it creates confusion and erodes trust. 3. **Verify warranty eligibility** before promising replacement to ensure a smooth handoff. | --- ## Coach Appendix *Highest-signal trend:* Technical inaccuracies (reset durations, admin URLs, missing WAN/SIM checks) caused two escalations. Focus next week on precise KB reference use and structured hardware troubleshooting flows for 4G/5G and mesh models. --- ## 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 | 3.00 | INBOUND | FGW5500 | HARDWARE | ↑ Escalated | | [#LTS00131160](https://linksys.happyfox.com/staff/ticket/131160/) | 2026-05-28 02:08:02 | 1.90 | INBOUND | MX6200 | HARDWARE | ↑ Escalated | | [#LTS00131189](https://linksys.happyfox.com/staff/ticket/131189/) | 2026-05-28 06:51:08 | 3.00 | INBOUND | MBE7000 | SETUP | ↻ Callback set |