gerlie.miguello@concentrix.com — Coaching Report
Week of 2026-05-25 – 2026-05-31
At a Glance
| Calls Handled | Avg Handle Time | Top Product | Top Problem | Cases Documented | Cases Escalated |
|---|---|---|---|---|---|
| 34 | 19m 53s | MX2000 | CONNECTIVITY | 27 | 4 |
Scorecard
| Dimension | This Week | Calls Reviewed |
|---|---|---|
| Accuracy | 2.00 | 32 |
| Protocol | 1.81 | 32 |
| Communication | 2.13 | 32 |
| Overall | 2.13 | 32 |
Based on 32 calls reviewed. Score range: 1.0–4.0.
This Week's Coverage
Models Supported
| Model | Calls | Avg Score |
|---|---|---|
| MX2000 | 4 | 1.38 |
| WHW03 | 4 | 1.88 |
| MBE7000 | 4 | 2.25 |
| SPNMX55GC | 2 | 1.50 |
| E9450 | 2 | 2.25 |
Key pattern: Lower scores on MX2000 calls suggest a need for deeper familiarity with this model’s mesh behavior and troubleshooting paths.
Problem Categories
| Category | Calls | Avg Score | Focus Area? |
|---|---|---|---|
| CONNECTIVITY | 19 | 2.00 | ✓ |
| SETUP | 5 | 2.00 | ✓ |
| ACCESS | 4 | 1.75 | ✓ |
| CONFIGURATION | 3 | 2.50 |
Connectivity & Setup are the primary focus areas this week, with room for improvement in accuracy and protocol adherence.
What Went Well
Clear, actionable guidance on MX6200 series compatibility
“The MX6202 is compatible as both parent and child node within the MX6200 series. If you purchase a single unit, the MX6201 is the correct model for a standalone setup.”
This concise, KB-aligned advice helped the customer make an informed purchase decision without ambiguity.
Successful node re-pairing on MX6200
“I moved the node close to the parent, performed a 15-second reset until solid blue, and re-added it through the Linksys app. The node now shows solid white with a strong signal.”
The agent followed the exact KB steps for MX6200 reset and pairing, resulting in a confirmed fix.
Growth Opportunities
Verify product model before giving troubleshooting steps
In several calls, the agent provided model-specific guidance without confirming the exact hardware version, leading to incorrect instructions and confusion. For example:
“You must set up a Linksys device as the primary router wired to the modem.”
This advice is not required for WHW01 node addition in a non-Linksys network and contradicts KB guidance. Always confirm the product model and family before recommending steps.
Provide accurate LED interpretation and reset durations
Materially incorrect LED guidance and reset times were given, such as:
“The solid blue light means the node is ready” (for WHW03, solid purple is the ready state)
“Hold the reset button for 15 seconds” (WHW03 requires 10 seconds)
These inaccuracies can mislead customers and delay resolution. Always reference the official LED guide and reset procedures for the specific model.
Next Week's Focus
- Confirm model and family before any troubleshooting — ask for the exact product model and serial number upfront.
- Reference the LED guide for the specific device when discussing status indicators.
- Use model-specific reset times (e.g., 10 seconds for WHW03, 15 seconds for MX series) and verify they match KB.
- Validate fixes by asking the customer to confirm connectivity, signal strength, or successful re-pairing before closing the call.
Technical Accuracy
Improvement — Incorrect technical advice on router admin access
“The router password is the same as the Wi‑Fi password.”
This is factually incorrect and contradicts KB guidance for WHW03.
Improvement — Incorrect compatibility guidance
“MBE7000 is compatible with WHW03 mesh nodes.”
MBE7000 uses 5-press pairing and is not interoperable with WHW03 WPS-based mesh.
Improvement — Incorrect URL provided for router admin access
“Visit support.linkys.com.com to access the router.”
The correct URL is support.linksys.com.
Improvement — Incorrect admin credentials provided for MBE7000
“Use admin/admin to log in.”
The default username for MBE7000 is root, not admin.
Coaching Moments
Improvement — Misleading LED interpretation for WHW03
“Solid blue means the node is ready.”
WHW03 uses solid purple to indicate ready status.
Improvement — Incorrect reset duration for MX series nodes
“Hold the reset button for 15 seconds.”
MX series nodes require a 10-second reset.
Improvement — Incorrect default SSID and password guidance
“The default SSID is ‘_Velop Setup’ and the password is ‘0’.”
Neither is a valid default for MX2000.
Escalation Lessons: What L2 Did
#TE00130750 — Resolved by Level 2
| What L1 saw | Customer reported Wi‑Fi connectivity issues and a purple LED on an MR20X router. L1 misinterpreted the purple LED (Velop‑specific) and offered only paid support after failed payment. |
|---|---|
| Why it escalated | L1 failed to provide any technical troubleshooting, misapplied LED meaning, and did not create a case. |
| What L2 did | L2 clarified the LED state, processed a callback, and attempted to reach the customer to validate connectivity and guide through basic troubleshooting. |
| Current state | Resolved after L2 callback and follow-up. |
| L1 learning points | 1. Validate LED meaning per model (MR series uses solid blue, not purple). 2. Offer self‑help even for out‑of‑warranty devices (e.g., power cycle, WAN check). 3. Document every interaction in HappyFox. |
#TE00130829 — Resolved by Level 2
| What L1 saw | Wired mesh nodes showed as Wi‑Fi connected in the app and exhibited unstable backhaul. L1 gave incorrect pairing instructions and used the wrong IP address. |
|---|---|
| Why it escalated | L1 provided inconsistent technical guidance and failed to confirm the product model before troubleshooting. |
| What L2 did | L2 clarified backhaul detection, guided through correct pairing steps, and confirmed node status via the router UI. |
| Current state | Resolved after L2 re-pairing and validation. |
| L1 learning points | 1. Confirm model before giving model‑specific steps. 2. Use correct IP (myrouter.info or myrouter.local) for router UI access. 3. Validate backhaul via the router UI, not just the app. |
#LTS00131009 — Resolved by Level 2
| What L1 saw | Customer could not access the router UI on an SPNMX42CF node. L1 misidentified the product and gave incorrect URL advice. |
|---|---|
| Why it escalated | L1 failed to follow the proper SPNM reset and pairing procedure and referred the customer to ISP support without resolution. |
| What L2 did | L2 directed the customer to the correct local IP, guided through a full node reset, and confirmed UI access. |
| Current state | Resolved after L2 reset and UI validation. |
| L1 learning points | 1. Use the correct local IP (myrouter.info or [REDACTED_PHONE]) for SPNM series. 2. Follow the 10‑second reset for SPNM nodes. 3. Do not refer to ISP unless the issue is clearly ISP-related. |
#TE00131428 — Resolved by Level 2
| What L1 saw | Main MX2000 node showed solid red after removing the ISP router; child nodes were red/blinking. L1 gave incorrect reset durations and default credentials. |
|---|---|
| Why it escalated | L1 provided wrong technical information and failed to verify WAN connectivity. |
| What L2 did | L2 clarified reset procedures, guided the customer through modem reboot, and confirmed node pairing via the app. |
| Current state | Resolved after L2 modem reboot and node re-pairing. |
| L1 learning points | 1. Use 10‑second reset for MX series nodes, not 15 seconds. 2. Verify WAN link before concluding hardware fault. 3. Never suggest ‘0’ as a password — it’s insecure and incorrect. |
Coach Appendix
This week’s highest-signal trend is the recurring pattern of incorrect technical guidance — especially around LED interpretation, reset durations, and model-specific steps. The agent needs to prioritize model confirmation before troubleshooting and strict adherence to KB-led procedures. Focus in the next coaching session should be on reviewing the LED reference guide, reset procedures by model, and model-specific pairing flows to eliminate contradictions and improve first-call resolution.