joziel.licmoan@concentrix.com — Coaching Report

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


At a Glance

Calls HandledAvg Handle TimeTop ProductTop ProblemCases DocumentedCases Escalated
3419m 16sMR7350CONNECTIVITY341

Scorecard

DimensionThis WeekCalls Reviewed
Accuracy2.7034
Protocol2.2034
Communication2.6034
Overall2.7034

Where Time Goes

Product Families

FamilyCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationNote
WRT173m 1s2.801.002.002.00Outlier: 4.7x weekly median handle time
MX627m 40s2.502.672.172.83Outlier: 1.8x weekly median handle time
WHW427m 8s3.003.502.252.25Outlier: 1.7x weekly median handle time
LN120m 35s2.204.002.002.00
MR615m 38s2.702.332.332.50
EA715m 4s2.542.711.862.57
E614m 7s2.753.171.832.50
OTHER49m 12s2.953.252.253.00
RE13m 57s1.601.001.002.00

Key Observations

Problem Categories

CategoryCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationFocus Area?
CONNECTIVITY1422m 9s2.602.902.202.60
ACCESS613m 22s2.702.301.802.70
SETUP922m 27s2.602.402.202.60
NO TROUBLESHOOTING NEEDED312m 47s3.003.702.302.70

Week-over-Week Movement

What Went Well

  1. Accurate Model Identification

> “WUSB6300… Windows 10 64-bit…”

> Correctly identified the product model from the serial number and confirmed the need for a 64-bit driver.

#LTS00131717

  1. Effective Mesh Recovery Guidance

> “All nodes now solid blue and internet works; monitor the node with -72 dBm signal…”

> Guided the customer through full factory resets, password recovery, and signal-strength validation, restoring connectivity.

#LTS00132274


Growth Opportunities

  1. Correct Reset Procedures

> “Hold the reset button for 30 seconds…”

> Incorrectly advised 30-second resets for WHW03, EA7300, and VLP01 (KB specifies 10–15 seconds). This caused unnecessary delays and confusion.

#LTS00074179

Next Step: Use KB-defined reset durations (e.g., 10 seconds for WHW03, 15 seconds for EA series) and verify LED behavior post-reset.

  1. Warranty Verification Before Troubleshooting

> “This node is actually one of our first generation router…”

> Assumed out-of-warranty status without lookup, risking non-compliance when offering paid support or advanced troubleshooting.

#LTS00132483

Next Step: Perform warranty checks via serial number before proceeding with diagnostics or quoting paid support.


Next Week's Focus


Technical Accuracy

Improvement

Incorrectly stated that Wi-Fi password and router admin password are the same for MR7350, contradicting KB guidance.

#LTS00086970

Improvement

Incorrectly claimed Linksys Smart Wi-Fi cloud service and myrouter.info are discontinued for WHW03, contradicting KB.

#LTS00074179

Improvement

Falsely claimed firmware updates cost $15 for MX2000, violating accuracy and compliance policies.

#LTS00101564

Improvement

Incorrectly stated that the Linksys app is discontinued for MR8300, contradicting KB.

#LTS00132051

Improvement

Provided a fictional model number ‘M4X4X Ray 6220’ instead of MX6200.

#LTS00132051

Improvement

Introduced fabricated technical concepts (‘device manager’, ‘communicator files’) with no basis in KB.

#LTS00132483


Coaching Moments

No additional coaching moments were extracted after the technical review.


Escalation Lessons: What L2 Did

#TE00132427 — Pending with Level 2

What L1 SawWhy it EscalatedRelated Call ChainWhat L2 DidCurrent StateL1 Learning Points
MR7500 mesh node flashing blue, SSID not broadcasting. Customer (IT professional) insisted on immediate replacement.Customer demanded expedited RMA without isolation; L1 unable to verify defect or warranty status.Previous L1 call (joziel) closed with callback promise; L2 claimed ticket from TE queue.L2 attempted callback, left message, and requested receipt via email. No technical diagnosis performed.Pending customer response for receipt; no resolution yet.1. Collect serial number, proof of purchase, and warranty status before escalation.<br>2. Guide customer through isolation steps (e.g., bypass test, WAN check).<br>3. Document clear next steps and avoid vague “callback promised” closures.

