Coach & QA View

hazelmae.advincula@concentrix.com — Week of 2026-06-21 – 2026-06-27

Hybrid Week 1 Risk Flags

Coaching Summary

Declining performance with low resolution rates and accuracy issues this week

Consistent protocol violations and technical inaccuracies in troubleshooting, particularly around device identification and configuration guidance

Key calls: #LTS00003727

Risk Flags

Critical dimension below threshold

Accuracy and protocol scores critically low (1/1) due to incorrect guidance and protocol violations.

ExampleProvided impossible DNS values 'DNS1 488' and 'DNS 2884444' during troubleshooting on #LTS00003727

Correct behavior: Refer to KB for valid DNS configurations and collect required device information before troubleshooting

Impact: Customer received incorrect instructions that could cause network disruption or security risks

Related: #LTS00003727

View ticket #LTS00003727

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 product model, serial number, or warranty information — critical protocol violation for technical support.
#LTS00003727  ·  call 0fb598dc-7143-11f1-99f3-42010a5a3f83
improvement
Provided factually incorrect and technically impossible DNS values ('DNS1 488', 'DNS 2884444') — severe accuracy failure contradicting the KB.
#LTS00003727  ·  call 0fb598dc-7143-11f1-99f3-42010a5a3f83

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
You mentioned escalation during the call with #LTS00003727 — let's review the protocol steps for ensuring all required information is collected before considering escalation.
2
When providing configuration values like DNS settings, how do you currently verify the information against KB documentation?
3
Can we walk through a structured troubleshooting flow for Parental Controls issues to ensure we cover all required verification steps?
4
What process do you use to confirm customer understanding after providing technical 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
#LTS000037272026-06-261111MX2000CONNECTIVITY
Call ended without resolution. Escalation mentioned but not executed (no case number, timeline, or confirmation).