Vincent — Coaching Report

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

At a Glance

Scorecard

Scores reflect data from 2 calls reviewed this week (range: 1.4 – 2.4 overall).

This Week's Coverage

Models Supported

Model-specific note:

Lower scores on MR2000 calls suggest familiarity gaps with this device's setup flow, particularly around reset procedures and pairing methods.

Problem Categories

Category insights:

• CONNECTIVITY calls show the greatest need for improvement, with low scores driven by incorrect technical guidance and unresolved issues.
• ACCESS calls performed better but still highlight the importance of verifying resolution before closing.

What Went Well

Professional communication during complex troubleshooting

“Agent remained calm and professional throughout the call despite customer confusion and repeated questions.”

This poise helped keep the customer engaged and cooperative, even when technical guidance was misaligned. Maintaining a calm tone and clear explanations is a solid foundation to build on.

Growth Opportunities

Correct technical instructions for MR2000 reset procedures

The MR2000 requires a 10‑second reset (not 30 seconds) and does not support the 5‑press pairing method. Using the correct reset duration and avoiding unsupported pairing steps will prevent customer confusion and improve first‑call resolution rates.

Next step:

• Review the MR2000 device KB for exact reset and recovery steps.
• Practice the 10‑second reset flow and confirm it aligns with the device’s behavior.

Verify resolution before closing calls, especially for password/access changes

While the customer reported that things “seem to be working” after changing the Wi‑Fi password, the agent did not confirm that:

1. The password change succeeded (e.g., by having the customer reconnect a device), and
2. The Linksys app setup completed fully.

Verification prevents “ghost fixes” and ensures the customer isn’t left stranded after the call ends.

Next step:

• Build a quick verification checklist for access/password cases (e.g., “Can you confirm the device is now connected?” or “Is the app showing connected?”).
• Use this checklist before any closure or escalation.

Next Week's Focus

1. Master MR2000 reset flows — memorize the 10‑second reset and avoid mentioning unsupported methods (e.g., 5‑press pairing).
2. Add a verification step to every access/password case — ask the customer to confirm the fix before ending the call.
3. Collect essential data early — serial number, warranty status, and product model on every call to avoid protocol gaps.
4. Review SPNM reset guidance — ensure you’re using the Pair-button method, not the 5‑press method, for SPNM-family devices.

Technical Accuracy

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.

#LTS00114431

Improvement

Agent provided incorrect 5-press reset instructions for a SPNM-family router, which is not a supported method for this product line (KB specifies Pair-button method only).

#LTS00114431

Strength

Agent provided a clear and patient explanation of the difference between Wi‑Fi password and Linksys account login, helping reduce customer confusion.

#LTS00114431

Escalation Lessons: What L2 Did

No escalations occurred this week, so there are no L2 resolution patterns to review. Ensure any future escalations include detailed L2 notes so we can learn from them.

Coach Appendix

Internal use only — not for agent viewing

• Highest-signal trend: Persistent technical inaccuracies around reset procedures (30‑second vs. 10‑second reset, 5‑press vs. Pair-button) led to unresolved cases and customer confusion.
• Key pattern to address: Early data collection (model, serial, warranty) and strict adherence to device-specific KB reset steps will reduce errors and improve closure rates.
• Evidence: Both calls involved reset guidance that conflicted with product-specific KB articles; neither call collected serial/warranty data, and both ended without confirmed resolution.