Coach & QA View

glecelmae.leonor@concentrix.com — Week of 2026-06-21 – 2026-06-27

1 Risk Flags

Coaching Summary

Developing performance with critical technical accuracy gaps despite successful resolution outcome.

Technical inaccuracies in device-specific knowledge (LED states, model verification) combined with strong execution of resolution procedures.

Risk Flags

Critical dimension below threshold

Call had accuracy score of 1 (below 2.5 threshold) and protocol score of 2 (below 2.0 threshold).

ExampleAgent incorrectly explained LED states and skipped model verification during troubleshooting.

Correct behavior: Accurately reference model-specific KB documentation for status indicators and always verify product model before recommending advanced procedures.

Impact: Risk of customer misunderstanding LED states leading to incorrect self-troubleshooting attempts.

Week-over-Week Progress

No prior-week comparison available yet.

Scorecard

DimensionWeek AverageCalls Reviewed
Overall3.01
Technical Accuracy1.01
Protocol2.01
Communication3.01

V2 Rubric (Shadow Grading)

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

CategoryWeek Average
Resolution3.75
Technical Accuracy3.12
Communication3.75
Customer Ownership5.0
Escalation Judgment5.0
Customer Experience5.0

Score Diagnostics

Based on 1 calls reviewed this week.

Accuracy
1.00
Protocol
2.00
Communication
3.00
Overall
3.00

Technical Findings

improvement
Incorrect LED interpretation: claimed solid red LED indicates setup mode (02:00), directly contradicting the KB (led_intelligent_mesh_consumer.md). This is a critical accuracy error.
call 15474352-6f06-11f1-a42a-42010a62006f
improvement
Failed to confirm product model before recommending 5-press method, risking incorrect procedure on unsupported models (e.g., SPNM/LN series with Pair button).
call 15474352-6f06-11f1-a42a-42010a62006f

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 successful application of the 5-press method shows strong technical execution when information is correct - well done on confirming resolution through LED changes.
2
You mentioned solid red indicates setup mode at 02:00, but our KB states this means 'No internet connection'. How can we build a verification habit for device-specific indicators?
3
Before recommending advanced recovery procedures next week, what checklist will you use to confirm the exact product model and supported features?
4
When closing calls after technical guidance, how will you systematically confirm the customer observed the expected outcome to prevent post-call 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
15474352-6f06-11f1-a42a-42010a62006fINBOUND2026-06-23312381.2%
Developing
CONNECTIVITY
Node rejoined the mesh; customer can now relocate the node.