Coaching Summary
Mixed performance with technical inaccuracies impacting customer guidance despite strong device identification skills
Tendency to provide recommendations without verifying KB documentation and omitting critical post-troubleshooting verification steps
Key calls: #LTS00136293, #LTS00100300, #EOS00136290
Risk Flags
Provided materially inaccurate mesh compatibility information that could lead to customer purchasing incompatible hardware
Correct behavior: Verify mesh compatibility against velop_mesh_compatibility.md before making recommendations
Impact: Customer may purchase incompatible node rendering network non-functional
Related: #LTS00136293
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 3.2 | 3 |
| Technical Accuracy | 3.67 | 3 |
| Protocol | 3.0 | 3 |
| Communication | 2.0 | 3 |
V2 Rubric (Shadow Grading)
V2 overall: 34.39% across 3 v2-scored calls this week
| Category | Week Average |
|---|---|
| Resolution | 1.88 |
| Technical Accuracy | 1.15 |
| Communication | 2.08 |
| Customer Ownership | 1.69 |
| Escalation Judgment | 0.0 |
| Customer Experience | 2.02 |
- Partial Resolution: 2
- Unresolved: 1
Score Diagnostics
Based on 3 calls reviewed this week.
Technical Findings
Call Handling Findings
- Technical accuracy verificationValidate mesh compatibility against KB before recommending products and always verify internet connectivity post-troubleshooting
- Troubleshooting completenessFollow documented troubleshooting sequence and collect device identifiers before declaring hardware obsolete
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 |
|---|---|---|---|---|---|---|---|---|---|---|
| #EOS00136290INBOUND | 2026-07-08 | — | 3.1 | 5 | 2 | 2 | 7.5% Needs Improvement | E1200 | SETUP | Advised replacement of the obsolete router. |
| #LTS00136293INBOUND | 2026-07-08 | — | 2.8 | 1 | 3 | 2 | 21.5% Needs Improvement | MX2000 | NO TROUBLESHOOTING NEEDED | Advised to purchase a Linksys mesh node (e.g., Atlas Wi-Fi 6) for coverage extension, despite incompatibility risks. |
| #LTS00100300INBOUND | 2026-07-08 | — | 3.7 | 5 | 4 | 2 | 74.2% Developing | MX4200 | CONNECTIVITY | Most nodes show solid green/blue; mesh appears restored. Customer later confirmed Wi-Fi working during app check. Case closed with case number 100 300. |