Your weekly coaching path

Week-over-Week Progress

Scorecard

Main focus: Incorrect default credentials

V2 Rubric (Shadow Grading)

V2 overall: 41.17% across 41 v2-scored calls this week9 auto-zeros

• Unresolved: 17
• Successful Resolution: 14
• Ownership Gap: 5
• Partial Resolution: 5

Where Did the Time Go

By Product Family

By Problem Category

What You Did Well

• Early device detail collection12 of 32 callsProactively collected model and serial number in 12 of your 32 calls, enabling accurate troubleshooting. Examples include calls #LTS00133413 (SPNM60) and #LTS00133423 (WHW03).
  Why this matters: Reduces repeat calls and enables precise resolution planning
  #LTS00133413  ·  #LTS00133423  ·  #LTS00133431
• Accurate reset guidance8 of 32 callsCorrectly guided customers through factory reset procedures in 8 calls, including LED state verification. Notable in #LTS00133468 (E8450) and #LTS00133615 (WHW03).
  Why this matters: Restores access and prevents data loss when applied correctly
  #LTS00133468  ·  #LTS00133615  ·  #LTS00133622

Growth Focus

• Incorrect default credentials7 of 32 callsProvided wrong default admin passwords or IP addresses in 7 calls, such as advising 'admin' for SPNM60 series (#LTS00133413) and misstating local IP as phone number (#LTS00133423).
  Why this matters: Leads to failed logins, customer frustration, and repeat calls
  Example: In #LTS00133413, advising 'admin' as default password prevented login despite the correct method being available.
  What better looks like: Verify device-specific defaults from KB before providing credentials; confirm with customer after reset.
  #LTS00133413  ·  #LTS00133423  ·  #LTS00133440
• Skipped troubleshooting steps9 of 32 callsBypassed key diagnostics like recovery key process and modem tests in 9 calls, leading to unresolved issues or escalation. Seen in #LTS00133423 (WHW03) and #LTS00133495 (MBE7000).
  Why this matters: Increases callback risk and reduces first-call resolution
  Example: In #LTS00133423, skipping 5-press pairing and LED validation led to unresolved mesh issues.
  What better looks like: Follow KB sequence: power cycle, verify modem, test basic connectivity before advanced steps.
  #LTS00133423  ·  #LTS00133495  ·  #LTS00133584

Callback Flags

No callback chains detected.

Documentation Accuracy

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 callbacks due to unresolved issues and ensures first-call resolution
  This week: #LTS00133413
• Step 2
  Always verify default credentials and URLs against KB before providing them to customers; confirm with customer after reset.
  Why: Avoids failed logins and builds customer trust through accuracy
  This week: #LTS00133423
• Step 3
  Follow KB sequence: power cycle, verify modem, test basic connectivity before advanced troubleshooting steps.
  Why: Reduces escalations and resolves issues faster
  This week: #LTS00133495
• Step 4
  When guiding mesh node resets, confirm LED changed to solid purple (WHW03) or solid blue (Cognitive Mesh) before proceeding.
  Why: Ensures correct reset state and prevents misdiagnosis
  This week: #LTS00133615

Escalation Lessons

No escalated case learning this week.

Evidence Calls