Coaching Summary
Declining performance with consistent failure to follow documented troubleshooting protocols
Systematic omission of foundational diagnostics and provision of unsupported procedures
Key calls: #LTS00008682
Risk Flags
Critical dimension below threshold
Scored accuracy=1 and protocol=1 (both below minimum thresholds) due to undocumented procedures and missed diagnostics
ExampleInstructed undocumented reset procedure and skipped WAN verification during MX5300 configuration call
Correct behavior: Follow KB-documented reset procedures and complete foundational WAN/modem diagnostics before device-specific troubleshooting
Impact: Risk of device damage, unresolved connectivity issues, and repeat calls
Related: #LTS00008682
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 1.0 | 1 |
| Technical Accuracy | 1.0 | 1 |
| Protocol | 1.0 | 1 |
| Communication | 1.0 | 1 |
V2 Rubric (Shadow Grading)
No v2 shadow-grading data available for this week.
Score Diagnostics
Based on 1 calls reviewed this week.
Technical Findings
improvement
Provided incorrect reset procedure: instructed customer to hold reset button until LED turns off (transcript [02:00], [03:00]), which is not documented for any Linksys device.
#LTS00008682 · call 21a949f0-79ca-11f1-86fd-42010a663f85
improvement
Failed to verify WAN connection or perform modem power cycle—critical first step for red LED issues per KB.
#LTS00008682 · call 21a949f0-79ca-11f1-86fd-42010a663f85
improvement
Did not identify or use correct LED interpretation for red, purple, or blinking lights—ignored KB guidance entirely.
#LTS00008682 · call 21a949f0-79ca-11f1-86fd-42010a663f85
improvement
Assumed pairing method without confirming model compatibility—MHC4200 is not a recognized Linksys mesh model.
#LTS00008682 · call 21a949f0-79ca-11f1-86fd-42010a663f85
Call Handling Findings
- Incorrect troubleshooting proceduresAlways verify WAN connectivity, perform modem power cycle for LED issues, follow documented reset procedures, and confirm device model compatibility before assuming mesh capabilities.
- Incomplete diagnostic approachSystematically verify WAN connection, power cycle modem, and interpret LED states before proceeding to device-specific troubleshooting.
Calibration Notes
None recorded this week.
Callback Chains
No callback chains detected.
Documentation Mismatches
No documentation mismatches found.
Suggested Coaching Conversation
1
Your dedication to guiding customers through complex setups is evident - let's refine how we approach MX series troubleshooting to ensure every step aligns with current KB guidelines.
2
When customers report LED issues, what specific WAN and modem checks do you perform before moving to device-specific steps?
3
How can we verify device model compatibility before demonstrating pairing procedures?
4
Let's review the current MX mesh reset KB articles together - can you walk me through the exact steps you would follow for an MX5300 with solid red LED?
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 |
|---|---|---|---|---|---|---|---|---|---|---|
| #LTS00008682 | 2026-07-07 | — | 1 | 1 | 1 | 1 | — | MX5300 | CONFIGURATION | No resolution achieved. Issue unresolved. Recommend verifying model compatibility, performing correct factory reset, and following documented mesh setup procedure if applicable. If the MHC4200 is not a supported model, advise the customer on correct hardware. |
Feedback
✓ Feedback submitted — thank you!