Coach & QA View

dennis.gamolo@concentrix.com — Week of 2026-06-14 – 2026-06-20

Hybrid Week 1 Risk Flags

Coaching Summary

Declining performance with critical technical inaccuracies observed in the sole call this week

Systematic omission of device data collection and provision of contradicted Wi-Fi band guidance

Key calls: #LTS00075610

Risk Flags

Critical dimension below threshold

Delivered materially incorrect technical guidance with accuracy score of 1.0 on a single call this week

ExampleClaimed 5GHz = Wi-Fi 6 and 6GHz = Wi-Fi 7 at timestamp [13:00] during troubleshooting on #LTS00075610

Correct behavior: Reference current Wi-Fi Alliance standards and KB articles before explaining band/standard relationships

Impact: Customer received false technical foundation preventing effective self-troubleshooting

Related: #LTS00075610

View ticket #LTS00075610

Week-over-Week Progress

No prior-week comparison available yet.

Scorecard

DimensionWeek AverageCalls Reviewed
Overall1.81
Technical Accuracy1.01
Protocol2.01
Communication2.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
2.00
Communication
2.00
Overall
1.80

Technical Findings

improvement
Provided materially incorrect technical information: claimed 5GHz = Wi-Fi 6 and 6GHz = Wi-Fi 7 (transcript [13:00]), directly contradicting Wi-Fi Alliance standards and KB guidance on Wi-Fi band/standard relationships.
#LTS00075610  ·  call f7e22b54-6863-11f1-b732-42010a663f80
improvement
Failed to collect product model/serial number and warranty status despite troubleshooting a specific device.
#LTS00075610  ·  call f7e22b54-6863-11f1-b732-42010a663f80
improvement
Did not guide the customer through the correct steps to change SSID/password on an LN1602 using the 'Incredible-WiFi' interface (linksys_now_wifi_settings.md).
#LTS00075610  ·  call f7e22b54-6863-11f1-b732-42010a663f80

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 acknowledgment of physical obstacles affecting signal was spot-on—let's build on that diagnostic strength.
2
How do you currently verify Wi-Fi band/standard relationships before providing technical explanations?
3
Walk me through your process for collecting device identifiers and warranty status on hardware-specific calls.
4
What steps would you take differently if a customer asked about SSID/password changes on an LN1602 today?

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
#LTS000756102026-06-151.8122WRT1200ACNO TROUBLESHOOTING NEEDED
No definitive fix provided. Customer will test performance and may call back or return the product.