Your weekly coaching path

Week-over-Week Progress

Scorecard

Main focus: Incorrect pairing method

V2 Rubric (Shadow Grading)

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

• Ownership Gap: 1

Where Did the Time Go

By Product Family

By Problem Category

What You Did Well

• Customer info collection1 of 1 callsCollected customer's phone number and name across 1 of 1 calls.
  Why this matters: Ensures proper follow-up and personalized service for the customer.
  #LTS00035663
• Troubleshooting attempts1 of 1 callsAttempted multiple troubleshooting steps (power cycle, reset, pairing) across 1 of 1 calls.
  Why this matters: Demonstrates thoroughness and effort to resolve issues before escalation.
  #LTS00035663

Growth Focus

• Incorrect pairing method1 of 1 callsUsed 5-press pairing method on a likely SPNM6x series node, which is incorrect (should use Pair button method per KB) across 1 of 1 calls. This misapplication led to unresolved issue and customer frustration.
  Why this matters: Incorrect technical guidance leads to unresolved issues, repeat calls, and diminished customer trust.
  Example: In call #LTS00035663, the agent instructed a 5-press reset on a SPNM6x node instead of using the Pair button, resulting in failed pairing and no resolution.
  What better looks like: Verify product model and use the correct pairing method: Pair button for SPNM60/62 series per led_cog_mesh_group_d_spnm60_62.md.
  #LTS00035663
• Missing model verification1 of 1 callsFailed to collect or confirm product model and serial number across 1 of 1 calls, leading to incorrect troubleshooting path and unresolved issue.
  Why this matters: Without accurate device details, troubleshooting is guesswork, increasing resolution time and callback risk.
  Example: In call #LTS00035663, the agent guessed 'SPN MX 55' without verification, causing misapplied troubleshooting steps.
  What better looks like: Before proceeding, confirm the exact product model and serial number with the customer and cross-reference KB articles.
  #LTS00035663

Callback Flags

No callback chains detected.

Documentation Accuracy

No documentation mismatches detected this week.

Practice Plan

• Step 1
  Before initiating any troubleshooting steps, verify the exact product model and serial number with the customer and confirm against KB requirements.
  Why: Skipping model verification leads to misapplied procedures, unresolved issues, and repeat calls.
  This week: #LTS00035663
• Step 2
  For SPNM60/62 series mesh nodes, use the Pair button method instead of the 5-press reset for pairing.
  Why: Using incorrect pairing methods prevents successful node registration and causes customer frustration.
  This week: #LTS00035663
• Step 3
  Always confirm parent node internet connectivity before attempting child node pairing or troubleshooting.
  Why: Attempting pairing without internet on the parent node is futile and wastes time for both agent and customer.
  This week: #LTS00035663
• Step 4
  When guiding customers through recovery key usage, clearly distinguish it from router passwords and confirm successful authentication.
  Why: Confusing recovery keys with passwords leads to failed attempts and security risks.
  This week: #LTS00035663

Escalation Lessons

No escalated case learning this week.

Evidence Calls