girlyjoy.pocot@concentrix.com — Coaching Report

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

At a Glance

Scorecard

Scores reflect 25 calls reviewed. Overall scores ranged from 1.3 to 4.4.

This Week's Coverage

Models Supported

Key pattern: Lower scores on WHW03 calls suggest a need for deeper familiarity with Velop setup flows and troubleshooting nuances specific to this model line.

Problem Categories

Connectivity focus area: The lower average score (2.1) for connectivity issues indicates a need to refine diagnostic steps and technical accuracy for internet/WAN related problems. Pay special attention to modem status checks, LED interpretation, and systematic isolation of ISP vs. device issues.

What Went Well

Strength: Accurate mesh node pairing guidance

Correctly guided 5-press pairing method for MX6200 (KB-compliant).

This demonstrates solid knowledge of mesh pairing procedures for Cognitive Mesh devices. The customer was able to restore the missing 2.4 GHz network and pair a child node successfully.

#LTS00098076

Strength: Effective Wi‑Fi band separation

Successfully guided customer through separating 2.4 GHz and 5 GHz SSIDs on MX2000 via web UI.

The agent provided clear, step‑by‑step instructions that enabled the customer to resolve their issue and achieve the desired network configuration.

#LTS00037460

Growth Opportunities

Improvement: Factory reset duration accuracy

Provided materially wrong factory reset instruction (30 seconds instead of 10–15 seconds) for EA7430 model.

What “good” looks like: Always verify reset durations against the current KB for the specific model. For EA7430, the correct duration is 10–15 seconds. When in doubt, default to the KB-specified time and confirm with the customer before proceeding.

#LTS00130746

Improvement: Product compatibility validation

Incorrectly advised that VLP01 nodes are compatible with MX5500 system, despite known cross-generation incompatibility.

What “good” looks like: Before confirming node compatibility, always cross-reference the official compatibility matrix or KB articles. When uncertain, escalate to a technical specialist or provide a disclaimer that the advice is provisional and should be verified with the customer.

#LTS00124287

Next Week's Focus

1. Double-check reset durations — Before instructing any factory reset, pull the exact duration from the KB for the specific model and confirm it with the customer.
2. Verify node compatibility — Use the official compatibility matrix or escalate when unsure; never assume cross-generation compatibility.
3. Collect model and serial number — Make this a non-negotiable first step in every call to enable accurate troubleshooting and warranty checks.
4. Validate resolution — After guiding a customer through troubleshooting, always confirm that the issue is truly resolved (e.g., test connectivity, verify LED states, or have the customer confirm functionality).

Technical Accuracy

Improvement

Provided factually incorrect 5-press pairing method for Velop system that uses app-based node addition.

This guidance was not applicable to the customer’s WHW03 Velop system, which relies on app-based pairing rather than physical button presses. Correct pairing for Velop requires using the Linksys app to add nodes.

#TE00130787

Improvement

Incorrect factory reset duration (30 seconds instead of 10–15 seconds) for EA7430 model.

Specifying an incorrect reset time risks an incomplete factory reset, leaving the customer with unresolved issues. The KB clearly states 10–15 seconds for EA7430 series devices.

#TE00130963

Strength

Correctly instructed hard reset procedure for MX6200: hold reset until LED off, then wait for solid blue (per KB Section B).

This step-by-step guidance aligned with documented KB procedures and successfully restored mesh functionality for the customer.

#LTS00130895

Improvement

Incorrect LED guidance for WHW03 model setup.

Providing inaccurate LED color interpretations (e.g., referencing “solid purple/hot pink”) can mislead customers and hinder proper setup. WHW03 LEDs follow standard Velop patterns (solid blue = ready, blinking white = pairing, solid white = online).

#LTS00130911

Improvement

Incorrect URL provided during troubleshooting for E8450 model.

Supplying a non-existent support URL (support.lynxus.com) creates confusion and undermines trust. Always use verified Linksys domains (e.g., myrouter.local, linksyssmartwifi.com, or the appropriate web UI address).

