Zhiliang Chen — Coaching Report

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

At a Glance

Scorecard

3 calls reviewed; score range: 1.0 – 3.0

This Week's Coverage

Models Supported

Lower scores on MBE7000 calls suggest a need for deeper familiarity with this model's firmware update flow and admin UI.

Problem Categories

The SETUP category shows room for improvement, especially around accurate UI guidance and efficient troubleshooting for firmware and connectivity issues.

What Went Well

This week, you showed resilience and persistence in guiding customers through complex setups. One standout moment was your ability to see a customer through to a working solution despite initial confusion:

#LTS00131366

"Persisted through customer confusion and eventually guided them to correct cable connections. Provided correct URL and default login credentials. Successfully guided customer to complete Wi‑Fi setup and achieve solid blue LED status. Confirmed resolution with customer and provided closure."

This demonstrates your capacity to stay calm, follow structured troubleshooting, and confirm success — qualities that will serve you well as you refine your technical accuracy.

Growth Opportunities

1. Avoid inventing UI elements or steps not in KB documentation

In one call, you directed a customer to a non‑existent “CA” button in the MBE7000 admin UI, which directly contradicted our knowledge base and left the customer stranded:

#LTS00130811

"Provided materially incorrect technical guidance by inventing a non‑existent ‘CA’ button in the MBE7000 admin UI, directly contradicting the KB."

What good looks like:

• Always verify UI element names and locations against the current KB or device manual before instructing a customer.
• If you’re unsure, say, “Let me check the exact steps for your model and get back to you,” rather than guessing.
• After guiding a customer through a process, confirm they see the expected result (e.g., “Did the firmware update complete successfully?”).

2. Engage the customer’s language and perform basic troubleshooting before escalating

In another call, you played repeated language prompts instead of engaging the customer, and no troubleshooting was performed:

#LTS00131366

"Failed to acknowledge or confirm customer’s language (English), leading to repeated irrelevant Cantonese prompts. Did not collect product model, serial number, or warranty information despite clear need. Provided no actual troubleshooting for a setup issue."

What good looks like:

• Greet the customer in the language they use (e.g., “I see you’re speaking English — I’ll continue in English”).
• Collect basic info upfront: product model, serial number, and brief description of the issue.
• Run a quick loop of foundational checks (reset, cable connections, LED interpretation) before considering escalation.
• If the issue remains unresolved after these steps, document what you tried and clearly explain the next action (“I’ll open an escalation for our technical team and follow up shortly”).

Next Week's Focus

1. Start every call with model/serial collection — even if the customer mentions the product early, confirm the exact model and ask for the serial number.
2. Cross‑check UI guidance — before mentioning any button, menu, or step, glance at the KB article for that exact model.
3. Validate each action — after a customer performs a step (e.g., reset, cable swap), ask a confirming question (“Is the LED now solid blue?”).
4. Close the loop — if a call ends without a clear resolution, note the next step for the customer and set a follow‑up (callback, email, or escalation).

Technical Accuracy

Improvement

#LTS00130811

"Invented non‑existent ‘CA’ button in MBE7000 admin UI, contradicting KB and leaving call unresolved. No validation of firmware update was performed."

Note: inventing UI elements undermines trust and leaves customers without a path forward. Always verify against KB before instructing customers. Confirm success after each major step.

Improvement

#LTS00131366

"Failed to engage customer speaking English, repeatedly played Cantonese prompts. No troubleshooting performed for MX5300 setup issue, leaving call unresolved."

Note: Engaging the customer’s language and running basic troubleshooting (reset, cables, LED checks) are essential first steps. Avoid letting automated prompts dominate the call.

Improvement

#LTS00131366

"Incorrect LED guidance (validating purple/pink as reset modes) and excessive looping on reset instructions reduced call efficiency."

Note: Purple/pink LEDs are not standard reset indicators on Linksys devices. Validate LED meanings against the device’s spec sheet, and avoid repeating the same instruction many times — summarize and move forward.

Coaching Moments

Improvement

#LTS00131366

"Repeated the phrase ‘Pressing the reset button and there was no response’ 15+ times between [69:51–70:35], creating excessive looping and poor call control."

Note: Repetitive looping frustrates customers and wastes time. If a step isn’t working, try an alternative approach (e.g., “Since the reset didn’t change the LED, let’s try reconnecting the WAN cable”) and avoid repeating the same instruction.

Escalation Lessons: What L2 Did

No escalated cases were recorded this week, and the activity log shows 0 cases escalated. This suggests that while some calls ended unresolved, they were not formally escalated to Level 2. To improve resolution rates, consider completing the following before escalation becomes necessary:

• Verify model and serial number.
• Run a quick loop of foundational troubleshooting (reset, cables, LED interpretation, ISP check).
• Confirm each step with the customer and document the outcome.
• If the issue persists after these steps, open an escalation with a concise summary of what was tried and what remains unresolved.

Coach Appendix

Highest-signal trend: Three of four calls ended unresolved due to inaccurate technical guidance (invented UI elements) or failure to engage/basic troubleshoot. The single resolved call succeeded because the agent persisted through confusion, verified cable connections, and confirmed a working LED. Focus next week on verifying KB steps before instructing customers and running a quick foundational loop (reset, cables, LED) for setup issues.