noha.magdy@sutherlandglobal.com — Coaching Report

Week of 2026-05-25 – 2026-05-31

At a Glance

Scorecard

Scores reflect 1 calls reviewed. Overall score range: lowest = 3, highest = 3.

This Week's Coverage

Models Supported

No models scored below 2.5 this week.

Problem Categories

No categories require deeper drill-down this week.

What Went Well

Appropriate escalation

Escalated the case appropriately after exhausting available troubleshooting options [70:53].

#TE00130713

Empathy and customer acknowledgment

Displayed empathy at the end of the call, acknowledging customer frustration [72:04–72:25].

#TE00130713

Growth Opportunities

Confirm product model at the start of every call

The current call suffered from delayed product model identification, leading to an incorrect troubleshooting path and an invalid admin URL. What good looks like: Ask for the exact product model name (e.g., “LN1200”) within the first 30 seconds of the call and verify it against the customer’s device before proceeding with any troubleshooting.

Use the correct admin URL for LN1200 devices

Providing the wrong admin URL ([REDACTED_PHONE]) for an LN1200 device caused confusion and failed attempts. What good looks like: For LN1200 devices, always direct customers to log in at myrouter.info or myrouter.local. Confirm the URL matches the device’s cognitive mesh requirements before proceeding.

Next Week's Focus

1. Open every call with a model confirmation question — e.g., “Could you confirm the exact model name of your device? I’ll make sure we use the right steps for you.”
2. Reference the correct admin URL for LN1200 and other cognitive mesh devices — keep myrouter.info/myrouter.local top-of-mind.
3. Avoid extended unexplained holds — if you must place a customer on hold for more than 2 minutes, explain why and give a clear ETA for returning to the call.
4. Collect serial numbers and topology details early — this speeds up escalation when needed and prevents re-asking later.

Technical Accuracy

Improvement

Agent provided incorrect router admin URL ([REDACTED_PHONE]) for LN1200 device that requires myrouter.info. This led to failed troubleshooting attempts and customer confusion.

#TE00130713

Improvement

Agent failed to identify product model until 73:43 into the call, causing significant delay and use of incorrect troubleshooting path. Should have confirmed model at call start.

#TE00130713

Improvement

Extended unexplained hold time from 39:35 to 48:41 (~9 minutes), severely impacting efficiency and customer experience.

#TE00130713

Improvement

Agent attempted to use wired backhaul despite customer stating secondary nodes lack Ethernet ports [67:20], indicating poor topology understanding for mesh devices.

#TE00130713

Strength

Agent eventually identified product model as LN1200 and collected full serial number [73:43–77:33], enabling proper escalation. Also collected customer contact information for follow-up.

#TE00130713

Escalation Lessons: What L2 Did

#TE00130713 — Resolved by Level 2

What L1 saw:

Customer had an LN1200 mesh system where child 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 (resets, app pairing, URL guidance) and could not get the mesh to function; the case was handed off after collecting serial numbers and basic troubleshooting history.

What L2 did:

1. Asked about LED colors and Wi‑Fi bar count to assess signal and node state.
2. Suggested a wired connection to the main unit for direct access to myrouter.local/myrouter.info.
3. Guided the customer through a full mesh rebuild: resetting all nodes, using the 5‑press pairing method, and verifying connectivity via the web interface.
4. Confirmed resolution after the customer reported stable connectivity and proper LED behavior.

Current state: Resolved — customer confirmed stable mesh operation after following L2’s rebuild instructions.

L1 learning points:

• For LN1200 cognitive mesh devices, always start with the model name and use myrouter.info/myrouter.local for admin access.
• Before escalation, run a full mesh rebuild: factory reset all nodes, then 5‑press pairing, and verify via the web interface.
• Ask about LED colors and signal strength (Wi‑Fi bars) to quickly identify connectivity issues and avoid unnecessary steps.

Coach Appendix

Weekly trend: The sole call this week involved an LN1200 mesh setup failure. Key issues included delayed model identification, incorrect admin URL usage, extended unexplained hold time, and an attempted wired backhaul despite the customer’s statement that secondary nodes lacked Ethernet ports. While the agent appropriately escalated after exhausting options and showed empathy at the call’s end, these process gaps impacted efficiency and customer experience.

Next coaching focus: Reinforce the importance of confirming product model within the first 30 seconds of every call, especially for cognitive mesh devices, and ensure correct admin URLs (myrouter.info/myrouter.local) are used from the outset. Practice concise hold explanations and avoid topology mismatches (e.g., recommending wired backhaul to devices without Ethernet ports).

This Week's Calls