Coach & QA View

zhiliang.chen@concentrix.com — Week of 2026-06-28 – 2026-07-04

Hybrid Week 2 Risk Flags

Coaching Summary

Declining performance with consistently low scores and unresolved issues this week

Systematic failure to identify product models and apply correct troubleshooting protocols

Key calls: #LTS00135272

Risk Flags

Critical accuracy score

Scored accuracy of 1/5 on a call requiring basic product identification

ExampleFailed to identify or confirm device model during troubleshooting

Correct behavior: Always verify product model and firmware before proceeding with any steps

Impact: Provided invalid instructions causing customer confusion

Related: #LTS00135272

View ticket #LTS00135272

Critical protocol score

Scored protocol of 1/5 by skipping warranty checks and case creation

ExampleBypassed standard Linksys support protocol during hardware issue handling

Correct behavior: Follow full protocol including warranty verification and case documentation for all hardware issues

Impact: Customer left without clear escalation path or documentation

Related: #LTS00135272

View ticket #LTS00135272

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 identify or confirm the product model before troubleshooting
#LTS00135272  ·  call e3478de0-7454-11f1-9c92-42010a663f80
improvement
Provided vague/incorrect reset instructions that did not match KB procedures for FGW5500
#LTS00135272  ·  call e3478de0-7454-11f1-9c92-42010a663f80

Call Handling Findings

Calibration Notes

None recorded this week.

Callback Chains

No callback chains detected.

Documentation Mismatches

No documentation mismatches found.

Suggested Coaching Conversation

1
I noticed you initiated a ticket for the customer, which shows good awareness of documentation needs even in challenging calls.
2
In the HARDWARE call #LTS00135272, what steps did you take to verify the customer's device model before suggesting troubleshooting?
3
How can we ensure reset instructions always match the exact KB procedures for each product line?
4
What process can we implement to double-check protocol compliance before ending calls with unresolved issues?

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
#LTS001352722026-06-301111FGW5500HARDWARE
No resolution achieved; advise customer to contact Linksys support again with full device details or schedule a technician.