#LTS00131420

Coaching Moments

Improvement

Did not verify the exact Velop model before giving pairing instructions.

The agent instructed a 15-second reset on the child node, which may have factory reset it unnecessarily. Additionally, warranty verification was blocked by an unrealistic request for a receipt screenshot, preventing progress.

#TE00130787

Strength

Collected the main router serial number early in the call.

This shows awareness of protocol, though the agent did not follow through with full data collection or model verification.

#TE00130787

Improvement

Excessive focus on receipt screenshot for warranty despite no impact on immediate troubleshooting.

Requesting a receipt screenshot before any technical steps created a barrier the customer could not overcome, delaying resolution.

#TE00130787

Improvement

Failed to confirm internet connectivity or WAN status despite main router showing solid red light.

The solid red light indicated a WAN/internet loss, which should have been diagnosed before attempting node pairing.

#TE00130787

Escalation Lessons: What L2 Did

#TE00130787 — Resolved by Level 2

What L1 saw:

Customer wanted to add a new Velop node to an existing WHW03 system. The main router showed a solid red light (WAN/internet loss), and the customer experienced app login issues and inconsistent node lighting (blue flashing, then pink/red mix).

Why it escalated:

The case exceeded the L1 support threshold and was beyond the agent’s shift hours. L1 was unable to resolve the WAN issue or successfully guide node addition due to incorrect pairing instructions and an unresolved red-light internet outage.

What L2 did:

L2 confirmed the WAN issue, guided a full factory reset of the main router, and reconfigured the mesh system using the Linksys app. They verified internet connectivity, re-added the child node via the app, and ensured all nodes showed solid white LEDs. L2 also provided detailed steps for future troubleshooting and confirmed the customer’s understanding.

Current state: Resolved — internet restored, mesh nodes fully functional.

L1 learning points:

1. Check WAN/Internet status first: Always verify the main router’s WAN LED and internet connectivity before attempting mesh node setup. A solid red light indicates a WAN issue that must be resolved first.
2. Use app-based pairing for Velop: Velop systems (WHW03) use app-based node addition; avoid instructing physical button resets unless explicitly required by the model and KB.
3. Collect model and serial number early: This enables targeted troubleshooting and accurate warranty checks.

#TE00130963 — Resolved by Level 2

What L1 saw:

Customer reported selective connectivity issues — specific apps (Walmart, Amazon) and Roku TV were unable to access the internet (error: “No Internet”), while other apps and general browsing were working normally. The customer had an EA7430 router, and the agent attempted basic troubleshooting but failed to resolve the issue.

Why it escalated:

The issue was complex and required advanced diagnostics beyond L1 capabilities, such as firmware re-flash and deep packet inspection. L1 also failed to gather sufficient technical data (e.g., firmware version, modem logs) to proceed effectively.

What L2 did:

L2 performed advanced troubleshooting, including firmware re-flash, DNS configuration checks, and ISP coordination. They identified a misconfigured DNS setting that was blocking specific domains and corrected it. L2 also verified that the router’s firmware was up to date and guided the customer through additional tests to ensure stability.

Current state: Resolved — internet connectivity restored for all applications.

L1 learning points:

1. Gather detailed technical data: Collect firmware version, modem logs, and ISP settings early to enable effective troubleshooting.
2. Check DNS settings: For selective connectivity issues, verify DNS configuration as a common root cause.
3. Escalate early when needed: If basic troubleshooting fails and the issue requires advanced diagnostics, escalate promptly to L2 with all relevant information.

Coach Appendix

Weekly trend: The most significant technical gap this week was inaccurate technical instructions, particularly around factory reset durations and mesh node pairing methods. These errors led to unresolved issues and unnecessary escalations. Moving forward, focus on verifying KB guidance for model-specific procedures and systematically collecting model/serial information before providing troubleshooting steps.

Key pattern to address in next coaching: Consistently missing model and serial number collection in calls, which hinders accurate support and warranty determination. This should be a non-negotiable first step in every interaction.

This Week's Calls