# venнемir.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 | 10m 7s | MX6200 | CONNECTIVITY | 34 | 2 | --- ## Scorecard | Dimension | This Week | Calls Reviewed | |---------------|-----------|----------------| | Accuracy | 2.50 | 34 | | Protocol | 1.90 | 34 | | Communication | 2.20 | 34 | | Overall | 2.30 | 34 | *Scores reflect a range from 1.1 (lowest) to 3.9 (highest) across 34 calls reviewed.* --- ## Where Time Goes ### Models Supported | Model | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | |----------|-------|-----------------|-------------|--------------|--------------|-------------------| | MX5500 | 2 | 34m 37s | 1.80 | 1.00 | 2.00 | 2.00 | | MBE7000 | 2 | 19m 19s | 3.00 | 4.00 | 1.50 | 2.50 | | MX6200 | 4 | 15m 50s | 3.00 | 4.00 | 2.00 | 2.50 | | WHW03 | 3 | 7m 34s | 1.90 | 2.30 | 1.70 | 2.00 | | MX4200 | 3 | 12m 32s | 2.10 | 2.30 | 1.30 | 2.30 | **Key Observations** - **MX5500** and **WHW03** clusters show the longest handle times combined with the lowest overall scores (1.8–1.9). This pattern suggests these models may benefit from targeted protocol reviews and additional self-help resources. - **MX6200** and **MBE7000** have strong accuracy but lower protocol scores, indicating opportunities to streamline escalation triggers and documentation steps. ### Problem Categories | Category | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Focus Area? | |----------------|-------|-----------------|-------------|--------------|--------------|-------------------|-------------| | CONNECTIVITY | 18 | 12m 05s | 2.20 | 2.80 | 1.80 | 2.10 | ✓ | | SETUP | 9 | 12m 43s | 2.10 | 2.30 | 1.70 | 2.10 | ✓ | | ACCESS | 4 | 11m 29s | 2.40 | 2.50 | 2.30 | 2.50 | ✓ | | CONFIGURATION | 1 | 4m 00s | 1.20 | 1.00 | 1.00 | 1.00 | ✓ | **Focus Area Insights** - **CONNECTIVITY** and **SETUP** categories dominate handle time and show room for improvement in protocol adherence. Review LED interpretation guides and modem-testing workflows for these issues. - **ACCESS** cases (e.g., account verification, app login) require clearer self-help pathways to reduce repeat contacts. --- ## What Went Well ### Strength 1: Accurate Warranty Guidance > *"Your router has already been considered as end of life and is no longer eligible for free troubleshooting. As always, troubleshooting steps and guides are available on support.linksys.com at no cost."* [#LTS00131024](https://linksys.happyfox.com/staff/ticket/131024/) Calvin consistently set accurate expectations around warranty status and directed customers to self-help resources, reducing unnecessary escalations. ### Strength 2: Mesh Troubleshooting Precision > *"Try putting them back to the same floor because flashing red indicates they can't detect the main one. Wait for them to finish flashing white."* [#LTS00094375](https://linksys.happyfox.com/staff/ticket/94375/) When guiding mesh node re-pairing, Calvin used model-specific LED indicators (white = ready, red = no connection) to diagnose and resolve issues efficiently. ### Strength 3: Polite Call Control > *"I do apologize for the hold time, and I appreciate your patience while we look into this."* [#LTS00101153](https://linksys.happyfox.com/staff/ticket/101153/) Calvin maintained professionalism even during extended holds, acknowledging customer frustration and reinforcing trust. --- ## Growth Opportunities ### Opportunity 1: Technical Accuracy in Reset Procedures > *"Hold the reset button until the LED turns off. This may take approximately 20 seconds."* [#LTS00131214](https://linksys.happyfox.com/staff/ticket/131214/) **What “Good” Looks Like** - **Correct Duration**: For WHW01/Velos, the factory reset requires holding the button for **10 seconds** (not 20) until the LED blinks off. - **Next Step**: Confirm the reset was successful by verifying the admin page loads at `http://myrouter.local`. - **Action**: Review KB articles for model-specific reset times and practice these steps in shadowing sessions. ### Opportunity 2: Consistent Product Data Collection > *"Can you provide the serial number of the Linksys device?"* [#LTS00131468](https://linksys.happyfox.com/staff/ticket/131468/) **What “Good” Looks Like** - **Early Collection**: Ask for **model and serial number** within the first 30 seconds of the call to enable accurate KB alignment. - **Verification**: Cross-check the model against the serial number using the internal lookup tool. - **Action**: Use the script: “To help me find the best solution quickly, could you share the exact model and serial number of your device?” --- ## Next Week's Focus 1. **Model/Serial Script Drill** Practice asking for model and serial number in the first 30 seconds of every call using a consistent script. 2. **Reset Time Audit** Review KB reset procedures for WHW, MX, and LN families; create a cheat sheet for common models. 3. **LED Interpretation Quiz** Complete a quick quiz on LED meanings (e.g., solid red = no WAN, blinking white = resetting) to build confidence. 4. **Escalation Threshold Check** Before escalating, confirm basic troubleshooting (power cycle, cable check, LED status) is documented in the case notes. --- ## Technical Accuracy **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. [#LTS00101153](https://linksys.happyfox.com/staff/ticket/101153/) **Improvement** > *Agent provided incorrect default admin password ('admin') for WHW01, contradicting KB which states unique password on label.* [#LTS00131214](https://linksys.happyfox.com/staff/ticket/131214/) **Improvement** > *Agent provided clearly invalid URL (martmartwifif.com) instead of support.linksys.com, constituting a severe technical accuracy error.* [#LTS00125542](https://linksys.happyfox.com/staff/ticket/125542/) --- ## Escalation Lessons: What L2 Did ### [#TE00122939](https://linksys.happyfox.com/staff/ticket/122939/) — Resolved by Level 2 - **What L1 Saw**: Customer’s WHW01 mesh nodes showed solid red LEDs after a Comcast modem upgrade. L1 guided a factory reset and 5-press pairing but did not verify modem connectivity. - **Why It Escalated**: Issue persisted post-reset; L1 did not confirm WAN status or guide modem testing. - **What L2 Did**: L2 confirmed modem internet connectivity by having the customer test with a laptop, then re-initialized the mesh system using the correct admin page (`http://myrouter.local`). - **L1 Learning Points**: 1. Always verify modem WAN status before resetting mesh nodes. 2. Use `http://myrouter.local` for admin access instead of relying on app connectivity. 3. Document modem test results in the case notes before escalating. ### [#TE00092429](https://linksys.happyfox.com/staff/ticket/92429/) — Resolved by Level 2 - **What L1 Saw**: Customer couldn’t verify their Linksys account after an ISP change; verification link expired. - **Why It Escalated**: L1 collected screenshots but did not use internal tools to verify account status. - **What L2 Did**: L2 accessed backend tools to validate account details, issued a new verification link, and guided the customer through re-verification. - **L1 Learning Points**: 1. Use internal account verification tools when customers report expired links. 2. Proactively offer to resend verification emails instead of waiting for customer-initiated screenshots. 3. Confirm account status in real-time to avoid unnecessary escalations. --- ## Coach Appendix *Internal use only* - **Top Trend**: 12 unresolved calls stem from incomplete troubleshooting on CONNECTIVITY/SETUP issues. Focus next week on structured diagnosis (LED → WAN → node status). - **Recurring Pattern**: 5 calls involved incorrect reset durations or unsupported procedures (e.g., 5-press on Velop). Prioritize KB review for reset flows. - **Evidence**: Quotes and outcomes above reflect documented inaccuracies and missed protocol steps; use these as coaching anchors. --- ## This Week's Calls | Case | Date | Score | Direction | Product | Category | Outcome | |------|------|-------|-----------|---------|----------|---------| | [#LTS00130705](https://linksys.happyfox.com/staff/ticket/130705/) | 2026-05-25 | 1.3 | INBOUND | EA7300 | CONNECTIVITY | No clear path given | | [#TE00122939](https://linksys.happyfox.com/staff/ticket/122939/) | 2026-05-25 | 2.4 | INBOUND | WHW01 | CONNECTIVITY | Pending resolution | | [#LTS00057293](https://linksys.happyfox.com/staff/ticket/57293/) | 2026-05-25 | 3.0 | INBOUND | WHW01 | SETUP | Closed with self-help | | [#LTS00130230](https://linksys.happyfox.com/staff/ticket/130230/) | 2026-05-25 | 1.5 | INBOUND | SPNMX55 | CONNECTIVITY | Abandoned or vague | | [#LTS00130857](https://linksys.happyfox.com/staff/ticket/130857/) | 2026-05-26 | 3.0 | INBOUND | EA7300 | SETUP | Customer declined path | | [#LTS00101153](https://linksys.happyfox.com/staff/ticket/101153/) | 2026-05-26 | 1.1 | INBOUND | WHW03 | CONNECTIVITY | Abandoned or vague | | [#LTS00101153](https://linksys.happyfox.com/staff/ticket/101153/) | 2026-05-26 | 1.5 | OUTBOUND | WHW03 | CONNECTIVITY | Customer to test modem | | [#LTS00130179](https://linksys.happyfox.com/staff/ticket/130179/) | 2026-05-26 | 1.8 | INBOUND | RE7000 | SETUP | Relocate extender | | [#LTS00070759](https://linksys.happyfox.com/staff/ticket/70759/) | 2026-05-26 | 1.8 | INBOUND | MX5500 | CONNECTIVITY | Contact ISP | | [#LTS00131018](https://linksys.happyfox.com/staff/ticket/131018/) | 2026-05-27 | 3.0 | INBOUND | MBE7000 | CONNECTIVITY | Pending resolution | | [#LTS00131024](https://linksys.happyfox.com/staff/ticket/131024/) | 2026-05-27 | 4.0 | INBOUND | E2500 | CONNECTIVITY | Closed with self-help | | [#TE00092429](https://linksys.happyfox.com/staff/ticket/92429/) | 2026-05-27 | 3.1 | INBOUND | MX8500 | ACCESS | Escalated correctly | | [#LTS00131054](https://linksys.happyfox.com/staff/ticket/131054/) | 2026-05-27 | 3.0 | INBOUND | WHW03 | CONNECTIVITY | Customer declined path | | [#LTS00095569](https://linksys.happyfox.com/staff/ticket/95569/) | 2026-05-27 | 1.5 | INBOUND | LN1100 | SETUP | Abandoned or vague | | [#LTS00125542](https://linksys.happyfox.com/staff/ticket/125542/) | 2026-05-27 | 1.4 | INBOUND | RE7000 | SETUP | No resolution achieved | | [#LTS00110405](https://linksys.happyfox.com/staff/ticket/110405/) | 2026-05-27 | 3.0 | INBOUND | MR8300 | CONNECTIVITY | Closed with self-help | | [#LTS00110405](https://linksys.happyfox.com/staff/ticket/110405/) | 2026-05-27 | 3.0 | INBOUND | MR8300 | CONNECTIVITY | Password reset completed | | [#GI00131206](https://linksys.happyfox.com/staff/ticket/131206/) | 2026-05-28 | 3.0 | INBOUND | — | ACCESS | Callback or followup | | [#LTS00131208](https://linksys.happyfox.com/staff/ticket/131208/) | 2026-05-28 | 1.8 | INBOUND | SPNMX57CF | SETUP | Pending resolution | | [#LTS00131214](https://linksys.happyfox.com/staff/ticket/131214/) | 2026-05-28 | 1.4 | INBOUND | WHW01 | SETUP | Abandoned or vague | | [#LTS00131222](https://linksys.happyfox.com/staff/ticket/131222/) | 2026-05-28 | 3.0 | INBOUND | E5350 | CONNECTIVITY | Abandoned or vague | | [#LTS00131020](https://linksys.happyfox.com/staff/ticket/131020/) | 2026-05-28 | 3.0 | INBOUND | SPNMX55CF | CONNECTIVITY | No valid resolution | | [#LTS00131065](https://linksys.happyfox.com/staff/ticket/131065/) | 2026-05-28 | 1.2 | INBOUND | EA9300 | SETUP | Incorrectly closed | | [#LTS00131264](https://linksys.happyfox.com/staff/ticket/131264/) | 2026-05-28 | 1.9 | INBOUND | MX4200 | CONNECTIVITY | Abandoned or vague | | [#LTS00131263](https://linksys.happyfox.com/staff/ticket/131263/) | 2026-05-28 | 1.2 | INBOUND | MR8300 | CONFIGURATION | Incorrectly closed | | [#LTS00131298](https://linksys.happyfox.com/staff/ticket/131298/) | 2026-05-28 | 3.0 | INBOUND | MX4200 | CONNECTIVITY | Closed with self-help | | [#LTS00131305](https://linksys.happyfox.com/staff/ticket/131305/) | 2026-05-28 | 1.8 | INBOUND | MX2000 | SETUP | Callback or followup | | [#GI00131206](https://linksys.happyfox.com/staff/ticket/131206/) | 2026-05-28 | 3.2 | INBOUND | MX2000 | ACCESS | Closed with self-help | | [#LTS00102579](https://linksys.happyfox.com/staff/ticket/102579/) | 2026-05-29 | 3.0 | INBOUND | RE6500 | CONNECTIVITY | Abandoned or vague | | [#LTS00131392](https://linksys.happyfox.com/staff/ticket/131392/) | 2026-05-29 | 1.3 | INBOUND | MX2000 | SETUP | Abandoned or vague | | [#LTS00129010](https://linksys.happyfox.com/staff/ticket/129010/) | 2026-05-29 | 2.8 | INBOUND | E900 | CONNECTIVITY | Abandoned or vague | | [#LTS00094375](https://linksys.happyfox.com/staff/ticket/94375/) | 2026-05-29 | 3.0 | INBOUND | MBE7000 | SETUP | Closed correctly | | [#LTS00077800](https://linksys.happyfox.com/staff/ticket/77800/) | 2026-05-29 | 3.9 | INBOUND | MX6200 | CONNECTIVITY | Closed with self-help | | [#LTS00131436](https