Coach & QA View

dorothybelle.oraiz@concentrix.com — Week of 2026-07-05 – 2026-07-11

Hybrid Week 1 Risk Flags

Coaching Summary

Mixed performance with technical inaccuracies impacting customer guidance despite strong device identification skills

Tendency to provide recommendations without verifying KB documentation and omitting critical post-troubleshooting verification steps

Key calls: #LTS00136293, #LTS00100300, #EOS00136290

Risk Flags

Incorrect Guidance

Provided materially inaccurate mesh compatibility information that could lead to customer purchasing incompatible hardware

ExampleTold customer any Linksys mesh product works with MR9000 despite KB stating cross-generation incompatibility

Correct behavior: Verify mesh compatibility against velop_mesh_compatibility.md before making recommendations

Impact: Customer may purchase incompatible node rendering network non-functional

Related: #LTS00136293

View ticket #LTS00136293

Week-over-Week Progress

Overall moved up 0.76 vs. last week.; Accuracy moved up 0.92 vs. last week.
Overall+0.76 ▲
Accuracy+0.92 ▲
Protocol+1.12 ▲
Comms-0.25 ▼
Handle time: +16m 03s longer avg
• MX handle time moved up by 18m 34s vs. last week.

Scorecard

DimensionWeek AverageCalls Reviewed
Overall3.23
Technical Accuracy3.673
Protocol3.03
Communication2.03

V2 Rubric (Shadow Grading)

V2 overall: 34.39% across 3 v2-scored calls this week

CategoryWeek Average
Resolution1.88
Technical Accuracy1.15
Communication2.08
Customer Ownership1.69
Escalation Judgment0.0
Customer Experience2.02

Score Diagnostics

Based on 3 calls reviewed this week.

Accuracy
3.67
Protocol
3.00
Communication
2.00
Overall
3.20

Technical Findings

improvement
Incorrectly stated any Linksys mesh product works with MR9000, contradicting KB velop_mesh_compatibility.md
#LTS00136293  ·  call 86b7409e-7a6b-11f1-883e-42010a62006f
improvement
Failed to verify internet connectivity after mesh restoration, violating velop_wifi_connectivity.md Step 4
#LTS00100300  ·  call 2865d612-7a6c-11f1-a0b8-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 accurate identification of the E1200 as obsolete and MR9000 model details shows strong foundational knowledge - let's build on that strength.
2
When recommending mesh nodes for MR9000, what KB documentation do you reference to confirm compatibility?
3
How can we ensure we always verify internet connectivity after completing mesh restorations?
4
What steps can we take to avoid ambiguous instructions like 'press release press release' during critical procedures?

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
#EOS00136290INBOUND2026-07-083.15227.5%
Needs Improvement
E1200SETUP
Advised replacement of the obsolete router.
#LTS00136293INBOUND2026-07-082.813221.5%
Needs Improvement
MX2000NO TROUBLESHOOTING NEEDED
Advised to purchase a Linksys mesh node (e.g., Atlas Wi-Fi 6) for coverage extension, despite incompatibility risks.
#LTS00100300INBOUND2026-07-083.754274.2%
Developing
MX4200CONNECTIVITY
Most nodes show solid green/blue; mesh appears restored. Customer later confirmed Wi-Fi working during app check. Case closed with case number 100 300.

Feedback