# 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 | *Score range: lowest 2.00, highest 3.00 across 1 calls reviewed.* --- ## Where Time Goes ### Models Supported | Model | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | |---------|-------|-----------------|-------------|--------------|--------------|-------------------| | LN1200 | 1 | 80m 33s | 3.00 | 2.00 | 2.00 | 2.00 | **Key Pattern**: The single LN1200 call consumed exceptionally long handle time (80m 33s) while achieving only moderate scores across all dimensions. This suggests the agent encountered significant challenges with this specific product that impacted both efficiency and effectiveness. ### Problem Categories | Category | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Focus Area? | |----------|-------|-----------------|-------------|--------------|--------------|-------------------|-------------| | SETUP | 1 | 80m 33s | 3.00 | 2.00 | 2.00 | 2.00 | ✓ | **SETUP Focus Area**: The setup category shows a clear pattern of inefficiency and lower performance. The extended handle time combined with moderate scores indicates a need for more structured troubleshooting approaches and better early case framing for setup-related issues. --- ## Week-over-Week Movement *No prior-week comparison data available to analyze movement patterns.* --- ## What Went Well ### Escalation and Information Collection You effectively gathered critical device information when it mattered most, enabling proper escalation. This deliberate focus on collecting serial numbers and model details ensured the next team had what they needed to resolve the issue. ### Empathy in Closure You closed the call with genuine acknowledgment of the customer's frustration, which is essential for maintaining trust even when technical resolution isn't fully achieved at Level 1. This empathetic closing helped preserve the customer's perception of support quality despite the challenges encountered. --- ## Growth Opportunities ### Streamline Early Troubleshooting with Correct Product Identification **What better looks like**: Start every mesh-related call by confirming the exact product model within the first 30 seconds. For LN1200 devices specifically: - Verify the device is part of the Cognitive Mesh family - Use `myrouter.info` (not IP addresses) for admin interface access - Follow the standard full-mesh rebuild procedure: reset all nodes → 5-press pairing → verification via myrouter.info > This prevents the wasted time and confusion from using incorrect troubleshooting paths for specific product families. ### Manage Hold Times Proactively **What better looks like**: When holds are necessary (e.g., checking backend systems or waiting for customer actions), set clear expectations immediately: - State the expected hold duration ("I'll be with you again in about 5 minutes while I check this for you") - Provide regular updates if holds extend beyond estimates - Avoid extended unexplained holds that erode customer confidence and impact efficiency metrics > This transforms holds from frustrating silences into moments of professionalism and transparency. --- ## Next Week's Focus - **Practice the 30-second product identification script** for all mesh calls: "To ensure I guide you correctly, could you confirm the exact model name on your device label? Is this an LN1200, WHW, MX, or another model?" - **Create a quick reference cheat sheet** for LN1200-specific troubleshooting: admin URL (myrouter.info), pairing method (5-press), common LED states, and verification steps. - **Set hold time expectations** at the first mention of a hold: "I'll need to check this for you - I'll be right back in about 3 minutes while I gather the necessary information." - **Review full mesh rebuild procedures** for Cognitive Mesh devices, focusing on the sequence: reset → 5-press pairing → verification via myrouter.info. --- ## Technical Accuracy ### **Improvement** Failed to identify product model early (LN1200), leading to incorrect admin URL ([REDACTED_PHONE]) for a device that requires myrouter.info. [#TE00130713](https://linksys.happyfox.com/staff/ticket/130713/) ### **Improvement** Did not follow standard full-mesh rebuild procedure for Cognitive Mesh devices (reset all, 5-press pairing, verify via myrouter.info). [#TE00130713](https://linksys.happyfox.com/staff/ticket/130713/) ### **Improvement** Extended unexplained hold time (~9 minutes) without communication, impacting customer experience. [#TE00130713](https://linksys.happyfox.com/staff/ticket/130713/) --- ## Coaching Moments ### **Strength** > DISPLAYED EMPATHY AT THE END OF THE CALL, ACKNOWLEDGING CUSTOMER FRUSTRATION. *Note*: This empathetic closing helped maintain trust despite technical limitations. Continuing this approach will support positive customer perceptions even when cases require escalation. [#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 with LN1200 mesh system experiencing persistent node pairing failures, inability to access admin interface, and connection drops when moving away from main unit. **Why it escalated**: L1 exhausted available troubleshooting options without resolving the core mesh connectivity issues, particularly after multiple failed reset and pairing attempts. **What L2 did**: - Performed advanced troubleshooting focusing on signal strength and physical topology - Guided customer through wired backhaul testing using a computer connected directly to the main unit - Verified LED states and Wi-Fi bar indicators to diagnose connectivity issues - Ultimately determined the child nodes required a full factory reset and rebuild using the correct myrouter.info interface **Current state**: Resolved after successful mesh rebuild and verification of proper node behavior. **L1 learning points**: 1. For LN1200 mesh issues, **always verify product model early** and use myrouter.info as the admin interface 2. When nodes won't join or stay connected, **guide customers through a full mesh rebuild**: reset all devices → use 5-press pairing → verify via myrouter.info 3. For signal drop issues when moving away, **suggest wired backhaul testing** and check LED states to identify potential hardware limitations --- ## Coach Appendix **Highest-signal weekly trend**: The single LN1200 setup call revealed critical gaps in early product identification and mesh-specific troubleshooting protocols, resulting in extended handle time and moderate scores. Focus next week should prioritize rapid model confirmation and standardized mesh rebuild procedures to improve both efficiency and effectiveness for this product category. **Key pattern for next coaching**: The agent needs to develop stronger initial diagnostic frameworks for mesh technology calls, particularly around product family identification and interface access methods, to prevent repeating similar efficiency and accuracy challenges. --- ## 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+00:00 | 3.00 | INBOUND | LN1200 | SETUP | ↑ Escalated |