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 1s | MX5300 | CONNECTIVITY | — | — |
Scorecard
| Dimension | This Week | Calls Reviewed |
|---|---|---|
| Accuracy | 3.00 | 4 |
| Protocol | 2.00 | 4 |
| Communication | 2.25 | 4 |
| Overall | 2.55 | 4 |
4 calls reviewed; overall score range: 1.2 – 3.0
Where Time Goes
Models Supported
| Model | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication |
|---|---|---|---|---|---|---|
| MX5300 | 3 | 14m 46s | 2.40 | 2.67 | 2.00 | 2.00 |
| MBE7000 | 1 | 5m 40s | 3.00 | 4.00 | 2.00 | 3.00 |
| MX2000 | 1 | 12m 14s | — | — | — | — |
MX5300 dominates call volume and time; scores are consistently below average across all dimensions, indicating a need for focused improvement on this model.
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 | ✓ |
| ACCESS | 1 | 5m 40s | 3.00 | 4.00 | 2.00 | 3.00 | |
| NO TROUBLESHOOTING NEEDED | 1 | 4m 25s | 3.00 | 3.00 | 2.00 | 2.00 |
CONNECTIVITY calls are both numerous and time-consuming, with low overall and accuracy scores. This is a clear focus area for next week.
Week-over-Week Movement
No prior-week comparison data available.
What Went Well
- Accurate model identification
> You can... we... our other VLAB models can all work. You don't necessarily have to get the 5350.
- Basic troubleshooting steps
> Sir, what model of device do you have?
Growth Opportunities
- Contradictory and vague guidance
> 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. Our white cylindrical ones can all work.
What better looks like: Provide a clear, verified compatibility list or direct the customer to a knowledge-base article. Avoid mixed messages about product series.
- Lack of follow-up and documentation
> Agent confirmed MX5300 can serve as primary router due to better performance, but gave no definitive compatibility list or follow-up resources.
What better looks like: Always create a HappyFox case, document the interaction, and provide next steps or self-help resources in writing (email, KB article, or follow-up call).
Next Week's Focus
- Create a HappyFox case for every call that requires follow-up, even if the issue seems minor.
- Before giving technical advice, verify the exact product model, serial number, and warranty status.
- Use knowledge-base articles to support guidance — especially for compatibility questions — and share the link with the customer.
- When handling CONNECTIVITY issues, always verify modem/WAN connectivity first.
Technical Accuracy
Improvement
- Incorrect reset time for MX series (20 seconds instead of ~10 seconds) — contradicts KB guidance.
Improvement
- Failed to verify modem/WAN connectivity, a critical first step in Internet/WAN Setup issues.
Improvement
- Did not confirm serial number, warranty status, or RMA eligibility despite customer inquiry about repair procedure.
Improvement
- Contradictory guidance on model compatibility without verifying customer's exact product or warranty status.
Coaching Moments
Strength
You can... we... our other VLAB models can all work. You don't necessarily have to get the 5350.
Strength
Sir, what model of device do you have?
Escalation Lessons: What L2 Did
No escalation learning data available this week.
Coach Appendix
- Weekly trend: MX5300 connectivity issues dominate call volume and time, with consistently low accuracy and overall scores. The agent needs to focus on precise technical guidance, documentation, and verification of modem/WAN connectivity before proceeding.
- Key pattern: Multiple calls lacked HappyFox case creation and clear next steps, leading to unresolved issues and customer follow-up needs. This pattern should inform the next coaching conversation, emphasizing case documentation and structured follow-up plans.
This Week's Calls
| Case | Date | Score | Direction | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00130823 | 2026-05-26 | 3.0 | INBOUND | MX5300 | NO TROUBLESHOOTING NEEDED | — |
| #LTS00131001 | 2026-05-27 | — | INBOUND | MX2000 | CONNECTIVITY | — |
| #LTS00131168 | 2026-05-28 | 3.0 | INBOUND | MBE7000 | ACCESS | ↻ Callback set |
| #LTS00131186 | 2026-05-28 | 3.0 | INBOUND | MX5300 | CONNECTIVITY | — |
| #LTS00131186 | 2026-05-28 | 1.2 | INBOUND | MX5300 | CONNECTIVITY | — |