Your weekly coaching path

Week-over-Week Progress

Scorecard

Main focus: Technical Accuracy

V2 Rubric (Shadow Grading)

V2 overall: 38.61% across 28 v2-scored calls this week4 auto-zeros

• Unresolved: 10
• Successful Resolution: 8
• Ownership Gap: 5
• Partial Resolution: 5

Where Did the Time Go

By Product Family

By Problem Category

What You Did Well

• Proactive Troubleshooting12 of 26 calls resolved successfullyConsistently guided customers through multi-step resets and configuration changes, often resolving issues on the first attempt. For example, in #LTS00136247, the agent successfully restored internet connectivity after a factory reset and SSID reconfiguration.
  Why this matters: Reduces repeat calls and customer frustration by delivering effective first-contact resolution.
  #LTS00136247  ·  #LTS00136295  ·  #LTS00136415
• Clear Communication19 of 26 calls rated communication >=3.0Maintained polite, professional tone and set clear expectations throughout interactions. In #LTS00136096, the agent apologized for hold times and provided structured guidance despite technical challenges.
  Why this matters: Builds trust and improves customer satisfaction even when issues are complex.
  #LTS00136096  ·  #LTS00136415  ·  #LTS00136776

Growth Focus

• Technical Accuracy9 of 26 calls contained URL errorsFrequent provision of incorrect support URLs (e.g., support.lingus.com, support.linaxes.com) and misstated default credentials. These errors appeared in 9 of 26 calls, risking customer confusion and additional support requests.
  Why this matters: Incorrect information increases customer effort and may violate KB compliance standards.
  Example: In #LTS00136099, the agent provided 'support.lingus.com' instead of the correct 'support.linksys.com', causing customer confusion during self-help attempts.
  What better looks like: Always verify and use the official support.linksys.com domain when providing web resources.
  #LTS00136099  ·  #LTS00135409  ·  #LTS00136096
• Diagnostic Rigor7 of 12 connectivity cases lacked WAN verificationIn 7 calls with connectivity issues, the agent skipped basic WAN diagnostics (e.g., modem status checks, LAN cable verification) before attempting complex mesh troubleshooting. This led to inefficient problem-solving in cases like #LTS00136587.
  Why this matters: Skipping isolation steps prolongs resolution time and increases customer frustration.
  Example: In #LTS00136587, the agent began 5-press pairing without verifying the WAN port LED or modem status, missing an upstream ISP issue.
  What better looks like: Always confirm WAN connectivity (modem lights, direct LAN test) before proceeding with mesh-specific troubleshooting.
  #LTS00136587  ·  #LTS00136295  ·  #LTS00094528

Callback Flags

No callback chains detected.

Documentation Accuracy

Practice Plan

• Step 1
  Before guiding any mesh troubleshooting, always verify WAN port LED status and perform a direct modem-to-laptop test
  Why: Skipping WAN diagnostics leads to wasted time on downstream fixes for upstream issues
• Step 2
  Use only the official support.linksys.com domain when providing web resources; double-check URLs before speaking
  Why: Incorrect URLs cause customer confusion and additional support requests
  This week: #LTS00136099 (provided 'support.lingus.com')
• Step 3
  When resetting devices, state the exact duration (e.g., 'Hold the reset button for 10 seconds') and confirm completion with the customer
  Why: Inconsistent timing instructions lead to incomplete resets and repeated issues
  This week: #LTS00136587 (inconsistent reset timing caused confusion)
• Step 4
  For password recovery, always verify the default credential printed on the device before suggesting alternatives
  Why: Misstated defaults prevent successful login and frustrate customers
  This week: #LTS00136099 (incorrectly stated MX4200 default password)
• Step 5
  After resolving connectivity issues, explicitly confirm internet access across all reported devices before closing
  Why: Partial resolutions leave unresolved issues that generate repeat calls

Escalation Lessons

Evidence Calls

Feedback