aysah.bagumbaran — Coaching Report

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

At a Glance

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

• Improve accuracy in product model identification and troubleshooting steps.
• Reduce materially false technical claims and incorrect guidance.
• Enhance protocol adherence, especially for warranty verification and case documentation.

What Went Well

1. Accurate technical guidance for unmanaged switch

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

#LTS00131316

1. Clear explanation of guest network security

> "The distinction between Wi‑Fi password and router admin password is critical. The default admin password is ‘admin’ for this model."

#LTS00130772

1. Effective self-help path for password reset

Guided customers to access router UI via local IP and change Wi‑Fi password, avoiding unnecessary escalation.

Growth Opportunities

1. Avoid unsupported troubleshooting methods

> "Use another server in testing the speed - the devices used during the speed test are getting RSSI that's beyond the acceptable threshold - test the connection of the device while close to the parent node..."

#TE00130759

What better looks like: Verify product model compatibility before suggesting troubleshooting steps (e.g., 5‑press pairing is invalid for WHW01). Always reference KB for model-specific procedures.

1. Prevent materially false technical claims

> "The MX2000 router can deliver up to 3 Gbps Wi‑Fi speed"

#TE00130759

What better looks like: Cross‑check product specifications against KB before stating performance capabilities. Use precise language (e.g., "up to 2.5 Gbps on 5 GHz band").

Next Week's Focus

• Verify product model and warranty status before initiating troubleshooting.
• Avoid model‑specific pitfalls (e.g., never use 5‑press pairing on WHW01; use Pair button or web UI).
• Double‑check technical claims against KB before stating speeds, defaults, or capabilities.
• Document all steps in HappyFox to improve handoff consistency.

Technical Accuracy

Improvement

Agent provided three invalid registration URLs: register.lingncist.com, register.linkages.com, and register.rgsestination.com. Correct URL is register.linksys.com per KB.

#TE00130759

Improvement

Agent claimed the MX2000 can deliver up to 3 Gbps Wi‑Fi speed, which is factually incorrect per the MX2000's specifications in the KB.

#TE00130759

Improvement

Agent used '5‑press' pairing method on WHW01, which is not supported for this model. Correct method is Pair button or web UI Add Node per KB.

#LTS00131057

Improvement

Agent provided 'admin' as default router admin password without verifying product model, which is incorrect for many Linksys models (e.g., newer Velop, MX, SPNM use different defaults).

#LTS00130772

Coaching Moments

Improvement

"All right, since you want to apply for the paid support, Adam, because your product is out of warranty, let me set expectation that this paid support is a one time non-refundable..."

#LTS00131254

Note: Immediately upselling paid support without attempting basic troubleshooting violates protocol. Always attempt free self-help steps first.

Improvement

"I'm sorry, as a based on the information provided, the ethernet port on the ZenBook MX200's ethernet port is allowed up to 1 gig."

#GI00130724

Note: Providing irrelevant technical details about non-Linksys devices (ZenBook) confuses the issue. Focus on the customer’s actual Linksys product.

Escalation Lessons: What L2 Did

#TE00130759 — Pending with Level 2

• What L1 saw: Customer reported slow speed/poor range on MX2000 mesh system. L1 collected serial number, attempted warranty verification, and escalated.
• Why it escalated: Customer requested L2 intervention due to unresolved performance issues.
• What L2 did:

- Verified RSSI levels and device placement.

- Conducted speed tests using alternate servers.

- Recommended express forwarding and callback.

• Current state: Callback scheduled; ticket remains open.
• L1 learning points:

1. Always confirm mesh node placement and RSSI before escalation.

2. Use KB-guided speed-test procedures (e.g., universal_speed_performance.md).

3. Document exact troubleshooting steps attempted to avoid repeat work.

#TE00131076 — Resolved by Level 2

• What L1 saw: Customer couldn’t access MR5500 cloud account after password resets. L1 verified account lock status and escalated.
• Why it escalated: Cloud account remained locked despite 24‑hour wait.
• What L2 did:

- Reset cloud account password via backend tools.

- Verified account unlock and re‑authenticated customer.

• Current state: Resolved.
• L1 learning points:

1. Confirm cloud‑service status (e.g., account lock) before escalating.

2. Provide clear 24‑hour wait instructions with exact time windows.

3. Document password‑reset attempts in HappyFox for L2 visibility.

Coach Appendix

Highest-signal trend: Materially false technical claims and unsupported troubleshooting steps (e.g., invalid URLs, incorrect speeds, unsupported pairing) caused escalations and customer confusion. Focus next week on KB validation before guidance and model‑specific protocol adherence.

This Week's Calls