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 |
|---|---|---|---|---|---|
| 7 | 12m 23s | MBE7000 | HARDWARE | 3 | 2 |
Work Mix Lens
- Frontline-heavy week: 8 LTS queue calls vs 0 TE-owned calls.
- Coach as a frontline agent: emphasize safe troubleshooting branches, closure hygiene, and clear customer-facing next steps.
- Merged HappyFox agent aliases: Weiyu Zeng, weiyu.zeng@concentrix.com
Scorecard
| Dimension | This Week | Calls Reviewed |
|---|---|---|
| Accuracy | 2.29 | 7 |
| Protocol | 1.86 | 7 |
| Communication | 1.86 | 7 |
| Overall | 2.30 | 7 |
Where Time Goes
Product Families
| Family | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Note |
|---|---|---|---|---|---|---|---|
| OTHER | 1 | 22m 4s | 3.00 | 3.00 | 2.00 | 2.00 | |
| MBE | 3 | 20m 0s | 2.47 | 1.67 | 2.00 | 2.00 | |
| LN | 1 | 14m 13s | 3.00 | 3.00 | 2.00 | 2.00 | |
| MX | 3 | 8m 29s | 2.23 | 2.33 | 1.33 | 1.67 |
Key Observations
- OTHER is one of the slowest families at 22m 4s.
- MBE is one of the slowest families at 20m 0s.
Problem Categories
| Category | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Focus Area? |
|---|---|---|---|---|---|---|---|
| HARDWARE | 3 | 17m 46s | 2.63 | 2.33 | 2.00 | 1.67 | ✓ |
| SETUP | 2 | 14m 36s | 3.00 | 2.50 | 1.50 | 1.50 | |
| CONNECTIVITY | 2 | 19m 10s | 2.20 | 1.50 | 2.00 | 2.00 | ✓ |
Week-over-Week Movement
- Overall moved up 0.29 vs. last week.
- Communication moved down 0.32 vs. last week.
- Average handle time moved down by 11m 47s.
- Family swing: MX handle time moved down by 31m 11s vs. last week.
- Family swing: OTHER handle time moved up by 7m 28s vs. last week.
What Went Well
- Accurate serial number collection
> 59A10M26E04628
- Warranty claim initiation
> “Initiated a valid warranty claim for hardware replacement, aligning with support protocol for in-warranty devices.”
Growth Opportunities
- Correct reset guidance
MX4200 reset duration should be ~10s (KB standard), not 20–30s. Avoid undocumented “rescue mode” procedures.
- Avoid technical inaccuracies
Replace non-existent terms like “Nauta” with documented troubleshooting. Limit repetitive power cycles to diagnostic-purpose loops only.
Next Week's Focus
- Verify reset durations against KB before guiding customers (e.g., MX4200: ~10s, MX6200: ~10s).
- Use only documented troubleshooting terms (e.g., “factory reset,” “power cycle”) and avoid ad-hoc labels.
- Confirm admin URLs early (e.g., MBE7000:
http://myrouter.info, not[REDACTED_PHONE]). - Provide mesh-node pairing options: 5-press, factory reset, or web UI setup—never assume LED status alone confirms meshing.
Technical Accuracy
Improvement
Provided incorrect reset duration (20–30s) for MX4200; KB specifies ~10s. Invented undocumented 'rescue mode' power-cycling procedure.
Improvement
Used non-existent term 'Nauta' multiple times, creating confusion. Performed three redundant 30-second power-cycle loops without diagnostic purpose.
Improvement
Failed to identify correct admin URL for MBE7000 (should be http://myrouter.info, not [REDACTED_PHONE]). Skipped essential steps: power-cycling modem/router, checking WAN cable, confirming physical connections.
Improvement
Provided factually incorrect LED interpretation: stated solid white light on MX6200 means node is already meshed, which is false per KB. Failed to offer any correct mesh-node pairing procedure (e.g., 5-press, Pair button, factory reset, or web UI setup).
Coaching Moments
No additional coaching moments were extracted after the technical review.
Escalation Lessons: What L2 Did
#LTS00131007 — Resolved by Level 2
- What L1 saw: FGW5500 router with red globe light (no signal) and poor Wi-Fi for a week; China Mobile confirmed no ISP issue.
- Why it escalated: Persistent hardware symptoms after reset and SSID verification; no WAN/SIM validation performed.
- What L2 did: Resolution steps not documented in local snapshot—case marked “Updated” but no technical resolution details provided.
- Current state: Resolved via warranty claim for hardware replacement.
- L1 learning points:
1. Always verify WAN/SIM status and perform modem power-cycle for 4G/5G routers.
2. Use structured troubleshooting: reset (10–15s), firmware check, SIM validation.
3. Document LED observations and correlate with symptom patterns before concluding hardware failure.
#LTS00131160 — Pending with Level 2
- What L1 saw: MX6200 Velop 6E failing to broadcast SSID; solid blue LED after reset.
- Why it escalated: Incorrect reset duration (20s vs. ~10s) and undocumented “Nauta” references created confusion; no warranty verification.
- What L2 did: Resolution steps not documented in local snapshot—case marked “Updated” but no technical resolution details provided.
- Current state: Updated—awaiting customer response to resubmit interface screenshots.
- L1 learning points:
1. Use correct reset durations per KB (MX6200: ~10s).
2. Avoid non-standard terminology; use only documented steps.
3. Verify warranty status before initiating replacement and collect serial/purchase details upfront.
Coach Appendix
Highest-signal trend: Hardware and connectivity issues dominate this week’s volume, with consistent gaps in reset guidance accuracy, undocumented procedures, and admin URL verification. Focus next coaching on diagnostic rigor for hardware symptoms, strict adherence to KB reset durations, and early validation of router accessibility (e.g., correct admin URLs, WAN status). Maintain verbatim quote governance—no reconstructed dialogue permitted.
This Week's Calls
| Case | Date | Score | Direction | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00130991 | 2026-05-27 01:00:09+00:00 | 3.0 | INBOUND | LN11011202 | SETUP | Customer will manually change the 2.4 GHz channel and test printer connectivity; if the issue persists, they will call back. |
| #LTS00130999 | 2026-05-27 03:32:55+00:00 | 1.8 | INBOUND | MX4200 | HARDWARE | Customer to try reset and rescue steps independently; no follow-up scheduled or support path provided beyond recontacting support. |
| #LTS00131007 | 2026-05-27 07:30:47+00:00 | 3.0 | INBOUND | FGW5500 | HARDWARE | 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). |
| #LTS00131160 | 2026-05-28 02:08:02+00:00 | 1.9 | INBOUND | MX6200 | HARDWARE | Agent concluded hardware fault, collected serial, purchase, and contact details, and promised to send an email within 5–10 minutes with replacement instructions. |
| #LTS00131189 | 2026-05-28 06:51:08+00:00 | 3.0 | INBOUND | MBE7000 | SETUP | Schedule a callback at 9 am for further troubleshooting and possible factory reset. No self-help materials or KB articles sent. |
| #LTS00131375 | 2026-05-29 07:02:07+00:00 | 3.0 | INBOUND | MX5300 | SETUP | None – call ended without resolution, case creation, or clear next step. |
| #LTS00131376 | 2026-05-29 07:17:09+00:00 | 3.0 | INBOUND | MBE7000 | CONNECTIVITY | Customer instructed to monitor the network for a few days after changes; no immediate verification of fix. |
| #LTS00131376 | 2026-05-29 07:55:59+00:00 | 1.4 | INBOUND | MBE7000 | CONNECTIVITY | None provided; call ended without resolution, escalation, or follow-up. |