zhiliang.chen@concentrix.com — Coaching Report

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

At a Glance

Scorecard

Where Time Goes

Product Families

Key Observations

• MBE is one of the slowest families at 6m 58s.

Problem Categories

Week-over-Week Movement

• Improve technical accuracy and adherence to KB protocols for speed-performance issues.
• Ensure proper escalation and follow-up for unresolved technical issues.

What Went Well

• Acknowledged need for advanced support

The agent recognized when an issue was beyond their scope, indicating an understanding of escalation boundaries.

> “Hi Team,Here is a customer issue that needs to be escalated for further handling.”

#TE00129512

Growth Opportunities

• Replace incorrect technical explanations with KB-backed troubleshooting

Good looks like: Using accurate, documented steps (e.g., verifying WAN speed, checking firmware, testing wired connections) instead of mischaracterizing Wi‑Fi as “half‑duplex” or referencing non‑existent “connectors.”

> “Actually, it's like this: because Wi-Fi wireless is half-duplex two-way communication, so its actual output is 1200 Mbps.”

#TE00129512

• Collect critical product details before troubleshooting

Good looks like: Asking for the router model, serial number, and firmware version upfront, then using that data to guide precise diagnostics and avoid vague promises like “upgrade.”

Next Week's Focus

1. Start every speed‑performance call with model/serial/firmware collection. Use the “Speed Diagnosis” KB checklist to structure the interview.
2. Apply the universal speed‑performance workflow: WAN speed test → wired baseline → reset → firmware update → node placement review.
3. Escalate clearly: If after these steps the issue persists, initiate escalation with a concise summary (symptoms, tests done, current speed numbers) and set a callback window.
4. Avoid jargon and undefined terms: Replace phrases like “half‑duplex” or “connector” with plain language and documented steps from the KB.

Technical Accuracy

Improvement

No transcript quote provided.

Agent provided incorrect technical explanation: Wi‑Fi is full‑duplex, not half‑duplex, and does not inherently halve advertised speed. Referenced non‑existent “connector” that could be “reduced” to improve speed (no KB support).

#TE00129512

Improvement

No transcript quote provided.

Agent failed to perform any troubleshooting steps (WAN speed verification, wired baseline test, reset, firmware check, node placement guidance) despite KB guidance for speed‑performance issues (universal_speed_performance.md, universal_speed_diagnosis.md).

#TE00129512

Improvement

No transcript quote provided.

Agent promised an undefined “upgrade” without defining the process, initiating escalation, or setting callback expectations, leading to unresolved issue and incorrect closure status (abandoned_or_vague).

#TE00129512

Coaching Moments

Improvement

“Actually, it's like this: because Wi-Fi wireless is half-duplex two-way communication, so its actual output is 1200 Mbps.”

Agent used factually incorrect technical reasoning (Wi‑Fi is full‑duplex) and introduced non‑existent concepts (“connector”) that cannot be acted upon, undermining credibility and delaying resolution.

#TE00129512

Escalation Lessons: What L2 Did

#TE00129512 — Pending with Level 2

• What L1 saw: Customer reported fluctuating Wi‑Fi speeds (60‑300 Mbps) on an MBE7000, claiming advertised speeds of 500‑600 Mbps were not met. L1 took no diagnostic steps, mischaracterized Wi‑Fi technical properties, and promised an undefined “upgrade” without escalation or follow‑up.
• Why it escalated: The case was escalated due to unresolved performance issues, incorrect technical explanations, and lack of documented troubleshooting or escalation path.
• Related call chain: This was the third contact for the same issue. The first call (agent xiaoge.ji) documented the problem but did not resolve it. The second call (agent zhiliang.chen) escalated correctly but failed to document next steps. The third call (agent zhiliang.chen again) abandoned the issue with a vague “upgrade” promise.
• What L2 did: L2 requested network topology, sysinfo logs, and additional client device testing. They clarified that iPhones cannot display link speed and suggested deleting preferred networks to isolate the issue. They also asked for 6GHz client testing to verify performance.
• Current state: Pending customer-provided diagnostics (topology, sysinfo logs, additional device testing).
• L1 learning points:

1. Always collect model, serial number, firmware version, and network topology early in speed‑performance calls.

2. Use the universal speed‑performance workflow: WAN speed test → wired baseline → reset → firmware update → node placement review.

3. If speed issues persist after these steps, escalate with a clear summary of tests performed, current speeds, and any customer-provided diagnostics, and set a callback window.

Coach Appendix

• The single call this week highlights a critical gap in technical accuracy and escalation discipline for high‑end mesh performance issues. The agent’s use of incorrect technical explanations and failure to follow documented troubleshooting steps led to an unresolved case and a sharp drop in scores week‑over‑week. Focus next week on strict adherence to the KB speed‑diagnosis workflow, accurate technical language, and clear escalation pathways.

This Week's Calls