# dorothybelle.oraiz@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 | | --- | --- | --- | --- | --- | --- | | 22 | 24m 50s | MX4200 | CONNECTIVITY | 22 | 1 | ## Scorecard | Dimension | This Week | Calls Reviewed | | --- | --- | --- | | Accuracy | 2.60 | 22 | | Protocol | 1.80 | 22 | | Communication | 2.10 | 22 | | Overall | 2.40 | 22 | ## Where Time Goes **Product Families** | Family | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Note | | --- | --- | --- | --- | --- | --- | --- | --- | | MX | 7 | 49m 40s | 2.27 | 2.57 | 1.57 | 1.86 | Outlier: 2.7x weekly median handle time | | WHW | 6 | 36m 30s | 3.00 | 2.00 | 1.83 | 2.50 | Outlier: 2.0x weekly median handle time | | MBE | 1 | 21m 47s | 2.80 | 2.00 | 2.00 | 2.00 | | | MR | 4 | 14m 38s | 1.70 | 1.50 | 1.25 | 2.00 | | | E | 2 | 7m 30s | 2.25 | 3.00 | 1.50 | 2.00 | | | EA | 6 | 6m 30s | 2.55 | 3.50 | 1.83 | 1.83 | | **Key Observations** - MX is the slowest family at 49m 40s; outlier: 2.7x weekly median handle time. - WHW is the slowest family at 36m 30s; outlier: 2.0x weekly median handle time. **Problem Categories** | Category | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Focus Area? | | --- | --- | --- | --- | --- | --- | --- | --- | | CONNECTIVITY | 14 | 31m 22s | 2.40 | 2.40 | 1.80 | 2.10 | ✓ | | SETUP | 6 | 23m 41s | 2.30 | 2.30 | 1.70 | 2.00 | ✓ | | ACCESS | 2 | 78m 7s | 1.50 | 1.00 | 1.50 | 2.00 | ✓ | ## Week-over-Week Movement - Incorrect reset and pairing procedures for Velop/MX devices - Premature escalation to paid support without exhausting free troubleshooting - Failure to verify warranty status before offering support paths - Inaccurate LED and technical guidance leading to unresolved issues ## What Went Well > **Strength**: Accurate model identification > The agent correctly identified the product model (MX4200) early in the call, which is essential for appropriate troubleshooting and support path selection. > `[#TE00131348](https://linksys.happyfox.com/staff/ticket/131348/)` > **Strength**: Clear paid support explanation > The agent clearly explained paid support terms, cost, and session limits, ensuring the customer understood the support options and expectations. > `[#LTS00130795](https://linksys.happyfox.com/staff/ticket/130795/)` --- ### Growth Opportunities > **Improvement**: Incorrect reset procedures > The agent instructed a 20-second reset hold time for Velop MX4200, but the KB specifies a 10-second hold. This incorrect guidance can lead to unresolved issues and customer frustration. > **Next Step**: Always verify reset durations against the KB before instructing customers. > `[#TE00131348](https://linksys.happyfox.com/staff/ticket/131348/)` > **Improvement**: Premature paid support offer > The agent offered paid support without first confirming that free troubleshooting could resolve the issue, which may have discouraged the customer from attempting self-help steps. > **Next Step**: Exhaust free troubleshooting options and provide clear self-help resources before escalating to paid support. > `[#LTS00131131](https://linksys.happyfox.com/staff/ticket/131131/)` --- ### Next Week's Focus - **Verify reset durations**: Always cross-check reset procedures with the KB before instructing customers, especially for Velop and MX series devices. - **Standardize mesh setup guidance**: Develop clear, step-by-step instructions for mesh setup, including pairing methods and LED interpretations, to reduce ambiguity and improve consistency. - **Improve escalation criteria**: Establish clearer criteria for when to escalate to paid support versus offering self-help resources, ensuring customers are guided appropriately. - **Enhance communication clarity**: Work on reducing long silences and off-topic conversations to improve call efficiency and customer experience. --- ### Technical Accuracy **Improvement** Incorrect reset duration for Velop MX4200; KB specifies 10 seconds for factory reset. `[#TE00131348](https://linksys.happyfox.com/staff/ticket/131348/)` **Improvement** Incorrect default admin password suggestion; MX4200 uses password printed on label, not 'admin'. `[#TE00131348](https://linksys.happyfox.com/staff/ticket/131348/)` **Improvement** IPv6 disabled without diagnostic justification; potential masking of root cause. `[#TE00131348](https://linksys.happyfox.com/staff/ticket/131348/)` **Improvement** Incorrect admin URL suggested; correct URL is `[REDACTED_PHONE]` or `myrouter.local`. `[#TE00131348](https://linksys.happyfox.com/staff/ticket/131348/)` **Improvement** Factually incorrect LED interpretation; solid red on WHW03 indicates WAN/internet failure, not successful factory reset. `[#LTS00131486](https://linksys.happyfox.com/staff/ticket/131486/)` --- ### Coaching Moments **Strength** > The agent correctly identified the product model (MX4200) early in the call, which is essential for appropriate troubleshooting and support path selection. > `[#TE00131348](https://linksys.happyfox.com/staff/ticket/131348/)` **Strength** > The agent clearly explained paid support terms, cost, and session limits, ensuring the customer understood the support options and expectations. > `[#LTS00130795](https://linksys.happyfox.com/staff/ticket/130795/)` --- ### Escalation Lessons: What L2 Did ### [#TE00131348](https://linksys.happyfox.com/staff/ticket/131348/) — Resolved by Level 2 - **What L1 saw**: Customer unable to access specific websites (e.g., own Bluehost site) when using Linksys MX4200 mesh; works via ISP router; intermittent hangs and slow loads. - **Why it escalated**: L1 applied incorrect troubleshooting steps (unsupported 5-press pairing, 20-second reset) and failed to resolve the issue. - **Related call chain**: This was part of a multi-call chain involving multiple agents and escalating attempts to resolve the issue. - **What L2 did**: L2 reviewed the case, identified the incorrect procedures used by L1, and applied correct troubleshooting steps including verifying WAN connectivity, adjusting IPv6 settings, and guiding the customer through proper reset and reconfiguration. - **Current state**: The case is resolved, with the customer able to access websites again. - **L1 learning points**: - Always verify reset durations against the KB before instructing customers. - Use supported pairing methods for the specific device family. - Collect and verify product model and serial number early in the call to ensure appropriate guidance. --- ### Coach Appendix - **Highest-signal weekly trend**: Incorrect reset and pairing procedures for Velop/MX devices led to unresolved issues and customer frustration. - **Recurring technical pattern**: Premature escalation to paid support without exhausting free troubleshooting options and failure to verify warranty status before offering support paths. - **Evidence**: Evidence already surfaced in the main report, including incorrect reset durations, unsupported pairing methods, and incomplete warranty verification. --- ### This Week's Calls | Case | Date | Score | Direction | Product | Category | Outcome | |---|---|---|---|---|---|---| | [#LTS00107115](https://linksys.happyfox.com/staff/ticket/107115/) | 2026-05-25 | 3.00 | INBOUND | MR8300 | CONNECTIVITY | ✓ Resolved | | [#LTS00117148](https://linksys.happyfox.com/staff/ticket/117148/) | 2026-05-25 | 2.80 | INBOUND | MBE7000 | CONNECTIVITY | ✓ Likely resolved | | [#LTS00130795](https://linksys.happyfox.com/staff/ticket/130795/) | 2026-05-25 | 3.00 | INBOUND | WHW03 | CONNECTIVITY | ✓ Likely resolved | | [#LTS00130802](https://linksys.happyfox.com/staff/ticket/130802/) | 2026-05-26 | 3.00 | INBOUND | WHW03 | CONNECTIVITY | ✓ Resolved | | [#LTS00130966](https://linksys.happyfox.com/staff/ticket/130966/) | 2026-05-26 | 3.00 | INBOUND | E5400 | CONNECTIVITY | ✓ Likely resolved | | [#LTS00084720](https://linksys.happyfox.com/staff/ticket/84720/) | 2026-05-26 | 2.80 | INBOUND | WHW03 | SETUP | ✓ Likely resolved | | [#LTS00081570](https://linksys.happyfox.com/staff/ticket/81570/) | 2026-05-27 | 3.00 | INBOUND | WHW03 | CONNECTIVITY | ✓ Likely resolved | | [#LTS00131113](https://linksys.happyfox.com/staff/ticket/131113/) | 2026-05-27 | 1.00 | INBOUND | EA6400 | CONNECTIVITY | ⚠ Closed incorrectly | | [#LTS00131113](https://linksys.happyfox.com/staff/ticket/131113/) | 2026-05-27 | 3.00 | INBOUND | EA6400 | CONNECTIVITY | ⏳ Pending | | [#LTS00131131](https://linksys.happyfox.com/staff/ticket/131131/) | 2026-05-28 | 3.00 | INBOUND | MX4200 | CONNECTIVITY | ✓ Likely resolved | | [#LTS00131133](https://linksys.happyfox.com/staff/ticket/131133/) | 2026-05-28 | 1.10 | INBOUND | MX8500 | SETUP | ⏳ Pending | | [#LTS00131133](https://linksys.happyfox.com/staff/ticket/131133/) | 2026-05-28 | 3.00 | OUTBOUND | MX8500 | SETUP | ✓ Likely resolved | | [#LTS00131157](https://linksys.happyfox.com/staff/ticket/131157/) | 2026-05-28 | 3.00 | INBOUND | EA8300 | ACCESS | ⏳ Pending | | [#LTS00131165](https://linksys.happyfox.com/staff/ticket/131165/) | 2026-05-28 | 1.60 | INBOUND | MR6350 | SETUP | ↻ Callback set | | [#LTS00131165](https://linksys.happyfox.com/staff/ticket/131165/) | 2026-05-28 | 1.10 | INBOUND | MR6350 | SETUP | ⏳ Pending | | [#LTS00131317](https://linksys.happyfox.com/staff/ticket/131317/) | 2026-05-28 | 3.00 | INBOUND | WHW01 | SETUP | ✓ Likely resolved | | [#LTS00131339](https://linksys.happyfox.com/staff/ticket/131339/) | 2026-05-28 | 3.00 | INBOUND | EA9500 | CONNECTIVITY | ⚠ Closed incorrectly | | [#LTS00131344](https://linksys.happyfox.com/staff/ticket/131344/) | 2026-05-28 | 2.30 | INBOUND | EA7500 | ACCESS | ⏳ Pending | | [#TE00131348](https://linksys.happyfox.com/staff/ticket/131348/) | 2026-05-28 | 1.40 | INBOUND | MX4200 | ACCESS | ↑ Escalated | | [#LTS00076343](https://linksys.happyfox.com/staff/ticket/76343/) | 2026-05-28 | 1.10 | INBOUND | MR5500 | CONNECTIVITY | — | | [#LTS00131486](https://linksys.happyfox.com/staff/ticket/131486/) | 2026-05-29 | 3.00 | INBOUND | WHW03 | SETUP | ⏳ Pending | | [#LTS00131514](https://linksys.happyfox.com/staff/ticket/131514/) | 2026-05-29 | 3.40 | INBOUND | MX4200 | SETUP | ✓ Resolved | | [#LTS00131512](https://linksys.happyfox.com/staff/ticket/131512/) | 2026-05-29 | 3.00 | INBOUND | MX2000 | SETUP | ⏳ Pending | | [#LTS00131516](https://linksys.happyfox.com/staff/ticket/131516/) | 2026-05-30 | 1.50 | INBOUND | E2500 | CONNECTIVITY | ⏳ Pending | | [#LTS00081622](https://linksys.happyfox.com/staff/ticket/81622/) | 2026-05-30 | 1.00 | INBOUND | MX2000 | SETUP | ⏳ Pending |