Your weekly coaching path

Week-over-Week Progress

Scorecard

Main focus: Incorrect Product Guidance

V2 Rubric (Shadow Grading)

V2 overall: 70.88% across 12 v2-scored calls this week

• Successful Resolution: 5
• Partial Resolution: 4
• Unresolved: 3

Where Did the Time Go

By Product Family

By Problem Category

What You Did Well

• Clear Technical Guidance3 of 12 callsProvided step-by-step instructions to reset and re-pair child nodes, resulting in all nodes online across SPNM60 calls #LTS00134188, #LTS00134585, and #LTS00134919.
  Why this matters: Ensures customers can independently resolve mesh connectivity issues, reducing repeat calls and improving first-contact resolution.
  #LTS00134188  ·  #LTS00134585  ·  #LTS00134919
• Model Identification3 of 12 callsCollected correct model numbers early in calls for SPNM60, WHW03, and MX2000 devices, enabling accurate troubleshooting #LTS00134188, #LTS00134415, #LTS00134612.
  Why this matters: Prevents misdiagnosis and irrelevant steps, streamlining resolution and improving customer experience.
  #LTS00134188  ·  #LTS00134415  ·  #LTS00134612

Growth Focus

• Incorrect Product Guidance2 of 12 callsProvided inaccurate statements about Linksys cloud access availability for SPNM60 and misrepresented mesh compatibility between Wi‑Fi 6 and Wi‑Fi 7 devices, leading to confusion #LTS00134188, #LTS00134734.
  Why this matters: Misinformation risks customer frustration, repeat calls, and potential hardware misuse or instability.
  Example: In #LTS00134734, agent stated 'they will work they are compatible sir' about mixing SPNM60 (Wi‑Fi 6) and SPNM57 (Wi‑Fi 7) nodes, contradicting KB documentation.
  What better looks like: Verify mesh generation compatibility using KB before advising configurations; reference velop_mesh_compatibility.md for cross-generation rules.
  #LTS00134188  ·  #LTS00134734
• Incomplete Verification2 of 12 callsFailed to verify post-change connectivity or performance after configuration adjustments on SPNM60TB and MX2000 calls, leaving resolution status unconfirmed #LTS00134210, #LTS00134612.
  Why this matters: Unverified fixes risk unresolved issues resurfacing, leading to callbacks and reduced customer trust.
  Example: In #LTS00134210, after renaming the SSID and adjusting security settings, the agent ended the call without confirming the customer could reconnect devices or monitor performance.
  What better looks like: After making changes, guide the customer to test connectivity (e.g., reconnect devices, load a website) and confirm stability before closing.
  #LTS00134210  ·  #LTS00134612

Callback Flags

No callback chains detected.

Documentation Accuracy

No documentation mismatches detected this week.

Practice Plan

• Step 1
  Before closing any call where the issue is not confirmed fixed, ask the customer to test the fix on the call and confirm it works.
  Why: Unverified fixes risk recurrence and callbacks, reducing customer trust and increasing repeat contact rates.
• Step 2
  Always verify product model before providing model-specific instructions (URLs, passwords, reset procedures).
  Why: Incorrect model guidance leads to confusion, failed steps, and potential device misconfiguration.
  This week: #LTS00134734
• Step 3
  When discussing mesh compatibility, reference velop_mesh_compatibility.md and confirm node generations match before proceeding.
  Why: Cross-generation mesh setups are unsupported and cause instability; misguidance risks long-term issues.
  This week: #LTS00134734
• Step 4
  Use the correct extender setup URL (http://extender.linksys.com) and confirm browser compatibility before proceeding.
  Why: Incorrect URLs prevent access to configuration interfaces, delaying resolution and frustrating customers.
  This week: #LTS00134738
• Step 5
  After making configuration changes, guide the customer through post-change connectivity tests (e.g., reconnect devices, load a website).
  Why: Ensures the fix is validated before closing, improving first-contact resolution and reducing callbacks.

Escalation Lessons

No escalated case learning this week.

Evidence Calls