Coaching Summary
Performance declined this week with critical technical inaccuracies leading to an unresolved case
Agent provided incorrect product identification and compatibility advice while failing to execute basic validation steps
Key calls: #LTS00112615
Risk Flags
Scored accuracy=1.0 and protocol=1.0 due to fundamental technical inaccuracies and compliance failure
Correct behavior: Verify product existence in KB before discussion; consult mesh compatibility matrix; collect email per PCI policy
Impact: Customer received false information, no resolution provided, and compliance violation occurred
Related: #LTS00112615
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 1.1 | 1 |
| Technical Accuracy | 1.0 | 1 |
| Protocol | 1.0 | 1 |
| Communication | 2.0 | 1 |
V2 Rubric (Shadow Grading)
V2 overall: 0.0% across 1 v2-scored calls this week1 auto-zero
| Category | Week Average |
|---|---|
| Resolution | 0.0 |
| Technical Accuracy | 0.0 |
| Communication | 0.0 |
| Customer Ownership | 0.0 |
| Escalation Judgment | — |
| Customer Experience | 0.0 |
- Unresolved: 1
Score Diagnostics
Based on 1 calls reviewed this week.
Technical Findings
Call Handling Findings
- Product identification accuracyVerify product model names against official Linksys product list before discussing features; consult velop_mesh_compatibility KB article for mesh compatibility.
- Technical validation protocolFor mesh compatibility queries, confirm backhaul method (Ethernet vs. wireless), reference adjacent_device_setup_scenarios.md, and provide tested configuration steps.
Calibration Notes
None recorded this week.
Callback Chains
No callback chains detected.
Documentation Mismatches
No documentation mismatches found.
Suggested Coaching Conversation
Coaching Best Practices
Five Principles for Effective Coaching Conversations
- SBI feedback model — Describe the Situation, the Behavior you observed, and its Impact. Avoid labels (“you always…”) — describe the specific instance.
- Ask more than you tell — Start with “What did you notice on that call?” before offering your interpretation. Agents who self-diagnose retain more.
- Recognition before correction — Open with a genuine strength observation. Agents in a defensive posture can’t hear coaching.
- Psychological safety first — Frame mistakes as data, not character. “That call had a tricky wrinkle — let’s pull it apart” lands better than “you made an error here.”
- Close with a specific commitment — End every coaching conversation with one thing the agent will try on their next call, and a follow-up check-in within 48 hours.
Deep Evidence
| Case | Date | Duration | Overall | Accuracy | Protocol | Comms | V2 | Product | Issue Type | Outcome |
|---|---|---|---|---|---|---|---|---|---|---|
| #LTS00112615 | 2026-06-29 | — | 1.1 | 1 | 1 | 2 | 0.0% Needs Improvement | MX5500 | NO TROUBLESHOOTING NEEDED | Agent advised customer to visit the Linksys website for product information without providing specific guidance or troubleshooting. |