Your weekly coaching path

Week-over-Week Progress

Scorecard

Main focus: Incomplete customer intake

V2 Rubric (Shadow Grading)

V2 overall: 50.0% across 2 v2-scored calls this week

• Partial Resolution: 2

Where Did the Time Go

Product family breakdown not available.

By Problem Category

What You Did Well

• KB-aligned script delivery1 of 2 callsThe automated message provided factually correct information regarding product registration and support eligibility, consistent with KB guidance, ensuring customers receive accurate initial directives on 1 call this week.
  Why this matters: Delivers correct first-contact information, reducing customer confusion and potential misdirected inquiries.
• Precise opening script adherence1 of 2 callsThe agent delivered a technically accurate opening script aligning with KB guidance on warranty and paid-support eligibility, setting clear expectations for the customer on 1 call this week.
  Why this matters: Establishes clear support parameters early, improving customer experience and reducing ambiguous requests.

Growth Focus

• Incomplete customer intakeappeared in 2 of 2 callsThe agent failed to collect essential customer information — product model, serial number, and issue description — on both calls this week. For example, on call 724311b0-70ed-11f1-b847-42010a62006f, no product details or problem were gathered, and on call 969da990-70f1-11f1-b1b0-42010a62006f, the agent did not ask for model/serial or reason for calling.
  Why this matters: Missing critical data prevents accurate diagnosis, leading to unresolved issues, repeat calls, and potential escalation.
  Example: On call 969da990-70f1-11f1-b1b0-42010a62006f, the agent delivered an opening script but never asked for the customer's product model or the issue they were experiencing, resulting in no troubleshooting being performed.
  What better looks like: Always open calls by requesting product model, serial number, and a brief issue description before proceeding with any troubleshooting.
• No troubleshooting initiationappeared in 2 of 2 callsThe agent did not initiate any diagnostic steps or provide next-step guidance on either call. Both interactions ended without actionable support, such as on call 724311b0-70ed-11f1-b847-42010a62006f where no troubleshooting was offered despite the call being routed to support.
  Why this matters: Failing to start troubleshooting leaves customers unsupported, increasing frustration and likelihood of callbacks or escalations.
  Example: During call 724311b0-70ed-11f1-b847-42010a62006f, after the automated message, the agent did not offer any troubleshooting steps or ask the customer to describe their issue, leading to an abandoned interaction.
  What better looks like: After collecting basic info, immediately begin appropriate troubleshooting based on the reported issue or guide the customer to self-help resources.

Callback Flags

No callback chains detected.

Documentation Accuracy

No documentation mismatches detected this week.

Practice Plan

• Step 1
  Before starting any troubleshooting, always collect product model, serial number, and a brief issue description from the customer.
  Why: Missing critical data prevents accurate diagnosis, leading to unresolved issues and repeat calls.
• Step 2
  After gathering basic info, immediately begin appropriate troubleshooting based on the reported issue or guide the customer to relevant self-help resources.
  Why: Failing to initiate troubleshooting leaves customers unsupported, increasing frustration and likelihood of callbacks.
• Step 3
  Practice engaging live customers from the first ring by asking open-ended questions to surface the actual issue.
  Why: Ensures we actually hear the customer's problem before proceeding, avoiding abandoned-or-vague closures.

Escalation Lessons

No escalated case learning this week.

Evidence Calls