Coaching Summary
Performance shows technical inaccuracies and inefficient call handling despite successful resolution in one case.
Agent provides incorrect technical details and uses excessive repetition, leading to reduced accuracy and unresolved issues.
Key calls: #LTS00134380, #LTS00134917
Risk Flags
Accuracy below threshold
Accuracy score of 2.0 on call #LTS00134380, indicating significant misunderstanding or incomplete resolution.
ExampleProvided wrong router IP address and conflicting password policies during MX5500 setup.
Correct behavior: Verify technical details from KB before communicating to customer; ensure accuracy of guidance.
Impact: Customer may be unable to access router or configure it correctly, leading to frustration and potential security issues.
Related: #LTS00134380
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.6 | 2 |
| Technical Accuracy | 3.0 | 2 |
| Protocol | 2.5 | 2 |
| Communication | 2.5 | 2 |
V2 Rubric (Shadow Grading)
No v2 shadow-grading data available for this week.
Score Diagnostics
Based on 2 calls reviewed this week.
Technical Findings
improvement
Provided wrong router IP address ([REDACTED_PHONE]) at [21:03], which is invalid and would prevent access.
#LTS00134380 · call 2a90cf54-6e97-11f1-baef-42010a660053
improvement
Gave conflicting password policy: claimed minimum 10 characters [28:13], then 8 [41:29], and incorrectly stated special characters are not allowed [40:34], when MX5500 supports them.
#LTS00134380 · call 2a90cf54-6e97-11f1-baef-42010a660053
strength
Correctly used the 5-press method for pairing the child node on an MX5500, which is valid per KB documentation.
#LTS00134380 · call 2a90cf54-6e97-11f1-baef-42010a660053
improvement
Mischaracterized pink LED as acceptable [54:30]; MX5500 should show solid purple when ready for setup, not pink.
#LTS00134380 · call 2a90cf54-6e97-11f1-baef-42010a660053
improvement
Excessive repetition and unnecessary confirmations leading to poor efficiency.
#LTS00134917 · call 75c9d228-710c-11f1-82c1-42010a660053
Call Handling Findings
- Inaccurate technical guidanceVerify correct IP address in KB before stating it; clearly state password requirements as 8+ characters with optional special characters for MX5500.
- Inefficient call controlSummarize steps clearly, confirm fix before closing, and provide explicit next steps if issue persists.
Calibration Notes
None recorded this week.
Callback Chains
No callback chains detected.
Documentation Mismatches
No documentation mismatches found.
Suggested Coaching Conversation
1
Your correct use of the 5-press method for MX5500 mesh pairing in #LTS00134380 was excellent—let's discuss how to maintain that precision in other technical guidance.
2
In #LTS00134380, you provided an incorrect router IP address and conflicting password policies. How can we ensure every technical detail is verified against KB before sharing it with customers?
3
The repetition in #LTS00134917 extended the call without resolution. What strategies can we use to streamline confirmations and end calls with clear next steps?
4
When guiding customers through complex setups, how can we balance thoroughness with efficiency to avoid overwhelming them or extending call times unnecessarily?
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 |
|---|---|---|---|---|---|---|---|---|---|---|
| #LTS00134380 | 2026-06-23 | — | 2.8 | 2 | 3 | 3 | — | MX5500 | SETUP | Mesh network fully set up, internet confirmed, both nodes visible in app. |
| #LTS00134917 | 2026-06-26 | — | 2.4 | 4 | 2 | 2 | — | WHW03 | CONNECTIVITY | Factory reset the Linksys router and re‑configure; if issue persists, consider replacement. |