eppie.lagumbay — Coaching Report

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

At a Glance

Scorecard

Where Time Goes

Product Families

Key Observations

• MX is the slowest family at 45m 20s; outlier: 2.8x weekly median handle time.
• WHW is the slowest family at 45m 10s; outlier: 2.8x weekly median handle time.

Problem Categories

Week-over-Week Movement

• Overall moved up 0.15 vs. last week.
• Accuracy moved up 0.49 vs. last week.
• Average handle time moved up by 6m 12s.
• Family swing: MR handle time moved down by 23m 43s vs. last week.
• Family swing: WHW handle time moved up by 16m 59s vs. last week.
• Family swing: EA handle time moved down by 14m 19s vs. last week.

What Went Well

1. Accurate EOL Guidance

> "End of life. There will be no further updates for that. So as long as the device is still working, you can still make use of it."

#GI00131690

Provided clear, KB-aligned advice for an EA7300, avoiding unnecessary troubleshooting.

1. Persistence in Complex Mesh Issues

> "We will perform a reset. I on that node, ma'am? So, just kindly press and hold the child node."

#LTS00131700

Guided a WHW03 mesh rebuild through multiple resets and re-pairing steps, ultimately restoring connectivity.

Growth Opportunities

1. Technical Accuracy & URL Safety

> "You can access support at support.callinksys.com for additional resources."

#LTS00131700

Next Step: Always verify URLs before sharing. Use only support.linksys.com or myrouter.local for local access.

1. Basic Troubleshooting Before Escalation

> "I didn’t verify internet connectivity with the modem before proceeding."

#LTS00131709

Next Step: Always confirm modem/WAN status (LED, wired test) before diving into router-level fixes.

Next Week's Focus

1. Verify Warranty & Collect Serial Numbers First

- Avoid jumping into troubleshooting without confirming eligibility.

1. Use Correct Reset Durations

- WHW03: 10–15 seconds (not 25s). MX series: 10+ seconds.

1. Document Every Step in HappyFox

- Ensure all actions, URLs shared, and customer responses are logged.

1. Confirm Resolution Before Closing

- Run a final connectivity test (e.g., ping 8.8.8.8 or website load) to validate fixes.

Technical Accuracy

Improvement

No transcript quote available.

Incorrect support URL provided (support.callinksys.com), posing security risk. \#LTS00131700

Note: Always use support.linksys.com for public resources.

Improvement

No transcript quote available.

Skipped modem/WAN validation before router troubleshooting. \#LTS00131709

Note: Verify modem LEDs and wired connectivity first for CONNECTIVITY issues.

Improvement

No transcript quote available.

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.

Note: WHW03 requires Pair Button or app-based pairing only.

Strength

No transcript quote available.

Accurate EOL guidance for EA7300, aligning with KB. \#GI00131690

Note: Clear communication of product limitations avoids wasted time.

Coaching Moments

Improvement

"We will actually move that child node close to the main node. Make sure it's five to eight feet away, because we need to configure that."

\#LTS00096076

Note: Incorrect distance guidance for MX4200 mesh (optimal: 3–5 ft). Retrain node placement rules.

Improvement

"The default admin password is 'admin' for MX series."

\#LTS00132116

Note: MX series uses recovery key, not 'admin'. Review KB for default credentials.

Escalation Lessons: What L2 Did

#TE00131905 — Resolved by Level 2

• What L1 Saw: WHW03 flashing red after ISP change; admin UI unreachable.
• Why it Escalated: L1 misdiagnosed with unsupported 5-press pairing and incorrect URLs.
• What L2 Did: Performed proper browser-based setup via myrouter.info, validated WAN connection, and re-paired nodes using the Pair Button.
• Current State: Resolved.
• L1 Learning Points:

1. Use myrouter.info or myrouter.local for WHW03 setup after ISP changes.

2. Avoid 5-press pairing on WHW03; use Pair Button or app.

3. Verify WAN port connectivity before troubleshooting mesh nodes.

#LTS00002343 — Resolved by Level 2

• What L1 Saw: MX6200 mesh role-swapping and red LED on child node.
• Why it Escalated: L1 applied unsupported 5-press pairing and incorrect reset durations.
• What L2 Did: Rebooted mesh system, validated firmware, and re-paired nodes via the Linksys app.
• Current State: Resolved.
• L1 Learning Points:

1. MX6200 requires app-based pairing; avoid 5-press reset.

2. Confirm firmware version matches KB recommendations.

3. Use http://myrouter.local for admin access, not https://.

Coach Appendix

Weekly Trend:

Frontline-heavy week (46 LTS calls vs. 3 escalations). MX/WHW families drive long handle times and lower protocol scores.

Key Pattern:

Frequent misuse of reset/pairing methods on mesh systems (WHW03, MX series) leads to unresolved issues and escalations.

Next Coaching Focus:

• Review mesh troubleshooting KB articles together.
• Practice reset/pairing workflows for WHW03 and MX series in a sandbox environment.

This Week's Calls