Your weekly coaching path

Week-over-Week Progress

Scorecard

Main focus: Inaccurate Product Information

V2 Rubric (Shadow Grading)

No v2 shadow-grading data available for this week.

Where Did the Time Go

By Product Family

By Problem Category

What You Did Well

• Customer Concern Acknowledgment1 of 3 callsAcknowledged the customer's concern about the blinking red LED and the desire to add another node, as noted in call #GI00043822.
  Why this matters: Acknowledging customer concerns builds trust and shows active listening, encouraging further collaboration.
  #GI00043822
• Wired Backhaul Suggestion1 of 3 callsMentioned the possibility of using wired backhaul as an alternative solution, a valid option per KB, in call #GI00043822.
  Why this matters: Offering alternative solutions expands troubleshooting options and may resolve issues when wireless methods fail.
  #GI00043822

Growth Focus

• Inaccurate Product InformationOccurred in 1 of 3 calls, but critically impacted resolution.Provided materially inaccurate product availability information (falsely claimed MX5500 and MX2000 are discontinued) and failed to follow standard troubleshooting steps for blinking red LED on MX4200, as seen in call #GI00043822.
  Why this matters: Incorrect product information can lead customers to make decisions based on false data, potentially causing equipment waste or delays. Skipping standard troubleshooting steps prevents issue resolution and increases callback risk.
  Example: In call #GI00043822, the agent told the customer that MX5500 and MX2000 are discontinued (they are not), and did not guide the customer through power-cycle, factory reset, or Ethernet verification for the blinking red LED.
  What better looks like: Reference KB documentation for product support status and follow led_intelligent_mesh_consumer.md for blinking red LED troubleshooting: verify power, cables, ISP connection, perform factory reset, and guide through 5-press method when applicable.
  #GI00043822
• Incomplete TroubleshootingAppeared in 2 of 3 calls.Failed to collect essential product details, perform structured troubleshooting, or clarify the customer's issue, leading to unresolved calls. Seen in calls #GI00132019 and #LTS00127750.
  Why this matters: Skipping basic troubleshooting steps and failing to gather information prevents accurate diagnosis, leading to unresolved issues, customer frustration, and increased callback rates.
  Example: In call #LTS00127750, the agent instructed random reset presses for an MX6200 mesh node instead of the KB-defined 5-press method, and skipped verification of WAN/ISP connectivity and cable connections.
  What better looks like: At the start of each call, collect device model, serial number, and environment details. Follow KB troubleshooting flows step-by-step, including verification of upstream connections, structured resets (e.g., 5-press method), and LED interpretation per device family.

  From four to six minutes, correct.

  #GI00132019  ·  #LTS00127750

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 unresolved issues and callbacks by ensuring the customer validates the solution before hanging up.
  This week: #LTS00127750
• Step 2
  At the start of each call, verify the exact product model, serial number, and warranty status to ensure accurate troubleshooting.
  Why: Missing product details leads to incorrect guidance and unresolved calls.
  This week: #GI00043822
• Step 3
  Follow KB-defined troubleshooting steps for mesh node connectivity issues, including checking WAN/ISP connections, performing structured resets (e.g., 5-press method), and referencing LED interpretation guides.
  Why: Skipping steps prevents resolution and increases repeat calls.
  This week: #LTS00127750
• Step 4
  Provide only up-to-date information about product support status, referencing KB documentation to avoid misleading customers.
  Why: False claims about discontinued models can cause customer frustration and poor decisions.
  This week: #GI00043822

Escalation Lessons

No escalated case learning this week.

Evidence Calls