# Xiangjie Zhang — 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 |
| --- | --- | --- | --- | --- | --- |
| 5 | 12m 21s | MX5300 | CONNECTIVITY | — | — |

## Scorecard
| Dimension | This Week | Calls Reviewed |
| --- | --- | --- |
| Accuracy | 3.00 | 4 |
| Protocol | 2.00 | 4 |
| Communication | 2.25 | 4 |
| Overall | 2.55 | 4 |

## Where Time Goes
**Product Families**
| Family | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Note |
| --- | --- | --- | --- | --- | --- | --- | --- |
| MX | 4 | 14m 1s | 2.40 | 2.67 | 2.00 | 2.00 |  |
| MBE | 1 | 5m 40s | 3.00 | 4.00 | 2.00 | 3.00 |  |

**Key Observations**
- MX is one of the slowest families at 14m 1s.
- MBE is one of the slowest families at 5m 40s.

**Problem Categories**
| Category | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Focus Area? |
| --- | --- | --- | --- | --- | --- | --- | --- |
| CONNECTIVITY | 3 | 17m 13s | 2.07 | 2.50 | 2.00 | 2.00 | ✓ |
| NO TROUBLESHOOTING NEEDED | 1 | 4m 25s | 3.00 | 3.00 | 2.00 | 2.00 |  |
| ACCESS | 1 | 5m 40s | 3.00 | 4.00 | 2.00 | 3.00 |  |

## Week-over-Week Movement
- Overall moved down 0.40 vs. last week.
- Accuracy moved up 0.25 vs. last week.
- Protocol moved up 0.25 vs. last week.
- Communication moved up 0.25 vs. last week.
- Average handle time moved down by 6m 31s.
- Family swing: MX handle time moved down by 15m 36s vs. last week.

## What Went Well

*Accurate model identification*: Consistently identified MX5300 as the product model early in calls, providing a clear starting point for troubleshooting.  
> **MX5300, it cannot connect to the internet.**  
[#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/)

*Basic troubleshooting steps*: Applied valid first-line actions like modem restarts and app reinstallations, aligning with KB guidance.  
> **Sir, included Wi-Fi?**  
[#LTS00131168](https://linksys.happyfox.com/staff/ticket/131168/)

---

## Growth Opportunities

*Contradictory guidance on compatibility*: Avoid mixed messages about Mesh model compatibility. Provide a clear, consistent compatibility list and direct customers to official resources.  
> **No, you must stick with the VLAB series. Because we have other series that can work together, but they use different technology, so that kind won't be supported.**  
[#LTS00130823](https://linksys.happyfox.com/staff/ticket/130823/)

*Deeper diagnostics for unresolved issues*: When issues persist after basic steps, move quickly to router-side diagnostics (web UI access, firmware checks) and verify warranty status. Document findings and set clear next steps.  

---

## Next Week's Focus

* Create and reference a HappyFox case for every customer interaction to ensure continuity and accountability.
* Master LED state interpretation for MX series devices and apply it consistently in troubleshooting.
* Practice verifying modem/WAN connectivity as a mandatory first step in all connectivity issues.
* Develop a concise script for explaining Mesh compatibility, including a link to the official compatibility matrix.

---

## Technical Accuracy

**Improvement**  
> *None*  
*Incorrect reset duration for MX5300 (20 seconds instead of ~10 seconds), leading to ineffective troubleshooting.*  
[#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/)

**Improvement**  
> *None*  
*Misinterpreted LED states (e.g., purple light as readiness), leading to false expectations and unresolved connectivity issues.*  
[#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/)

**Improvement**  
> *None*  
*Failed to verify modem/WAN connectivity, a critical first step in Internet/WAN Setup issues.*  
[#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/)

**Improvement**  
> *None*  
*Provided contradictory information about compatible Mesh models (VLAB vs. 'white cylindrical' only), creating confusion.*  
[#LTS00130823](https://linksys.happyfox.com/staff/ticket/130823/)

**Improvement**  
> *None*  
*Did not perform router-side diagnostics (e.g., web UI access, firmware check) despite customer reporting persistent app crashes and zero device visibility.*  
[#LTS00131168](https://linksys.happyfox.com/staff/ticket/131168/)

---

## Coaching Moments

*No additional coaching moments were extracted after the technical review.*

---

## Escalation Lessons: What L2 Did

*No escalated case learning was available for this report.*

---

## Coach Appendix

*Highest-signal trend: Connectivity issues on MX5300 dominate call volume and handle time, with consistent gaps in LED interpretation, modem/WAN verification, and deeper diagnostics. Focus next week on building confidence in these core troubleshooting branches and documentation habits.*

---

## This Week's Calls

| Case | Date | Score | Direction | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| [#LTS00130823](https://linksys.happyfox.com/staff/ticket/130823/) | 2026-05-26 05:54 | 3 | INBOUND | MX5300 | NO TROUBLESHOOTING NEEDED | — |
| [#LTS00131001](https://linksys.happyfox.com/staff/ticket/131001/) | 2026-05-27 05:42 | — | INBOUND | MX2000 | CONNECTIVITY | — |
| [#LTS00131168](https://linksys.happyfox.com/staff/ticket/131168/) | 2026-05-28 02:50 | 3 | INBOUND | MBE7000 | ACCESS | Callback set |
| [#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/) | 2026-05-28 06:25 | 3 | INBOUND | MX5300 | CONNECTIVITY | — |
| [#LTS00131186](https://linksys.happyfox.com/staff/ticket/131186/) | 2026-05-28 06:29 | 1.2 | INBOUND | MX5300 | CONNECTIVITY | — |