rubierosa.levi@concentrix.com — Coaching Report

Week of 2026-06-01 – 2026-06-07


At a Glance

Calls HandledAvg Handle TimeTop ProductTop ProblemCases DocumentedCases Escalated
924m 50sEA8100CONNECTIVITY9

Scorecard

DimensionThis WeekCalls Reviewed
Accuracy2.119
Protocol1.899
Communication2.339
Overall2.339

Where Time Goes

Product Families

FamilyCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationNote
EA363m 36s1.731.331.331.67Outlier: 2.9x weekly median handle time
RE225m 27s2.803.502.003.00
MR121m 53s
SPN216m 50s3.053.002.002.00
MX18m 58s3.001.003.003.00

Key Observations

Problem Categories

CategoryCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationFocus Area?
CONNECTIVITY417m 30s2.201.751.752.25
SETUP220m 0s2.802.501.502.50
CONFIGURATION124m 43s2.803.002.003.00
GENERAL INQUIRY117m 5s1.101.001.002.00
ACCESS119m 53s3.305.003.002.00

Week-over-Week Movement

What Went Well

Technical guidance on Wi-Fi password re-entry
"Provided correct technical guidance to delete and re-enter Wi-Fi network [08:00]. Confirmed customer’s report of connection and closed call appropriately [19:00]."
#LTS00132376

Growth Opportunities

Incorrect technical guidance on router password recovery
"Inaccurate technical guidance: recovery-key reset is not a valid method for MX4200 Velop routers. This contradicts the KB, which specifies factory reset or app re-pairing for password recovery on Velop devices."
#LTS00131535
Next step: Confirm device model and direct customers to model-specific KB articles before suggesting recovery methods.
Protocol violations and lack of case information collection
"Failed to collect essential product details (model, serial, warranty). Did not follow a logical troubleshooting sequence; jumped between steps."
#LTS00132367
Next step: Systematically gather model, serial, and warranty status at call start, then follow step-by-step KB-guided troubleshooting.

Next Week's Focus

* Practice model-specific password recovery paths for Velop and non-Velop devices before suggesting resets

* Implement a standardized opening script to capture model, serial, and warranty status on all calls

* Use KB articles as primary troubleshooting guides for CONNECTIVITY issues; document steps taken

For unresolved cases, set clear follow-up actions (callback, email resources) before closing


Technical Accuracy

Improvement

Incorrect technical guidance: recovery-key reset is not supported for MX4200 Velop routers. The correct method is factory reset or app re-pairing.

#LTS00131535

Improvement

Provided wrong website URL ('Linksys wi-fi.com') instead of correct domain or status page for service outage. No escalation or self-help path provided.

#LTS00131750

Improvement

Provided incorrect reset instructions ('RESETTER20') for FGW5500 router. No standard troubleshooting protocol followed.

#LTS00094562

Improvement

Misidentified SPNM55 as SPMX55, leading to incorrect assumptions about device compatibility and irrelevant guidance (Verizon modems).

#LTS00131999

Improvement

Provided incorrect IP addresses ([REDACTED_PHONE], [REDACTED_PHONE]) and omitted correct direct UI URL for EA8100 router admin access.

#LTS00132367


Coaching Moments

No additional coaching moments were extracted after the technical review.


Escalation Lessons: What L2 Did

No escalated case learning was available for this report.


Coach Appendix

Highest-signal trend: EA product family calls consume 2.9x weekly median handle time with consistently low accuracy/protocol scores. Recurring pattern of model-specific technical guidance errors (password recovery, reset procedures) and incomplete case information collection. Prioritize model-specific KB adherence and structured information gathering in next coaching session.


This Week's Calls

CaseDateScoreDirectionProductCategoryOutcome
#LTS001315352026-06-013.0INBOUNDMX4200CONNECTIVITY✓ Resolved
#LTS001317492026-06-022.8INBOUNDRE6700CONFIGURATION✓ Likely resolved
#GI001317502026-06-021.1INBOUNDGENERAL INQUIRYNo clear path given
#LTS001317542026-06-022.8INBOUNDRE6400SETUP✓ Likely resolved
#LTS001317552026-06-02INBOUNDMR7350CONNECTIVITY
#LTS000945622026-06-031.0INBOUNDEA8100CONNECTIVITY⏳ Pending
#LTS001319992026-06-032.8INBOUNDSPNMX55SETUPCustomer declined path
#LTS001323672026-06-051.4OUTBOUNDEA8100CONNECTIVITY↻ Callback set
#LTS001323762026-06-053.3INBOUNDSPNM60TBACCESS✓ Resolved