Coach & QA View

leo.lluisma@concentrix.com — Week of 2026-06-14 – 2026-06-20

Hybrid Week 1 Risk Flags

Coaching Summary

Declining performance with severe engagement and protocol gaps despite perfect accuracy on a single call.

Complete failure to transition from script to active customer support, resulting in abandoned calls and low scores.

Key calls: #LTS00103689

Risk Flags

Protocol Violation

Failed to engage with customer or acknowledge requests, resulting in protocol score of 1 on CONNECTIVITY call.

ExampleDid not respond to customer's modem/router confusion or callback request at [03:00], leaving call abandoned.

Correct behavior: After script, transition to active listening: greet customer, confirm issue understanding, and document all requests.

Impact: Customer felt ignored, leading to unresolved issue and potential repeat contact.

Related: #LTS00103689

View ticket #LTS00103689

Week-over-Week Progress

No prior-week comparison available yet.

Scorecard

DimensionWeek AverageCalls Reviewed
Overall1.81
Technical Accuracy5.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
5.00
Protocol
1.00
Communication
1.00
Overall
1.80

Technical Findings

improvement
Failed to respond to customer's modem/router confusion after initial greeting, leaving inquiry unaddressed.
#LTS00103689  ·  call d589c080-6c3c-11f1-898f-42010a623f91
improvement
Did not acknowledge or confirm customer's callback request at [03:00], failing to set expectations.
#LTS00103689  ·  call d589c080-6c3c-11f1-898f-42010a623f91
improvement
No troubleshooting steps initiated despite clear customer issue; violated basic support protocol.
#LTS00103689  ·  call d589c080-6c3c-11f1-898f-42010a623f91

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
Your accuracy score of 5 shows strong technical knowledge — let's build on that by improving how we engage customers after the script.
2
What processes can we use to ensure we always acknowledge and document customer requests like callback times?
3
How can we initiate at least one troubleshooting step on every technical call, even when issues seem straightforward?
4
Let's role-play transitioning from script to active support: greet, confirm understanding, and collect details before proceeding.

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
#LTS00103689INBOUND2026-06-201.8511WHW03CONNECTIVITY
None – agent did not respond to customer after initial greeting.