# Zhiliang Chen — 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 | 45m 52s | MX5300 | SETUP | — | — | --- ## Scorecard | Dimension | This Week | Calls Reviewed | |---|---|---| | Accuracy | 1.33 | 3 | | Protocol | 1.67 | 3 | | Communication | 1.67 | 3 | | Overall | 1.97 | 3 | *3 calls reviewed; score range: 1.0 – 3.0* --- ## This Week's Coverage ### Models Supported | Model | Calls | Avg Score | |---|---|---| | MX5300 | 3 | 1.67 | | MBE7000 | 1 | 1.90 | Lower scores on MX5300 calls suggest a need for stronger familiarity with this model's setup flow, especially around LED interpretation and initial configuration. ### Problem Categories | Category | Calls | Avg Score | Focus Area? | |---|---|---|---| | SETUP | 4 | 1.97 | ✓ | The **SETUP** category shows the biggest opportunity this week. The lower average score points to inconsistencies in guiding customers through initial router configuration — particularly around firmware updates, LED status interpretation, and collecting critical device information upfront. --- ## What Went Well ### Persistence through customer confusion > Persisted through customer confusion and eventually guided them to correct cable connections [85:49–86:13]. [#LTS00131366](https://linksys.happyfox.com/staff/ticket/131366/) You demonstrated resilience when the customer struggled with basic setup concepts. By staying on the line and walking them through cable connections step-by-step, you helped them reach a working state (solid blue LED). This kind of persistence is exactly what helps customers feel supported even when they're frustrated. --- ## Growth Opportunities ### Incorrect technical guidance and UI navigation The call to the MBE7000 customer included guidance that simply doesn't exist in the product UI — specifically references to a non-existent **"CA" button** in the admin interface. This not only confused the customer but also wasted time that could have been spent on productive troubleshooting. **What good looks like:** Before directing customers to specific UI elements, always verify their existence against current product documentation or the live interface. When in doubt, suggest the customer look for similarly named options or offer to walk through the exact path together. --- ### Failure to engage and collect critical information In the MX5300 call, repeated language prompts played instead of meaningful engagement. You never confirmed the customer's language preference, collected the model/serial number, or even identified whether this was a new setup or a troubleshooting scenario. **What good looks like:** Start every call by confirming the customer's preferred language, then immediately collect the product model and serial number (if available). This context lets you tailor troubleshooting and avoid irrelevant steps. For setup calls, ask whether this is a fresh install or an existing device that's stopped working — the answer dramatically changes the support path. --- ## Next Week's Focus 1. **Start stronger:** Confirm language preference and collect model/serial number within the first 30 seconds of every call. 2. **Verify before you guide:** When mentioning UI elements, double-check their existence in current documentation or suggest the customer look for similarly named options. 3. **Reduce looping:** If a customer repeats a phrase or question, acknowledge their frustration, summarize what you've already tried, and propose a clear next step — don't re-hash the same ground. 4. **Validate progress:** After guiding a customer through any action (reset, cable change, login), ask them to confirm the observed result before moving forward. --- ## Technical Accuracy ### **Improvement** Provided materially incorrect technical guidance by inventing a non-existent 'CA' button in the MBE7000 admin UI, directly contradicting the KB. No validation of the update was performed. [#LTS00130811](https://linksys.happyfox.com/staff/ticket/130811/) ### **Improvement** Failed to acknowledge or confirm customer's language (English), leading to repeated irrelevant Cantonese prompts. No actual troubleshooting for setup issue was performed. [#LTS00131366](https://linksys.happyfox.com/staff/ticket/131366/) ### **Improvement** Instructed 5-press reset without confirming device model. Provided inaccurate LED color references, validating 'purple' and 'pink' lights as reset modes, which are not standard Linksys indicators. [#LTS00131366](https://linksys.happyfox.com/staff/ticket/131366/) ### **Strength** Successfully guided customer to complete Wi-Fi setup and achieve solid blue LED status. Provided correct URL and default login credentials. [#LTS00131366](https://linksys.happyfox.com/staff/ticket/131366/) --- ## Coaching Moments ### **Strength** > Persisted through customer confusion and eventually guided them to correct cable connections [85:49–86:13]. This moment shows your best trait: persistence. Even when the customer was struggling to follow basic steps, you stayed calm and guided them to a working configuration. Keeping this patience will help more customers succeed. --- ## Escalation Lessons: What L2 Did No escalated cases were recorded this week. The two unresolved calls (#LTS00130811 and #LTS00131366) would benefit from either a full setup walkthrough or escalation to Level 2 for deeper technical diagnosis. --- ## Coach Appendix *Highest-signal trend:* All three lower-scoring calls shared a common pattern — insufficient upfront information collection (model, serial, setup vs. troubleshooting) combined with occasional technically inaccurate guidance. Next week’s focus on early engagement and verification should directly address these gaps. The single high-scoring call demonstrates that when you collect context early and guide step-by-step, customers can achieve successful outcomes even with initial confusion. --- ## This Week's Calls | Case | Date | Score | Direction | Product | Category | Outcome | |---|---|---|---|---|---|---| | [#LTS00130811](https://linksys.happyfox.com/staff/ticket/130811/) | 2026-05-26 01:04:37+00:00 | 1.9 | INBOUND | MBE7000 | SETUP | ⚠ Closed incorrectly | | [#LTS00131366](https://linksys.happyfox.com/staff/ticket/131366/) | 2026-05-29 04:53:05+00:00 | 1.0 | INBOUND | MX5300 | SETUP | ⚠ Closed incorrectly | | [#LTS00131366](https://linksys.happyfox.com/staff/ticket/131366/) | 2026-05-29 05:03:03+00:00 | — | INBOUND | MX5300 | SETUP | — | | [#LTS00131366](https://linksys.happyfox.com/staff/ticket/131366/) | 2026-05-29 05:18:19+00:00 | 3.0 | INBOUND | MX5300 | SETUP | ✓ Likely resolved |