Coach & QA View

noha.magdy@sutherlandglobal.com — Week of 2026-06-21 – 2026-06-27

Hybrid Week 1 Risk Flags

Coaching Summary

Declining performance with all score dimensions at minimum values due to fundamental process gaps

Complete lack of device validation and troubleshooting execution leading to unresolved cases

Key calls: #LTS00065475

Risk Flags

Critical dimension scores

Accuracy and protocol scores at minimum values (1/5) due to complete lack of proper device identification and troubleshooting

ExampleAgent accepted invalid model 'MX M502' and ended call without any troubleshooting on #LTS00065475

Correct behavior: Follow KB procedures for device validation, serial number collection, and minimum troubleshooting steps before closure

Impact: High risk of repeat call and potential warranty claim errors

Related: #LTS00065475

View ticket #LTS00065475

Week-over-Week Progress

No prior-week comparison available yet.

Scorecard

DimensionWeek AverageCalls Reviewed
Overall1.01
Technical Accuracy1.01
Protocol1.01
Communication1.01

V2 Rubric (Shadow Grading)

No v2 shadow-grading data available for this week.

Score Diagnostics

Based on 1 calls reviewed this week.

Accuracy
1.00
Protocol
1.00
Communication
1.00
Overall
1.00

Technical Findings

improvement
Failed to collect accurate product model — 'MX M502' is not a valid Linksys model; should have clarified or corrected (e.g., MX5500, MX5300).
#LTS00065475  ·  call 3ecdf7de-6f97-11f1-bb4f-42010a663f85
improvement
Did not verify or properly record the serial number — accepted garbled input without correction or validation.
#LTS00065475  ·  call 3ecdf7de-6f97-11f1-bb4f-42010a663f85
improvement
Did not perform any troubleshooting despite customer describing a hardware issue.
#LTS00065475  ·  call 3ecdf7de-6f97-11f1-bb4f-42010a663f85
improvement
Did not create or reference a support case.
#LTS00065475  ·  call 3ecdf7de-6f97-11f1-bb4f-42010a663f85

Call Handling Findings

Calibration Notes

None recorded this week.

Callback Chains

No callback chains detected.

Documentation Mismatches

Agent documented assumption of resolution while grader marked issue as not applicable and closure was abandoned

Grader says: not_applicable
Agent documented: assumed issue resolved per agent documentation

Suggested Coaching Conversation

1
Your detailed documentation efforts are evident in the case notes — let's discuss how we can pair that with stronger upfront device validation.
2
When customers mention specific model numbers that don't match our KB lists, what verification steps do you currently use?
3
Can we walk through the minimum troubleshooting requirements for hardware malfunction cases before closing?
4
How can we ensure every unresolved call gets either a troubleshooting step executed or a clear escalation path documented?

Coaching Best Practices

Five Principles for Effective Coaching Conversations

  1. SBI feedback model — Describe the Situation, the Behavior you observed, and its Impact. Avoid labels (“you always…”) — describe the specific instance.
  2. Ask more than you tell — Start with “What did you notice on that call?” before offering your interpretation. Agents who self-diagnose retain more.
  3. Recognition before correction — Open with a genuine strength observation. Agents in a defensive posture can’t hear coaching.
  4. 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.”
  5. 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

CaseDateDurationOverallAccuracyProtocolCommsV2ProductIssue TypeOutcome
#LTS000654752026-06-241111MBE7000CONNECTIVITY
None provided.