aysah.bagumbaran — Coaching Report

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

At a Glance

Scorecard

Scores reflect a week with limited call volume (34 calls reviewed). Overall scores range from 1.1 to 3.6.

This Week's Coverage

Models Supported

Pattern Note: Lower scores on WHW03 and MX2000 calls suggest a need to reinforce familiarity with these mesh systems, particularly around pairing, LED interpretation, and troubleshooting connectivity issues.

Problem Categories

Focus Areas:

• CONNECTIVITY and SETUP categories show the lowest average scores (1.9–2.0). These areas need targeted coaching to improve diagnostic accuracy and resolution efficiency.
• ACCESS issues also require attention, as scores here are marginally lower than overall averages.

What Went Well

Strength: Accurate Technical Guidance on Unmanaged Switch

Agent correctly identified SE3005 as an unmanaged switch with no firewall capabilities and accurately directed customer to adjust firewall settings on their router (Spectrum or eero). Technical accuracy score 5.

#LTS00131316

Strength: Clear Explanation of Wi-Fi vs Router Admin Password Distinction

Agent clearly explained the critical distinction between Wi-Fi password and router admin password at [05:00]-[06:00], preventing ongoing confusion. Successfully guided customer to access router dashboard.

#LTS00130772

Growth Opportunities

Improvement: Incorrect Product Information and URLs Provided

Agent provided materially incorrect product information: invented non-existent model 'MBE77' ([03:00]), falsely claimed Velop Pro 7 is a standalone router ([05:00]), and provided three invalid registration URLs (register.lingncist.com, register.linkages.com, register.rgsestination.com). Accuracy score 1.

#GI00130724

Next Step: Always verify product model existence and URL validity before sharing. Use the official register.linksys.com domain for registration guidance.

Improvement: Premature Paid Support Offers Without Troubleshooting

Agent prematurely offered paid support without attempting any free troubleshooting steps. Multiple calls show no troubleshooting performed: MR9000 (call_id c8023f2e), RE9000 (call_id c6f01870), MR8300 (call_id d8b7fd9c).

#LTS00130731 | #LTS00130754 | #GI00130724

Next Step: Before offering paid support, always run at least one basic troubleshooting step (e.g., reboot, signal check, band selection) and provide self-help resources where applicable.

Next Week's Focus

1. Verify Product Models and URLs: Double-check product model existence and use only official Linksys domains (e.g., register.linksys.com) when providing registration or purchase information.
2. Perform At Least One Basic Troubleshooting Step: For any connectivity or setup issue, complete at least one foundational troubleshooting action (e.g., reboot, reset, LED check) before escalating or offering paid support.
3. Reinforce Mesh System Familiarity: Review WHW03, MX2000, and MR8300 pairing procedures, LED meanings, and troubleshooting flows to improve confidence and accuracy.
4. Use Empathy and Active Listening: Acknowledge customer frustration early, paraphrase their concerns to confirm understanding, and avoid interrupting or rushing through solutions.

Technical Accuracy

Improvement

Agent provided three invalid registration URLs: register.lingncist.com, register.linkages.com, and register.rgsestination.com. Also claimed MX2000 can deliver up to 3 Gbps Wi-Fi speed (factually incorrect). No technical troubleshooting performed for Wi-Fi performance issue.

#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

Agent provided incorrect registration URL 'register.linksus.com' instead of 'register.linksys.com'. Mispronounced 'Linksys' as 'lynxus' throughout call. Failed to collect product model, serial number, or warranty status.

#TE00131076

Improvement

Agent incorrectly claimed WHW03 is no longer supported by Linksys app due to firmware updates and cloud service removal, contradicting KB (velop_router_setup.md). No troubleshooting performed. Repeatedly mispronounced brand as 'Lynxis'.

#LTS00130915

Strength

Agent correctly identified SE3005 as an unmanaged switch with no firewall capabilities. Accurately directed customer to adjust firewall settings on their router (Spectrum or eero). Technical accuracy score 5.

#LTS00131316

Coaching Moments

Improvement

Agent provided three invalid registration URLs: register.lingncist.com, register.linkages.com, and register.rgsestination.com. Also claimed MX2000 can deliver up to 3 Gbps Wi-Fi speed (factually incorrect). No technical troubleshooting performed for Wi-Fi performance issue.

#TE00130759

Improvement

#LTS00131057

Improvement

Agent provided incorrect registration URL 'register.linksus.com' instead of 'register.linksys.com'. Mispronounced 'Linksys' as 'lynxus' throughout call. Failed to collect product model, serial number, or warranty status.

#TE00131076

Improvement

Agent incorrectly claimed WHW03 is no longer supported by Linksys app due to firmware updates and cloud service removal, contradicting KB (velop_router_setup.md). No troubleshooting performed. Repeatedly mispronounced brand as 'Lynxis'.

#LTS00130915

Escalation Lessons: What L2 Did

#TE00130759 — Callback

What L1 saw:

• Customer reported slow speed and poor range on a new MX2000 mesh system.
• L1 collected serial number and model but provided incorrect registration URLs and false technical claims about MX2000 speed capabilities.

Why it escalated:

• Customer requested escalation to a higher technician/L2 agent due to unsatisfactory resolution.

What L2 did:

• Performed proper speed and mesh diagnostics, including using another server for testing, checking RSSI levels, and testing device connections close to the parent node.
• Provided specific troubleshooting steps: express forwarding, testing with another server, and verifying RSSI thresholds.

Current state:

• Ticket marked as "Callback" — L2 scheduled a follow-up call for further troubleshooting.

L1 learning points:

1. Always verify registration URLs and avoid providing invalid domains.
2. For MX2000 speed issues, perform basic diagnostics (speed test, RSSI check, node placement) before escalation.
3. Clarify product capabilities accurately — MX2000 does not support 3 Gbps Wi-Fi speeds.

#TE00131076 — Resolved

What L1 saw:

• Customer couldn’t access their Linksys cloud account after password changes.
• L1 failed to collect device details and provided an incorrect registration URL.

Why it escalated:

• Issue persisted after 24 hours, prompting escalation to L2.

What L2 did:

• Verified account lock-out policies and guided the customer through account recovery steps.
• Confirmed that cloud access issues were resolved after password reset and waiting period.

Current state:

• Ticket marked as "Resolved."

L1 learning points:

1. Always collect product model, serial number, and warranty status for cloud account issues.
2. Use the correct registration URL (register.linksys.com).
3. Set clear expectations for account recovery (e.g., 24-hour wait period after password reset).

Coach Appendix

Weekly Trend Summary:

This week’s performance highlights a critical need to reinforce technical accuracy and protocol adherence. Key issues include providing invalid URLs, incorrect product claims, premature paid support offers, and PCI compliance violations. Focus should shift to verifying information before sharing, performing basic troubleshooting, and ensuring clear communication of product capabilities.

Recurring Patterns:

• Technical Inaccuracy: Multiple calls involved incorrect URLs, product claims, and LED interpretations.
• Protocol Violations: Failure to collect essential information (model, serial, warranty) and PCI compliance breaches.
• Premature Escalation/Paid Offers: Offering paid support before basic troubleshooting steps were attempted.

Evidence:

• Calls #TE00130759, #LTS00131057, and #TE00131076 exemplify the need for stricter verification and troubleshooting before escalation or paid support offers.

This Week's Calls