Coach & QA View

vincent.tobias@linksys.com — Week of 2026-06-14 – 2026-06-20

1 Risk Flags

Coaching Summary

Performance this week shows strong technical accuracy but very low overall scores due to inconsistent verification and closure practices.

Agent delivers correct technical guidance but fails to verify customer success or provide clear call summaries, leaving issues unresolved.

Key calls: #LD00121165

Risk Flags

Critical dimension below threshold

Call had accuracy score of 5.0 but protocol and communication scores below 2.0, indicating major gaps in call structure and customer engagement.

ExampleAgent collected email without explaining purpose, failed to verify solution, and ended call without recap — all contributing to poor protocol/communication scores.

Correct behavior: Follow KB guidelines for information collection, verify solutions functionally, and provide clear call summaries before closure.

Impact: Customer remained uncertain if issue was resolved, leading to potential repeat calls and reduced trust.

Related: #LD00121165

View ticket #LD00121165

Week-over-Week Progress

No prior-week comparison available yet.

Scorecard

DimensionWeek AverageCalls Reviewed
Overall2.21
Technical Accuracy5.01
Protocol2.01
Communication2.01

V2 Rubric (Shadow Grading)

V2 overall: 84.52% across 1 v2-scored calls this week

CategoryWeek Average
Resolution5.0
Technical Accuracy5.0
Communication2.5
Customer Ownership5.0
Escalation Judgment
Customer Experience1.79

Score Diagnostics

Based on 1 calls reviewed this week.

Accuracy
5.00
Protocol
2.00
Communication
2.00
Overall
2.20

Technical Findings

strength
Accurately identified SPNM60 as not supported by Linksys app (KB-confirmed).
#LD00121165  ·  call a0741dc0-6a5a-11f1-a6b0-42010a623f91
improvement
Failed to verify whether customer could successfully log in via web UI, leaving resolution unconfirmed and causing customer frustration.
#LD00121165  ·  call a0741dc0-6a5a-11f1-a6b0-42010a623f91

Call Handling Findings

Calibration Notes

Callback Chains

No callback chains detected.

Documentation Mismatches

No documentation mismatches found.

Suggested Coaching Conversation

1
I noticed you provided accurate technical guidance for the SPNM60 router limitations in your call today — that's excellent product knowledge.
2
Can you walk me through your process for verifying that a customer has successfully completed a troubleshooting step? How do you ensure they’ve actually resolved the issue?
3
When you collect customer information like email addresses, what steps do you take to explain why you need it and how it will be used?
4
How do you currently summarize resolution steps before closing a call? Let's discuss ways to make this more effective for customer confidence.
5
What strategies could you use to confirm customers have the necessary credentials before providing login instructions?

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
#LD00121165INBOUND2026-06-172.252284.5%
Developing
SPNM60ACCESS
Access router via web browser at http://192.168.1.1 or http://myrouter.local and log in with admin password from router label.