Coaching Summary
Performance shows critical gaps in protocol structure and technical guidance despite accurate product identification.
Calls lack verifiable closure steps and standard recovery path offerings when email delivery blocks cloud access.
Key calls: #LTS00035865
Risk Flags
Critical dimension below threshold
Protocol score of 2.0 indicates failed call control and documentation structure
ExampleAgent provided vague closure steps ('review support site') without verifying local login success or offering recovery key reset
Correct behavior: Use structured closure: 1) Verify local access 2) Provide exact KB links 3) Offer recovery key reset for email failure scenarios
Impact: Customer left without clear path to resolve, high callback risk
Related: #LTS00035865
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.8 | 1 |
| Technical Accuracy | 4.0 | 1 |
| Protocol | 2.0 | 1 |
| Communication | 2.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
Did not offer the recovery key password reset method, which is the standard procedure for cloud account password recovery when email delivery fails.
#LTS00035865 · call 94aca2c6-7911-11f1-bcd0-42010a660053
improvement
Failed to provide actionable next steps beyond advising local login and checking the support site.
#LTS00035865 · call 94aca2c6-7911-11f1-bcd0-42010a660053
Call Handling Findings
- Recovery key guidanceWhen email delivery fails for cloud account access, immediately present the recovery key password reset as the documented solution.
- Actionable next stepsProvide exact KB article links, step-by-step local login verification, and clear success criteria before closing.
Calibration Notes
- High accuracy (4.0) but low protocol (2.0) and overall (2.8) with unresolved technical status - needs human review of scoring consistency
Callback Chains
No callback chains detected.
Documentation Mismatches
No documentation mismatches found.
Suggested Coaching Conversation
1
You correctly identified the MX5300 model and registered email address in #LTS00035865 - that's excellent product knowledge.
2
When email delivery fails for cloud accounts, why did you choose not to offer the recovery key password reset method?
3
What specific next steps would you provide to a customer who can't log in locally after this advice?
4
How can we structure closures to ensure customers have a clear, verifiable path forward?
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 |
|---|---|---|---|---|---|---|---|---|---|---|
| #LTS00035865 | 2026-07-06 | — | 2.8 | 4 | 2 | 2 | — | MR7350 | SETUP | Customer advised to use the local router admin password for local access and review the support site for additional guidance. |
Feedback
✓ Feedback submitted — thank you!