Coaching Summary
Performance is developing with strong technical execution but requires improvement in accuracy and verification to move toward proficiency.
Tends to provide clear step-by-step guidance but occasionally delivers factually incorrect information and skips verification steps.
Key calls: #LTS00134188, #LTS00134734, #LTS00134738
Risk Flags
Incorrect Guidance
Provided materially false information about Linksys cloud service discontinuation and mesh compatibility between Wi‑Fi 6 and Wi‑Fi 7 devices.
ExampleIn #LTS00134734, agent stated 'they will work they are compatible sir' about mixing SPNM60 (Wi‑Fi 6) and SPNM57 (Wi‑Fi 7) nodes, contradicting KB.
Correct behavior: Reference velop_mesh_compatibility.md; only same-generation nodes may be mixed. Verify cloud service status per current KB before stating availability.
Impact: Risk of unstable mesh network and misleading claims about remote access capabilities.
Related: #LTS00134188, #LTS00134734
Protocol Violation
Failed to verify WAN/Internet connection before proceeding with configuration changes on WHW03 mesh calls.
ExampleIn #LTS00134415, agent instructed 5-press reset and node reconfiguration without first confirming internet connectivity at the modem level.
Correct behavior: Always verify basic connectivity (e.g., modem lights, wired connection) before advanced troubleshooting to avoid unnecessary steps.
Impact: Wasted time and potential misdiagnosis if underlying connectivity issues persist.
Related: #LTS00134415
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.76 | 12 |
| Technical Accuracy | 2.67 | 12 |
| Protocol | 2.75 | 12 |
| Communication | 2.83 | 12 |
V2 Rubric (Shadow Grading)
V2 overall: 70.88% across 12 v2-scored calls this week
| Category | Week Average |
|---|---|
| Resolution | 3.57 |
| Technical Accuracy | 3.49 |
| Communication | 3.12 |
| Customer Ownership | 4.19 |
| Escalation Judgment | 0.0 |
| Customer Experience | 3.39 |
- Successful Resolution: 5
- Partial Resolution: 4
- Unresolved: 3
Score Diagnostics
Based on 12 calls reviewed this week.
Technical Findings
improvement
Provided factually incorrect statement about remote Linksys cloud access being unavailable for SPNM60 model, contradicting KB guidance.
#LTS00134188 · call 077257fc-6e12-11f1-87ba-42010a62006f
improvement
Claimed default admin password is 'admin' for SPNMX55 without confirming model-specific defaults, which may not apply to ISP-provisioned devices.
#LTS00134730 · call 550e7e66-7072-11f1-a6e0-42010a62006f
improvement
Advised 5-press pairing on WHW03 parent node before verifying WAN/Internet connection and collecting full serial number/warranty status.
#LTS00134415 · call b1d24670-6eef-11f1-80a5-42010a62006f
improvement
Directed customer to http://[REDACTED_PHONE] for extender setup instead of the correct http://extender.linksys.com URL.
#LTS00134738 · call 5e746076-7084-11f1-b27d-42010a623f91
strength
Correctly guided SPNM60 customer through local web interface access, password reset via recovery key, and node re-pairing, resulting in solid white LEDs.
#LTS00134585 · call a56f8278-6fab-11f1-9ee0-42010a623f91
Call Handling Findings
- Incorrect Product GuidanceVerify mesh generation compatibility using KB before advising configurations; reference velop_mesh_compatibility.md for cross-generation rules.
- Incomplete VerificationAfter making changes, guide the customer to test connectivity (e.g., reconnect devices, load a website) and confirm stability before closing.
Calibration Notes
- Escalation_judgment score was null despite clear escalation need; human review recommended to verify grading logic for protocol violations.
- Overall score of 1.8 with accuracy 1.0 suggests potential grading inconsistency; human review needed to assess if low accuracy was justified.
Callback Chains
No callback chains detected.
Documentation Mismatches
No documentation mismatches found.
Suggested Coaching Conversation
1
Your clear, step-by-step guidance on the SPNM60 mesh setup in #LTS00134585 was excellent—let's discuss how we can consistently apply that level of precision across all calls.
2
In #LTS00134734, you mentioned Wi‑Fi 6 and Wi‑Fi 7 nodes are compatible. Let's review the mesh compatibility KB together to ensure we reference accurate rules.
3
You've done well at collecting model numbers early, which helps us avoid missteps. How can we build on that to also verify connectivity status before diving into advanced troubleshooting?
4
Verifying post-change connectivity seems to be an area for growth. Can we role-play a scenario where we confirm a fix before closing the call?
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 |
|---|---|---|---|---|---|---|---|---|---|---|
| #LTS00134188INBOUND | 2026-06-22 | — | 3.3 | 3 | 3 | 3 | 83.5% Developing | SPNM60CF | CONNECTIVITY | Router accessed, child nodes re-added and now show solid white; issue resolved. |
| #LTS00134210INBOUND | 2026-06-22 | — | 2.8 | 3 | 4 | 2 | 61.0% Needs Improvement | SPNM60TB | CONNECTIVITY | SSID rename and security settings saved; customer to reconnect devices and monitor performance. No further troubleshooting performed on-site. |
| #LTS00134415INBOUND | 2026-06-23 | — | 2.8 | 1 | 2 | 2 | 76.8% Developing | WHW03 | HARDWARE | Wi-Fi name and password updated; nodes appear online. Customer advised to reinstall the Linksys app and verify connectivity. |
| #LTS00113027INBOUND | 2026-06-23 | — | 2.8 | 1 | 2 | 3 | 36.7% Needs Improvement | E5350 | CONNECTIVITY | Advised the customer to contact the Dish technician/installer to resolve the issue or return the device, as it is not a Linksys product ([13:00]). |
| #LTS00134585INBOUND | 2026-06-24 | — | 3 | 3 | 2 | 3 | 95.8% Meets / Exceeds | SPNM60CF | ACCESS | New admin password set; router and mesh nodes are now online. |
| #LTS00134586INBOUND | 2026-06-24 | — | 1.1 | 1 | 1 | 2 | 36.9% Needs Improvement | SPNMX56TB | CONNECTIVITY | No resolution; advised customer to call back (no scheduled callback). |
| #LTS00134612INBOUND | 2026-06-24 | — | 2.8 | 5 | 4 | 3 | 79.9% Developing | MX2000 | CONNECTIVITY | Monitor node LEDs; if they remain solid blue, relocate the node. If they revert to red/flashing, call back. Ticket LCS001 opened for follow‑up. |
| #LTS00134730INBOUND | 2026-06-25 | — | 3.1 | 4 | 4 | 3 | 71.6% Developing | SPNMX55 | ACCESS | Password reset completed; customer given instructions to hide SSID via local UI. No final verification of SSID status. |
| #LTS00134734INBOUND | 2026-06-25 | — | 2.1 | 1 | 3 | 3 | 75.2% Developing | SPNMX57CF | SETUP | Setup completed in app, but network is likely unstable due to incompatible mesh generations. Customer should be advised to use only same-generation nodes for stable operation. |
| #LTS00134738INBOUND | 2026-06-25 | — | 1.8 | 1 | 1 | 3 | 48.8% Needs Improvement | MX4200 | CONNECTIVITY | Created a support case and advised the customer to consider returning the device to Amazon; further debugging to be performed on a callback. |
| #LTS00134764INBOUND | 2026-06-25 | — | 3.6 | 4 | 3 | 3 | 87.7% Meets / Exceeds | MX6200 | CONNECTIVITY | Router is online and internet works; issue resolved. |
| #LTS00134919INBOUND | 2026-06-26 | — | 3.9 | 5 | 4 | 4 | 96.7% Meets / Exceeds | SPNM60CF | CONNECTIVITY | Wi‑Fi performance appears improved after separating the networks; monitor and contact support if the issue returns. |