Coaching Summary
Performance shows technical accuracy gaps despite generally stable ownership and communication scores.
Tends to skip foundational diagnostics (WAN/modem checks) and provides model-specific LED guidance without verification.
Key calls: #LTS00134213, #LTS00134255, #LTS00134938
Risk Flags
PCI Violation
Collected full credit card numbers over unsecured phone lines without documented secure handling in 2 calls this week
ExampleIn #LTS00134938, agent recorded full card number, expiration, and security code during payment processing
Correct behavior: Use only documented secure payment gateways; never record card details over phone
Impact: Severe data breach risk and regulatory non-compliance
Related: #LTS00134938
Materially Incorrect Guidance
Provided factually wrong LED state information in 5 calls this week, contradicting KB definitions
ExampleIn #LTS00134213 told customer 'solid pink' indicates online status for WHW series nodes
Correct behavior: Reference KB for exact LED definitions per model before instruction
Impact: Customer confusion, potential hardware damage risk, and repeat calls
Related: #LTS00134213, #LTS00134247, #LTS00134935
Incomplete Diagnostics
Skipped WAN/modem verification in 4 connectivity calls before troubleshooting mesh nodes
ExampleIn #LTS00134610 began node resets without checking modem internet status
Correct behavior: Always perform modem isolation test (Step 1 in velop_wifi_connectivity.md) before node-specific steps
Impact: Misdiagnosis of ISP vs mesh issues, extended resolution times
Related: #LTS00134610, #LTS00134935, #LTS00134738, #LTS00134255
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.44 | 46 |
| Technical Accuracy | 2.2 | 46 |
| Protocol | 1.78 | 46 |
| Communication | 2.61 | 46 |
V2 Rubric (Shadow Grading)
V2 overall: 55.05% across 41 v2-scored calls this week5 auto-zeros
| Category | Week Average |
|---|---|
| Resolution | 2.38 |
| Technical Accuracy | 2.66 |
| Communication | 3.02 |
| Customer Ownership | 4.0 |
| Escalation Judgment | 2.27 |
| Customer Experience | 3.34 |
- Unresolved: 19
- Partial Resolution: 13
- Successful Resolution: 9
Score Diagnostics
Based on 46 calls reviewed this week.
Technical Findings
improvement
Provided incorrect LED state guidance ('solid pink') for WHW01 nodes in #LTS00134935, contradicting KB which defines solid purple as setup-ready state.
#LTS00134935 · call da6d63f0-7163-11f1-8c0d-42010a623f91
improvement
Advised unsupported 5-press pairing on LN1600 node in #LTS00028269; correct method is Pair button per universal_mesh_node_management.md.
#LTS00028269 · call 34314272-6f01-11f1-af7c-42010a623f91
improvement
Failed to verify modem internet connectivity before troubleshooting mesh nodes in #LTS00134610, violating Step 1 of velop_wifi_connectivity.md.
#LTS00134610 · call bd3c8b0e-6fd7-11f1-ace4-42010a62006f
strength
Correctly applied 5-press pairing method for MX4200SH nodes in #LTS00134732, resolving connectivity issues per universal_5press_models.md.
#LTS00134732 · call 85b532fa-6fa3-11f1-a83c-42010a623f91
improvement
Provided non-standard recovery reset steps (unplug/replug cycle) instead of documented 10-20s reset button hold in #LTS00134587.
#LTS00134587 · call 5cf603fa-6fc4-11f1-a6e0-42010a62006f
Call Handling Findings
- Inaccurate LED GuidanceConfirm product model first, reference KB for exact LED definitions, and validate state before proceeding.
- Omitted Critical DiagnosticsAlways verify parent node status, check WAN connectivity, and perform modem isolation before node-specific steps.
Calibration Notes
- High overall score (3.5) despite critical PCI violation (card data collection) and incomplete diagnostics; requires human review of scoring consistency
- Overall score of 3.0 with successful resolution but material LED guidance errors; needs review of T3 scoring boundaries
Callback Chains
No callback chains detected.
Documentation Mismatches
#LTS00134740low
Grader marked issue as unresolved ('No further troubleshooting or confirmation completed') while agent documentation implies successful web UI access and login.
Grader says: Use http://myrouter.info for router management. Agent to forward request for app compatibility to engineering. No further troubleshooting or confirmation completed.
Agent documented: Educated the cx that the nodes aren’t compatible with the Linksys app * Cx seems disappointed * However, informed the cx that we can still manage the system via the web UI * Cx understood * Accessed http://myrouter.info * Logged into the web UI
Suggested Coaching Conversation
1
Your calm demeanor and clear explanations were appreciated by customers this week - particularly in #LTS00134193 where you managed a frustrated customer well. Let's discuss how we can strengthen diagnostic rigor before providing model-specific instructions.
2
I noticed several instances where LED state definitions were provided without model verification (e.g., #LTS00134213). How do you approach confirming product models before giving device-specific guidance?
3
The PCI violation in #LTS00134938 highlights a critical compliance risk. Let's review secure payment handling protocols and documentation requirements.
4
Your mesh troubleshooting in #LTS00134255 skipped essential WAN verification. What steps do you take to isolate ISP vs mesh issues before proceeding with node resets?
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 |
|---|---|---|---|---|---|---|---|---|---|---|
| #LTS00134185INBOUND | 2026-06-22 | — | 3.5 | 2 | 2 | 4 | 100.0% Meets / Exceeds | WHW03 | SETUP | Node successfully paired; customer can now relocate and use it. |
| #LTS00134186INBOUND | 2026-06-22 | — | 3 | 3 | 3 | 3 | 91.7% Meets / Exceeds | SPNMX57CF | CONFIGURATION | Customer instructed to use distinct SSIDs to manually assign devices to 2.4 GHz or 5 GHz bands. No further troubleshooting or confirmation was performed on the primary device (laptop). |
| #LTS00134193INBOUND | 2026-06-22 | — | 2.8 | 1 | 2 | 2 | — | UNKNOWN | ACCESS | Provide correct guidance: access https://linksyssmartwifi.com, use 'Forgot password' or account settings to change the email, or create a new Linksys cloud account and re-associate the router. |
| #LTS00134197INBOUND | 2026-06-22 | — | 2.8 | 2 | 3 | 2 | 83.6% Developing | SPNMX56HF | CONFIGURATION | Wi-Fi disabled on router; issue resolved. |
| #LTS00134201INBOUND | 2026-06-22 | — | 3 | 2 | 2 | 4 | 61.6% Needs Improvement | SPNMX56CF | CONNECTIVITY | Node re-paired and operational; no further action required. |
| #LTS00134206INBOUND | 2026-06-22 | — | 3.8 | 5 | 3 | 2 | 72.3% Developing | SPNM60CF | ACCESS | Customer successfully logged into the router’s web interface and set a new admin password; mesh nodes are online. |
| #LTS00134213INBOUND | 2026-06-22 | — | 1.8 | 1 | 1 | 3 | 45.8% Needs Improvement | SPNMX55GC | CONNECTIVITY | Advised to reboot the parent node; issue remains unresolved pending further action. |
| #LTS00134222OUTBOUND | 2026-06-22 | — | 1.4 | 1 | 1 | 3 | 38.7% Needs Improvement | E1500 | ACCESS | Agent promised to email step-by-step instructions for retrieving the Wi-Fi password. |
| #GI00134273INBOUND | 2026-06-22 | — | 2.8 | 1 | 2 | 2 | 58.3% Needs Improvement | GENERAL INQUIRY | Informed customer that Linksys does not sell an outdoor bridge; suggested TP-Link product and advised contacting TP-Link for setup. | |
| #LTS00134230INBOUND | 2026-06-22 | — | 2.8 | 4 | 2 | 3 | 0.0% Needs Improvement | MX8500 | CONNECTIVITY | Offered paid-support session and directed to online support articles; no technical fix applied. |
| #LTS00134232INBOUND | 2026-06-22 | — | 2.8 | 2 | 1 | 3 | 0.0% Needs Improvement | WHW03 | CONNECTIVITY | Both child nodes re-paired and are now solid green; Wi-Fi bands confirmed. Email follow-up instructions sent. |
| #LTS00134247INBOUND | 2026-06-22 | — | 2.8 | 2 | 2 | 3 | 66.1% Needs Improvement | MR7350 | CONNECTIVITY | Sent step-by-step email instructions for router reconfiguration; customer to follow. |
| #LTS00134255INBOUND | 2026-06-22 | — | 2.1 | 2 | 2 | 3 | 89.4% Meets / Exceeds | MX6200 | CONNECTIVITY | Agent will email a detailed step-by-step guide and ticket number; customer may call back to complete pairing. |
| #LTS00134404INBOUND↩ cb | 2026-06-23 | — | 2.1 | 2 | 2 | 3 | 78.9% Developing | SPNM60CF | CONNECTIVITY | Customer renamed 2.4 GHz SSID to 'Rall_2.4' and saw it on iPad, but Ring Doorbell connectivity was not tested. No escalation, callback, or follow-up was offered. |
| #LTS00134404INBOUND↩ cb | 2026-06-23 | — | 2.8 | 3 | 2 | 2 | 50.9% Needs Improvement | SPNM60CF | CONNECTIVITY | Customer advised to contact Ring support for firmware updates or compatibility assistance. |
| 915c5eee-6eea-11f1-afa9-42010a62006fINBOUND | 2026-06-23 | — | 2.8 | 1 | 2 | 2 | 33.3% Needs Improvement | WHW03 | CONNECTIVITY | Customer instructed to monitor Wi-Fi performance for 24–48 hours; ticket created for follow-up if issue persists. |
| #LTS00134420INBOUND | 2026-06-23 | — | 2.2 | 4 | 2 | 2 | 90.4% Meets / Exceeds | EA6100 | SETUP | Router reconfigured; printer and Ring camera still cannot connect. Customer advised to perform device-specific troubleshooting or consult KB articles. |
| #LTS00028269 | 2026-06-23 | — | 1.1 | 1 | 1 | 2 | — | EA6100 | NO TROUBLESHOOTING NEEDED | Agent incorrectly declared issue resolved and closed call despite customer reporting no internet. No valid resolution or next steps provided. |
| #LTS00134437INBOUND | 2026-06-23 | — | 2.8 | 1 | 1 | 3 | 39.6% Needs Improvement | WHW01P | CONNECTIVITY | Offered paid 60-minute support for $15 or to email step-by-step instructions; customer chose email. |
| #LTS00134447INBOUND | 2026-06-23 | — | 2.8 | 3 | 2 | 3 | 0.0% Needs Improvement | WRT3200ACM | SETUP | Agent will email step‑by‑step instructions for accessing the router UI and retrieving the Wi‑Fi password. |
| #LTS00134455INBOUND | 2026-06-23 | — | 2.8 | 3 | 1 | 2 | 0.0% Needs Improvement | MR7350 | SETUP | Promised to email step‑by‑step reset/re‑configuration instructions; offered paid support for $15. |
| #GI00134460INBOUND | 2026-06-23 | — | 2.8 | 2 | 3 | 3 | 81.8% Developing | MX6200 | CONNECTIVITY | Child node reconnected; router password reset completed. |
| #LTS00134580INBOUND | 2026-06-24 | — | 3.1 | 2 | 2 | 3 | 84.7% Developing | SPNMX56TB | ACCESS | Customer accessed the router dashboard; Wi‑Fi name/password can be changed as needed. |
| #LTS00087941INBOUND | 2026-06-24 | — | 1.8 | 1 | 1 | 2 | 40.0% Needs Improvement | WHW01 | CONNECTIVITY | Agent advised purchasing replacement mesh nodes; no warranty verification, escalation, or callback was offered. |
| #LTS00134587INBOUND | 2026-06-24 | — | 2.8 | 1 | 1 | 3 | 50.3% Needs Improvement | SPNMX56TB | HARDWARE | Advised customer to contact ISP (Tube) for router replacement; provided ISP phone number. |
| #LTS00134588INBOUND | 2026-06-24 | — | 1.3 | 1 | 1 | 2 | 55.4% Needs Improvement | E1200 | CONNECTIVITY | Agent promised to email step-by-step instructions for retrieving the Wi-Fi password, but no instructions were provided during the call and no confirmation of follow-up was established. |
| b23fd688-6fce-11f1-a95c-42010a623f91INBOUND | 2026-06-24 | — | 1.1 | 1 | 1 | 2 | 2.4% Needs Improvement | MBE7000 | GENERAL INQUIRY | No resolution provided. Call ended without closure, recap, or next steps. |
| #LTS00134605INBOUND | 2026-06-24 | — | 2.8 | 1 | 2 | 3 | 52.5% Needs Improvement | EA8300 | CONNECTIVITY | Offered $15 paid support for a 60‑minute troubleshooting session or to email step‑by‑step reset/reconfiguration instructions. |
| #GI00134607INBOUND | 2026-06-24 | — | 1.1 | 1 | 1 | 2 | — | SETUP | No resolution; call ended after customer indicated the device is not a Linksys product. | |
| #LTS00134610INBOUND | 2026-06-24 | — | 1.5 | 1 | 2 | 3 | 33.8% Needs Improvement | WHW01 | CONNECTIVITY | Customer to perform modem direct test and mesh reboot per KB. If issue persists, follow up for further troubleshooting or escalation. |
| #LTS00134621INBOUND | 2026-06-24 | — | 1.8 | 1 | 1 | 2 | 0.0% Needs Improvement | WHW03 | ACCESS | Offered paid-support service; no successful password reset confirmed. |
| #LTS00134612INBOUND | 2026-06-25 | — | 3.3 | 5 | 2 | 3 | 62.7% Needs Improvement | MX2000 | CONNECTIVITY | Customer advised to contact Panasonic support (03448443899) for assistance connecting the telephone to the Wi-Fi network. |
| #LTS00134732OUTBOUND | 2026-06-25 | — | 2.9 | 2 | 2 | 3 | 61.6% Needs Improvement | MX4200SH | SETUP | Nodes are now online; customer can relocate them. |
| #LTS00134737INBOUND | 2026-06-25 | — | 3.2 | 5 | 2 | 3 | 90.4% Meets / Exceeds | SPNM60TB | ACCESS | Customer was instructed to apply changes via the web UI; no confirmation of successful execution was obtained. |
| #LTS00134739INBOUND | 2026-06-25 | — | 2 | 2 | 2 | 2 | 81.9% Developing | SPNM60CF | CONNECTIVITY | Customer to attempt Ring doorbell connection after channel changes; agent did not verify success or provide further steps. |
| #LTS00134740INBOUND | 2026-06-25 | — | 2.8 | 5 | 3 | 4 | 68.0% Needs Improvement | SPNM60TB | ACCESS | Use http://myrouter.info for router management. Agent to forward request for app compatibility to engineering. No further troubleshooting or confirmation completed. |
| #LTS00134744INBOUND | 2026-06-25 | — | 2.8 | 4 | 2 | 2 | — | MR9000 | CONNECTIVITY | Offered paid support ($15) or to email step-by-step instructions for reverting bridge mode. |
| #LTS00134738INBOUND | 2026-06-25 | — | 1.8 | 1 | 2 | 2 | 55.0% Needs Improvement | MX4200 | CONNECTIVITY | Escalate to higher tier for hardware evaluation/replacement. |
| 092eb68c-709f-11f1-88e6-42010a623f91INBOUND | 2026-06-25 | — | 1.4 | 1 | 1 | 2 | 75.0% Developing | SETUP | Reset parent node via 5-press method, wait for solid blue, then re-add child nodes; callback scheduled to verify completion. | |
| 85833616-70a6-11f1-94e0-42010a660053OUTBOUND | 2026-06-25 | — | 3 | 3 | 2 | 3 | 83.3% Developing | CONNECTIVITY | All nodes are now solid blue and the network is operational; no further action required. | |
| 5d5eafd4-70ac-11f1-85d8-42010a660053OUTBOUND | 2026-06-25 | — | 1.6 | 2 | 1 | 2 | — | CONNECTIVITY | None – issue remains unresolved. Customer requires reset, browser setup, or replacement guidance. | |
| #LTS00134923INBOUND | 2026-06-26 | — | 2 | 2 | 2 | 2 | 50.1% Needs Improvement | SPNMX56CF | ACCESS | Callback scheduled for further troubleshooting; issue remains unresolved. |
| eaa0c4da-715c-11f1-bb12-42010a62006fINBOUND | 2026-06-26 | — | 3.5 | 4 | 2 | 3 | 81.9% Developing | SETUP | Issue resolved during call: main node turned solid white, child nodes reconnected. No further action required. | |
| 79bbe922-715f-11f1-9d43-42010a62006fINBOUND | 2026-06-26 | — | 3.5 | 3 | 3 | 3 | 70.1% Developing | MX2000 | CONNECTIVITY | Node now shows solid blue; customer can relocate it and use it as part of the mesh. |
| #LTS00134935INBOUND | 2026-06-26 | — | 1.8 | 1 | 1 | 3 | 42.9% Needs Improvement | MX4200SF | CONNECTIVITY | Customer instructed to contact ISP to verify modem internet connection; no further Linksys action taken. |
| #LTS00134938INBOUND | 2026-06-26 | — | 1.8 | 3 | 1 | 2 | 32.6% Needs Improvement | WHW01 | CONNECTIVITY | Ticket #134938 created; customer advised to call back for further assistance. |