Coach Appendix

High-signal trend: Inconsistent reset procedures and warranty verification dominate accuracy gaps. Focus next coaching on KB-aligned reset durations (10–15 seconds) and mandatory serial-based warranty checks before troubleshooting or escalation. Avoid fabricated terms; rely strictly on KB.


This Week's Calls

CaseDateScoreDirectionProductCategoryOutcome
#LTS000869702026-06-01 18:042.80INBOUNDMR7350ACCESS✓ Likely resolved
#LTS000741792026-06-01 18:572.80INBOUNDWHW03ACCESS✓ Likely resolved
#LTS001316792026-06-01 19:262.90INBOUNDEA7450CONNECTIVITY✓ Likely resolved
#LTS001317022026-06-01 20:353.00INBOUNDEA8100CONNECTIVITY✓ Likely resolved
#LTS001316272026-06-01 21:302.90INBOUNDE1200ACCESS✓ Likely resolved
#LTS001317172026-06-01 22:104.10INBOUNDWUSB6300NO TROUBLESHOOTING NEEDED✓ Resolved
#LTS001317262026-06-01 22:363.20INBOUNDE2500CONNECTIVITY✓ Likely resolved
#LTS001015642026-06-02 16:441.80INBOUNDMX2000CONNECTIVITY⏳ Pending
#LTS001221992026-06-02 17:483.00INBOUNDMX6200CONNECTIVITY✓ Resolved
#LTS001321002026-06-02 19:562.80INBOUNDMR7350SETUP✓ Resolved
#LTS001315682026-06-02 19:592.20INBOUNDLN3111NO TROUBLESHOOTING NEEDED↻ Callback set
#LTS001319102026-06-02 21:052.80INBOUNDEA7300CONNECTIVITY✓ Likely resolved
#LTS001320362026-06-03 15:433.90INBOUNDWUSB6300NO TROUBLESHOOTING NEEDED✓ Resolved
#LTS001320512026-06-03 16:301.80INBOUNDMR8300ACCESS✓ Likely resolved
#LTS001320692026-06-03 17:062.80INBOUNDE5400CONNECTIVITY✓ Resolved
#LTS001320792026-06-03 17:412.80INBOUNDEA6700CONNECTIVITY✓ Likely resolved
#LTS001320932026-06-03 18:503.00INBOUNDWHW03ACCESS✓ Likely resolved
#LTS001321002026-06-03 19:113.30INBOUNDMR7350SETUP✓ Resolved
#LTS001321262026-06-03 21:161.80INBOUNDMX2000SETUP⏳ Pending
#LTS001321262026-06-03 21:451.60INBOUNDMX2000SETUP
#LTS001322612026-06-04 16:071.80INBOUNDEA7200ACCESS⏳ Pending
#LTS001322652026-06-04 16:293.20INBOUNDMR8300CONNECTIVITY✓ Likely resolved
#LTS001322742026-06-04 16:533.30INBOUNDWHW03CONNECTIVITY✓ Resolved
#LTS001322852026-06-04 17:542.00INBOUNDVLP01SETUP⏳ Pending
#LTS001322992026-06-04 19:021.60INBOUNDRE6300SETUP↻ Callback set
#LTS001323062026-06-04 19:262.80INBOUNDE2500SETUP✓ Likely resolved
#LTS001323182026-06-04 20:391.80INBOUNDVLP01SETUP⏳ Pending
#LTS001323252026-06-04 21:412.80INBOUNDE5400CONNECTIVITY✓ Resolved
#LTS001323282026-06-04 22:102.90INBOUNDWHW03CONNECTIVITY✓ Likely resolved
#TE001324272026-06-05 16:002.60INBOUNDMR7500CONNECTIVITY↑ Escalated
#LTS001324412026-06-05 17:361.80INBOUNDE5350CONNECTIVITY↻ Callback set
#LTS001324592026-06-05 19:312.80INBOUNDWRT54G2CONNECTIVITY✓ Resolved
#LTS000443332026-06-05 20:503.80INBOUNDMX6200SETUP✓ Resolved
#LTS001324832026-06-05 21:331.40INBOUNDEA8300SETUP