# 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 58s | MX5300 | SETUP | — | — |

---

## Scorecard

| Dimension | This Week | Calls Reviewed |
|---|---|---|
| Accuracy | 1.33 | 4 |
| Protocol | 1.67 | 4 |
| Communication | 1.67 | 4 |
| Overall | 1.67 | 4 |

*4 calls reviewed — scores range from 1.0 to 3.0 overall.*

---

## This Week's Coverage

### Models Supported

| Model | Calls | Avg Score |
|---|---|---|
| MX5300 | 3 | 2.00 |
| MBE7000 | 1 | 1.90 |

Lower scores on MX5300 calls suggest a need for deeper familiarity with this model's setup flow, particularly around LED interpretation and initial configuration.

### Problem Categories

| Category | Calls | Avg Score | Focus Area? |
|---|---|---|---|
| SETUP | 4 | 1.97 | ✓ |

The SETUP category shows consistently low scores (1.97 average). The pattern suggests struggles with guiding customers through initial device configuration — especially around firmware updates, LED status interpretation, and collecting critical information like product model and serial number early in the call.

---

## What Went Well

### Persistent Guidance Through Complexity

> **Correctly directed customer to the official Linksys support site for firmware download and collected customer contact information for follow-up.**
> 
> [#LTS00130811](https://linksys.happyfox.com/staff/ticket/130811/)

You maintained focus on essential next steps even when the customer was confused, ensuring they had the right resources and a path for follow-up.

### Successful Resolution Path

> **Provided correct URL (http://[REDACTED_PHONE]) and default login credentials (ADMIN), successfully guided customer to complete Wi-Fi setup and achieve solid blue LED status. Confirmed resolution with customer.**
> 
> [#LTS00131366](https://linksys.happyfox.com/staff/ticket/131366/)

Despite early call challenges, you persisted through confusion and eventually guided the customer to a working solution, confirming the solid blue LED and functional internet connection.

---

## Growth Opportunities

### Avoid Inventing UI Elements

> **Incorrectly directed customer to a non-existent 'CA' button in the MBE7000 admin UI, contradicting KB documentation**
> 
> [#LTS00130811](https://linksys.happyfox.com/staff/ticket/130811/)

**What better looks like:**  
- **Verify UI element names against the KB or device screenshots before instructing customers.**  
- **When in doubt, guide the customer to navigate via menu paths (e.g., “Go to Administration > Firmware Update”) rather than relying on memorized button labels.**  
- **Confirm the customer sees the expected screen after each step.**

### Engage Proactively and Troubleshoot Systematically

> **Failed to engage with customer, repeatedly played automated prompts, provided no actual troubleshooting for setup issue**
> 
> [#LTS00131366](https://linksys.happyfox.com/staff/ticket/131366/)

**What better looks like:**  
- **Greet the customer promptly, confirm language preference, and acknowledge their issue.**  
- **Collect critical details upfront: product model, serial number, current LED state, and recent changes.**  
- **Use a structured troubleshooting flow: reset → cable check → web UI access → LED validation → ISP check.**  
- **Validate each step with the customer before moving on.**

---

## Next Week's Focus

1. **Start every call with a quick “Can you confirm the exact model number?”** — this prevents missteps with model-specific guidance (e.g., 5-press reset rules).
2. **Create a simple checklist for SETUP calls:**  
   - Confirm language → Model/Serial → LED state → Reset (if needed) → Cable connections → Web UI access → ISP check → Test internet.
3. **When guiding through UI navigation, always reference the exact menu path (e.g., “Administration > Firmware Update”) instead of unique button names.**
4. **After each troubleshooting step, ask the customer to verify the result (“Is the LED now solid blue?”) before proceeding.**

---

## Technical Accuracy

### **Improvement**

> Agent provided materially incorrect technical guidance by inventing a non-existent 'CA' button in the MBE7000 admin UI, directly contradicting the KB. Failed to correct misdirection when customer expressed confusion. No post-update validation performed.
> 
> [#LTS00130811](https://linksys.happyfox.com/staff/ticket/130811/)

**Note:** This was a clear case of providing UI guidance that does not exist in the device. Always cross-check against KB articles or device screenshots before instructing customers on specific buttons or menu options. After directing a customer to perform an action (e.g., firmware update), always confirm success through visible indicators (LED, web UI, internet connectivity) or customer confirmation.

### **Improvement**

> Agent failed to engage with customer. Repeated automated Cantonese prompts played despite customer speaking English. No actual troubleshooting steps (reset, web UI access, LED interpretation, ISP check) performed. At [05:09], gave technically incorrect and nonsensical instruction.
> 
> [#LTS00131366](https://linksys.happyfox.com/staff/ticket/131366/)

**Note:** The call suffered from a complete lack of agent engagement and troubleshooting. The agent must actively acknowledge the customer, confirm language preference, and guide through a structured troubleshooting flow. Avoid relying on automated prompts when the customer is clearly trying to communicate in English.

### **Improvement**

> Agent provided inaccurate LED color references, validating 'purple' and 'pink' lights as reset modes, which are not standard Linksys indicators. Repeated the phrase 'Pressing the reset button and there was no response' 15+ times, creating excessive looping. Did not collect product model at start, risking incorrect 5-press reset guidance.
> 
> [#LTS00131366](https://linksys.happyfox.com/staff/ticket/131366/)

**Note:** This call highlights several technical accuracy gaps: misinterpreting LED states, creating call inefficiency through looping, and failing to collect essential product information upfront. Always refer to standard Linksys LED indicators and avoid validating non-standard colors. Collect the product model early to ensure appropriate guidance (e.g., 5-press reset rules vary by model).

### **Strength**

> Agent correctly directed customer to the official Linksys support site for firmware download and collected customer contact information for follow-up.
> 
> [#LTS00130811](https://linksys.happyfox.com/staff/ticket/130811/)

**Note:** This is a solid example of providing the right resource and ensuring follow-up information is captured. Continue this practice — directing customers to official resources and collecting contact details enables effective follow-through.

### **Strength**

> Agent provided correct URL (http://[REDACTED_PHONE]) and default login credentials (ADMIN), successfully guided customer to complete Wi-Fi setup and achieve solid blue LED status. Confirmed resolution with customer.
> 
> [#LTS00131366](https://linksys.happyfox.com/staff/ticket/131366/)

**Note:** Despite early challenges, the agent eventually provided accurate navigation instructions and confirmed a successful outcome. This demonstrates persistence and the ability to recover from early call difficulties by focusing on verified steps and customer confirmation.

---

## Coaching Moments

### **Improvement**

> **Failed to engage with customer, repeatedly played automated prompts, provided no actual troubleshooting for setup issue**
> 
> [#LTS00131366](https://linksys.happyfox.com/staff/ticket/131366/)

When a customer is clearly trying to communicate in English, it’s essential to acknowledge them directly and avoid relying on automated language prompts. Engaging proactively — greeting the customer, confirming their language preference, and guiding them through structured troubleshooting — builds trust and moves the call forward efficiently.

### **Improvement**

> **Provided inaccurate LED color references, validating 'purple' and 'pink' lights as reset modes, which are not standard Linksys indicators. Repeated the phrase 'Pressing the reset button and there was no response' 15+ times, creating excessive looping. Did not collect product model at start, risking incorrect 5-press reset guidance.**
> 
> [#LTS00131366](https://linksys.happyfox.com/staff/ticket/131366/)

Accurate LED interpretation is critical for troubleshooting. Always refer to standard Linksys LED indicators and avoid validating non-standard colors. Collecting the product model early prevents misapplying reset procedures (e.g., 5-press rules vary by model). Structured troubleshooting and avoiding repetitive looping keeps calls efficient and productive.

---

## Escalation Lessons: What L2 Did

*No escalation cases were recorded for this week. All calls were handled at Level 1, though several remained unresolved. The primary technical patterns to avoid — inventing UI elements, misinterpreting LEDs, and failing to engage — are highlighted above in the Technical Accuracy and Coaching Moments sections.*

---

## Coach Appendix

*This week’s highest-signal trend is the consistent struggle with SETUP calls, particularly around firmware updates and device configuration. Accuracy scores were low across the board (1.33) due to a combination of incorrect UI guidance (MBE7000 “CA” button), failure to engage and troubleshoot (MX5300 setup call), and inefficient call control (excessive looping on reset button feedback). The single resolved call (#LTS00131366) shows that persistence through confusion, accurate navigation instructions, and confirmation of the solid blue LED can lead to success — but this was the exception, not the pattern. Focus for next week should be on structured troubleshooting flows, verifying UI guidance against KBs, and proactive customer engagement from the first interaction.*