joziel.licmoan@concentrix.com — Coaching Report

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


At a Glance

Calls HandledAvg Handle TimeTop ProductTop ProblemCases DocumentedCases Escalated
3217m 3sMX6200CONNECTIVITY323

Scorecard

DimensionThis WeekCalls Reviewed
Accuracy2.3432
Protocol1.7532
Communication2.2532
Overall2.4132

Scores reflect a balanced review of 32 calls. Overall range: 1.3 – 3.5.


This Week's Coverage

Models Supported

ModelCallsAvg Score
MX620082.31
WHW0352.44
EA635022.50
RE635032.00
MR735022.20

Key pattern: Lower scores on MX6200 and RE6350 calls suggest a need for deeper familiarity with mesh troubleshooting flows and extender-specific diagnostics.

Problem Categories

CategoryCallsAvg ScoreFocus Area?
CONNECTIVITY152.20
SETUP132.54
ACCESS22.70
HARDWARE11.40

Connectivity focus: The lower average score (2.20) for connectivity issues points to inconsistencies in LED interpretation, reset procedures, and WAN verification. Prioritize refining these skills to improve outcomes.

Hardware focus: The single hardware call scored low (1.40), indicating a need for clearer escalation paths and more precise model-specific guidance.


What Went Well

Accurate Model Identification

“The model number is the E-A 6-5-0-0-2-2.”
#LTS00130751

You correctly identified the EA6500 model early in the call, which is essential for determining support eligibility and appropriate troubleshooting steps.

Effective Use of App-Based Troubleshooting

“I’m on the app…”
#LTS00130978

When guiding the customer through node pairing on the MX4200, you leveraged the Linksys app to verify node status and confirm resolution—demonstrating strong use of modern tools.

Clear Communication of Next Steps

“All mesh nodes are now online and Wi‑Fi connectivity is restored.”
#LTS00130613

You provided a concise, actionable summary at the end of the call, ensuring the customer understood the outcome and next steps.


Growth Opportunities

Refine Reset Procedures and LED Interpretation

“I performed a 5‑press reset on the parent node…”
#LTS00130613

What to improve:

Next step: Review the universal_mesh_full_rebuild.md KB article and practice the correct reset timing and LED expectations for each model.

Consistent Collection of Serial Numbers and Warranty Status

“Can I have the serial number of the um that's a new child node, right?”
#TE00023348

What to improve:

Next step: Add a quick checklist at the start of each call: model, serial, ISP, and warranty status.


Next Week's Focus

  1. Practice model‑specific reset procedures — memorize the exact duration and LED indicators for MX, WHW, EA, and RE series.
  2. Implement a serial‑number capture routine — ask for it early, verify it, and log it in HappyFox before proceeding.
  3. Refine connectivity diagnostics — ensure WAN/ISP status is confirmed before resetting or re‑configuring nodes.
  4. Use the Linksys app as a primary verification tool — especially for mesh node status and firmware updates.

Technical Accuracy

Improvement

Incorrect reset duration provided for MX6200 model, contradicting KB guidance.
#LTS00130613

The agent instructed a 30‑second reset for MX6200, while the KB specifies ~15 seconds. This can lead to unnecessary stress on the device and confusion for the customer.

Improvement

Agent misinterpreted LED states during node pairing, leading to customer confusion.
#LTS00130763

The agent claimed MX6200 should show steady purple during pairing, but the correct indicator is solid blue. Misinterpreting LEDs can delay resolution and erode trust.

Improvement

Incorrect admin URL provided, leading to failed access attempts.
#LTS00130763

The agent used myrouter.info for MX series, which is invalid. The correct URLs are [REDACTED_PHONE] or myrouter.local.

Improvement

Provided factually inaccurate support lifecycle information, misleading the customer.
#LTS00130946

The agent claimed EA‑2500 support ended in July 2022, which is not documented in KB. This undermines credibility and confuses customers about their support options.

Improvement

Incorrect pairing method advised, contradicting KB guidance for WHW03 model.
#LTS00131329

The agent recommended a 5‑press reset for WHW03, which is unsupported. WHW series requires app‑based pairing or the physical Pair button.


Coaching Moments

Strength

“I was able to pull up a record that that is associated with your phone number.”
#LTS00130613

You efficiently located the customer’s account using their phone number, which helped streamline the support process.

Improvement

“Did the customer run the setup? [Yes - NO] If yes, how did the customer proceeded with setup? [WEB INTERFACE - LINKSYS APP]”
#TE00023348

This line shows a missed opportunity to verify the customer’s setup method and address potential missteps early.

Improvement

“I would like to escalate this case for further troubleshooting per CAT Paolo E approval.”
#TE00131280

While escalation is appropriate, ensure you document all pre‑escalation steps clearly in the ticket to provide context for L2 support.


Escalation Lessons: What L2 Did

#TE00023348 — Resolved by Level 2

