Coaching Summary
Performance shows improvement in resolution rate but requires strengthening technical accuracy and protocol adherence.
Frequent technical inaccuracies and incomplete troubleshooting, particularly around mesh setup and product capabilities.
Key calls: #LTS00135105, #LTS00135175, #LTS00135755, #LTS00135618
Risk Flags
Critical dimension below threshold
4 calls had accuracy <2.5, with one at accuracy=1 (call #LTS00135105) indicating severe technical failures.
Example Told MBE7000 user it is not a mesh router and advised return without troubleshooting (call #LTS00135105).
Correct behavior: Verify product capabilities via KB before responding; attempt standard mesh troubleshooting.
Impact: Customer forced to return functional device and experienced extended downtime.
Related: #LTS00135105, #LTS00135278, #LTS00135292, #LTS00135755
Repeat issue across 2+ calls
Mesh connectivity failures recurred across SPNM60CF (calls #LTS00135111, #LTS00135175) and WHW03 (calls #LTS00135614, #LTS00135755).
ExampleFailed to diagnose iOS Private WiFi Address on SPNM60 after SSID change (call #LTS00135111).
Correct behavior: Check iOS Private WiFi Address setting after SSID changes; use less disruptive fixes before factory reset.
Impact: Extended downtime and repeated callbacks for same issue.
Related: #LTS00135111, #LTS00135175, #LTS00135614, #LTS00135755
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.42 | 17 |
| Technical Accuracy | 2.41 | 17 |
| Protocol | 2.0 | 17 |
| Communication | 2.12 | 17 |
V2 Rubric (Shadow Grading)
V2 overall: 50.9% across 17 v2-scored calls this week1 auto-zero
| Category | Week Average |
|---|---|
| Resolution | 2.65 |
| Technical Accuracy | 2.3 |
| Communication | 2.65 |
| Customer Ownership | 3.29 |
| Escalation Judgment | 3.75 |
| Customer Experience | 1.91 |
- Partial Resolution: 6
- Successful Resolution: 6
- Unresolved: 3
- Ownership Gap: 2
Score Diagnostics
Based on 17 calls reviewed this week.
Technical Findings
improvement
Claimed MBE7000 is not a mesh router (call #LTS00135105), contradicting KB; customer needed return instead of troubleshooting.
#LTS00135105 · call 9b603c3e-73a0-11f1-b715-42010a663f85
improvement
Provided invalid router URL '[REDACTED_PHONE]' for WHW03 access (call #LTS00135175), preventing customer from configuring cameras.
#LTS00135175 · call 590cfdaa-747b-11f1-8405-42010a623f91
improvement
Instructed MX4200 user to add node without factory reset (call #LTS00135618), violating universal_mesh_full_rebuild.md requirements.
#LTS00135618 · call 8a95a6fa-7607-11f1-b0d9-42010a623f91
improvement
Referenced non-existent 'pink' LED states on MR7350 (call #LTS00135755), causing confusion and contradicting spnm_router_setup.md.
#LTS00135755 · call c357416e-76da-11f1-a111-42010a660053
strength
Correctly applied 5-press pairing on WHW03 parent node (call #LTS00135114), resolving connectivity per universal_5press_models.md.
#LTS00135114 · call 98aa4f7c-73b2-11f1-aec9-42010a623f91
Call Handling Findings
- Technical accuracy gapsVerify product specs and KB articles before responding; use exact LED terminology (blue/solid blue, white/solid white, red/blinking red).
- Incomplete troubleshootingAlways confirm parent node connectivity before addressing child nodes; follow isolation protocol per KB.
Calibration Notes
- Very short call (duration null) scored overall=1.1; grader may have had limited signal to assess technical accuracy.
- Overall=1.0 but resolution marked true; needs verification of actual customer outcome vs agent documentation.
Callback Chains
No callback chains detected.
Documentation Mismatches
No documentation mismatches found.
Suggested Coaching Conversation
1
Your guided resets on the SPNM60 and WHW03 calls showed strong ownership—let's discuss how we can pair that with even more precise product verification.
2
When you mentioned the MBE7000 wasn't a mesh router, what sources did you reference to confirm that claim?
3
Can we walk through the steps you take to verify parent node connectivity before troubleshooting child nodes? Let's use #LTS00135614 as a case study.
4
How do you decide when to use the 5-press method versus other pairing options? Let's align this with KB guidance using #LTS00135618.
5
You correctly avoided paid support on out-of-warranty calls—what checks do you perform to ensure you're not missing valid self-help options?
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 |
|---|---|---|---|---|---|---|---|---|---|---|
| #LTS00135105 | 2026-06-29 | — | 1.1 | 1 | 1 | 2 | 62.6% Needs Improvement | MBE70 | SETUP | Agent advised the customer to return the MBE7000 and purchase a matching model. |
| #LTS00135111INBOUND | 2026-06-29 | — | 2.8 | 2 | 2 | 2 | 57.1% Needs Improvement | SPNM60CF | CONNECTIVITY | Phone now connects; advise keep current SSID/password or change carefully after confirming device settings. |
| #LTS00135114INBOUND | 2026-06-29 | — | 2.8 | 2 | 2 | 2 | 77.2% Developing | WHW03 | SETUP | All nodes are online, Wi-Fi SSID/password updated, internet connectivity restored. |
| #LTS00135278INBOUND | 2026-06-30 | — | 1 | 1 | 1 | 1 | 48.9% Needs Improvement | SPNM60CF | CONNECTIVITY | not_fixed |
| #LTS00135175INBOUND | 2026-06-30 | — | 2.8 | 1 | 2 | 2 | 31.1% Needs Improvement | MX2000 | CONNECTIVITY | Advised customer to contact camera manufacturer for setup assistance or download their app; offered callback for future router issues. |
| #LTS00135292INBOUND | 2026-06-30 | — | 1 | 1 | 1 | 1 | 39.4% Needs Improvement | WHW03 | CONFIGURATION | not_fixed |
| #LTS00135459INBOUND | 2026-07-01 | — | 2.1 | 2 | 3 | 2 | 4.2% Needs Improvement | SPNM60CF | ACCESS | Suggested purchasing an MX57 router; no valid resolution or self-help path provided. |
| #LTS00135464INBOUND | 2026-07-01 | — | 2.6 | 4 | 2 | 2 | 27.1% Needs Improvement | SPNMX56CF | SETUP | Wait for firmware update to complete (≈15‑30 min) and monitor node status; if nodes remain unjoined, customer to call back for further assistance. |
| #LTS00135476INBOUND↩ cb | 2026-07-01 | — | 2.8 | 1 | 2 | 2 | 42.8% Needs Improvement | EA7450 | ACCESS | Provided email with instructions; suggested factory reset if admin password cannot be retrieved. No confirmation of successful access or password change. |
| #LTS00135476INBOUND↩ cb | 2026-07-01 | — | 3.9 | 5 | 3 | 3 | 81.9% Developing | EA7450 | ACCESS | Reassured customer that the password visibility feature is secure and does not expose the password; no further action required. |
| #LTS00135482INBOUND | 2026-07-01 | — | 2.8 | 2 | 2 | 3 | 86.9% Meets / Exceeds | SPNMX57GC | CONNECTIVITY | Customer applied changes and reported TV signal appeared restored. |
| #LTS00135614INBOUND | 2026-07-02 | — | 2.8 | 3 | 3 | 2 | 79.7% Developing | WHW03 | CONNECTIVITY | One child node briefly stabilized but reverted to red. Customer advised to contact ISP (GigaClear) for replacement power unit. |
| #LTS00135618INBOUND | 2026-07-02 | — | 2.2 | 4 | 2 | 3 | 59.9% Needs Improvement | SPNMX42CF | SETUP | Agent advised temporary placement of the new node next to the main router but provided no further instructions or verification steps. |
| #LTS00135630INBOUND | 2026-07-02 | — | 3.3 | 5 | 3 | 3 | 0.0% Needs Improvement | WHW03 | SETUP | Offered paid‑support ($15/hr) and possible guide; no technical fix applied. |
| #LTS00135749INBOUND | 2026-07-03 | — | 3.4 | 5 | 3 | 3 | 84.7% Developing | MX2000 | CONNECTIVITY | Two nodes restored to solid blue; customer advised to reboot or relocate the remaining red node and was sent a home-networking guide. |
| #LTS00135755INBOUND↩ cb | 2026-07-03 | — | 1 | 1 | 1 | 1 | 36.5% Needs Improvement | MR7350 | CONNECTIVITY | not_fixed |
| #LTS00135755OUTBOUND↩ cb | 2026-07-03 | — | 2.8 | 1 | 1 | 2 | 45.5% Needs Improvement | MR7350 | CONNECTIVITY | Wi-Fi name and password changed; customer reconnected to the new network. However, technical guidance contained serious inaccuracies that could cause future issues. |