limuel.saura — Coaching Report

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

At a Glance

Scorecard

Scores reflect the number of calls reviewed (34) and the score range (lowest to highest overall).

This Week's Coverage

Models Supported

Lower scores on MR2000 and RE6350 calls suggest familiarity gaps with these devices' setup flows.

Problem Categories

SETUP calls are a focus area this week, with lower scores indicating a need for more structured troubleshooting and clearer guidance during initial configuration steps.

What Went Well

Correct Model Identification and Pairing Guidance

Correctly identified the product model (MX6200) early in the call and used the correct 5-press pairing method for Velop/Cognitive Mesh families.

#LTS00101304

Effective Use of Local Admin Access for Troubleshooting

Guided customer to access router locally via http://myrouter.local, which is a correct URL per KB.

#LTS00101304

Growth Opportunities

Incorrect Technical Guidance on Account Recovery and LED Behavior

Uh, the email that is has that has been associated to the account, uh then after that then you can then use a new email. You need to, yeah. You need to start over. Uh, yeah. Yes, the network will still be there, it's just that the account will not be- will no longer going to exist.

#TE00130749

What better looks like: Provide accurate account recovery steps per KB, such as password reset or recovery key verification, instead of advising account deletion. Clarify LED behavior based on the specific model and its documented meaning.

Premature Escalation Without Troubleshooting

No troubleshooting performed for degraded Velop system performance; premature recommendation to upgrade hardware without diagnostics.

#GI00130756

What better looks like: Perform basic diagnostics (reboot, signal check, firmware verification) before recommending hardware upgrades. Collect serial number and warranty status to guide appropriate support paths.

Next Week's Focus

1. Practice account recovery flows — Review KB articles for password reset, recovery key usage, and email change procedures. Conduct mock scenarios to ensure accurate guidance.
2. Master LED indicators for each model — Create a quick-reference cheat sheet for common LED behaviors (e.g., solid purple = setup ready on MX2000, red = no internet on EA series).
3. Implement structured troubleshooting for setup issues — Use a step-by-step checklist: reset, power cycle, WAN check, firmware update, then consider hardware options.
4. Improve call control and silence management — Use concise language, confirm understanding after each step, and avoid unnecessary repetition.

Technical Accuracy

Improvement

Uh, the email that is has that has been associated to the account, uh then after that then you can then use a new email. You need to, yeah. You need to start over. Uh, yeah. Yes, the network will still be there, it's just that the account will not be- will no longer going to exist.

Incorrect guidance on account recovery: claimed account must be removed and recreated to change email, which contradicts KB (universal_password_login.md).

#TE00130749

Improvement

Okay. So um are I mean do you experience this once or like let's say for example like twice or like whole week? Oh okay.

No troubleshooting performed for degraded Velop system performance; premature recommendation to upgrade hardware without diagnostics.

#GI00130756

Improvement

Failed to verify WAN/Internet LED status or perform basic connectivity troubleshooting despite identifying pulsing white LED as internet loss.

#LTS00130782

Improvement

Incorrect support URL provided; failed to verify WAN/ISP connectivity despite customer reporting no internet.

#LTS00130782

Improvement

Incorrect LED behavior guidance: stated MX2000 LED can go from white to red and back to white, contradicting KB (solid white = healthy; red = error).

#LTS00055780

Improvement

Incorrect default admin password ('admin') provided for MR20MS model; KB states default password is printed on the label.

#TE00130897

Coaching Moments

Improvement

Okay. So um are I mean do you experience this once or like let's say for example like twice or like whole week? Oh okay.

No troubleshooting performed for degraded Velop system performance; premature recommendation to upgrade hardware without diagnostics.

#GI00130756

Improvement

Failed to verify WAN/Internet LED status or perform basic connectivity troubleshooting despite identifying pulsing white LED as internet loss.

#LTS00130782

Improvement

Incorrect support URL provided; failed to verify WAN/ISP connectivity despite customer reporting no internet.

#LTS00130782

Improvement

Incorrect LED behavior guidance: stated MX2000 LED can go from white to red and back to white, contradicting KB (solid white = healthy; red = error).

#LTS00055780

Improvement

Incorrect default admin password ('admin') provided for MR20MS model; KB states default password is printed on the label.

#TE00130897

Improvement

Incorrect warranty/support end date provided (March 11, 2026), which is impossible and misleading.

#LTS00130918

Improvement

Incorrect default Wi-Fi SSID ('_Linksys Setup') provided for MX2000; KB states default SSID is 'LinksysXXXX'.

#LTS00130928

Improvement

Incorrect 5-press reset guidance for Velop 6E parent node, which is unsupported for extender pairing.

#LTS00130965

Improvement

Incorrect admin URL ('http://myrouter') provided; KB states correct URL is 'http://myrouter.local'.

#LTS00039798

Improvement

Incorrect guidance on router-admin password reset via email, which is not supported by Linksys firmware.

#LTS00131067

Improvement

Incorrect claim that router’s web UI cannot be accessed unless on local network; KB explicitly states local access is supported via IP/mDNS.

#TE00131076

Improvement

Incorrect claim that Linksys Smart Wi-Fi accounts are discontinued; KB confirms ongoing support for Smart Wi-Fi accounts.

#LTS00131228

Improvement

Incorrect 5-press reset guidance for SPNM-series device, which is not supported per KB.

#LTS00131401

Improvement

