dorothybelle.oraiz@concentrix.com — Coaching Report

Week of 2026-05-25 – 2026-05-31


At a Glance

Calls HandledAvg Handle TimeTop ProductTop ProblemCases DocumentedCases Escalated
2224m 17sMX4200CONNECTIVITY221

Scorecard

DimensionThis WeekCalls Reviewed
Accuracy2.6022
Protocol1.8022
Communication2.2022
Overall2.4022

Where Time Goes

Product Families

FamilyCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationNote
MX749m 40s2.272.571.571.86Outlier: 2.7x weekly median handle time
WHW636m 30s3.002.001.832.50Outlier: 2.0x weekly median handle time
MBE121m 47s2.802.002.002.00
MR414m 38s1.701.501.252.00
E27m 30s2.253.001.502.00
EA66m 30s2.553.501.831.83

Key Observations

Problem Categories

CategoryCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationFocus Area?
CONNECTIVITY1328m 40s2.302.301.802.20
SETUP725m 2s2.302.401.702.10
ACCESS278m 8s1.501.001.502.00

Week-over-Week Movement

What Went Well

  1. Accurate model identification

> "MX4200 Velop mesh system... solid magenta LED indicates setup mode."

#TE00131348

Consistently identified product models early, enabling targeted troubleshooting.

  1. Professional communication

> "Thank you for calling Linksys. My name is Belle. Is this your first time calling?"

#LTS00130802

Maintained polite, clear introductions and active listening throughout calls.

  1. Effective mesh re-pairing

> "Guided customer to use the Linksys Smart Wi-Fi app to add the node... node displayed solid white LED."

#LTS00081570

Successfully restored mesh connectivity using app-based re-addition for a Velop node.


Growth Opportunities

  1. Correct model-specific procedures

> "Performed 5-press pairing method on the parent node (not supported for Velop WHW/MX/MR nodes per KB)."

#LTS00117148

Next step: Always confirm product model before issuing pairing/reset instructions. For Velop (WHW/MX/MR), use 10-second reset and app-based pairingnever 5-press.

  1. Avoid premature paid support offers

> "Unfortunately, your model is no longer under warranty. But we do offer paid support. Is it okay if I charge $60 for a phone session?"

#LTS00131113

Next step: Verify warranty status via serial number lookup before offering paid support. Exhaust free troubleshooting (reset, diagnostic checks) first.


Next Week's Focus

  1. Model-first troubleshooting: Confirm product model and warranty status in the first 30 seconds of every call.
  2. Reset procedure calibration: Use 10-second hold for Velop (WHW/MX/MR) resets — never 20 seconds or 5-press.
  3. Warranty validation: Cross-check serial numbers against warranty databases before mentioning paid support.
  4. Call control: Reduce silences by preparing next steps while the customer performs actions (e.g., "While you reset, I’ll pull up the KB article").

Technical Accuracy

Improvement

"Provided incorrect reset duration (20 seconds vs. KB-recommended 10 seconds for Velop devices)."

#TE00131348

Materially incorrect reset guidance risks customer error. Always use KB-specified durations: 10 seconds for Velop, 20 seconds for SPNM/E-series.

Improvement

"Incorrectly claimed EA2500 V4 is incompatible with the Linksys app — KB confirms support for legacy Linksys Smart Wi-Fi app."

#LTS00131516

Misinformation undermines trust. Verify app compatibility via KB before stating limitations.

Improvement

"Disabled IPv6 without diagnostic justification, potentially masking the root cause."

#TE00131348

Avoid unilateral configuration changes. Test IPv6 impact in isolation or defer to L2 if uncertain.


Coaching Moments

Strength

"Collected serial number and confirmed out-of-warranty status before processing payment."

#LTS00130802

Clear adherence to payment protocol: warranty check → transparent cost disclosure → informed consent.

Improvement

"Did not verify internet connectivity after node addition; resolution assumed based on LED only."

#LTS00081570

Always validate functional connectivity (ping, speed test) after hardware changes. LED status alone is insufficient.


Escalation Lessons: What L2 Did

#TE00131348 — Resolved by Level 2

What L1 SawWhy it EscalatedWhat L2 DidCurrent StateL1 Learning Points
Customer unable to access own website via MX4200 mesh (works on ISP router). Intermittent hangs/slow loads. L1 performed 20s reset, 5-press pairing (invalid), cleared cache.Incorrect troubleshooting (invalid reset/pairing), no WAN/IPv6 diagnostics, premature escalation.L2 verified IPv6 misconfiguration, adjusted DNS settings, confirmed ISP gateway handoff, validated connectivity via speed test.Resolved — website accessible, speeds restored.1. Gather full topology: WAN type, ISP settings, node count. <br>2. Validate IPv6/DNS: Test nslookup, ping 8.8.8.8. <br>3. Use model-specific resets: 10s hold for MX4200, never 5-press.

Coach Appendix

Internal use only — not for agent distribution.

Weekly Trend:

Actionable Notes:


This Week's Calls

CaseDateScoreDirectionProductCategoryOutcome
#LTS001071152026-05-253.00INBOUNDMR8300CONNECTIVITYCustomer declined path
#LTS001171482026-05-252.80INBOUNDMBE7000CONNECTIVITY✓ Likely resolved
#LTS001307952026-05-253.00INBOUNDWHW03CONNECTIVITY✓ Likely resolved
#LTS001308022026-05-263.00INBOUNDWHW03CONNECTIVITY✓ Resolved
#LTS001309662026-05-263.00INBOUNDE5400CONNECTIVITYCustomer declined path
#LTS000847202026-05-262.80INBOUNDWHW03SETUPClosed with self-help
#LTS000815702026-05-273.00INBOUNDWHW03CONNECTIVITY✓ Likely resolved
#LTS001311132026-05-271.00INBOUNDEA6400CONNECTIVITYAbandoned or vague
#LTS001311132026-05-273.00INBOUNDEA6400CONNECTIVITYAbandoned or vague
#LTS001311312026-05-283.00INBOUNDMX4200CONNECTIVITYCustomer declined path
#LTS001311332026-05-281.10INBOUNDMX8500SETUPAbandoned or vague
#LTS001315142026-05-293.40INBOUNDMX4200SETUP✓ Resolved
#LTS001315122026-05-293.00INBOUNDMX2000SETUPAbandoned or vague
#LTS001315162026-05-301.50INBOUNDE2500CONNECTIVITYAbandoned or vague
#LTS000816222026-05-301.00INBOUNDMX2000SETUPAbandoned or vague
#TE001313482026-05-281.40INBOUNDMX4200ACCESS↑ Escalated
#LTS001314862026-05-293.00INBOUNDWHW03SETUPClosed with self-help