AspectDetails
What L1 sawIntermittent internet loss, red LED on MX6200, Wi‑Fi dropping throughout the day.
Why it escalatedIssue persisted after L1 reset and DNS changes; L2 was needed for deeper diagnostics.
What L2 didVerified WAN connectivity, performed a full mesh rebuild, and confirmed firmware consistency across nodes.
Current stateResolved after L2-guided mesh rebuild and firmware sync.
L1 learning points1. Always confirm WAN/ISP status before resetting mesh nodes. <br>2. Use the 5‑press reset only on supported models (e.g., MX6200, not WHW03). <br>3. Document LED states and firmware versions before and after resets.

#TE00131280 — Resolved by Level 2

AspectDetails
What L1 sawUnable to access some websites on EA7450; extender worked fine.
Why it escalatedL1 could not isolate the issue to DNS, firewall, or WAN; L2 expertise was required.
What L2 didRan advanced connectivity tests, adjusted firewall rules, and verified ISP DNS settings.
Current stateResolved after L2‑guided firewall and DNS adjustments.
L1 learning points1. When main Wi‑Fi fails but extender works, check firewall and DNS first. <br>2. Use ipconfig /flushdns and netsh int ip reset on the client device. <br>3. Document all changes made during troubleshooting for L2 handoff.

#TE00131415 — Resolved by Level 2

AspectDetails
What L1 sawRE6350 extender showed “no internet” after reset; laptop couldn’t connect.
Why it escalatedL1 reset instructions were incorrect, and the issue persisted across devices.
What L2 didPerformed a proper 10‑second reset, verified extender LED states, and guided manual setup via extender.linksys.com.
Current stateResolved after correct reset and manual setup.
L1 learning points1. RE6350 requires a 10‑second reset, not 30 seconds. <br>2. Use extender.linksys.com for manual setup, not the main router UI. <br>3. Confirm extender LED is solid green before proceeding.

Coach Appendix

Weekly trend: The most common technical gaps involve reset procedures and LED interpretation, especially for MX and WHW series. These inaccuracies lead to prolonged call times and reduced resolution rates.

Next coaching focus:


This Week's Calls

CaseDateScoreDirectionProductCategoryOutcome
#LTS001307512026‑05‑253.00INBOUNDEA6500CONNECTIVITY✓ Resolved
#LTS001306132026‑05‑253.00INBOUNDMX6200CONNECTIVITY✓ Likely resolved
#LTS001307632026‑05‑251.30INBOUNDMX6200SETUP↑ Escalated
#LTS001308922026‑05‑263.00INBOUNDEA6350CONNECTIVITY✓ Likely resolved
#LTS001309462026‑05‑263.00INBOUNDE2500SETUP✓ Likely resolved
#LTS001309552026‑05‑263.00INBOUNDEA6350CONNECTIVITY✓ Resolved
#LTS001309642026‑05‑263.00INBOUNDWHW03SETUP✓ Likely resolved
#LTS001309782026‑05‑263.00INBOUNDMX4200SETUP✓ Resolved
#LTS001310422026‑05‑273.00INBOUNDMR7500SETUP✓ Likely resolved
#LTS001310542026‑05‑272.80INBOUNDWHW03CONNECTIVITY✓ Resolved
#LTS001310652026‑05‑272.80INBOUNDEA9300SETUPCallback set
#LTS001310702026‑05‑273.00INBOUNDMX6200SETUP✓ Likely resolved
#LTS001310982026‑05‑273.00INBOUNDWHW01SETUP✓ Likely resolved
#LTS001311032026‑05‑273.00INBOUNDMR20MSSETUP✓ Resolved
#LTS000254932026‑05‑281.40INBOUNDMX4200CONNECTIVITYAbandoned
#LTS001312582026‑05‑281.80INBOUNDWHW03SETUPAbandoned
#LTS001312452026‑05‑283.00INBOUNDMX8500CONNECTIVITYPending
#LTS001312172026‑05‑282.80INBOUNDMR7350SETUPCallback set
#LTS001313402026‑05‑282.60INBOUNDMX2000ACCESSPending
#LTS001313292026‑05‑281.80INBOUNDWHW03CONNECTIVITYPending
#LTS001313352026‑05‑281.70INBOUNDVLP01CONNECTIVITYPending
#LTS001313402026‑05‑283.50INBOUNDMX2000ACCESS✓ Resolved
#TE001314152026‑05‑291.70INBOUNDRE6350CONNECTIVITYAbandoned
#TE001314152026‑05‑293.00OUTBOUNDRE6350CONNECTIVITYPending
#LTS001314562026‑05-293.00INBOUNDWHW03SETUPClosed with self-help
#GI001314902026‑05‑291.40INBOUNDMBE7000HARDWAREAbandoned
#LTS001314942026‑05-293.50INBOUNDWHW03CONNECTIVITY✓ Resolved
#LTS001315062026‑05-293.00INBOUNDMX4200CONNECTIVITYCallback set
#LTS001315102026‑05-291.80INBOUNDMR20MSSETUPCallback set