Your weekly coaching path

Week-over-Week Progress

Scorecard

Main focus: Inaccurate LED Guidance

V2 Rubric (Shadow Grading)

V2 overall: 55.05% across 41 v2-scored calls this week5 auto-zeros

• Unresolved: 19
• Partial Resolution: 13
• Successful Resolution: 9

Where Did the Time Go

By Product Family

By Problem Category

What You Did Well

• Precise Mesh PairingUsed in 12 of 38 callsCorrectly applied the 5-press pairing method for WHW03 and MX series nodes across multiple calls, ensuring reliable mesh integration (e.g., #LTS00134185, #LTS00134201).
  Why this matters: Ensures mesh networks remain fully operational and avoids costly repeat calls for node pairing issues.
  #LTS00134185  ·  #LTS00134201  ·  #LTS00134232
• Calm Customer ManagementObserved in 18 of 38 callsMaintained reassuring tone and managed expectations effectively during complex troubleshooting, particularly with frustrated customers (e.g., #LTS00134193, #LTS00134255).
  Why this matters: Reduces escalations and improves customer satisfaction scores.
  #LTS00134193  ·  #LTS00134255  ·  #LTS00134404

Growth Focus

• Inaccurate LED GuidanceAppeared in 9 of 38 callsProvided incorrect LED state information (e.g., 'solid pink' for Velop nodes) and failed to verify product models before instruction, leading to confusion and unresolved issues (e.g., #LTS00134213, #LTS00134247).
  Why this matters: Materially incorrect guidance risks customer safety, creates repeat calls, and violates protocol accuracy requirements.
  Example: In #LTS00134213, agent stated 'solid pink' indicates online status for MX6200, contradicting KB which defines solid blue as ready state.
  What better looks like: Confirm product model first, reference KB for exact LED definitions, and validate state before proceeding.
  #LTS00134213  ·  #LTS00134247  ·  #LTS00134610
• Omitted Critical DiagnosticsOccurred in 7 of 38 callsSkipped essential steps like WAN verification, parent node LED checks, and modem isolation before troubleshooting child nodes, causing unresolved connectivity issues (e.g., #LTS00134255, #LTS00134935).
  Why this matters: Incomplete diagnostics extend resolution time, increase callbacks, and risk misdiagnosis of root causes.
  Example: In #LTS00134255, agent began 5-press pairing without confirming parent node was solid blue, a required precondition per KB.
  What better looks like: Always verify parent node status, check WAN connectivity, and perform modem isolation before node-specific steps.
  #LTS00134255  ·  #LTS00134935  ·  #LTS00134738

Callback Flags

No callback chains detected.

Documentation Accuracy

Practice Plan

• Step 1
  Always verify product model and LED state definitions before providing technical guidance, referencing KB articles for exact specifications.
  Why: Prevents materially incorrect instructions that compromise customer safety and create repeat calls.
• Step 2
  Complete full diagnostic flow for mesh connectivity issues: 1) Verify parent node solid blue, 2) Check WAN/modem status, 3) Perform modem isolation test before node-specific steps.
  Why: Skips in diagnostics extend resolution time and risk misdiagnosis of root causes.
  This week: #LTS00134255 (omitted parent node verification)
• Step 3
  Never collect or store credit card details over unsecured phone channels; use only documented secure payment pathways.
  Why: Violates PCI compliance and risks severe regulatory penalties.
  This week: #LTS00134938 (full card details collected)
• Step 4
  Confirm successful login/access before proceeding with configuration steps, and provide concise post-resolution recaps.
  Why: Prevents premature closure and ensures customer confidence in resolution.
  This week: #LTS00134740 (login declared successful without confirmation)
• Step 5
  For out-of-warranty devices, first offer KB-aligned self-help steps before suggesting paid support or email instructions.
  Why: Aligns with OOW best-effort policy and reduces unnecessary service costs.
  This week: #LTS00134605 (immediate paid support offer without diagnostics)

Escalation Lessons

Evidence Calls