Incorrect local-access URL provided (http://www.local.local); KB states correct URL is 'http://myrouter.local'.

#LTS00131412

Improvement

No factory reset or power-cycle guidance provided for E5400 setup issue, violating standard troubleshooting flow.

#LTS00131421

Improvement

Incorrect 5-press reset guidance for SPNM60, which is not supported per KB.

#LTS00131449

Improvement

Incorrect URL provided (extender.tp-link.com); KB states correct URL is 'extender.linksys.com'.

#TE00131415

Improvement

Incorrect support URL provided (support.lingless.com); KB states correct URL is 'support.linksys.com'.

#LTS00131502

Improvement

Incorrect default admin password ('admin') provided for MR20MS; KB states default password is printed on the label.

#LTS00131507

Escalation Lessons: What L2 Did

#TE00130749 — Pending with Level 2

What L1 saw:

Customer wanted to remove the email used to create a Linksys cloud account but no longer had access to the original email. The account was associated with a WHW03 router.

Why it escalated:

L1 incorrectly advised deleting and recreating the account, which contradicts KB procedures. No standard account recovery steps were attempted.

Related call chain:

This was the initial contact; no prior interactions were documented.

What L2 did:

L2 initiated a callback process, acknowledging the need for email removal or account deletion. They communicated with HQ to determine the proper steps for account management and set expectations for a callback.

Current state:

The ticket is pending HQ feedback, indicating that L2 is awaiting guidance on how to proceed with the account email change.

L1 learning points:

1. Attempt standard account recovery first: Try password reset or recovery key verification before considering account deletion.
2. Verify ownership: Confirm the customer is the original account owner and collect necessary details (new email, spelling confirmation).
3. Escalate with clear documentation: Provide L2 with all relevant information, including device model, serial number, and a detailed summary of the customer’s request.

#TE00130897 — Resolved

What L1 saw:

Customer was setting up a new MR20MS router and needed help connecting it to their modem. The router showed a solid magenta/purple LED, and the Wi-Fi indicated "Connected without internet."

Why it escalated:

L1 provided incorrect default admin password and an unsupported 5-press reset procedure for the MR20MS. Internet connectivity was not restored during the call.

Related call chain:

This was the initial escalation. Subsequent calls involved other agents attempting to resolve the issue but ultimately failed to provide a solution.

What L2 did:

L2 performed a detailed diagnosis, verified WAN connectivity, corrected the admin password, and guided the customer through proper reset and configuration steps. They confirmed internet connectivity and ensured the router was properly set up.

Current state:

The ticket is resolved, with internet connectivity restored and the router configured correctly.

L1 learning points:

1. Use the correct default admin password: For MR20MS, the default password is printed on the device label, not "admin."
2. Follow model-specific reset procedures: The 5-press reset is not valid for MR20MS; use the standard factory reset method.
3. Verify WAN connectivity: Always check modem and WAN status before troubleshooting router configuration.

#TE00131076 — Resolved

What L1 saw:

Customer was locked out of their Linksys mobile app after multiple failed password reset attempts on an MR5500 router.

Why it escalated:

L1 incorrectly claimed that the router’s web UI could not be accessed off-network and failed to guide the customer through proper password recovery steps.

Related call chain:

This was the initial escalation. Follow-up calls involved other agents, but L2 ultimately resolved the issue.

What L2 did:

L2 guided the customer through the correct "Forgot Password" flow for the Linksys cloud account, including reinstalling the app and verifying email. They also provided self-help resources and confirmed that local access via http://myrouter.local was possible.

Current state:

The ticket is resolved, with the customer regaining access to their account and the router.

L1 learning points:

1. Guide customers through proper password recovery: Use the "Forgot Password" link, app reinstall, and email verification.
2. Clarify local access options: Explain that the router’s web UI can be accessed locally via IP/mDNS even without internet.
3. Provide self-help resources: Offer KB articles or email instructions to support customer independence.

#TE00131415 — Resolved

What L1 saw:

Customer reported that a laptop connected to a RE6350 extender showed "no internet," while other devices worked fine.

Why it escalated:

L1 advised the customer to contact their ISP (CenturyLink) without performing any router-level troubleshooting or verifying internet connectivity.

Related call chain:

This was the initial escalation. Follow-up calls involved other agents, but L2 ultimately resolved the issue.

What L2 did:

L2 verified internet connectivity on the primary router, guided the customer through extender configuration, and ensured the laptop could connect to the extender’s network. They also provided self-help steps for future reference.

Current state:

The ticket is resolved, with the laptop now showing internet connectivity through the extender.

L1 learning points:

1. Verify internet connectivity on the primary router: Always check WAN status before focusing on extenders.
2. Guide customers through extender configuration: Provide step-by-step instructions for adding and configuring extenders.
3. Offer self-help resources: Provide KB articles or email instructions to support customer independence.

Coach Appendix

Weekly Trend Summary:

The agent handled 34 calls this week, with a focus on connectivity and setup issues. The most common models were MX2000 and MR2000, indicating a need for stronger familiarity with these product lines. Technical accuracy was a recurring challenge, particularly around account recovery, LED behavior, and model-specific procedures. Protocol adherence varied, with some calls lacking essential steps like serial number collection or warranty verification.

Key Coaching Focus for Next Week:

• Technical Accuracy: Prioritize review of KB articles for account recovery, LED indicators, and model-specific setup procedures. Conduct mock calls to practice accurate guidance.
• Troubleshooting Discipline: Implement a structured troubleshooting flow for setup and connectivity issues, ensuring basic steps (reset, power cycle, WAN check) are always performed before escalation.
• Protocol Compliance: Ensure all calls collect essential information (model, serial, warranty status) and create HappyFox cases where appropriate. Practice concise call control to reduce silence and improve efficiency.

This Week's Calls

| #GI00131499 | 2026-05-29 21:51:48+00:00 | 2.