aysah.bagumbaran — Coaching Report

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

At a Glance

Work Mix Lens

• Frontline-heavy week: 24 LTS queue calls vs 2 TE-owned calls.
• Coach as a frontline agent: emphasize safe troubleshooting branches, closure hygiene, and clear customer-facing next steps.

Scorecard

Where Time Goes

Product Families

Key Observations

• MX is the slowest family at 32m 9s; outlier: 2.1x weekly median handle time.
• E is the slowest family at 26m 24s; outlier: 1.8x weekly median handle time.

Problem Categories

Week-over-Week Movement

• Overall moved up 0.30 vs. last week.
• Accuracy moved up 0.39 vs. last week.
• Protocol moved up 0.17 vs. last week.
• Average handle time moved up by 1m 06s.
• Family swing: E handle time moved up by 18m 54s vs. last week.
• Family swing: MBE handle time moved down by 14m 10s vs. last week.
• Family swing: WHW handle time moved up by 9m 19s vs. last week.

What Went Well

1. Accurate technical guidance for unmanaged switch

> “The SE3005 is an unmanaged switch with no firewall capabilities. Firewall settings must be adjusted on the router (Spectrum or eero).”

#LTS00131316

1. Clear explanation of guest network security

> “I’m going to see the number of your Linksys. Is that up? The serial number of your Linksys router…”

#LTS00130772

Growth Opportunities

1. Correct model identification and technical claims

> “The WHW03 is no longer supported by the Linksys app due to firmware updates and cloud service removal.”

#TE00130759

What better looks like: Verify product support status via KB before stating discontinuation; confirm app compatibility with current firmware.

1. PCI compliance and secure transaction handling

> “[REDACTED] full credit-card number, expiration date, and CVV collected over unsecured line.”

#LTS00131057

What better looks like: Use secure payment portals; never collect full card details over the phone.

Next Week's Focus

• Model-first triage: Confirm product model and warranty status before providing password defaults or troubleshooting steps.
• WAN validation: For red LED or connectivity issues, always check WAN cable, modem power cycle, and ISP status first.
• Self-help paths: Offer KB articles or email guides for out-of-warranty setup questions to reduce handle time.
• Secure data handling: Redirect paid-support transactions to secure portals; document only last four digits if needed.

Technical Accuracy

Improvement

Provided three invalid registration URLs: register.lingncist.com, register.linkages.com, and register.rgsestination.com.

Correct KB reference: https://support.linksys.com/kb/article/90-en/.

#TE00130759

Improvement

Incorrect speed claim for MX2000 model (stated up to 3 Gbps Wi‑Fi speed; actual max is 2.4 GHz/5 GHz only).

#TE00130759

Improvement

Incorrect technical information about guest Wi‑Fi security on EA7300 (claimed HTTP authentication; actual WPA2).

#LTS00130889

Improvement

PCI compliance violation: full credit-card details collected over unsecured line.

#LTS00131057

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

Incorrect registration URL provided during cloud-access issue.

#TE00131076

Strength

Accurate model identification and guidance for band separation on MX6200.

#LTS00130947

Coaching Moments

No additional coaching moments were extracted after the technical review.

Escalation Lessons: What L2 Did

#TE00130759 — Callback

• What L1 saw: MX2000 mesh system with slow speed/poor range after node setup; customer requested escalation.
• Why it escalated: L1 lacked speed-test diagnostics, misstated MX2000 capabilities, and provided invalid registration URLs.
• What L2 did:

- Verified WAN connectivity and modem sync.

- Confirmed MX2000 specs (no 3 Gbps Wi‑Fi; max 1 Gbps on 5 GHz).

- Guided customer through node reset and placement optimization.

• Current state: Callback scheduled; L2 awaiting customer response.
• L1 learning points:

1. Run speed tests and check RSSI before escalation.

2. Reference KB for model-specific speeds and registration URLs.

3. Validate node placement and WAN link quality.

#TE00131076 — Resolved

• What L1 saw: MR5500 cloud account locked out after password resets; customer unable to access app.
• Why it escalated: L1 failed to collect model/serial, mispronounced brand, and provided incorrect registration URL.
• What L2 did:

- Explained discontinued Linksys cloud app; directed to web UI (http://myrouter.local).

- Reset cloud account lockout via backend tools.

- Provided temporary password and reset instructions.

• Current state: Resolved.
• L1 learning points:

1. Confirm cloud service status for MR5500 (discontinued).

2. Always collect model/serial before troubleshooting.

3. Use correct URLs (register.linksys.com, not linksus.com).

Coach Appendix

• Weekly trend: Frontline-heavy week dominated by connectivity and setup issues on WHW03, MX, and E families. Accuracy improved but protocol consistency lags—prioritize model verification and WAN diagnostics.
• Recurring patterns:

- Model misidentification leading to incorrect guidance (e.g., WHW03 app support, MX2000 speeds).

- PCI violations during paid-support transactions.

- Incomplete self-help redirection for out-of-warranty setup questions.

• Next coaching focus: Reinforce model-specific KB lookup, secure payment handling, and structured WAN/LED troubleshooting for connectivity cases.

This Week's Calls

| [#LTS00131254](https://linksys.happyfox