Coaching Summary
Stable performance with critical gaps in MX device LED interpretation and escalation documentation.
Tends to misapply 5-press reset on non-supported models and under-document escalations.
Key calls: #TE00136055, #LTS00135960
Risk Flags
Escalated but unresolved
2 escalations lacked documentation of L1 observations and next steps.
ExampleMX2000 access case #TE00136055 escalated without noting IP conflict or callback promise.
Correct behavior: Document key findings and next steps in HappyFox before escalating.
Impact: Delayed L2 resolution and potential repeat calls.
Related: #TE00136055
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.34 | 45 |
| Technical Accuracy | 2.44 | 45 |
| Protocol | 1.89 | 45 |
| Communication | 2.29 | 45 |
V2 Rubric (Shadow Grading)
V2 overall: 46.99% across 40 v2-scored calls this week2 auto-zeros
| Category | Week Average |
|---|---|
| Resolution | 2.11 |
| Technical Accuracy | 1.9 |
| Communication | 2.72 |
| Customer Ownership | 3.66 |
| Escalation Judgment | 2.67 |
| Customer Experience | 1.96 |
- Unresolved: 17
- Partial Resolution: 11
- Successful Resolution: 7
- Appropriate Escalation: 3
- Ownership Gap: 2
Score Diagnostics
Based on 45 calls reviewed this week.
Technical Findings
improvement
LN1400 requires Pair button method per universal_mesh_node_management.md; 5-press caused repeated failures.
#LTS00135960 · call c8939672-7942-11f1-a1dc-42010a623f91
improvement
Escalated MX2000 IP conflict without documenting shifting IPs ([REDACTED_PHONE], [REDACTED_PHONE]) or Cox redirection observed.
#TE00136055 · call b7e010c6-796f-11f1-b0d9-42010a623f91
Call Handling Findings
- LED State InterpretationReference KB led_intelligent_mesh_consumer.md: solid blue = online, ready for configuration.
- Escalation DocumentationDocument key findings (e.g., IP shifts, LED behavior) and promised callbacks in HappyFox.
Calibration Notes
- Short call (19m) with low accuracy (1) but clear technical errors; review for grading consistency.
Callback Chains
No callback chains detected.
Documentation Mismatches
No documentation mismatches found.
Suggested Coaching Conversation
1
Your calm handling of frustrated customers on MX2000 cases shows strong empathy—we should leverage this in training.
2
Let's review the LED state guide together: how do we differentiate between 'solid blue' (online) and 'flashing red' (error) on MX series?
3
When escalating, what specific details should we always capture in HappyFox to help L2 engineers?
4
How can we verify customer understanding before proceeding with advanced steps like IP changes?
Coaching Best Practices
Five Principles for Effective Coaching Conversations
- SBI feedback model — Describe the Situation, the Behavior you observed, and its Impact. Avoid labels (“you always…”) — describe the specific instance.
- Ask more than you tell — Start with “What did you notice on that call?” before offering your interpretation. Agents who self-diagnose retain more.
- Recognition before correction — Open with a genuine strength observation. Agents in a defensive posture can’t hear coaching.
- Psychological safety first — Frame mistakes as data, not character. “That call had a tricky wrinkle — let’s pull it apart” lands better than “you made an error here.”
- Close with a specific commitment — End every coaching conversation with one thing the agent will try on their next call, and a follow-up check-in within 48 hours.
Deep Evidence
| Case | Date | Duration | Overall | Accuracy | Protocol | Comms | V2 | Product | Issue Type | Outcome |
|---|---|---|---|---|---|---|---|---|---|---|
| #LTS00135960INBOUND↩ cb | 2026-07-06 | — | 1.2 | 1 | 2 | 2 | 16.7% Needs Improvement | LN1400 | CONNECTIVITY | No resolution achieved. Customer needs to use correct Pair button method for LN1400 and recover cloud account via password reset at https://linksyssmartwifi.com. |
| #LTS00135369INBOUND | 2026-07-06 | — | 2.8 | 2 | 2 | 2 | 74.0% Developing | LN1100 | CONNECTIVITY | Customer reported Wi-Fi now connects; no further action required. |
| #LTS00135960INBOUND↩ cb | 2026-07-06 | — | 1 | 1 | 1 | 1 | 0.0% Needs Improvement | LN1400 | CONNECTIVITY | None – agent did not respond or engage. |
| #LTS00135960INBOUND↩ cb | 2026-07-06 | — | 1.8 | 5 | 1 | 2 | — | LN1400 | CONNECTIVITY | No resolution or next step provided. |
| #LTS00135978INBOUND | 2026-07-06 | — | 3.8 | 5 | 4 | 4 | 64.2% Needs Improvement | MR7310 | CONNECTIVITY | Advised that the MR7320 is end-of-support and may be the performance bottleneck; recommended hardware upgrade. |
| #LTS00135991INBOUND | 2026-07-06 | — | 2.8 | 1 | 2 | 2 | 49.2% Needs Improvement | MR7500 | CONNECTIVITY | Both extenders now show solid blue, indicating they are successfully added to the mesh network. However, internet connectivity was not verified, and the agent provided incorrect technical guidance during the call. |
| #LTS00135592INBOUND | 2026-07-06 | — | 2.8 | 1 | 2 | 2 | 16.5% Needs Improvement | EA8300 | CONNECTIVITY | Suggested upgrading the EA8300 router due to legacy status. |
| #LTS00136032INBOUND↩ cb | 2026-07-06 | — | 1.8 | 1 | 2 | 2 | 69.0% Needs Improvement | LN11011202 | CONNECTIVITY | Wired speed now matches ISP; Wi-Fi speed still low. Agent scheduled a callback for further investigation. |
| #LTS00136032OUTBOUND↩ cb | 2026-07-06 | — | 3.2 | 4 | 2 | 3 | 60.1% Needs Improvement | LN11011202 | CONNECTIVITY | Phone speed improved after disabling 2.4 GHz; monitor performance and email ticket sent for reference. |
| #TE00136055INBOUND | 2026-07-06 | — | 1.8 | 1 | 2 | 2 | 53.0% Needs Improvement | MX2000 | ACCESS | Escalated to Level-2 technician; callback promised. |
| #LTS00136084INBOUND | 2026-07-06 | — | 1.8 | 1 | 2 | 3 | 47.5% Needs Improvement | MR20EC | CONNECTIVITY | Customer will test the guest network after IPv6 is disabled and will call back if the problem remains. |
| #EOS00136176INBOUND | 2026-07-07 | — | 3.5 | 5 | 2 | 3 | 32.5% Needs Improvement | E5400 | ACCESS | Agent will email the customer detailed instructions for logging into the router locally and changing the SSID and password. |
| #LTS00136196INBOUND | 2026-07-07 | — | 2.8 | 3 | 2 | 2 | 33.5% Needs Improvement | MBE7000 | SETUP | Router admin access restored; Wi‑Fi name and password changed. Customer advised to reconnect devices to the new network. |
| #LTS00136209INBOUND | 2026-07-07 | — | 2.2 | 4 | 2 | 2 | 0.0% Needs Improvement | MX2000 | CONNECTIVITY | No resolution achieved. Customer advised to monitor app and run speed test with no further guidance. |
| #EOS00136240INBOUND | 2026-07-07 | — | 2.8 | 3 | 2 | 3 | — | EA9500 | CONNECTIVITY | Agent will send an email with setup instructions; no immediate fix applied. |
| #LTS00136267INBOUND↩ cb | 2026-07-07 | — | 1.8 | 2 | 2 | 2 | 32.5% Needs Improvement | MX2000 | CONNECTIVITY | Advise customer to test the modem directly (connect a laptop via Ethernet) to confirm WAN connectivity, then contact ISP if the modem shows no IP. If the modem works, schedule a higher‑level escalation within Linksys. |
| #LTS00136272INBOUND | 2026-07-07 | — | 2.9 | 2 | 2 | 3 | 67.6% Needs Improvement | MX2000 | CONNECTIVITY | Main router successfully reset via 5-press method; internet restored. Customer advised to reset child nodes individually if needed, but guidance was technically incorrect. |
| #EOS00136277INBOUND | 2026-07-07 | — | 2.8 | 3 | 2 | 2 | 24.2% Needs Improvement | WRT1200AC | HARDWARE | Agent will send an email with setup instructions; customer to follow the guide independently. |
| #LTS00136267INBOUND↩ cb | 2026-07-07 | — | 1.8 | 5 | 1 | 2 | — | MX2000 | CONNECTIVITY | Callback scheduled; customer instructed to keep phone charged and wait for call. |
| #LTS00136267OUTBOUND↩ cb | 2026-07-07 | — | 2.8 | 5 | 2 | 2 | 53.7% Needs Improvement | MX2000 | CONNECTIVITY | Customer to contact Spectrum to reprovision the old internet modem with the correct MAC address and then call back for further assistance. |
| #LTS00136363INBOUND | 2026-07-08 | — | 3.4 | 4 | 2 | 2 | 95.8% Meets / Exceeds | MX5500 | CONNECTIVITY | Wi-Fi network restored; customer can reconnect devices. No further action required. |
| #EOS00136393INBOUND | 2026-07-08 | — | 1.4 | 1 | 2 | 2 | 9.9% Needs Improvement | WRT54G | ACCESS | Agent will send an email with instructions; customer to apply them after the call. |
| #LTS00136397INBOUND | 2026-07-08 | — | 2.8 | 2 | 4 | 3 | 79.6% Developing | MX6200 | CONNECTIVITY | Child node re-paired and firmware updated; customer reported improved Wi-Fi stability. |
| #TE00136407INBOUND | 2026-07-08 | — | 2.8 | 5 | 2 | 2 | 56.9% Needs Improvement | MX6200 | ACCESS | Escalated to Level-2 technician; case number to be provided. |
| #EOS00136357INBOUND | 2026-07-08 | — | 2.2 | 3 | 2 | 2 | 34.3% Needs Improvement | ACCESS | None confirmed. Customer was to try reset steps, but no follow-up scheduled or verification performed. | |
| #EOS00136413INBOUND | 2026-07-08 | — | 2.8 | 1 | 2 | 2 | 15.8% Needs Improvement | WHW03V2 | GENERAL INQUIRY | Agent will send email with instructions for resetting and pairing the VLP01 extender, despite incompatibility with Velop mesh. |
| #EOS00136434INBOUND | 2026-07-08 | — | 1.3 | 1 | 1 | 2 | — | EA6350 | ACCESS | Agent promised to email password-reset instructions, but email address was not captured. |
| #LTS00136538INBOUND↩ cb | 2026-07-09 | — | 1 | 1 | 1 | 1 | — | WHW03 | CONNECTIVITY | No resolution or next step provided; call ended abruptly. |
| #LTS00136538OUTBOUND↩ cb | 2026-07-09 | — | 1.4 | 2 | 1 | 2 | 14.6% Needs Improvement | WHW03 | CONNECTIVITY | No resolution achieved. Customer left with incorrect instructions and no confirmation of success or clear next steps. |
| #LTS00136538OUTBOUND↩ cb | 2026-07-09 | — | 1.1 | 1 | 1 | 2 | 80.1% Developing | WHW03 | CONNECTIVITY | None provided. Call ended with customer still unable to access admin interface. |
| #EOS00136565INBOUND↩ cb | 2026-07-09 | — | 1.1 | 1 | 1 | 2 | 18.8% Needs Improvement | E8450 | HARDWARE | Agent promised to send generic troubleshooting instructions via email; no immediate resolution or actionable steps provided. |
| #EOS00136565OUTBOUND↩ cb | 2026-07-09 | — | 2.6 | 4 | 2 | 2 | 65.5% Needs Improvement | CONNECTIVITY | Escalated to Level 2 technical team; callback scheduled. | |
| #LTS00136571INBOUND | 2026-07-09 | — | 1 | 1 | 1 | 1 | 14.6% Needs Improvement | MX4200 | CONNECTIVITY | not_fixed |
| #LTS00136594INBOUND | 2026-07-09 | — | 3.6 | 4 | 3 | 3 | 75.3% Developing | MX5500 | CONFIGURATION | Both issues resolved: 2.4 GHz network now visible and printer accessible; previously faulty mesh node now stable with solid blue light. |
| #LTS00136680INBOUND | 2026-07-10 | — | 1.7 | 1 | 1 | 3 | 57.6% Needs Improvement | WHW0301CF | CONNECTIVITY | No resolution achieved. Customer left with unstable node (flashing red/blue). No valid next step provided. |
| #LTS00136687INBOUND | 2026-07-10 | — | 3.3 | 5 | 2 | 3 | 76.3% Developing | MX4200 | CONFIGURATION | Customer created a separate 2.4 GHz SSID and reported being able to select it. No further action required. |
| #LTS00136694INBOUND | 2026-07-10 | — | 4 | 4 | 3 | 4 | 70.3% Developing | WHW03 | SETUP | Node paired successfully; customer advised to relocate the node. |
| #LTS00136697INBOUND↩ cb | 2026-07-10 | — | 2.8 | 2 | 3 | 3 | 64.7% Needs Improvement | WHW03 | CONNECTIVITY | Customer needs to replace the Ethernet cable between modem and router with a certified gigabit (Cat-5e or Cat-6) cable and retest speed. |
| #LTS00136697INBOUND↩ cb | 2026-07-10 | — | 3.6 | 2 | 2 | 3 | 84.4% Developing | WHW03 | CONNECTIVITY | Issue resolved; no further action needed. |
| #EOS00136711INBOUND | 2026-07-10 | — | 3 | 4 | 3 | 3 | 37.5% Needs Improvement | RE6500 | ACCESS | Sent email with step‑by‑step setup instructions; customer to complete setup and verify connectivity. |
| #EOS00136720INBOUND | 2026-07-10 | — | 2.8 | 1 | 2 | 2 | 37.5% Needs Improvement | IA6350 | ACCESS | Agent will send email with instructions for parental controls. |
| #LTS00049494INBOUND | 2026-07-10 | — | 2.8 | 1 | 1 | 3 | 64.6% Needs Improvement | MR9610 | CONNECTIVITY | Customer accessed admin page, changed Wi-Fi name/password, router now solid blue. |
| #LTS00038144INBOUND | 2026-07-10 | — | 1 | 1 | 1 | 1 | 0.0% Needs Improvement | EA7500 | CONFIGURATION | No resolution; call ended without next steps. |
| #LTS00136729INBOUND | 2026-07-10 | — | 2.8 | 2 | 2 | 3 | 54.2% Needs Improvement | SPNMX56CF | CONNECTIVITY | Node appeared in app; customer believes it is connected. No verification of correct pairing method or web UI performed. Recommend confirming model number and using correct 5-press (parent) or Pair button method per KB. |
| #LTS00082441INBOUND | 2026-07-10 | — | 1 | 1 | 1 | 1 | 77.2% Developing | MX6200 | CONNECTIVITY | not_fixed |
Feedback
✓ Feedback submitted — thank you!