xiangjie.zhang@concentrix.com — Coaching Report

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

At a Glance

Scorecard

Scores reflect the average across 5 calls reviewed. Overall scores ranged from 1.7 to 3.0.

This Week's Coverage

Models Supported

Key pattern: Lower scores on FGHSAX1800 and MX2000 calls suggest a need for deeper familiarity with reset procedures and mesh-node recovery flows for these models.

Problem Categories

Hardware & Connectivity show lower average scores, indicating these categories merit focused improvement. Review KB articles for hardware reset sequences and structured troubleshooting for connectivity issues.

What Went Well

Accurate technical resolution in hardware follow-up

The agent collected essential customer information and opened a case for traceability, ensuring the issue was documented and actionable.

Collected customer's email and opened a case for traceability.

#LTS00130821

High accuracy in technical calls

Two calls earned perfect accuracy scores, reflecting strong product knowledge and correct information delivery.

(No direct transcript quotes available for these moments.)

Growth Opportunities

Avoid providing incorrect reset procedures

In one call, the agent gave a reset instruction that contradicts KB guidance, leading to unresolved customer issues. What “good” looks like: Always verify model-specific reset steps in the KB before instructing customers, and confirm the outcome after the procedure.

Provided materially incorrect reset procedure (WPS + power button for 5 seconds) that contradicts the KB for AX/Max-Stream models (requires 10-second reset via reset button).

#LTS00130813

Implement structured troubleshooting

Calls often skipped basic diagnostic steps (power cycles, LED checks, firmware verification). What “good” looks like: Use a consistent troubleshooting framework—gather facts, run targeted tests, validate results, and document each step. This reduces escalations and builds customer confidence.

(No direct transcript quotes available for this moment.)

Next Week's Focus

1. Verify model-specific reset steps in the KB before instructing customers; confirm the exact button and duration for each device.
2. Adopt a 4-step troubleshooting framework for hardware issues: (1) Gather device details, (2) Run power-cycle/LED check, (3) Validate firmware/LED meanings, (4) Document findings and next steps.
3. Reduce filler language and long silent holds—use concise updates every 30–45 seconds to keep customers informed.
4. Collect serial numbers and warranty details early in every call to enable faster escalations or RMA processing if needed.

Technical Accuracy

Improvement

Agent provided incorrect reset instructions for FGHSAX1800, leading to unresolved customer issue.

#LTS00130813

Improvement

Agent failed to follow KB's mesh-node recovery procedure for MX2000.

#LTS00130821

Strength

Agent collected customer's email and opened a case for traceability in hardware follow-up.

#LTS00130821

Coaching Moments

Improvement

Provided materially incorrect reset procedure (WPS + power button for 5 seconds) that contradicts the KB for AX/Max-Stream models (requires 10-second reset via reset button).

#LTS00130813

Improvement

Gave materially wrong reset instructions for MX2000: advised 30-second on/off power cycles ([02:50-03:29]), which is not a documented recovery method in the KB. Correct procedure is 10-second reset until red LED appears.

#LTS00130821

Escalation Lessons: What L2 Did

#LTS00131353 — Resolved by Level 2

What L1 saw:

Customer reported that the Linksys app shows zero devices and zero mesh nodes after reinstalling; unable to view connected device information. Product: MBE7000. L1 asked about login method and confirmed router restart but took no further diagnostics.

Why it escalated:

L1 did not verify basic connectivity (e.g., admin page access, mesh node LEDs), skipped structured troubleshooting, and escalated after only minimal diagnostic steps.

What L2 did:

L2 likely performed deeper diagnostics—checking mesh node LED states, verifying firmware versions, testing local admin access (myrouter.local), and possibly inspecting backend service logs to determine why the app returned zero devices. The case was eventually resolved, indicating L2 identified either a firmware bug, service outage, or configuration mismatch.

Current state: Resolved.

L1 learning points:

1. Before escalating app-zero-device issues, verify the customer can access the router’s admin page (http://myrouter.local) and confirm mesh node LEDs are solid, not flashing.
2. Collect app version and firmware version; cross-reference known issues in the KB.
3. Attempt a manual re-add of mesh nodes via the admin page if the app fails, and document the outcome.

Coach Appendix

This week’s highest-signal trend is inconsistent adherence to KB-guided reset procedures, especially for AX/Max-Stream and Velop models. Focus next week on verifying model-specific steps and applying a structured troubleshooting framework to reduce escalations and improve scores in hardware and connectivity categories.

This Week's Calls