zhiliang.chen@concentrix.com — Coaching Report

Week of 2026-05-25 – 2026-05-31

At a Glance

Scorecard

Scores based on 1 call reviewed. Score range: 1.00 (lowest) to 1.10 (highest).

Where Time Goes

Models Supported

Key Pattern: The MBE7000 is the sole product handled this week, with an average handle time of 6m 58s and consistently low scores across all categories. This suggests the agent needs more practice with high-complexity mesh router issues and better adherence to troubleshooting protocols for performance-related concerns.

Problem Categories

CONNECTIVITY Focus Area: The single connectivity call shows a critical need for improved technical accuracy and protocol adherence. The low scores indicate the agent missed fundamental troubleshooting steps and provided incorrect technical explanations, which directly impacts resolution quality for performance issues.

Week-over-Week Movement

Comparison to Prior Week (May 18-24):

• Call Volume: Down from 6 calls to 1 call this week
• Top Product/Category: Remains MBE7000 and CONNECTIVITY, but with significantly lower resolution rates
• Key Shift: While call volume decreased, the quality of handling for connectivity issues dropped dramatically, highlighting a need for focused coaching on technical accuracy and escalation protocols rather than just call volume management.

What Went Well

Recognized Complexity and Need for Advanced Support

"Actually, it's like this: because Wi-Fi wireless is half-duplex two-way communication, so its actual output is 1200 Mbps. I don't know what he's saying. He said from the main unit to the sub-unit, the sub-unit only has 500. But the main unit also only has 500. They said it's normal."

While the technical explanation was inaccurate, the agent acknowledged the issue's complexity and recognized when to involve advanced support—a crucial first step in handling high-end mesh router performance cases.

Growth Opportunities

Deliver Accurate Technical Explanations and Execute Full Troubleshooting

The agent provided factually incorrect technical explanations (e.g., mischaracterizing Wi-Fi as half-duplex) and skipped essential troubleshooting steps. What good looks like:

• Verify product model and firmware version first
• Perform baseline wired speed tests before diagnosing wireless issues
• Follow KB-guided troubleshooting sequences (reset, firmware update, placement checks)
• Use precise, documented terminology rather than approximations

Initiate Structured Escalations with Clear Next Steps

Instead of vague promises, good escalation looks like:

• Documenting all troubleshooting steps attempted
• Confirming escalation path with the customer ("I'll open a technical escalation and have an engineer review your case by [time]")
• Setting concrete follow-up expectations ("You'll receive an email with case details and next steps within 24 hours")
• Using HappyFox to create proper escalation tickets with all diagnostic data attached

Next Week's Focus

• Start every high-end mesh call with model/firmware verification before discussing symptoms
• Run a wired speed test as the first diagnostic step for any performance issue
• Document every troubleshooting action in the ticket before escalating
• Practice escalation scripts that clearly state next steps, timelines, and contact points

Technical Accuracy

Improvement

No transcript quote available

The agent provided incorrect technical explanations about Wi-Fi being "half-duplex" (Wi-Fi is full-duplex) and referenced a non-existent "connector" that could be "reduced" to improve speed. These inaccuracies contradicted KB guidance and undermined customer confidence. Next step: Review KB universal_speed_performance.md and universal_vpn_overhead.md to understand actual Wi-Fi technical specifications and performance factors.

Improvement

No transcript quote available

The agent failed to execute any standard troubleshooting steps (WAN speed verification, wired baseline test, reset, firmware check, node placement guidance) despite these being required by KB universal_speed_diagnosis.md and universal_speed_performance.md. Next step: Build a personal troubleshooting checklist for performance issues and practice executing all steps before concluding an issue is unsolvable at L1.

Improvement

No transcript quote available

Promising an undefined "upgrade" without initiating escalation, confirming process, or setting callback expectations violates protocol and leaves customers without resolution paths. Next step: Use the escalation decision tree in KB escalation_protocol.md to determine when to escalate, then follow the documented escalation workflow with clear communication.

Improvement

No transcript quote available

No warranty/RMA information was collected despite handling a high-value product (MBE7000) with unresolved performance issues. Next step: Always verify warranty status early in complex cases and document serial numbers, purchase dates, and support entitlements.

Coaching Moments

Strength

Acknowledged need for advanced support

"Actually, it's like this: because Wi-Fi wireless is half-duplex two-way communication, so its actual output is 1200 Mbps. I don't know what he's saying. He said from the main unit to the sub-unit, the sub-unit only has 500. But the main unit also only has 500. They said it's normal."

The agent recognized the limitations of their expertise and understood when to involve higher-level support—a critical soft skill for complex technical cases.

Escalation Lessons: What L2 Did

#TE00129512 — Pending with Level 2

What L1 saw: Customer reported severe Wi-Fi speed fluctuations (60-300 Mbps) on an MBE7000 mesh router advertised for 500+ Mbps. The router is in a small 600 sq ft home with no obvious obstacles.

Why it escalated: L1 failed to perform basic diagnostics (no wired speed test, no firmware check, no reset), provided incorrect technical explanations, and offered only a vague "upgrade" promise without initiating proper escalation.

Related call chain: This was the third contact for this case:

• First call (May 15): Agent provided incorrect technical explanations and failed to resolve
• Second call (May 19): Agent escalated correctly but didn't document proper diagnostics
• Third call (May 27): Agent promised undefined "upgrade" with no action

What L2 did: Level 2 requested detailed network topology information, sysinfo logs from both parent and child nodes, and suggested testing with alternative wireless client devices. They recognized that iPhone speed tests might not reflect actual link speeds and asked for additional diagnostic data to isolate the issue.

Current state: Pending customer-provided diagnostic data (network topology diagram, sysinfo logs, alternative client device tests).

L1 learning points:

1. Always collect model/serial/firmware/version information before discussing symptoms
2. Perform a wired speed test as the baseline for any wireless performance issue
3. Document every troubleshooting step in the ticket before escalating
4. When escalating, provide all available diagnostic data (speed test results, node placement details, firmware versions) to L2

Coach Appendix

Highest-signal weekly trend: The single connectivity case reveals a critical gap in technical accuracy and escalation protocol adherence. The agent needs focused coaching on executing full troubleshooting sequences for high-end mesh performance issues and using structured escalation pathways rather than vague promises.

Key pattern for next coaching: The agent tends to shortcut diagnostic steps when facing complex technical explanations. Building a personal troubleshooting checklist and practicing escalation scripts will help ensure consistent, protocol-driven handling of performance cases.

This Week's Calls