# noha.magdy@sutherlandglobal.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 | |---|---|---|---|---|---| | 1 | 80m 33s | LN1200 | SETUP | 1 | 1 | ## Scorecard | Dimension | This Week | Calls Reviewed | |---|---|---| | Accuracy | 2.00 | 1 | | Protocol | 2.00 | 1 | | Communication | 2.00 | 1 | | Overall | 3.00 | 1 | *Based on 1 calls reviewed. Score range: 3.00 (lowest) to 3.00 (highest).* ## This Week's Coverage ### Models Supported | Model | Calls | Avg Score | |---|---|---| | LN1200 | 1 | 3.00 | ### Problem Categories | Category | Calls | Avg Score | Focus Area? | |---|---|---|---| | SETUP | 1 | 3.00 | | --- ## What Went Well ### Appropriate escalation after exhausting troubleshooting options > Escalated the case appropriately after exhausting available troubleshooting options. [#TE00130713](https://linksys.happyfox.com/staff/ticket/130713/) ### Empathy displayed at call conclusion > Displayed empathy at the end of the call, acknowledging customer frustration. [#TE00130713](https://linksys.happyfox.com/staff/ticket/130713/) --- ## Growth Opportunities ### Incorrect product identification and troubleshooting path The agent did not ask for or confirm the product model early in the call, leading to an incorrect troubleshooting path and the use of an invalid admin URL. **Good looks like:** confirming the exact product model (LN1200 in this case) within the first 30 seconds, then referencing the correct admin URL (`myrouter.info`) and standard mesh-rebuild steps. [#TE00130713](https://linksys.happyfox.com/staff/ticket/130713/) ### Extended unexplained hold time The call included a 9‑minute unexplained hold that impacted efficiency and customer experience. **Good looks like:** limiting holds to under 2 minutes and always explaining the reason, next step, and expected return time before placing the customer on hold. [#TE00130713](https://linksys.happyfox.com/staff/ticket/130713/) --- ## Next Week's Focus - **Confirm product model in the first 30 seconds** of every call. If the customer mentions “extender” or “mesh,” ask for the exact product name/model number right away. - **Reference the correct admin URL** (`myrouter.info` for LN1200, MR9000, WHW, MX, and Velop) as soon as the model is confirmed. - **Use the full mesh-rebuild procedure** for Cognitive Mesh devices: factory reset all nodes, 5‑press pairing, then verify via `myrouter.info`. Document each step clearly. - **Keep holds under 2 minutes** and always explain why you’re putting the customer on hold, what you’re doing, and when you’ll return. --- ## Technical Accuracy ### **Improvement** Agent provided incorrect router admin URL (`[REDACTED_PHONE]`) for an LN1200 device that requires `myrouter.info`. This error stemmed from late product model identification (73:43 into the call). [#TE00130713](https://linksys.happyfox.com/staff/ticket/130713/) ### **Improvement** Agent failed to follow standard full-mesh rebuild procedure for Cognitive Mesh devices (reset all, 5‑press pairing, verify via `myrouter.info`). Troubleshooting steps were chaotic and contradictory. [#TE00130713](https://linksys.happyfox.com/staff/ticket/130713/) ### **Strength** Agent eventually identified product model as LN1200 and collected full serial numbers, enabling proper escalation. [#TE00130713](https://linksys.happyfox.com/staff/ticket/130713/) --- ## Coaching Moments ### **Strength** Appropriate escalation > Escalated the case appropriately after exhausting available troubleshooting options. [#TE00130713](https://linksys.happyfox.com/staff/ticket/130713/) ### **Strength** Empathy at conclusion > Displayed empathy at the end of the call, acknowledging customer frustration. [#TE00130713](https://linksys.happyfox.com/staff/ticket/130713/) --- ## Escalation Lessons: What L2 Did ### [#TE00130713](https://linksys.happyfox.com/staff/ticket/130713/) — Resolved by Level 2 **What L1 saw:** Customer had an LN1200 mesh system where nodes would not join or stay connected, the admin page was unreachable, and signal dropped when moving away from the main unit. **Why it escalated:** L1 exhausted troubleshooting options and correctly escalated after gathering device details but did not resolve the core mesh-rebuild issue. **What L2 did:** 1. Requested LED colors and Wi‑Fi bar count to assess signal and node state. 2. Guided the customer through a full mesh rebuild: wired connection to main unit, access via `myrouter.info`, factory reset of all nodes, and 5‑press pairing. 3. Verified connectivity after rebuild and provided follow‑up steps if issues persisted. **Current state:** Resolved. **L1 learning points:** - For LN1200 and other Cognitive Mesh devices, always use `myrouter.info` as the admin URL, not IP addresses. - When nodes fail to join, start with a full mesh rebuild: reset all devices, then 5‑press pair from the main unit. - Collect LED statuses and Wi‑Fi bar counts early to diagnose signal or pairing issues before escalating. --- ## Coach Appendix **Weekly trend:** The agent handled one complex setup call involving an LN1200 mesh system. Strengths included appropriate escalation and empathy, while key challenges involved late product identification, incorrect admin URL usage, and an extended unexplained hold. Focus for next week: confirm product model early, use correct admin URLs, and apply the standard mesh-rebuild procedure for Cognitive Mesh devices. --- ## This Week's Calls | Case | Date | Score | Direction | Product | Category | Outcome | |---|---|---|---|---|---|---| | [#TE00130713](https://linksys.happyfox.com/staff/ticket/130713/) | 2026‑05‑25 13:20:28 | 3 | INBOUND | LN1200 | SETUP | ↑ Escalated |