Your weekly coaching path

Week-over-Week Progress

Scorecard

Main focus: Inconsistent LED Interpretation

V2 Rubric (Shadow Grading)

V2 overall: 44.02% across 35 v2-scored calls this week2 auto-zeros

• Unresolved: 15
• Partial Resolution: 10
• Successful Resolution: 8
• Appropriate Escalation: 2

Where Did the Time Go

By Product Family

By Problem Category

What You Did Well

• Correct Mesh Reset ProceduresUsed in 8 of 20 calls involving mesh systemsApplied the 5-press reset method for WHW03 and MX series mesh systems across multiple calls, ensuring proper node pairing and stability. This was demonstrated in calls #LTS00135974, #LTS00136446, and #LTS00136591.
  Why this matters: Ensures customers can successfully recover mesh networks without unnecessary escalations, reducing repeat calls and improving customer satisfaction.
  #LTS00135974  ·  #LTS00136446  ·  #LTS00136591
• Accurate Product IdentificationPresent in 15 of 20 callsConsistently collected and verified product models and serial numbers early in calls, enabling targeted troubleshooting. This was evident in calls #LTS00135986, #LTS00056742, and #LTS00136019.
  Why this matters: Reduces misdiagnosis and ensures appropriate resolution paths are followed, improving first-call resolution rates.
  #LTS00135986  ·  #LTS00056742  ·  #LTS00136019

Growth Focus

• Inconsistent LED InterpretationAppeared in 4 of 8 WHW03 callsMisinterpreted LED states (e.g., referring to 'solid pink/magenta' instead of 'solid purple' for WHW03 ready state) causing customer confusion. This occurred in calls #LTS00135974 and #LTS00136056.
  Why this matters: Leads to incorrect troubleshooting steps and potential escalation of otherwise resolvable issues, increasing customer effort and frustration.
  Example: In call #LTS00135974, the agent stated 'solid pink/magenta' instead of the correct 'solid purple' for WHW03 readiness, delaying proper resolution.
  What better looks like: Use KB-defined LED color terminology (e.g., 'solid purple' for WHW03 ready state) and verify node status via the app or web UI before closing.
  #LTS00135974  ·  #LTS00136056
• Incomplete Node Stability VerificationOccurred in 5 of 12 mesh-related callsClosed calls without confirming long-term stability after initial fixes, leading to potential callbacks. Observed in calls #LTS00135974, #LTS00136056, and #LTS00136019.
  Why this matters: Customers may experience recurring issues if stability isn't validated, resulting in repeat calls and reduced trust in support.
  Example: In call #LTS00135974, the agent closed after nodes turned blue but didn't verify stability after relocating nodes, which later caused re-flashing.
  What better looks like: After initial resolution, instruct customers to monitor nodes for 24 hours and confirm stability before closing. Document final node status in the ticket.
  #LTS00135974  ·  #LTS00136056  ·  #LTS00136019

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: Prevents premature closures and reduces repeat calls due to unresolved issues.
• Step 2
  Use KB-defined LED color terminology (e.g., 'solid purple' for WHW03 ready state) and verify node status via the app or web UI before closing.
  Why: Avoids misdiagnosis and ensures customers receive accurate guidance, improving trust and reducing escalations.
  This week: #LTS00135974
• Step 3
  When troubleshooting mesh nodes, always confirm parent node internet connectivity before attempting child node pairing.
  Why: Ensures the root cause is addressed and prevents wasted time on dependent issues.
  This week: #LTS00136019

Escalation Lessons

Evidence Calls

Feedback