zhiliang.chen@concentrix.com — Coaching Report

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

At a Glance

Scorecard

Scores reflect 1 call reviewed. Score range: 1.1 (lowest) to 1.1 (highest).

This Week's Coverage

Models Supported

Pattern Note: The single call involved a high-end MBE7000 mesh router with connectivity/speed concerns. The low average score (1.1) highlights a need for stronger technical accuracy and troubleshooting consistency on this model.

Problem Categories

Focus Area Insight:

The CONNECTIVITY category shows a critical need for improved technical accuracy and troubleshooting discipline. The single call involved speed fluctuations and required clearer escalation pathways.

What Went Well

There were no explicit strengths highlighted in the data for this week. The focus will be on building foundational technical accuracy and escalation clarity going forward.

Growth Opportunities

1. Deliver technically accurate explanations

The agent provided an incorrect explanation about Wi‑Fi being “half‑duplex” and referenced a non‑existent “connector” that could be “reduced.” Accurate technical language builds trust and avoids confusion.

Next step: Review the KB article universal_speed_performance.md to understand Wi‑Fi duplex behavior and supported troubleshooting terminology. Practice explaining speed expectations using only documented concepts.

2. Perform structured troubleshooting before escalation

No troubleshooting steps were taken despite clear KB guidance for speed‑performance issues. Structured diagnostics (WAN speed test, wired baseline, firmware check, node placement review) are required before promising escalation.

Next step: Use the universal_speed_diagnosis.md checklist for all speed‑related calls. Document each step taken and the result before offering escalation.

Next Week's Focus

• Practice the universal speed‑diagnosis checklist on every connectivity/speed call — verify WAN speed, run a wired test, check firmware, and confirm node placement.
• Memorize three key Wi‑Fi facts: Wi‑Fi is full‑duplex, advertised speeds are maximums, and “connector” is not a supported troubleshooting term.
• When escalation is needed, clearly state: “I’ll open an escalation ticket, schedule a callback within X hours, and follow up with you at Y time.”
• Review escalation notes from L2 on the MBE7000 case to learn what technical data they required.

Technical Accuracy

Improvement

Agent provided factually incorrect technical explanation: stated Wi‑Fi is 'half‑duplex two‑way communication' limiting speed to 1200 Mbps. Wi‑Fi is full‑duplex and does not inherently halve advertised speed (contradicts KB universal_speed_performance.md)

#TE00129512

Improvement

Agent referenced non‑existent 'connector' that could be 'reduced' to improve speed - no KB reference exists for this term

#TE00129512

Improvement

No troubleshooting steps performed despite KB guidance for speed‑performance issues: no WAN speed verification, no wired baseline test, no reset, no firmware check, no node placement guidance

#TE00129512

Improvement

Agent promised undefined 'upgrade' without defining what it means, how it would be initiated, or when follow‑up would occur - no escalation path provided

#TE00129512

Escalation Lessons: What L2 Did

#TE00129512 — Pending with Level 2

What L1 saw:

Customer reported Wi‑Fi speed fluctuations (60‑300 Mbps) on an MBE7000 router advertised for 500‑600 Mbps. The agent offered an undefined “upgrade” without performing diagnostics or initiating escalation.

Why it escalated:

The case was escalated because L1 provided no actionable troubleshooting or escalation path — L2 needed to determine whether the issue was environmental, configuration-related, or a hardware/firmware problem.

What L2 did:

L2 requested network topology details, sysinfo logs from both parent and child nodes, and asked the customer to test with another wireless client device (preferably one supporting 6 GHz or Wi‑Fi 7). They also clarified that iPhones cannot display actual link speeds and suggested clearing preferred networks on the iPhone to isolate the issue.

Current state:

The case remains pending with Level 2, awaiting customer-provided logs and additional test results.

L1 learning points:

1. Collect topology and sysinfo logs early — these are essential for diagnosing mesh performance issues.
2. Ask for a wired speed test to establish a baseline and rule out ISP or modem limitations.
3. If the customer only has one wireless client, request they clear preferred networks and reconnect to the 6 GHz SSID to rule out profile-related interference.
4. Document every step taken and share findings with L2 to avoid repeated requests.

Coach Appendix

Highest-signal trend: The sole call involved severe technical accuracy gaps (incorrect Wi‑Fi duplex explanation, non‑existent “connector” term) and zero troubleshooting steps despite clear KB guidance for speed‑performance issues. The agent promised an undefined “upgrade” without escalation path or follow‑up expectation, resulting in an abandoned-or-vague closure status. Focus for next coaching should be on structured troubleshooting (universal_speed_diagnosis.md) and precise escalation protocols.

This Week's Calls