girlyjoy.pocot@concentrix.com — Coaching Report

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

At a Glance

Scorecard

Where Time Goes

Product Families

Key Observations

• EA is the slowest family at 24m 23s; outlier: 2.5x weekly median handle time.
• MX is the slowest family at 16m 35s; outlier: 1.7x weekly median handle time.

Problem Categories

Week-over-Week Movement

• Improve protocol adherence: Collect model/serial number and verify warranty status in every call.
• Correct technical guidance: Ensure reset durations, pairing methods, and URLs align with KB for specific models.
• Reduce PCI compliance risks: Never collect full credit card details over unsecured phone lines.
• Enhance troubleshooting: Provide accurate, model-specific guidance and verify resolution before ending calls.

What Went Well

1. Accurate Model-Specific Guidance for Cognitive Mesh

> "For WHW03, hold the reset button for 10 seconds until the LED turns solid purple, then pair using the 5-press method on the parent node."

#LTS00132077

1. Persistence and Adaptability Leading to Resolution

> "Switched to Microsoft Edge after Chrome failed, cleared cache, and retested the direct URL—customer regained access to the admin UI."

#LTS00132316

Growth Opportunities

1. Incorrect Technical Guidance on Reset Procedures

> "For RE6300, press and hold the reset button for 30 seconds." (Correct duration: 10 seconds)

#LTS00132224

Next Step: Always verify reset durations against KB before instructing customers. Use 10 seconds for RE6300/SPNM series.

1. Failure to Collect Essential Device Details

> "Proceeded with troubleshooting without confirming the model or serial number."

#LTS00131694

Next Step: Capture model, serial number, and warranty status in every call to enable accurate, model-specific support.

Next Week's Focus

• Standardize Device Identification: Begin every call by confirming model, serial number, and warranty status.
• Validate Reset Durations: Cross-check KB for reset times before instructing customers (e.g., 10s for RE6300, 15s for E1200).
• Prioritize Protocol Adherence: Follow documented troubleshooting sequences step-by-step to improve protocol scores.
• Reduce PCI Risks: Never collect full credit card details over unsecured phone lines.

Technical Accuracy

Improvement

• Provided incorrect default admin password (admin/1234) for E1200 — correct default is admin/admin.

#LTS00127328

Improvement

• Collected full credit card details (number, expiry, CVV) over unsecured phone line — severe PCI compliance violation.

#TE00131644

Improvement

5-press calibration: WHW03 and MX5500 can support 5-press pairing/recovery in supported child-node contexts. Do not coach this as unsupported solely because the product is Velop, WHW, MX, or MR; treat it as an error only when the evidence shows the method was wrong for the model/state, described as a factory reset by itself, failed without a pivot, or contradicted KB guidance.

#LTS00131694

Improvement

• Incorrectly stated that Linksys Smart Wi-Fi website is discontinued and email/password login is no longer possible.

#LTS00131863

Improvement

• Incorrect reset duration (30 seconds instead of 10 seconds) for RE6300 extender.

#LTS00132224

Strength

• Provided the exact KB-recommended direct UI URL workaround for MX8500 admin access issue, leading to resolution.

#LTS00132316

Improvement

• Provided incorrect URL 'myrouter.loco' instead of myrouter.local or [REDACTED_PHONE], causing customer confusion.

#LTS00132415

Escalation Lessons: What L2 Did

#TE00131644 — Resolved by Level 2

• What L1 Saw: Customer reset EA8300, couldn’t access admin page or Wi-Fi (orange LED). L1 provided conflicting reset instructions, collected credit card details insecurely, and escalated after failed troubleshooting.
• Why It Escalated: L1 gave incorrect URLs (myrouter.info, linxys02812.com), assumed Ethernet port existed despite USB-only connectivity, and failed to verify basic connectivity.
• What L2 Did:

1. Confirmed device was out of warranty and offered paid support.

2. Guided customer through factory reset (15s hold), incognito mode, and direct URL access.

3. Validated resolution by confirming solid blue LED and admin page access.

• Current State: Resolved.
• L1 Learning Points:

1. Verify model and ports before troubleshooting (EA8300 lacks Ethernet).

2. Use correct URLs (myrouter.local or [REDACTED_PHONE]).

3. Never collect payment details over unsecured lines.

#LTS00132316 — Resolved by Level 2

• What L1 Saw: MX8500 customer saw blue screen on smartgateway.com, couldn’t access admin UI. L1 provided incorrect URL (myrouter.cal) and failed to collect serial number.
• Why It Escalated: L1 didn’t attempt standard recovery steps (factory reset, cache clear) and gave invalid domain.
• What L2 Did:

1. Instructed power-cycle of modem/router.

2. Provided direct URL workaround ([REDACTED_PHONE]/ui/local/dynamic/index.html).

3. Guided customer through Microsoft Edge incognito mode, which succeeded.

• Current State: Resolved.
• L1 Learning Points:

1. Always attempt factory reset before escalating complex UI issues.

2. Use model-specific URLs (MX series: [REDACTED_PHONE]/ui/local/dynamic/index.html).

3. Capture serial number early to enable warranty checks and accurate guidance.

This Week's Calls