Your weekly coaching path

Week-over-Week Progress

Scorecard

Main focus: Call Engagement Protocol

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

• Accuracy Excellence1 of 1 callsDelivered perfect accuracy (score 5) by providing technically correct information during the CONNECTIVITY issue resolution for WHW03, though engagement was limited.
  Why this matters: Maintains technical credibility and reduces risk of misguidance, even in brief interactions.
  #LTS00103689

Growth Focus

• Call Engagement Protocol1 of 1 callsFailed to transition from automated script to active support, leaving customer's modem/router confusion unaddressed and callback request unconfirmed across the single CONNECTIVITY call (#LTS00103689).
  Why this matters: Risk of customer frustration, repeat calls, and compliance violations when support is not acknowledged.
  Example: Agent did not respond after initial greeting or acknowledge callback request at [03:00], resulting in abandoned call.
  What better looks like: After script, actively greet customer, confirm understanding of issue, and document all requests (e.g., callback times).
  #LTS00103689
• Case Documentation Completeness1 of 1 callsDid not collect required case information (model, serial, contact details) or initiate troubleshooting despite clear customer inquiry in the WHW03 CONNECTIVITY call (#LTS00103689).
  Why this matters: Incomplete documentation prevents effective escalation or follow-up, increasing resolution time.
  Example: Agent ended call without gathering serial number or attempting basic connectivity troubleshooting.
  What better looks like: Collect model, serial, and contact details within first 30 seconds; initiate at least one troubleshooting step before closing.
  #LTS00103689

Callback Flags

No callback chains detected.

Documentation Accuracy

No documentation mismatches detected this week.

Practice Plan

• Step 1
  Collect device model, serial number, and contact details within the first 30 seconds of every call.
  Why: Prevents escalation delays and ensures continuity if follow-up is needed.
• Step 2
  After initial script, actively acknowledge the customer's issue and confirm understanding before proceeding.
  Why: Builds trust and reduces risk of missed customer concerns.
  This week: #LTS00103689
• Step 3
  Initiation at least one troubleshooting step or knowledge base reference before closing any technical inquiry.
  Why: Ensures basic support is provided and reduces abandoned call perception.
  This week: #LTS00103689
• Step 4
  Document all customer requests (e.g., callback times, preferred contact methods) explicitly in case notes.
  Why: Creates clear handoff for callbacks and reduces miscommunication risk.
  This week: #LTS00103689

Escalation Lessons

No escalated case learning this week.

Evidence Calls