1Calls
2.90Avg Score
57m 34sAvg Handle Time
1Documented
0Escalated
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.9 | 1 |
| Technical Accuracy | 3.0 | 1 |
| Protocol | 2.0 | 1 |
| Communication | 4.0 | 1 |
Main focus: Model Number Verification
V2 Rubric (Shadow Grading)
V2 overall: 42.14% across 1 v2-scored calls this week
| Category | Week Average |
|---|---|
| Resolution | 0.62 |
| Technical Accuracy | 1.88 |
| Communication | 3.75 |
| Customer Ownership | 3.0 |
| Escalation Judgment | — |
| Customer Experience | 3.21 |
- Unresolved: 1
Where Did the Time Go
By Product Family
| Family | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Note |
|---|---|---|---|---|---|---|---|
| WHW | 1 | 57m 34s | 2.9 | 3.0 | 2.0 | 4.0 |
By Problem Category
| Category | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Focus? |
|---|---|---|---|---|---|---|---|
| SETUP | 1 | 57m 34s | 2.9 | 3.0 | 2.0 | 4.0 |
What You Did Well
- Professional Communication1 of 1 callsThe agent maintained clear and professional communication throughout the call, ensuring the customer understood the information provided. This occurred across 1 of 1 calls, specifically in ticket #LTS00096954.Why this matters: Clear communication reduces customer confusion and builds trust, leading to higher satisfaction.
- Realistic Expectation Setting1 of 1 callsThe agent set realistic expectations about the product's lifecycle, preparing the customer for potential limitations. This was demonstrated in 1 of 1 calls, ticket #LTS00096954.Why this matters: Managing expectations prevents future disputes and ensures customers make informed decisions.
Growth Focus
- Model Number Verification1 of 1 callsThe agent failed to obtain the model number, critical for determining compatibility and support pathing, in 1 of 1 calls (ticket #LTS00096954).Why this matters: Without the model number, recommendations may be inaccurate, leading to incorrect advice and potential callbacks.Example: In ticket #LTS00096954, the agent advised upgrading without confirming the model, which could have led to an unsuitable recommendation.What better looks like: Always obtain the model number before discussing compatibility or support options.
- KB Verification for EOL Dates1 of 1 callsThe agent provided an unverified discontinuation date without referencing the KB, risking inaccurate information, in 1 of 1 calls (ticket #LTS00096954).Why this matters: Unverified EOL dates can mislead customers about support options and product viability.Example: In ticket #LTS00096954, the agent stated November 6, 2023, as the discontinuation date without KB confirmation.What better looks like: Always verify discontinuation and EOL dates using official KB documentation before sharing with customers.
Callback Flags
No callback chains detected.
Documentation Accuracy
No documentation mismatches detected this week.
Practice Plan
- Step 1Always obtain the model number before discussing compatibility or support options.Why: Skipping this step can lead to incorrect recommendations and customer frustration.This week: #LTS00096954
- Step 2Verify product discontinuation and EOL dates using official KB documentation before sharing with customers.Why: Unverified dates may mislead customers about support availability.This week: #LTS00096954
- Step 3Consult velop_mesh_compatibility.md when assessing mesh expansion possibilities.Why: Missing this KB can result in premature recommendations to upgrade.This week: #LTS00096954
Escalation Lessons
No escalated case learning this week.
Evidence Calls
| Case | Date | Score | V2 | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00096954INBOUND | 2026-06-29 | 2.9 A 3P 2C 4 | 42.1% Needs Improvement | WHW03 | SETUP | Advise upgrade to a new Linksys mesh system to add additional nodes. |