Coach & QA View

paulo.real@concentrix.com — Week of 2026-06-14 – 2026-06-20

Frontline-Heavy Week 1 Risk Flags

Coaching Summary

Performance shows significant room for improvement with low average scores and unresolved issues

Inconsistent troubleshooting execution and frequent protocol deviations

Key calls: #LTS00133703, #LTS00133856

Risk Flags

Critical Dimension Below Threshold

Multiple calls with accuracy scores below 2.5 indicating severe technical guidance failures

ExampleCall 5a7ee5de-6910-11f1-82b4-42010a660053 had accuracy score of 1.0 due to incorrect remote-access steps on unsupported OS

Correct behavior: Follow KB guidelines for supported OSes and avoid unsupported remote-access attempts

Impact: Customer unable to resolve issue and potentially exposed to security risks

Related: #LTS00133703

Week-over-Week Progress

Overall moved up 0.19 vs. last week.; Accuracy moved up 0.21 vs. last week.
Overall+0.19 ▲
Accuracy+0.21 ▲
Protocol+0.19 ▲
Comms+0.17 ▲
Handle time: 15m 59s shorter avg
• EA handle time moved down by 93m 42s vs. last week.
• WHW handle time moved down by 32m 20s vs. last week.

Scorecard

DimensionWeek AverageCalls Reviewed
Overall2.1612
Technical Accuracy2.6712
Protocol1.512
Communication2.1712

V2 Rubric (Shadow Grading)

V2 overall: 34.84% across 11 v2-scored calls this week3 auto-zeros

CategoryWeek Average
Resolution1.7
Technical Accuracy2.02
Communication2.16
Customer Ownership2.39
Escalation Judgment1.25
Customer Experience1.75

Score Diagnostics

Based on 12 calls reviewed this week.

Accuracy
2.67
Protocol
1.50
Communication
2.17
Overall
2.16

Technical Findings

improvement
Provided incorrect router access URL for MX6200 (used myrouter.info instead of myrouter.local/[REDACTED_PHONE])
#LTS00133994  ·  call e2d0235a-6b66-11f1-94c5-42010a62006f
improvement
Suggested pair-button method for MX6200, which requires 5-press method
#LTS00133994  ·  call e2d0235a-6b66-11f1-94c5-42010a62006f

Call Handling Findings

Calibration Notes

Callback Chains

No callback chains detected.

Documentation Mismatches

No documentation mismatches found.

Suggested Coaching Conversation

1
Your commitment to verifying customer details is evident and greatly enhances our service quality. Let's discuss how we can strengthen our technical troubleshooting approach to improve resolution rates.
2
I've noticed several instances where standard troubleshooting sequences weren't fully followed. Could we review the KB flow for connectivity issues together?
3
How do you feel about adopting a more structured approach to firmware verification during initial diagnostics?
4
Let's explore ways to better document and communicate next steps to avoid customer confusion during complex 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
5a7ee5de-6910-11f1-82b4-42010a660053OUTBOUND2026-06-15111123.7%
Needs Improvement
LN1600CONNECTIVITY
Issue not resolved; advised customer to monitor connection after changes and to provide invoice for further warranty review. No clear next step or escalation was set.
#LTS00133703INBOUND2026-06-172.832335.9%
Needs Improvement
WRT1900ACCONNECTIVITY
Advised customer to replace the router with a newer system.
#LTS00133856INBOUND2026-06-182.84220.0%
Needs Improvement
EA9500NO TROUBLESHOOTING NEEDED
No functional resolution. Customer advised to access web UI but could not log in. No factory reset steps, paid-support path, or escalation offered.
#LTS00133984INBOUND2026-06-182.22220.0%
Needs Improvement
EA3500SETUP
Informed customer device is out of warranty; no further support path offered.
#LTS00133986INBOUND2026-06-181.41220.0%
Needs Improvement
EA6350CONNECTIVITY
Advised customer to purchase a new router as the current device is out of warranty and end-of-life, without offering any troubleshooting or self-help guidance.
#LTS00133994INBOUND↩ cb2026-06-181.411281.9%
Developing
MX6200CONNECTIVITY
Customer reported internet working after resets and re-pairing; agent did not verify resolution or provide follow-up steps.
#LTS00133994OUTBOUND↩ cb2026-06-181.7312MX6200CONNECTIVITY
Customer to monitor the node; no further action taken by agent.
#TE00133962OUTBOUND2026-06-192.811241.1%
Needs Improvement
WHW03CONNECTIVITY
No definitive fix; agent advised the customer to continue troubleshooting on their own and offered further assistance if needed.
#TE00133877OUTBOUND2026-06-191.841378.7%
Developing
MX2000CONFIGURATION
ISP is replacing the two MX2000 routers; customer to test after replacement and contact support if issue persists.
#LTS00134150INBOUND2026-06-192.842263.9%
Needs Improvement
EA7450CONNECTIVITY
Agent to email EA7450 user guide; customer to reboot and retry reservation.
#LTS00134161INBOUND2026-06-202.642231.7%
Needs Improvement
MX8500SETUP
Agent offered one-time support due to lack of receipt; no functional setup achieved; no self-help resources provided.
#TE00110086INBOUND2026-06-202.641326.4%
Needs Improvement
MX4200CONNECTIVITY
Escalated to higher department; supervisor will be notified; callback offered; awaiting response.