# vennemir.calvin@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 | 17m 10s | MX6200 | CONNECTIVITY | 34 | 2 | --- ## Scorecard | Dimension | This Week | Calls Reviewed | |---|---|---| | Accuracy | 2.70 | 34 | | Protocol | 1.90 | 34 | | Communication | 2.20 | 34 | | Overall | 2.40 | 34 | *Scores reflect the 34 calls reviewed this week. Overall scores range from 1.10 to 3.90.* --- ## This Week's Coverage ### Models Supported | Model | Calls | Avg Score | |---|---|---| | MX6200 | 5 | 2.40 | | WHW03 | 4 | 2.00 | | MX5500 | 2 | 1.80 | | EA7300 | 2 | 2.20 | | WHW01 | 2 | 2.80 | | MBE7000 | 2 | 3.00 | | MX4200 | 3 | 2.00 | | RE7000 | 2 | 1.60 | | MR8300 | 3 | 1.80 | | SPNMX55CF | 2 | 2.40 | **Key pattern:** Lower scores on MX5500 and RE7000 calls suggest a need for deeper familiarity with these models’ setup and troubleshooting flows. ### Problem Categories | Category | Calls | Avg Score | Focus Area? | |---|---|---|---| | CONNECTIVITY | 19 | 2.10 | ✓ | | SETUP | 9 | 2.30 | ✓ | | ACCESS | 4 | 2.30 | ✓ | | CONFIGURATION | 2 | 1.30 | ✓ | **CONNECTIVITY** and **SETUP** categories show the greatest opportunity for improvement. The lower average scores in these areas indicate that agents may benefit from additional training on common connectivity issues and structured setup procedures. --- ## What Went Well ### Correct identification of non-Linksys products > “Okay, it's Y as in yellow, 2, 5, 9, 1, 2, 0. C as in Charlie, 0, 0, again, number 4, 9, 7.” This call demonstrates the agent’s ability to correctly identify a TP-Link Deco mesh system and appropriately refer the customer to TP-Link support, avoiding incorrect Linksys-specific guidance. [#LTS00057293](https://linksys.happyfox.com/staff/ticket/57293/) ### Accurate troubleshooting guidance for mesh systems > “All right, k... wait for them to finish flashing well... still flashing. Yeah, they're all solid blue, I mean, no. No, now the other one is flashing as well. Sorry, I've got one solid blue. Yeah. Okay. Oh, now it's flashing blue. Flashing. Both of them flashing blue.” The agent successfully guided the customer through factory resets and re-pairing of mesh nodes, restoring connectivity and confirming resolution. This reflects strong adherence to KB-based troubleshooting for mesh systems. [#LTS00094375](https://linksys.happyfox.com/staff/ticket/94375/) --- ## Growth Opportunities ### Incorrect technical guidance on reset procedures > “All right, can you provide me the serial number of DMX-2000? … All right. 50 Delta 10 Mary 25 Charlie 67921. Thank you so much. Let me just quickly...” The agent instructed a 20-second factory reset for an MX2000, contradicting KB guidance which specifies 10 seconds. This incorrect duration can lead to failed resets and unresolved issues. [#LTS00131305](https://linksys.happyfox.com/staff/ticket/131305/) **What “good” looks like:** - Always verify reset durations against the KB for the specific model. - Confirm the reset was successful before proceeding with further steps. ### Failure to collect critical product information > “Right. It says I'm connected, but no, I don't know, no service or no signal. I don't know what the problem is. Um, I have a. Oh, wait. I thought I wrote that down, too. Um, I'm not sure if this is no. I have the serial number.” The agent failed to collect the model number in this call, which is essential for accurate troubleshooting and KB alignment. Without the model, guidance may be incorrect or unsafe. [#LTS00130705](https://linksys.happyfox.com/staff/ticket/130705/) **What “good” looks like:** - Always ask for and confirm the exact model number at the start of the call. - Use the model to select the appropriate KB article and troubleshooting path. --- ## Next Week's Focus 1. **Verify reset procedures:** Before instructing any factory reset, confirm the exact duration from the KB for the specific model. 2. **Collect model/serial early:** Ask for the model number and serial number within the first 2 minutes of the call to ensure accurate, safe guidance. 3. **Confirm resolution:** After guiding a reset or re-pairing, verify that the issue is truly resolved before closing the call. 4. **Use KB for LED interpretations:** Reference the KB for LED meanings specific to each model to avoid misdiagnosis. --- ## Technical Accuracy ### **Improvement** > This is a serious accuracy and safety risk, as it directs the customer to an incorrect and potentially unsafe website. [#LTS00130705](https://linksys.happyfox.com/staff/ticket/130705/) ### **Improvement** > 5-press reset is only valid for Cognitive Mesh (LN/MX6200/MBE) and not supported for Velop (WHW/MX/MR). This risks misdiagnosis and wasted effort. [#LTS00101153](https://linksys.happyfox.com/staff/ticket/101153/) ### **Improvement** > KB specifies 10 seconds for factory reset on these models. Incorrect guidance can lead to failed resets and unresolved issues. [#LTS00131214](https://linksys.happyfox.com/staff/ticket/131214/) ### **Improvement** > This is materially false and unsupported by KB. Routers do not have hard drives, and no such replacement policy exists. [#LTS00131473](https://linksys.happyfox.com/staff/ticket/131473/) ### **Strength** > Accurate troubleshooting aligned with KB guidance for mesh systems. [#LTS00094375](https://linksys.happyfox.com/staff/ticket/94375/) --- ## Coaching Moments ### **Improvement** > “All right, thank you so much for patiently waiting, Miss Gina, and I do apologize...” The agent collected payment before any diagnostic or identification steps, violating core support protocol. Payment should only be collected after establishing model compatibility and a clear troubleshooting path. [#LTS00101153](https://linksys.happyfox.com/staff/ticket/101153/) ### **Improvement** > “In this case, since currently it's a flashing red light, the next step is to contact directly your internet provider, since there's no available computer that we can wire directly.” The agent failed to follow standard troubleshooting flow for a flashing red WAN light. Basic steps such as power-cycling the router and checking WAN status should be performed before directing the customer to the ISP. [#LTS00101153](https://linksys.happyfox.com/staff/ticket/101153/) ### **Improvement** > “is available for fre trust gathering on our end paper gathering for the unit requires a $[REDACTED_PAYMENT_DIGITS] payment if you choose to proceed through the phone.” The agent incorrectly interpreted a solid green LED as meaning the extender is “set up properly.” KB states that a solid green LED only indicates power, not successful connection or signal strength. This misinterpretation can mislead customers. [#LTS00130179](https://linksys.happyfox.com/staff/ticket/130179/) ### **Improvement** > “Do you have a Linksys? Linksys router? But can you please provide the serial number? Can you please provide the serial number?” The agent failed to confirm that the customer owned a Linksys device before requesting serial/model details. This led to unnecessary back-and-forth and a missed opportunity to redirect the customer to the correct support channel. [#LTS00130230](https://linksys.happyfox.com/staff/ticket/130230/) --- ## Escalation Lessons: What L2 Did ### [#TE00122939](https://linksys.happyfox.com/staff/ticket/122939/) — Resolved by Level 2 - **What L1 saw:** Customer lost internet after upgrading to a new Comcast modem; Linksys mesh system showed no connectivity. - **Why it escalated:** L1 failed to collect product model/serial, did not verify modem connectivity, and initiated paid support without clear consent. - **Related call chain:** This was a repeat contact; the initial call was closed as “resolved” without actual resolution. - **What L2 did:** L2 guided the customer through modem testing, confirmed ISP connectivity, and re-pairing of mesh nodes. - **Current state:** Resolved. - **L1 learning points:** 1. Always collect model/serial number before troubleshooting. 2. Verify modem connectivity by testing with a laptop or another device. 3. Obtain explicit consent before initiating paid support. ### [#TE00092429](https://linksys.happyfox.com/staff/ticket/92429/) — Resolved by Level 2 - **What L1 saw:** Customer couldn’t verify their Linksys account due to a non-functional verification link. - **Why it escalated:** L1 did not use internal tools to verify the account and repeatedly asked for screenshots without clear next steps. - **Related call chain:** This was a follow-up call after an earlier unresolved interaction. - **What L2 did:** L2 reviewed the screenshot, verified the account manually, and provided a callback. - **Current state:** Resolved. - **L1 learning points:** 1. Use internal tools to verify account status when possible. 2. Provide clear, step-by-step instructions for screenshot submission. 3. Set clear expectations for callback timing. --- ## Coach Appendix **Weekly trend summary:** This week’s data shows a consistent challenge in accuracy and protocol adherence, particularly around model-specific guidance and reset procedures. The agent’s strengths lie in identifying non-Linksys products and guiding mesh system troubleshooting, but there is a clear need to improve technical accuracy, especially around reset durations and model verification. **Key focus for next coaching:** - Reinforce the importance of collecting model/serial numbers early in the call. - Review KB articles for reset procedures to ensure correct durations are provided. - Practice structured troubleshooting flows for connectivity issues, ensuring basic steps (power-cycle, WAN check) are completed before escalation or paid support. --- ## This Week's Calls | Case | Date | Score | Direction | Product | Category | Outcome | |---|---|---|---|---|---|---| | [#LTS00130705](https://linksys.happyfox.com/staff/ticket/130705/) | 2026-05-25 12:27:06+00:00 | 1.3 | INBOUND | EA7300 | CONNECTIVITY | Abandoned or vague | | [#TE00122939](https://linksys.happyfox.com/staff/ticket/122939/) | 2026-05-25 13:05:31+00:00 | 2.4 | INBOUND | WHW01 | CONNECTIVITY | Pending resolution | | [#LTS00057293](https://linksys.happyfox.com/staff/ticket/57293/) | 2026-05-25 15:44:33+00:00 | 3.0 | INBOUND | WHW01 | SETUP | Closed with self-help | | [#LTS00130230](https://linksys.happyfox.com/staff/ticket/130230/) | 2026-05-25 16:52:50+00:00 | 1.5 | INBOUND | SPNMX55 | CONNECTIVITY | Abandoned or vague | | [#LTS00130857](https://linksys.happyfox.com/staff/ticket/130857/) | 2026-05-26 13:17:10+00:00 | 3.0 | INBOUND | EA7300 | SETUP | Customer declined path | | [#LTS00101153](https://linksys.happyfox.com/staff/ticket/101153/) | 2026-05-26 14:05:09+00:00 | 1.1 | INBOUND | WHW03 | CONNECTIVITY | Abandoned or vague | | [#LTS00101153](https://linksys.happyfox.com/staff/ticket/101153/) | 2026-05-26 14:25:19+00:00 | 1.5 | OUTBOUND | WHW03 | CONNECTIVITY | Abandoned or vague | | [#LTS00130179](https://linksys.happyfox.com/staff/ticket/130179/) | 2026-05-26 17:43:09+00:00 | 1.8 | INBOUND | RE7000 | SETUP | Abandoned or vague | | [#LTS00070759](https://linksys.happyfox.com/staff/ticket/70759/) | 2026-05-26 18:01:01+00:00 | 1.8 | INBOUND | MX5500 | CONNECTIVITY | Pending resolution | | [#LTS00131018](https://linksys.happyfox.com/staff/ticket/131018/) | 2026-05-27 11:05:40+00:00 | 3.0 | INBOUND | MBE7000 | CONNECTIVITY | Pending resolution | | [#LTS00131024](https://linksys.happyfox.com/staff/ticket/131024/) | 2026-05-27 12:46:59+00:00 | 4.0 | INBOUND | E2500 | CONNECTIVITY | Closed with self-help | | [#TE00092429](https://linksys.happyfox.com/staff/ticket/92429/) | 2026-05-27 15:02:42+00:00 | 3.1 | INBOUND | MX8500 | ACCESS | Escalated correctly | | [#LTS00131054](https://linksys.happyfox.com/staff/ticket/131054/) | 2026-05-27 16:35:47+00:00 | 3.0 | INBOUND | WHW03 | CONNECTIVITY | Customer declined path | | [#LTS00095569](https://linksys.happyfox.com/staff/ticket/95569/) | 2026-05-27 17:24:47+00:00 | 1.5 | INBOUND | LN1100 | SETUP | Abandoned or vague | | [#LTS00125542](https://linksys.happyfox.com/staff/ticket/125542/) | 2026-05-27 18:19:14+00:00 | 1.4 | INBOUND | RE7000 | SETUP | Abandoned or vague | | [#LTS00110405](https://linksys.happyfox.com/staff/ticket/110405/) | 2026-05-27 20:51:28+00:00 | 3.0 | INBOUND | MR8300 | CONNECTIVITY | Abandoned or vague | | [#LTS00110405](https://linksys.happyfox.com/staff/ticket/110405/) | 2026-05-27 20:59:21+00:00 | 1.4 | INBOUND | MR8300 | CONNECTIVITY | Abandoned or vague | | [#LTS00110405](https://linksys.happyfox.com/staff/ticket/110405/) | 2026-05-27 21:17:02+00:00 | 3.2 | INBOUND | MR8300 | CONNECTIVITY | Closed with self-help | | [#GI00131206](https://linksys.happyfox.com/staff/ticket/131206/) | 2026-05-28 12:19:44+00:00 | 3.0 | INBOUND | | ACCESS | Callback or followup set | | [#LTS00131208](https://linksys.happyfox.com/staff/ticket/131208/) | 2026-05-28 12:35:05+00:00 | 1.8 | INBOUND | SPNMX57CF | SETUP | Pending resolution | | [#LTS00131214](https://linksys.happyfox.com/staff/ticket/131214/) | 2026-05-28 13:13:23+00:00 | 1.4 | INBOUND | WHW01 | SETUP | Abandoned or vague | | [#LTS00131222](https://linksys.happyfox.com/staff/ticket/131222/) | 2026-05-28 13:44:37+00:00 | 3.0 | INBOUND | E5350 | CONNECTIVITY | Abandoned or vague | | [#LTS00131020](https://linksys.happyfox.com/staff/ticket/131020/) | 2026-05-28 13:55:28+00:00 | 3.0 | INBOUND | SPNMX55CF | CONNECTIVITY | Abandoned or vague | | [#LTS00131065](https://linksys.happyfox.com/staff/ticket/131065/) | 2026-05-28 14:35:13+00:00 | 1.2 | INBOUND | EA9300 | SETUP | Incorrectly closed | | [#LTS00131264](https://linksys.happyfox.com/staff/ticket/131264/) | 2026-05-28 16:58:33+00:00 | 1.9 | INBOUND | MX4200 | CONNECTIVITY | Abandoned or vague | | [#LTS00131263](https://linksys.happyfox.com/staff/ticket/131263/) | 2026-05-28 19:08:52+00:00 | 1.2 | INBOUND | MR8300 | CONFIGURATION | Incorrectly closed | | [#LTS00131298](https://linksys.happyfox.com/staff/ticket/131298/) | 2026-05-28 19:41:52+00:00 | 3.0 | INBOUND | MX4200 | CONNECTIVITY | Closed with self-help | | [#LTS00131305](https://linksys.happyfox.com/staff/ticket/131305/) | 2026-05-28 19:55:04+00:00 | 1.8 | INBOUND | MX2000 | SETUP | Callback or followup set | | [#GI00131206](https://linksys.happyfox.com/staff/ticket/131206/) | 2026-05-28 23:01:13+00:00 | 3.2 | INBOUND | MX2000 | ACCESS | Closed with self-help | | [#LTS00102579](https://linksys.happyfox.com/staff/ticket/102579/) | 2026-05-29 01:49:01+00:00 | 3.0 | INBOUND | RE6500 | CONNECTIVITY | Abandoned or vague | | [#LTS00131392](https://linksys.happyfox.com/staff/ticket/131392/) | 2026-05-29 12:51:06+00:00 | 1.3 | INBOUND | MX2000 | SETUP | Abandoned or vague | | [#LTS00129010](https://linksys.happyfox.com/staff/ticket/129010/) | 2026-05-29 15:16:15+00:00 | 2.8 | INBOUND | E900 | CONNECTIVITY | Abandoned or vague | | [#LTS00094375](https://linksys.happyfox.com/staff/ticket/94375/) | 2026-05-29 15:30:51+00:00 | 3.3 | INBOUND | MBE7000 | SETUP | Closed correctly | | [#LTS00077800](https://linksys.happyfox.com/staff/ticket/77800/) | 2026-05-29 16:33:29+00:00 | 3.9 | INBOUND | MX6200 | CONNECTIVITY | Closed with self-help | | [#LTS00131436](https://linksys.happyfox.com/staff/ticket/131436/) | 2026-05-29 16:59:21+00:00 | 3.0 | INBOUND | MX6200 | CONNECTIVITY | Likely fixed unconfirmed | | [#LTS00011393](https://linksys.happyfox.com/staff/ticket/11393/) | 2026-05-29 17:08:10+00:00 | 3.1 | INBOUND | MX6200 | SETUP | Likely fixed unconfirmed | | [#LTS00131468](https://linksys.happyfox.com/staff/ticket/131468/) | 2026-05-29 19:08:34+00:00 | 3.0 | INBOUND | WHW03 | CONNECTIVITY | Closed with self-help | | [#LTS00131473](https://linksys.happyfox.com/staff/ticket/131473/) | 2026-05-29 19:31:40+00:00 | 1.3 | INBOUND | MX5300 | ACCESS | Incorrectly closed | | [#LTS00131392](https://linksys.happyfox.com/staff/ticket/131392/) | 2026-05-29 20:51:28+00:00 | 1.3 | INBOUND | MX2000 | SETUP | Abandoned or vague | | [#LTS00131468](https://linksys.happyfox.com/staff/ticket/131468/) | 2026-05-29 21:17:02+00:00 | 3.3 | INBOUND | MBE7000 | SETUP | Closed correctly |