girlyjoy.pocot@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 |
|---|---|---|---|---|---|
| 25 | 14m 31s | WHW03 | CONNECTIVITY | 25 | 2 |
Scorecard
| Dimension | This Week | Calls Reviewed |
|---|---|---|
| Accuracy | 2.30 | 25 |
| Protocol | 1.70 | 25 |
| Communication | 2.40 | 25 |
| Overall | 2.30 | 25 |
Scores reflect a small sample size (25 calls). Overall performance trends are visible but individual call variability remains high.
This Week's Coverage
Models Supported
| Model | Calls | Avg Score |
|---|---|---|
| WHW03 | 7 | 2.20 |
| MX6200 | 3 | 3.30 |
| EA7430 | 2 | 1.60 |
| EA8100 | 2 | 1.70 |
Key pattern: Lower scores on WHW03 and EA7430 calls suggest a need for deeper familiarity with these models’ setup and troubleshooting flows.
Problem Categories
| Category | Calls | Avg Score | Focus Area? |
|---|---|---|---|
| CONNECTIVITY | 12 | 2.20 | ✓ |
| SETUP | 9 | 2.50 | ✓ |
| ACCESS | 3 | 3.10 | |
| CONFIGURATION | 1 | 2.90 |
Focus areas — CONNECTIVITY and SETUP: These categories show the greatest opportunity for improvement. Common issues include WAN LED misinterpretation, incomplete factory reset instructions, and insufficient validation of mesh node pairing.
What Went Well
Accurate 5-press pairing guidance for MX6200
Correctly guided 5-press pairing method for MX6200 (KB-compliant).
#LTS00098076
This call demonstrates solid technical knowledge of mesh pairing procedures for MX6200 devices, a key strength this week.
Effective reset and recovery-key procedure
Provided accurate reset and recovery-key procedure fully aligned with the KB.
#LTS00131211
The agent delivered a textbook example of guiding a customer through a factory reset and recovery-key usage, ensuring the customer could regain access to the router’s admin interface.
Growth Opportunities
Incorrect factory reset instructions
Provided factually incorrect factory reset duration (30 seconds instead of 10–15 seconds) for AC7300 series, contradicting KB.
#LTS00130746
What “good” looks like:
- Always verify reset durations against the device-specific KB before instructing customers.
- For AC7300 series, the correct reset duration is 10–15 seconds, not 30 seconds.
- Confirm the reset was successful by checking LED behavior (solid blue/purple for ready state).
Failure to collect product model/serial
Failed to collect product model and serial number despite relevance to warranty and support pathing.
#LTS00130714, #TE00130963
What “good” looks like:
- Treat model/serial collection as a non-negotiable first step in every hardware support call.
- Use these details to verify warranty eligibility, guide troubleshooting, and create accurate HappyFox cases.
- Document the information in the case notes for future reference.
Next Week's Focus
- Standardize reset instructions – Create a quick reference sheet for common reset durations by model (e.g., AC7300: 10–15 sec, WHW03: 15 sec) and keep it handy during calls.
- Model/serial collection habit – Add a visible reminder in your script or CRM to ask for model and serial number within the first 30 seconds of every call.
- Validate mesh node pairing – After guiding a reset or pairing step, always ask the customer to confirm LED states and app visibility, then verify internet connectivity with a simple speed test or web browse.
- Reduce premature escalation – Before suggesting paid support, run through a quick checklist: power cycle modem/router, check WAN LED, verify cable connections, and confirm basic internet access from another device.
Technical Accuracy
Improvement
Provided factually incorrect 5-press pairing method for Velop system that uses app-based node addition.
#TE00130787
The agent mistakenly instructed a 5-press reset/pairing method for a Velop system, which relies on app-based node addition. This can lead to unnecessary factory resets and confusion.
Improvement
Provided materially wrong factory reset instruction (30 seconds instead of 10–15 seconds) for AC7300 series.
#LTS00130746
Specifying an incorrect reset duration risks incomplete resets and repeated customer frustration.
Improvement
Provided incorrect LED color state (solid purple/hot pink) for mesh node reset status, contradicting KB.
#LTS00130911
LED color guidance must align with documented norms; “solid purple/hot pink” is not a valid state for Linksys mesh nodes.
Improvement
Incorrectly advised VLP01 nodes are compatible with MX5500 system, despite known cross-generation incompatibility.
#LTS00124287
Cross-generation mesh node compatibility is strictly limited; advising otherwise can lead to hardware mismatches and failed setups.
Improvement
Provided non-existent URL 'support.lynxus.com' which does not resolve and is not a Linksys domain.
#LTS00131420
Using invalid support URLs undermines credibility and directs customers to dead ends.
Coaching Moments
Improvement
Did not verify the exact Velop model before giving pairing instructions.
Instructed 15-second reset on child node, which may have factory reset it unnecessarily and without warning.
Requested a receipt screenshot for warranty verification before any troubleshooting, creating a blocker the customer could not overcome.
Failed to confirm internet connectivity or WAN status despite main router showing solid red light.
#TE00130787
Improvement
Incorrectly claimed out-of-warranty status disqualifies customer from technical support; policy allows basic troubleshooting even for out-of-warranty devices.
Provided materially wrong factory reset instruction (30 seconds instead of 10–15 seconds) for AC7300 series, contradicting KB.
Failed to perform standard Level 1 troubleshooting: no power-cycle of modem, no verification of WAN LED, no cable check.
Abandoned call by refusing to assist further after warranty declaration, leaving customer with no actionable path.
#LTS00130746
Improvement
Advised full factory reset of both mesh nodes by holding reset until light turns off.
Later instructed to hold reset for 15 seconds.
Told customer to wait for solid purple/hot-pink LED before setup.
Mentioned 5-press reset/pairing method for main node.
#LTS00130911
Improvement
Customer decided to order VLP01 nodes based on agent's incorrect advice.
#LTS00124287
Improvement
Failed to collect or confirm the router model number before giving instructions; model was only revealed at [27:00] when UI loaded.
Did not verify the WAN LED status or physical Ethernet connection early in troubleshooting, a fundamental step for internet-WAN issues.
Repeated the same access instructions without adapting when the customer reported DNS errors, leading to looping.
#LTS00131420
Escalation Lessons: What L2 Did
#TE00130787 — Resolved by Level 2
| What L1 saw | Why it escalated | What L2 did | Current state | L1 learning points |
|---|---|---|---|---|
| Customer wanted to add a new Velop node; app login issues; node lights not progressing; main router red and no internet. | L1 provided incorrect 5-press pairing instructions for a Velop system that uses app-based setup, focused on warranty verification via receipt screenshot (which the customer could not provide), and failed to address the main router’s solid red light indicating WAN/internet loss. | L2 performed a callback, verified internet connectivity, guided a proper factory reset of the main router, and used the Linksys app to add the new node. Confirmed LED states and app visibility. | Resolved – node added, internet restored. | 1. Verify exact Velop model before giving pairing instructions. <br>2. Diagnose WAN/internet loss (solid red LED) before attempting node pairing. <br>3. Avoid making warranty verification a blocker before basic troubleshooting. |
| Related call chain – This was a repeat contact after an earlier closure with vague next steps. L2 had to restart diagnostics from scratch. |
#TE00130963 — Resolved by Level 2
| What L1 saw | Why it escalated | What L2 did | Current state | L1 learning points |
|---|---|---|---|---|
| Customer reported selective connectivity issue — specific applications (Walmart, Amazon) and Roku TV were unable to access the internet while other apps and general browsing worked normally. | L1 performed minimal troubleshooting (power cycled router, checked default Wi‑Fi credentials) but did not verify WAN status, skipped modem power cycle, and prematurely offered paid support. | L2 instructed a full power cycle of modem and router, verified WAN LED, guided through DNS flush and browser cache clearance, and confirmed resolution via speed test. | Resolved – all apps now functional. | 1. Always verify WAN connectivity (modem LED, WAN LED) before troubleshooting application-specific issues. <br>2. Perform a full power cycle of both modem and router for connectivity problems. <br>3. Use DNS flush and browser cache clearance as standard steps for selective app failures. |
| Related call chain – Multiple L1 attempts resulted in abandoned or vague closures; L2 provided structured troubleshooting and validation. |
Coach Appendix
Weekly trend: The agent’s strongest performances centered on accurate mesh pairing and reset/recovery procedures, but recurring gaps in model/serial collection, reset duration accuracy, and WAN validation persist. Focus next week on tightening protocol adherence for these high-impact areas to boost overall scores and reduce escalations.
This Week's Calls
| Case | Date | Score | Direction | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00130714 | 2026-05-25 13:32:40+00:00 | 1.7 | INBOUND | EA6350 | ACCESS | Customer to try uninstall/reinstall the app; no further action taken by agent. |
| #LTS00130746 | 2026-05-25 16:12:18+00:00 | 1.6 | INBOUND | EA7300 | CONNECTIVITY | Agent refused further support due to warranty status, offered to email setup instructions, and suggested paid support. No resolution achieved. |
| #LTS00098076 | 2026-05-25 20:53:30+00:00 | 3.4 | INBOUND | MX6200 | CONNECTIVITY | 2.4 GHz network restored and child node paired; customer can now connect devices. |
| #TE00130787 | 2026-05-25 21:37:52+00:00 | 1.8 | INBOUND | WHW03 | SETUP | Escalated to Level 2; callback scheduled. |
| #LTS00130862 | 2026-05-26 13:42:23+00:00 | 1.8 | INBOUND | EA8100 | CONNECTIVITY | Agent will email setup instructions; customer to perform another factory reset and reconfigure router. No confirmation of resolution or follow-up scheduled. |
| #LTS00130895 | 2026-05-26 16:04:54+00:00 | 3.5 | INBOUND | MX6200 | CONNECTIVITY | Node LED is solid white; advise to relocate to intended position and verify Wi‑Fi connectivity. Recommend follow-up if issues persist. |
| #LTS00130895 | 2026-05-26 16:25:12+00:00 | 1.5 | INBOUND | MX6200 | CONNECTIVITY | Agent falsely claimed prior agent resolved the issue; no resolution or next step provided. |
| #LTS00130911 | 2026-05-26 17:26:02+00:00 | 1.8 | INBOUND | WHW01 | SETUP | Agent offered to email generic setup instructions; no live verification of pairing or connectivity performed. Customer left to self-resolve. |
| #LTS00124287 | 2026-05-26 18:57:23+00:00 | 1.5 | INBOUND | MX5500 | CONNECTIVITY | Customer decided to order VLP01 nodes based on agent's incorrect advice. |
| #TE00130963 | 2026-05-26 20:46:57+00:00 | 1.6 | INBOUND | EA7430 | CONNECTIVITY | Agent instructed customer to perform a factory reset (30-second press) and offered to send email instructions; no verification, no follow-up scheduled, no case created. |
| #LTS00101153 | 2026-05-26 21:44:20+00:00 | 3.0 | INBOUND | WHW03 | CONNECTIVITY | Nodes showed solid blue and new SSID was visible, but connection stability was inconsistent. Customer reported temporary success but signal fluctuations and node reconnection issues. No further escalation or follow-up scheduled. |
| #LTS00131211 | 2026-05-28 12:58:08+00:00 | 3.5 | INBOUND | WHW03 | ACCESS | Customer will reset the router using the recovery key and then log into the app with the newly created admin password. |
| #LTS00131215 | 2026-05-28 13:10:21+00:00 | 2.8 | INBOUND | EA8300 | SETUP | Use the local web interface at http://192.168.1.1 to finish router setup. No verification was performed. |
| #LTS00131217 | 2026-05-28 13:13:39+00:00 | 3.4 | INBOUND | MR7350 | SETUP | Customer will connect to the router’s default Wi‑Fi network, access http://myrouter.local in a browser, and follow the on-screen setup wizard. Agent will email additional guidance. |
| #LTS00131238 | 2026-05-28 15:04:53+00:00 | 3.0 | INBOUND | E2500 | CONNECTIVITY | Agent claimed to send reset instructions via email to unconfirmed address; no verification of fix or next steps established. |
| #LTS00130463 | 2026-05-28 16:06:10+00:00 | 3.0 | INBOUND | SPNM60CF | SETUP | All LEDs are now solid white; network appears functional. |
| #LTS00131278 | 2026-05-28 17:41:28+00:00 | 1.3 | INBOUND | WHW03 | SETUP | No resolution achieved. Call ended without clear next steps or follow-up plan. |
| #LTS00131278 | 2026-05-29 19:56:49+00:00 | 1.8 | INBOUND | WHW03 | SETUP | No payment captured; customer advised to call back later. No clear next step or alternative provided. |
| #LTS00131299 | 2026-05-28 19:39:19+00:00 | 2.9 | INBOUND | WHW03 | CONFIGURATION | Agent sent email with KB article titled 'How to log into Linux mesh router surface' (likely typo for 'Linksys') and instructions to access myrouter.local to rename network. Advised to bypass browser security warning and try alternate browsers if needed. |
| #LTS00131306 | 2026-05-28 19:56:41+00:00 | 3.0 | INBOUND | EA7200 | ACCESS | Customer to perform the hard reset and follow the emailed instructions to set a new admin password. |
| #LTS00131324 | 2026-05-28 21:17:29+00:00 | 2.8 | INBOUND | LN11011202 | SETUP | All mesh nodes re‑added and internet works on laptop; advise customer to contact ISP regarding the blocked website. |
| #LTS00069740 | 2026-05-29 12:40:49+00:00 | 1.3 | INBOUND | E1000 | SETUP | Advised customer to purchase a new MR5500 router; no further troubleshooting. |
| #LTS00131420 | 2026-05-29 15:46:50+00:00 | 1.5 | INBOUND | E8450 | SETUP | Customer advised to contact ISP for WAN provisioning; no technical fix confirmed. |
| #LTS00131431 | 2026-05-29 16:28:33+00:00 | 3.0 | INBOUND | WHW03 | SETUP | Customer to perform factory reset of all nodes and re‑configure using default credentials; detailed email instructions to be sent. |
| #LTS00037460 | 2026-05-29 17:09:27+00:00 | 4.4 | INBOUND | MX2000 | SETUP | Separate 2.4 GHz and 5 GHz SSIDs created; customer confirmed both networks are visible. |
| #LTS00131452 | 2026-05-29 17:29:13+00:00 | 3.0 | INBOUND | MR9600 | CONNECTIVITY | Offered to email detailed troubleshooting steps or provide paid support; no technical fix confirmed. |
| #LTS00131472 | 2026-05-29 19:26:07+00:00 | 1.5 | INBOUND | EA8100 | CONNECTIVITY | Agent promised to send generic setup instructions via email and offered paid support ($15/hour). |
| #LTS00131431 | 2026-05-29 19:56:49+00:00 | 1.8 | INBOUND | WHW03 | SETUP | No payment captured; customer advised to call back later. No clear next step or alternative provided. |
| #LTS00131452 | 2026-05-29 17:29:13+00:00 | 3.0 | INBOUND | MR9600 | CONNECTIVITY | Offered to email detailed troubleshooting steps or provide paid support; no technical fix confirmed. |
| #LTS00131431 | 2026-05-29 19:56:49+00:00 | 1.8 | INBOUND | WHW03 | SETUP | No payment captured; customer advised to call back later. No clear next step or alternative provided. |
| #LTS00131452 | 2026-05-29 17:29:13+00:00 | 3.0 | INBOUND | MR9600 | CONNECTIVITY | Offered to email detailed troubleshooting steps or provide paid support; no technical fix confirmed. |
| #LTS00131472 | 2026-05-29 19:26:07+00:00 | 1.5 | INBOUND | EA8100 | CONNECTIVITY | Agent promised to send generic setup instructions via email and offered paid support ($15/hour). |
| #LTS00131431 | 2026-05-29 19:56:49+00:00 | 1.8 | INBOUND | WHW03 | SETUP | No payment captured; customer advised to call back later. No clear next step or alternative provided. |
| #LTS00131452 | 2026-05-29 17:29:13+00:00 | 3.0 | INBOUND | MR9600 | CONNECTIVITY | Offered to email detailed troubleshooting steps or provide paid support; no technical fix confirmed. |
| #LTS00131472 | 2026-05-29 19:26:07+00:00 | 1.5 | INBOUND | EA8100 | CONNECTIVITY | Agent promised to send generic setup instructions via email and offered paid support ($15/hour). |
| #LTS00131431 | 2026-05-29 19:56:49+00:00 | 1.8 | INBOUND | WHW03 | SETUP | No payment captured; customer advised to call back later. No clear next step or alternative provided. |