aysah.bagumbaran — Coaching Report

Week of 2026-06-01 – 2026-06-07

At a Glance

Scorecard

Where Time Goes

Product Families

Key Observations

• LN is the slowest family at 40m 1s; outlier: 1.6x weekly median handle time.
• MX is one of the slowest families at 34m 15s.

Problem Categories

Week-over-Week Movement

• Improve accuracy in technical guidance, especially for model-specific procedures.
• Enhance protocol adherence and resolution verification.
• Reduce premature escalation to paid support without basic troubleshooting.

What Went Well

1. Effective Troubleshooting Guidance

Guided customer through 5-press pairing on the parent MBE7000, confirmed successful reconnection (solid white), and advised relocation.

> "Guided customer through 5-press pairing on the parent MBE7000... successful reconnection (solid white)"

#LTS00131610

1. Clear Communication and Empathy

Used customer’s name (Joyce) to personalize the interaction and displayed empathy for age-related frustration during router setup.

> "Used customer's name (Joyce)... empathy for customer's age and frustration"

#LTS00131631

Growth Opportunities

1. Incorrect Technical Guidance

Provided incorrect reset duration (30 seconds) for MX6200 (KB specifies 10–15 seconds) and misdescribed LED behavior during reset.

> "Provided incorrect reset duration (30 seconds)... misdescribed LED behavior"

#LTS00125222

Next Step: Always cross-check model-specific reset procedures in KB before instructing customers.

1. Failure to Verify Resolution

Did not confirm whether the customer successfully reconnected the cable or restored internet connectivity after guidance.

> "Failed to confirm whether the customer successfully reconnected the cable..."

#LTS00131683

Next Step: End every connectivity call with a direct “Can you confirm your internet is now working?” check.

Next Week's Focus

• Verify Resolution: Close every call with a confirmed “Internet is working” or “Device is online” check.
• Model-Specific Reset Times: Memorize KB reset durations (e.g., MX6200: 10–15s, MR6350: 30s) to avoid errors.
• Standardize Setup Flow: Create a checklist for router registration (serial entry, WAN port, app vs. web UI).
• Empathy + Name Use: Continue personalizing calls with the customer’s name while maintaining efficiency.

Technical Accuracy

Strength

• Correct 5-press pairing for MBE7000

Guided customer through proper mesh-node pairing method per KB Section B.

#LTS00131610

Improvements

• Incorrect server dependency claim

Incorrectly stated local UI depends on remote server; KB confirms it is self-hosted.

#TE00131695

• Invalid URLs and recovery path

Provided non-existent URLs (register.plingsys.com) and omitted 5-digit recovery key steps.

#LTS00132295

• Unsupported pairing method

Applied 5-press pairing to MX6200, which only works on LN1100/MBE7000 per KB.

#LTS00132035

Coaching Moments

Strength

• Patience with LED confusion

> "Instructed power-cycle of child node after LED confusion... monitored changes until solid white."

#LTS00131610

Improvement

• LED misdescription

> "Misdescribed LED behavior: claimed it would blink red three times and turn off before blue — not accurate per KB."

#LTS00125222

Escalation Lessons: What L2 Did

#TE00131695 — Resolved by Level 2

• What L1 Saw: Customer couldn’t access MR20EC router UI (blank blue screen) after factory reset.
• Why it Escalated: L1 incorrectly attributed issue to downed remote server and lacked model-specific troubleshooting.
• What L2 Did: Verified router model, guided through correct 30s reset (LED behavior: solid red → flashing white → solid blue), and confirmed UI access via Ethernet.
• Current State: Resolved.
• L1 Learning Points:

1. Always confirm router model before troubleshooting.

2. Use model-specific reset steps (MR20EC: 30s hold, solid red → flashing white → solid blue).

3. Test UI access via Ethernet before declaring success.

#TE00083279 — Resolved by Level 2

• What L1 Saw: MX6200 child node showed solid red and disconnected.
• Why it Escalated: L1 used incorrect 30s reset and D-Link app suggestion; no mesh reconnection verification.
• What L2 Did: Guided through proper 10s reset, 5-press pairing (if Cognitive Mesh), and confirmed mesh status via app.
• Current State: Resolved.
• L1 Learning Points:

1. MX6200 requires 10s reset, not 30s.

2. Never recommend D-Link app for Linksys devices.

3. Always verify mesh status in app/admin UI after reset.

#LTS00132295 — Resolved by Level 2

• What L1 Saw: LN11011202 router UI stuck on “Trying to reach Linksys Now?”.
• Why it Escalated: L1 provided invalid URLs and claimed UI only works offline.
• What L2 Did: Confirmed firmware issue, guided through recovery-key password reset, and accessed UI via Ethernet.
• Current State: Resolved.
• L1 Learning Points:

1. Use recovery key for admin password reset (printed on device).

2. UI is accessible offline via Ethernet; no remote server dependency.

3. Provide correct direct URLs (e.g., http://[REDACTED_PHONE]).

Coach Appendix

• Top Trend: Increased call volume (+15) with stable resolution rate (38%). Communication and accuracy scores dipped slightly due to inconsistent technical guidance during SETUP and CONNECTIVITY calls.
• Key Pattern: Premature escalation to paid support without basic triage (e.g., power-cycle, WAN test) in 7/10 unresolved cases.
• Evidence: Focus on model-specific KB adherence and resolution verification to improve accuracy and communication scores next week.

This Week's Calls

| [#