Coaching Summary
No summary available.
Risk Flags
Two calls this week share issue_type_effective 'CONNECTIVITY' and both have technical_resolution_status 'not_fixed', indicating recurring unresolved connectivity problems.
Correct behavior: Follow KB troubleshooting for connectivity issues: verify power, cables, ISP connection, perform factory resets, and guide through structured pairing methods (e.g., 5-press) before closing.
Impact: Customers experience ongoing connectivity issues, leading to frustration and potential callbacks.
Related: #GI00043822, #LTS00127750
Two calls this week have accuracy scores below 2.0, indicating severe technical misguidance.
Correct behavior: Provide accurate product information and follow KB troubleshooting procedures; verify product model and serial number before advising.
Impact: Customers receive incorrect guidance, leading to wasted time and potential mis-purchasing.
Related: #GI00043822, #LTS00127750
Call #GI00132019 has protocol score 1, indicating failure to maintain professional and efficient call handling.
Correct behavior: Follow call handling protocol: greet customer, identify issue, gather necessary details, perform troubleshooting, and set clear next steps before closing.
Impact: Customer felt ignored and received no assistance, leading to frustration.
Related: #GI00132019
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 1.53 | 3 |
| Technical Accuracy | 2.33 | 3 |
| Protocol | 1.33 | 3 |
| Communication | 1.33 | 3 |
V2 Rubric (Shadow Grading)
No v2 shadow-grading data available for this week.
Score Diagnostics
Based on 3 calls reviewed this week.
Technical Findings
From four to six minutes, correct.
Call Handling Findings
- Inaccurate Product InformationReference KB documentation for product support status and follow led_intelligent_mesh_consumer.md for blinking red LED troubleshooting: verify power, cables, ISP connection, perform factory reset, and guide through 5-press method when applicable.
- Incomplete TroubleshootingAt the start of each call, collect device model, serial number, and environment details. Follow KB troubleshooting flows step-by-step, including verification of upstream connections, structured resets (e.g., 5-press method), and LED interpretation per device family.
Calibration Notes
None recorded this week.
Callback Chains
No callback chains detected.
Documentation Mismatches
No documentation mismatches found.
Suggested Coaching Conversation
No coaching conversation guide available.
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 |
|---|---|---|---|---|---|---|---|---|---|---|
| #GI00043822 | 2026-06-15 | — | 1.8 | 1 | 2 | 2 | — | MX4200 | CONNECTIVITY | No definitive fix; advise power-cycle, reset, and verify wiring; consider upgrade; follow-up needed. |
| #GI00132019 | 2026-06-16 | — | 1.8 | 5 | 1 | 1 | — | GENERAL INQUIRY | None; call ended without resolution or follow-up path. | |
| #LTS00127750 | 2026-06-16 | — | 1 | 1 | 1 | 1 | — | WHW03 | CONNECTIVITY | No resolution; agent did not provide clear next steps or escalation path. |