Zhiliang Chen — Coaching Report
Week of 2026-06-01 – 2026-06-07
At a Glance
| Calls Handled | Avg Handle Time | Top Product | Top Problem | Cases Documented | Cases Escalated |
|---|---|---|---|---|---|
| 5 | 19m 45s | LN1600 | SETUP | — | — |
Scorecard
| Dimension | This Week | Calls Reviewed |
|---|---|---|
| Accuracy | 2.50 | 4 |
| Protocol | 1.25 | 4 |
| Communication | 2.25 | 4 |
| Overall | 1.98 | 4 |
Where Time Goes
Product Families
| Family | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Note |
|---|---|---|---|---|---|---|---|
| LN | 2 | 18m 52s | 1.80 | 2.50 | 1.00 | 2.00 | |
| MBE | 1 | 13m 54s | 2.20 | 3.00 | 1.00 | 2.00 | |
| EA | 1 | 13m 8s | 2.10 | 2.00 | 2.00 | 3.00 |
Key Observations
- LN is one of the slowest families at 18m 52s.
- MBE is one of the slowest families at 13m 54s.
Problem Categories
| Category | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Focus Area? |
|---|---|---|---|---|---|---|---|
| SETUP | 4 | 16m 11s | 1.98 | 2.50 | 1.25 | 2.25 | ✓ |
| Unclassified | 1 | 47m 19s | — | — | — | — |
Week-over-Week Movement
- Improve technical accuracy (e.g., correct URLs, credentials, troubleshooting steps).
- Adhere to protocol (e.g., case documentation, follow-up, resolution verification).
- Address unresolved issues in SETUP category, especially for LN1600.
What Went Well
- Polite and patient communication
> "Okay, thank you"
Zhiliang maintained a courteous tone even when guiding customers through complex steps, contributing to a positive customer experience.
Growth Opportunities
- Technical accuracy and protocol adherence
> "Download firmware from www.ln1600.com"
What better looks like: Provide correct firmware URLs (e.g., official Linksys download pages) and verify default credentials against current KBs before instructing customers. Always confirm the customer can reach the admin page before proceeding.
- Case documentation and follow-up
> "Customer to try accessing the admin page via computer or iPad tomorrow; no further action taken by agent."
What better looks like: Create a HappyFox case for every hardware-related issue, document serial numbers, and set clear follow-up steps (e.g., callback time, verification checklist) to ensure continuity and accountability.
Next Week's Focus
- Verify model and serial numbers on every LN1600 or mesh call before troubleshooting.
- Create a HappyFox case for all hardware/setup issues, even if the customer declines immediate documentation.
- Confirm admin page accessibility (wired/Wi‑Fi, browser, VPN) before guiding customers through login steps.
- Use official Linksys resources for firmware/download links and default credentials.
Technical Accuracy
- Improvement
> Provided incorrect firmware download URL (www.ln1600.com) for LN1600 at [02:15].
Note: Always direct customers to official Linksys download pages and verify URLs against current KB articles.
- Improvement
> Incorrectly stated default login credentials (admin/admin) for LN1600, which uses a different default password per KB.
Note: Default credentials vary by model; consult the latest KB for accurate information before instructing customers.
- Improvement
> Did not verify if the customer could reach the admin page at [REDACTED_PHONE] despite advising it.
Note: Always confirm basic connectivity (wired/Wi‑Fi, browser access) before proceeding with admin-page troubleshooting.
- Improvement
> Failed to capture definitive model/serial number for MBE7000, leading to confusion and no standard mesh-node reset/pairing procedure.
Note: For mesh setups, always collect model/serial numbers and follow the documented reset/pairing flow; document steps taken.
Coaching Moments
- Strength
> "Okay, thank you"
Note: Polite acknowledgments help de-escalate frustration and build rapport, especially when customers are reporting intermittent issues.
Escalation Lessons: What L2 Did
No escalations occurred this week. All cases were resolved at Level 1 or documented for follow-up.
Coach Appendix
- Primary trend: Technical inaccuracies (URLs, credentials) and inconsistent protocol (case creation, serial capture) are the biggest barriers to resolution for LN1600 and mesh setups. Focus on verifying model details and using official resources will reduce repeat contacts.
- Key pattern: Calls involving LN1600 and setup issues show the lowest protocol scores. Reinforcing case documentation and follow-up steps will improve accountability and customer outcomes.