aysah.bagumbaran — Coaching Report

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

At a Glance

Scorecard

Scores range from 1.1 (lowest overall) to 3.6 (highest overall) across reviewed calls.

Where Time Goes

Models Supported

Key Observations:

• MX2000 and E7350 dominate handle time while scoring lowest on accuracy and overall ratings — indicates need for targeted troubleshooting training.
• WHW03 shows better balance but still benefits from deeper protocol adherence.

Problem Categories

Focus Areas:

• CONNECTIVITY calls average 2.1 overall with frequent protocol gaps (e.g., missing WAN checks).
• SETUP issues show similar patterns — prioritize structured troubleshooting flows and model-specific KB references.

What Went Well

1. Clear communication and customer engagement

> "I appreciate your patience while we work through this. Let’s start by resetting the modem and router, then I’ll guide you through re-pairing the nodes."

#LTS00130930 — Maintained polite tone and provided step-by-step instructions.

1. Accurate technical guidance for specific scenarios

> "To separate bands on your WHW03, we’ll rename the 2.4 GHz, 5 GHz, and 6 GHz SSIDs in the web UI. This ensures your sprinkler controller connects to the dedicated 2.4 GHz network."

#LTS00130930 — Aligned with KB guidance for band separation.

1. Effective self-help redirection

> "Since your SE3005 is an unmanaged switch, firewall settings must be adjusted on your router (Spectrum gateway or eero). I’ll email you the exact steps."

#LTS00131316 — Correctly identified device limitations and directed to appropriate resources.

Growth Opportunities

1. Technical accuracy and product knowledge

> "The Velop Pro 7 is a standalone router, not a mesh system — you can use it independently."

#GI00130724 — Next step: Always verify product specs before claiming capabilities. Velop Pro 7 is a mesh node requiring Intelligent Mesh setup.

1. Protocol adherence and troubleshooting depth

> "Your MX2000 can deliver up to 3 Gbps Wi-Fi speed — let’s escalate to Level 2 for further testing."

#TE00130759 — Next step: Run basic speed tests and WAN checks before escalation. MX2000’s max speed is 2.5 Gbps per KB.

Next Week's Focus

• Verify product models and specs before providing technical guidance (e.g., confirm MX2000 vs. MR9000 capabilities).
• Document serial numbers and warranty status for every call to enable accurate support eligibility checks.
• Perform basic connectivity diagnostics (WAN cable check, modem reboot, LED verification) before escalating connectivity issues.
• Use correct registration URL (register.linksys.com) — avoid inventing domains like register.lingncist.com.

Technical Accuracy

Improvement

Provided incorrect registration URLs (e.g., register.lingncist.com, register.linkages.com) for MX2000. Correct URL is register.linksys.com (KB: article 90-en).

#TE00130759

Improvement

5-press calibration: WHW03 and MX5500 can support 5-press pairing/recovery in supported child-node contexts. Do not coach this as unsupported solely because the product is Velop, WHW, MX, or MR; treat it as an error only when the evidence shows the method was wrong for the model/state, described as a factory reset by itself, failed without a pivot, or contradicted KB guidance.

#LTS00131057

Improvement

Incorrectly stated EA6900 is no longer supported. EA6900 remains supported with firmware updates (KB: EA69xx firmware matrix).

#LTS00131075

Strength

Accurately guided MX6200 customer to separate 2.4 GHz, 5 GHz, and 6 GHz bands via web UI, aligning with KB band-separation steps.

#LTS00130947

Escalation Lessons: What L2 Did

#TE00130759 — Pending with Level 2

• What L1 saw: Customer reported slow speeds/poor range on new MX2000 mesh system (3 days old). L1 collected serial number, verified product, but provided incorrect registration URLs and false speed claims.
• Why it escalated: Customer requested L2 after L1 failed to troubleshoot Wi-Fi performance (no speed test, no node placement check).
• What L2 did:

- Validated RSSI levels were beyond acceptable threshold.

- Recommended testing connection near parent node and using alternate server for speed tests.

- Scheduled callback to confirm defect and discuss pro-rated refund/RMA if needed.

• Current state: Callback pending; L2 awaiting customer availability.
• L1 learning points:

1. Always perform speed tests and RSSI checks before escalation.

2. Use correct registration URL (register.linksys.com).

3. MX2000 max speed is 2.5 Gbps — never claim 3 Gbps.

#TE00131076 — Resolved by Level 2

• What L1 saw: MR5500 customer couldn’t access cloud account after password resets. L1 escalated after 24-hour wait period expired with no resolution.
• Why it escalated: L1 failed to collect product/model details or verify app discontinuation for MR5500.
• What L2 did:

- Confirmed MR5500 cloud access was discontinued (per KB: MR55xx cloud retired in 2023).

- Guided customer to use local web UI (myrouter.info) for configuration.

- Updated ticket status to Resolved.

• Current state: Resolved via self-help.
• L1 learning points:

1. Know product-specific cloud support timelines (e.g., MR55xx retired).

2. Always redirect to local UI when cloud access is discontinued.

3. Collect model/serial upfront to avoid escalation delays.

Coach Appendix

High-level trend: Connectivity and setup calls dominate with prolonged handle times and inconsistent scores. Key gaps include insufficient troubleshooting depth (e.g., missing WAN checks) and occasional PCI violations (e.g., card data collection). Prioritize structured diagnostic flows for CONNECTIVITY/SETUP categories and reinforce data security protocols.

This Week's Calls