Your weekly coaching path

Week-over-Week Progress

Scorecard

Main focus: LED State Interpretation

V2 Rubric (Shadow Grading)

V2 overall: 46.99% across 40 v2-scored calls this week2 auto-zeros

• Unresolved: 17
• Partial Resolution: 11
• Successful Resolution: 7
• Appropriate Escalation: 3
• Ownership Gap: 2

Where Did the Time Go

By Product Family

By Problem Category

What You Did Well

• Mesh Node Pairing8 of 20 callsSuccessfully guided customers through 5-press pairing on MX2000 and MR7500 devices across 8 calls, achieving solid blue LED status and restored connectivity (e.g., #TE00136055, #LTS00135991).
  Why this matters: Reduces customer effort and repeat calls by ensuring correct node integration.

  Correctly used the 5-press pairing method, which is supported on MR7500 per universal_5press_models.md.

  #TE00136055  ·  #LTS00135991  ·  #LTS00136594
• Password Recovery5 of 20 callsAccurately guided customers through recovery key usage and admin password resets on LN1100 and E5400 devices in 5 calls, maintaining security protocols (e.g., #LTS00135369, #EOS00136176).
  Why this matters: Prevents unauthorized access while restoring customer control.

  Instructed use of 5-digit recovery key from router sticker to reset admin password.

  #LTS00135369  ·  #EOS00136176

Growth Focus

• LED State Interpretation4 of 20 callsMisinterpreted solid blue LED as 'ready for setup' instead of 'online' on MX2000/LN1400 devices in 4 calls, causing unnecessary resets (e.g., #LTS00135960, #TE00136055).
  Why this matters: Leads to extended handle times and customer confusion.
  Example: In #LTS00135960, instructed 5-press reset on LN1400 despite solid blue LED indicating readiness.
  What better looks like: Reference KB led_intelligent_mesh_consumer.md: solid blue = online, ready for configuration.

  Misinterpreted LED states: solid blue on LN1400 means ready, not setup mode requiring 5-press.

  #LTS00135960  ·  #TE00136055
• Escalation Documentation2 of 20 callsEscalated 2 cases without complete HappyFox documentation (e.g., #TE00136055, #TE00136407), missing L1 observations and next steps.
  Why this matters: Hinders L2 efficiency and repeat call prevention.
  Example: Escalated MX2000 access issue without noting IP conflict observations.
  What better looks like: Document key findings (e.g., IP shifts, LED behavior) and promised callbacks in HappyFox.
  #TE00136055  ·  #TE00136407

Callback Flags

No callback chains detected.

Documentation Accuracy

No documentation mismatches detected this week.

Practice Plan

• Step 1
  Before instructing any reset on MX/LN series routers, verify LED state against KB and confirm customer is on the correct network.
  Why: Prevents unnecessary resets and reduces handle time.
  This week: #LTS00135960
• Step 2
  For every escalation, document key observations (e.g., IP conflicts, LED behavior) and set explicit callback expectations in HappyFox.
  Why: Ensures L2 has context to resolve issues faster.
  This week: #TE00136055

Escalation Lessons

Evidence Calls

Feedback