Weiyu Zeng — 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 | 13m 6s | MBE7000 | CONNECTIVITY | — | — |
Scorecard
| Dimension | This Week | Calls Reviewed |
|---|---|---|
| Accuracy | 2.40 | 5 |
| Protocol | 1.60 | 5 |
| Communication | 2.00 | 5 |
| Overall | 2.44 | 5 |
Where Time Goes
Product Families
| Family | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Note |
|---|---|---|---|---|---|---|---|
| MBE | 2 | 21m 40s | 2.20 | 1.50 | 2.00 | 2.00 | Outlier: 1.5x weekly median handle time |
| LN | 1 | 14m 13s | 3.00 | 3.00 | 2.00 | 2.00 | |
| MX | 2 | 4m 48s | 2.40 | 3.00 | 1.00 | 2.00 |
Key Observations
- MBE is the slowest family at 21m 40s; outlier: 1.5x weekly median handle time.
- LN is one of the slowest families at 14m 13s.
Problem Categories
| Category | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Focus Area? |
|---|---|---|---|---|---|---|---|
| CONNECTIVITY | 2 | 21m 0s | 2.20 | 1.50 | 2.00 | 2.00 | ✓ |
| SETUP | 2 | 8m 47s | 3.00 | 4.00 | 1.50 | 1.50 | |
| HARDWARE | 1 | 6m 14s | 1.80 | 1.00 | 1.00 | 3.00 | ✓ |
Week-over-Week Movement
- Improve accuracy in technical guidance, especially for mesh node pairing and reset procedures.
- Address protocol gaps in call structure, resolution verification, and next steps.
- Enhance communication to handle urgent customer distress and mental health concerns.
What Went Well
Accurate serial number collection
"Yes, 59A, yes, 10M, yes, yes, OK, good, 04628, OK, good, that's all we need, we've noted it down, yes."
#LTS00131376
Structured troubleshooting steps
"Advised power-only reset with 20–30 second reset button hold."
#LTS00130999
Growth Opportunities
Incorrect technical guidance on mesh node pairing
"Provided factually incorrect LED interpretation: stated solid white light on MX6200 means node is already meshed, which is false and contradicts the KB."
#LTS00131376
What better looks like: Offer valid pairing instructions (5-press, Pair button, factory reset, or web UI setup) and verify customer access to the Linksys app or web UI before proceeding.
Failure to verify resolution or provide next steps
"No verification of whether steps resolved the issue before closing call. Call ended without resolution, escalation, or follow-up."
#LTS00130999
What better looks like: Confirm the fix is working, schedule a callback if needed, and document clear next steps for the customer.
Next Week's Focus
- Verify fixes before closing calls – Always ask the customer to confirm the issue is resolved and document the outcome.
- Use correct technical terminology – Replace terms like “5Gbps”/“6Gbps” with “5 GHz”/“6 GHz” and clarify regional regulatory limitations.
- Collect essential device information early – Model, serial number, and warranty status should be gathered at the start of each call.
- Address urgent customer concerns with empathy – Acknowledge distress, offer concrete next steps, and escalate when necessary.
Technical Accuracy
Improvement
Incorrectly interpreted solid white LED on MX6200 as 'already meshed', contradicting KB guidance. Failed to provide valid pairing instructions (5-press, Pair button, factory reset, or web UI setup).
#LTS00131376
Improvement
Provided incorrect reset duration (20–30s) for MX4200; KB specifies ~10s. Invented undocumented 'rescue mode' procedure without verification.
#LTS00130999
Improvement
Failed to address urgent customer distress and mental health concerns. No technical support, case creation, or next steps provided.
#LTS00131375
Improvement
Misrepresented 6 GHz unavailability as a national policy issue rather than regional regulatory or device compatibility limitation. Used incorrect terminology ('5Gbps', '6Gbps' instead of '5 GHz', '6 GHz').
#LTS00131376
Coaching Moments
Strength
"Accurately collected and confirmed the serial number: '59A10M26E04628'"
#LTS00131376
Strength
"Provided structured step-by-step instructions despite technical inaccuracies, improving clarity over chaotic troubleshooting."
#LTS00130999
Escalation Lessons: What L2 Did
No escalated cases were recorded this week.
Coach Appendix
Highest-signal weekly trend: The agent showed improvement in overall and accuracy scores but needs to focus on protocol gaps in call structure, resolution verification, and next steps. Technical inaccuracies—especially around mesh node pairing and reset procedures—require immediate attention. Collecting essential device information early and verifying fixes before closing calls will further enhance performance.
This Week's Calls
| Case | Date | Score | Direction | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00130991 | 2026-05-27 01:00:09+00:00 | 3.00 | INBOUND | LN11011202 | SETUP | Pending resolution |
| #LTS00130999 | 2026-05-27 03:32:55+00:00 | 1.80 | INBOUND | MX4200 | HARDWARE | ↑ Escalated |
| #LTS00131375 | 2026-05-29 07:02:07+00:00 | 3.00 | INBOUND | MX5300 | SETUP | ⚠ Closed incorrectly |
| #LTS00131376 | 2026-05-29 07:17:09+00:00 | 3.00 | INBOUND | MBE7000 | CONNECTIVITY | ✓ Likely resolved |
| #LTS00131376 | 2026-05-29 07:55:59+00:00 | 1.40 | INBOUND | MBE7000 | CONNECTIVITY | ⏳ Pending |