4Calls
1.85Avg Score
32m 36sAvg Handle Time
2Documented
0Escalated
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 1.85 | 4 |
| Technical Accuracy | 1.5 | 4 |
| Protocol | 1.75 | 4 |
| Communication | 2.25 | 4 |
Main focus: Technical Accuracy
V2 Rubric (Shadow Grading)
V2 overall: 47.74% across 3 v2-scored calls this week
| Category | Week Average |
|---|---|
| Resolution | 2.71 |
| Technical Accuracy | 2.4 |
| Communication | 2.5 |
| Customer Ownership | 3.21 |
| Escalation Judgment | 0.0 |
| Customer Experience | 2.38 |
- Partial Resolution: 2
- Unresolved: 1
Where Did the Time Go
By Product Family
| Family | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Note |
|---|---|---|---|---|---|---|---|
| WHW | 1 | 63m 08s | 1.4 | 1.0 | 1.0 | 2.0 | Outlier: 1.9x weekly median handle time |
| OTHER | 1 | 4m 40s | 2.0 | 1.0 | 2.0 | 3.0 |
By Problem Category
| Category | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Focus? |
|---|---|---|---|---|---|---|---|
| CONNECTIVITY | 3 | 41m 54s | 1.8 | 1.67 | 1.67 | 2.0 | ✓ |
| CONFIGURATION | 1 | 4m 40s | 2.0 | 1.0 | 2.0 | 3.0 |
What You Did Well
- Empathetic CommunicationUsed across multiple calls, notably in #LTS00135702Agent acknowledged the customer's frustration and used empathetic language at several points, particularly in call #LTS00135702 where they validated the customer's experience during a prolonged troubleshooting session.Why this matters: Maintaining empathy reduces customer frustration and builds trust, increasing the likelihood of successful resolution.
- Web UI NavigationDemonstrated in 2 calls (#LTS00135702, #LTS00135702)Agent successfully guided customers to the local web UI and executed key actions such as locating the Add Wireless Child Node option in call #LTS00135702 and changing Wi‑Fi credentials in call #LTS00135702.Why this matters: Directing customers to the router UI often resolves issues more efficiently than verbal guidance alone.
Growth Focus
- Technical AccuracyAppeared in 3 of 4 callsProvided incorrect technical guidance including LED interpretation, reset procedures, and product capabilities across multiple calls (e.g., claiming solid red is normal post-reset, stating Linksys app cannot add nodes for WHW03).Why this matters: Inaccurate guidance leads to unresolved issues, customer frustration, and increased callback rates.Example: In call #LTS00135702, the agent told the customer a solid red LED after reset was normal — KB states this indicates 'No internet connection' or 'Needs reset,' delaying proper diagnosis.What better looks like: Reference KB articles for LED meanings, reset steps, and product capabilities before providing guidance; verify claims with the customer.
- Information CollectionOccurred in 3 of 4 callsFailed to collect essential product model/serial numbers and warranty status in calls #LTS00135702, #LTS00135702, and #LTS00135873, impacting troubleshooting efficiency and escalation decisions.Why this matters: Missing product information prevents accurate diagnostics, warranty verification, and appropriate escalation.Example: In call #LTS00135702, the agent never asked for the router model or serial number, leading to inefficient troubleshooting and an unresolved case.What better looks like: Collect product model, serial number, and warranty status within the first 2 minutes of every call.
Callback Flags
No callback chains detected.
Documentation Accuracy
No documentation mismatches detected this week.
Practice Plan
- Step 1Collect product model, serial number, and warranty status within the first 2 minutes of every call.Why: Missing product information leads to inefficient troubleshooting, incorrect guidance, and potential warranty claim errors.This week: #LTS00135702
- Step 2Reference KB articles for LED meanings, reset procedures, and product capabilities before providing guidance; verify claims with the customer.Why: Inaccurate technical advice causes unresolved issues and erodes customer trust.This week: #LTS00135702
- Step 3Before closing any call, ask the customer to test the fix and confirm it works; document the verification step.Why: Closing without verification increases callback risk and repeat call volume.
- Step 4When encountering unresolved connectivity issues, initiate escalation or schedule a callback instead of ending the call vaguely.Why: Proper escalation ensures timely resolution and reduces customer effort.This week: #LTS00135702
- Step 5Verify router admin access (e.g., http://myrouter.local) before claiming devices are unsupported or end-of-life.Why: Skipping basic diagnostics leads to premature declarations of unsupported status.This week: #LTS00135873
Escalation Lessons
No escalated case learning this week.
Evidence Calls
| Case | Date | Score | V2 | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00135702INBOUND | 2026-07-02 | 1.4 A 1P 1C 2 | 53.3% Needs Improvement | WHW03 | CONNECTIVITY | Advised that the nodes appear defective and suggested upgrading to a newer mesh system; no further technical fix was achieved. |
| #LTS00135702INBOUND | 2026-07-02 | 2 A 2P 2C 2 | 58.2% Needs Improvement | CONNECTIVITY | Recommend verifying that all mesh nodes are online (no red LEDs), ensure the SSID is not hidden, forget the network on the phone and manually re-enter the SSID and password, and if the problem persists perform a factory reset of the parent node and re-add child nodes. Schedule a follow-up call if needed. | |
| #LTS00135702OUTBOUND | 2026-07-02 | 2 A 2P 2C 2 | 31.7% Needs Improvement | CONNECTIVITY | Agent advised manual reconnection and creation of a separate 2.4 GHz SSID but did not walk the customer through the router UI; no further action was scheduled. | |
| #LTS00135873INBOUND | 2026-07-03 | 2 A 1P 2C 3 | — | VLP-21 | CONFIGURATION | Agent will send an email with unspecified instructions for adding a child node. |