Your weekly coaching path

Week-over-Week Progress

Scorecard

Main focus: Product Model Verification

V2 Rubric (Shadow Grading)

V2 overall: 81.75% across 1 v2-scored calls this week

• Partial Resolution: 1

Where Did the Time Go

By Product Family

By Problem Category

What You Did Well

• Diagnostics Log Collection1 of 1 callsSuccessfully obtained router diagnostics logs from the customer across 1 of 1 calls, as noted in coaching moments, enabling targeted troubleshooting for the MX5500 connectivity issue in ticket #GI00084218.
  Why this matters: Securing diagnostics logs allows agents to identify root causes faster, reducing resolution time and customer effort.
  #GI00084218
• Mesh Power-Cycle Guidance1 of 1 callsGuided the customer through a complete power-cycle of the mesh system and verified LED status across 1 of 1 calls, ensuring proper reboot procedures were followed in ticket #GI00084218.
  Why this matters: Methodically power-cycling mesh nodes is essential for resolving intermittent connectivity issues and prevents prolonged downtime.
  #GI00084218

Growth Focus

• Product Model Verification1 of 1 callsFailed to ask for or confirm the product model number at the start of the call, delaying accurate troubleshooting in 1 of 1 calls (ticket #GI00084218). This omission risked applying incorrect steps for the MX5500 mesh system.
  Why this matters: Skipping model verification can lead to misdirected diagnostics, repeat calls, and unresolved issues due to device-specific factors.
  Example: In ticket #GI00084218, the agent began troubleshooting without confirming the MX5500 model, potentially misaligning steps with device specifics.
  What better looks like: Always confirm the exact product model (e.g., MX5500) and firmware version at the beginning of the call to tailor troubleshooting accurately.
  #GI00084218
• Firmware and Warranty Check1 of 1 callsDid not verify firmware version or warranty status before proceeding, missing critical update or eligibility factors in 1 of 1 calls (ticket #GI00084218). This gap prevented early determination of support scope and firmware-specific fixes.
  Why this matters: Verifying firmware ensures agents apply correct version-specific fixes; checking warranty determines support scope and avoids misdirected efforts.
  Example: In ticket #GI00084218, the agent started troubleshooting without confirming the MX5500's firmware version or warranty status.
  What better looks like: At the start of each call, confirm the product model, check the firmware version against the latest KB, and verify warranty status to guide appropriate troubleshooting paths.
  #GI00084218

Callback Flags

No callback chains detected.

Documentation Accuracy

No documentation mismatches detected this week.

Practice Plan

• Step 1
  Always confirm the exact product model and firmware version at the beginning of each call before proceeding with troubleshooting.
  Why: Skipping this step can lead to incorrect diagnostics and wasted time on irrelevant solutions.
  This week: #GI00084218
• Step 2
  Verify warranty status early to determine support eligibility and appropriate resolution paths.
  Why: Failing to check warranty may result in offering unsupported solutions or missing critical updates.
  This week: #GI00084218
• Step 3
  Ensure all email addresses provided for diagnostics are correct (e.g., support.linksys.com) before sending any requests.
  Why: Incorrect emails cause diagnostics to fail, prolonging issue resolution.
  This week: #GI00084218
• Step 4
  Proactively address any customer-reported network changes (e.g., LAN IP address modifications) during the troubleshooting process.
  Why: Ignoring such changes can lead to misconfigured troubleshooting steps and unresolved issues.
  This week: #GI00084218

Escalation Lessons

No escalated case learning this week.

Evidence Calls