1Calls
2.70Avg Score
7m 26sAvg Handle Time
1Documented
0Escalated
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.7 | 1 |
| Technical Accuracy | 4.0 | 1 |
| Protocol | 2.0 | 1 |
| Communication | 3.0 | 1 |
Main focus: Incomplete troubleshooting steps
V2 Rubric (Shadow Grading)
V2 overall: 59.82% across 1 v2-scored calls this week
| Category | Week Average |
|---|---|
| Resolution | 0.62 |
| Technical Accuracy | 2.81 |
| Communication | 3.75 |
| Customer Ownership | 5.0 |
| Escalation Judgment | 5.0 |
| Customer Experience | 4.29 |
- Unresolved: 1
Where Did the Time Go
Product family breakdown not available.
By Problem Category
| Category | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Focus? |
|---|---|---|---|---|---|---|---|
| CONNECTIVITY | 1 | 7m 26s | 2.7 | 4.0 | 2.0 | 3.0 |
What You Did Well
- Accurate customer data collection1 of 1 callsCollected serial number and phone number accurately across the call.Why this matters: Ensures proper identification and follow-up for the customer.
- Professional communication tone1 of 1 callsMaintained a polite and professional tone throughout the call.Why this matters: Builds customer trust and positive support experience.
Growth Focus
- Incomplete troubleshooting steps1 of 1 callsFailed to execute standard troubleshooting steps (power cycle router, verify WAN connection, check Wi-Fi broadcast settings) in 1 of 1 calls, leading to unresolved issue.Why this matters: Skipping basic troubleshooting delays resolution and increases callback risk.Example: In ticket #GI00009646, the agent asked about LED status and Wi-Fi visibility but did not perform a power cycle or check WAN connection before advising a callback.What better looks like: Systematically perform power cycle, WAN connection verification, and Wi-Fi broadcast settings check before escalating or setting callbacks.
- Missing product model confirmation1 of 1 callsDid not collect or confirm the product model number in 1 of 1 calls, hindering targeted troubleshooting.Why this matters: Without the model, appropriate diagnostics and solutions cannot be applied.Example: In ticket #GI00009646, the agent documented 'Model#: LRT214' in notes but did not confirm this during the live call, leading the grader to assess that it was never collected.What better looks like: Confirm the product model number verbally and document it early in every call to guide troubleshooting.
Callback Flags
No callback chains detected.
Documentation Accuracy
#GI00009646LOW
Grader saw: Did not collect or confirm product model number during call
Agent documented: Model#: LRT214 documented in agent notes
Agent documented product model in notes but grader assessed it was never confirmed during the live interaction.
Practice Plan
- Step 1Confirm the product model number verbally and document it within the first 30 seconds of every inbound call.Why: Missing model information prevents targeted troubleshooting and increases resolution time.This week: #GI00009646
- Step 2Perform power cycle, WAN connection verification, and Wi-Fi broadcast settings check before setting any callback or escalation.Why: Skipping these basic steps leads to unresolved issues and repeat calls.This week: #GI00009646
- Step 3Explicitly confirm warranty status before discussing replacement options or advanced solutions.Why: Ensures compliance and provides accurate support pathways to the customer.This week: #GI00009646
Escalation Lessons
No escalated case learning this week.
Evidence Calls
| Case | Date | Score | V2 | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #GI00009646INBOUND | 2026-06-16 | 2.7 A 4P 2C 3 | 59.8% Needs Improvement | CONNECTIVITY | Customer to call back when at home for full troubleshooting and possible hardware replacement |