Your weekly coaching path

Week-over-Week Progress

Scorecard

Main focus: Issue clarification failure

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

• Polite customer engagement1 of 1 callsUsed the customer's name and maintained a polite tone throughout the call, contributing to a positive customer experience.
  Why this matters: Polite engagement helps build rapport and can improve customer satisfaction even when resolution is delayed.
  #LTS00132912

Growth Focus

• Issue clarification failure1 of 1 callsFailed to clarify the customer's actual issue or goal despite the customer mentioning disconnecting from an old account, leading to no actionable resolution.
  Why this matters: Unclear issues result in wasted time, customer frustration, and increased callback risk as the root cause remains unaddressed.
  Example: In ticket #LTS00132912, the agent acknowledged the need to disconnect from an old account but did not explore the issue further, leaving the customer without guidance.
  What better looks like: Active listening and targeted questioning to confirm the exact customer goal (e.g., 'Are you trying to disconnect your mesh nodes from an old account?') before proceeding.
  #LTS00132912
• Missing product details1 of 1 callsDid not collect required product details (model/serial) for troubleshooting, nor follow up when the customer did not provide them, preventing proper diagnosis.
  Why this matters: Without device details, agents cannot reference KB articles or determine compatibility, increasing the chance of incorrect guidance and repeat calls.
  Example: In ticket #LTS00132912, the agent asked for serial numbers but did not persist when the customer did not provide them, and no alternative troubleshooting was offered.
  What better looks like: Persistently collect model and serial number, use KB lookup if unavailable, and explain why the information is needed before proceeding.
  #LTS00132912

Callback Flags

No callback chains detected.

Documentation Accuracy

No documentation mismatches detected this week.

Practice Plan

• Step 1
  Before proceeding with any troubleshooting, clearly confirm the customer's specific issue and goal by asking targeted questions.
  Why: Unclear issues lead to wasted time, incorrect solutions, and increased callbacks due to unresolved root causes.
  This week: #LTS00132912
• Step 2
  Collect and verify product model and serial number at the start of every call, and use this information to reference KB articles or compatibility matrices.
  Why: Without device details, agents cannot provide accurate guidance, potentially misapplying solutions and frustrating customers.
  This week: #LTS00132912
• Step 3
  Provide explicit, step-by-step instructions or share relevant KB links during the call, confirming the customer understands each step.
  Why: Customers need actionable guidance to resolve issues; vague promises like 'an email will follow' often result in unresolved cases.
  This week: #LTS00132912
• Step 4
  Before ending a call, summarize all promised actions (e.g., emails, callbacks) including content, timeline, and next steps, and get customer confirmation.
  Why: Clear closure prevents customer confusion and reduces follow-up calls due to unmet expectations.
  This week: #LTS00132912

Escalation Lessons

No escalated case learning this week.

Evidence Calls

Feedback