# alvin.edio@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 | |---|---|---|---|---|---| | 4 | 7m 52s | MBE7000 | CONNECTIVITY | 4 | 1 | --- ## Scorecard | Dimension | This Week | Calls Reviewed | |---|---|---| | Accuracy | 3.00 | 4 | | Protocol | 2.25 | 4 | | Communication | 2.00 | 4 | | Overall | 2.43 | 4 | *Scores reflect data from 4 calls reviewed. Overall scores ranged from 1.5 to 3.5.* --- ## This Week's Coverage ### Models Supported | Model | Calls | Avg Score | |---|---|---| | MBE7000 | 2 | 1.50 | | MX5300 | 1 | 3.50 | | WRT54G | 1 | 3.00 | **Key pattern:** Lower scores on MBE7000 calls suggest a need for stronger familiarity with this model's troubleshooting flows, especially around connectivity and performance diagnostics. ### Problem Categories | Category | Calls | Avg Score | Focus Area? | |---|---|---|---| | CONNECTIVITY | 2 | 1.50 | ✓ | | NO TROUBLESHOOTING NEEDED | 1 | 3.50 | | | SETUP | 1 | 3.00 | | | ACCESS | 1 | 1.70 | ✓ | **Connectivity and Access categories** show lower performance, indicating opportunities to strengthen diagnostic questioning and resolution pathways for these common issues. --- ## What Went Well ### Accurate EOL Product Guidance > “Informed customer that MX5300 is end-of-life with no new firmware; suggested adding nodes or upgrading to a newer model for better coverage.” *[#LTS00130800](https://linksys.happyfox.com/staff/ticket/130800/)* You correctly identified the MX5300 as end-of-life and accurately cited the final firmware release date (April 14, 2022) per KB. This clear communication helped set realistic expectations and offered constructive next steps. --- ## Growth Opportunities ### Strengthen Product Identification and Troubleshooting > “Misidentified the product as MBE70 instead of MX6200 at [03:00], leading to materially incorrect technical context.” *[#TE00128179](https://linksys.happyfox.com/staff/ticket/128179/)* **What “good” looks like:** - Always verify the exact product model and family before proceeding. For mesh systems, confirm whether it’s Velop/Intelligent Mesh (MX/EQ) or Cognitive Mesh (MBE/ME). - When performance issues arise, run at least one basic troubleshooting step (speed test, WAN check, node restart) before escalating. This validates the problem and gives you richer context for escalation. ### Provide Correct Account Management Guidance > “Advised factory reset for changing account email on EA-9300, which is incorrect. Correct method is via Linksys website/app.” *[#LTS00130806](https://linksys.happyfox.com/staff/ticket/130806/)* **What “good” looks like:** - For account-related changes (email, password, profile), always direct customers to the Linksys website or mobile app first. Explain the steps clearly and offer to stay on the line while they follow them. - Only suggest a factory reset when explicitly required by the issue (e.g., lost admin access), and always pair it with clear recovery instructions. --- ## Next Week's Focus 1. **Double-check product model and family** before any technical steps — especially for mesh systems. Use the KB’s product-family guide to confirm. 2. **Run one basic troubleshooting step** (speed test, WAN check, node restart) for any performance or connectivity issue before considering escalation. 3. **Master account-management pathways:** Keep a quick reference handy for changing email/password via the Linksys website/app, and practice guiding customers through it. 4. **Add empathy and acknowledgment** when customers express frustration or repeat issues — a brief “I understand this has been frustrating” goes a long way. --- ## Technical Accuracy ### **Improvement** > Misidentified product as MBE70 instead of MX6200, leading to incorrect technical context and no troubleshooting performed for a performance issue. [#TE00128179](https://linksys.happyfox.com/staff/ticket/128179/) — The MX6200 is a Velop/Intelligent Mesh node, while MBE70 is a Cognitive Mesh device with different firmware and pairing logic. This error caused the agent to skip basic troubleshooting (speed test, WAN check, node restart) that could have resolved or clarified the issue before escalation. ### **Improvement** > Advised factory reset for changing account email on EA-9300, which is incorrect. Correct method is via Linksys website/app. [#LTS00130806](https://linksys.happyfox.com/staff/ticket/130806/) — Changing the email address on a Linksys account is done through the website or mobile app, not by resetting the router. A factory reset would erase all settings and require reconfiguration, which is unnecessary and potentially harmful for this request. ### **Strength** > Correctly identified MX5300 as end-of-life and provided accurate last firmware date (April 14, 2022) per KB. [#LTS00130800](https://linksys.happyfox.com/staff/ticket/130800/) — The agent accurately referenced the KB documentation for end-of-life firmware and offered appropriate next steps (adding nodes or upgrading). --- ## Coaching Moments ### **Improvement** > “Misidentified the product as MBE70 instead of MX6200 at [03:00], leading to materially incorrect technical context.” [#TE00128179](https://linksys.happyfox.com/staff/ticket/128179/) Misidentifying the product family (Cognitive Mesh vs. Velop/Intelligent Mesh) derailed the technical approach. Always verify the exact model and family before troubleshooting or escalating. ### **Improvement** > “Advised factory reset for changing account email on EA-9300, which is incorrect. Correct method is via Linksys website/app.” [#LTS00130806](https://linksys.happyfox.com/staff/ticket/130806/) Providing the wrong solution for account email changes not only fails the customer but also risks additional issues from an unnecessary reset. Direct customers to the correct self-service path first. --- ## Escalation Lessons: What L2 Did ### [#TE00128179](https://linksys.happyfox.com/staff/ticket/128179/) — Resolved by Level 2 **What L1 saw:** - Customer reported buffering and poor performance after switching to business internet and replacing a mesh node with an MX6200. - L1 misidentified the device as MBE70, performed no troubleshooting, and escalated based on outdated Tier-2 notes. **Why it escalated:** - L1’s incorrect product identification and lack of basic troubleshooting steps made it impossible for L2 to proceed without re-evaluating the issue from scratch. **What L2 did:** - Reconfirmed the correct product (MX6200) and performed a full diagnostic: - Ran speed tests comparing speeds at the modem vs. mesh nodes. - Checked WAN status and VLAN configuration on the business internet connection. - Verified firmware versions on all nodes and performed a mesh reset/reconfiguration to clear artifacts from prior cloud services. - After identifying that the issue stemmed from discontinued LSWF services affecting web UI access, L2 guided the customer through a full mesh reset and reconfiguration. **Current state:** Resolved. **L1 learning points:** 1. Always verify the exact product model and family before troubleshooting or escalating. 2. For performance issues, run at least one basic troubleshooting step (speed test, WAN check, node restart) to gather data and validate the problem. 3. When in doubt about mesh node health, consider a mesh reset/reconfiguration as a safe, controlled first step — but only after confirming the correct product family. --- ## Coach Appendix *This week’s highest-signal trend is inconsistent product identification, especially for mesh systems, leading to skipped troubleshooting and escalations. Focus next week on confirming model/family upfront and running at least one basic diagnostic step for performance issues before escalation. Review the MBE vs. MX product-family KB guide and practice the speed-test/WAN-check/node-restart workflow.* --- ## This Week's Calls | Case | Date | Score | Direction | Product | Category | Outcome | |---|---|---|---|---|---|---| | [#LTS00130800](https://linksys.happyfox.com/staff/ticket/130800/) | 2026-05-25 23:53:38+00:00 | 3.5 | INBOUND | MX5300 | NO TROUBLESHOOTING NEEDED | ✓ Resolved | | [#TE00128179](https://linksys.happyfox.com/staff/ticket/128179/) | 2026-05-26 00:10:43+00:00 | 1.5 | INBOUND | MBE7000 | CONNECTIVITY | ↑ Escalated | | [#LTS00130803](https://linksys.happyfox.com/staff/ticket/130803/) | 2026-05-26 00:29:24+00:00 | 3.0 | INBOUND | WRT54G | SETUP | ✓ Likely resolved | | [#LTS00130806](https://linksys.happyfox.com/staff/ticket/130806/) | 2026-05-26 00:38:26+00:00 | 1.7 | INBOUND | EA9300 | ACCESS | ⚠ Closed incorrectly |