34Calls
2.38Avg Score
27m 23sAvg Handle Time
24Documented
2Escalated
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.38 | 34 |
| Technical Accuracy | 2.62 | 34 |
| Protocol | 1.88 | 34 |
| Communication | 2.44 | 34 |
Main focus: Incomplete model verification
V2 Rubric (Shadow Grading)
V2 overall: 48.43% across 31 v2-scored calls this week3 auto-zeros
| Category | Week Average |
|---|---|
| Resolution | 2.38 |
| Technical Accuracy | 2.25 |
| Communication | 2.5 |
| Customer Ownership | 3.5 |
| Escalation Judgment | 2.36 |
| Customer Experience | 1.69 |
- Unresolved: 13
- Successful Resolution: 8
- Partial Resolution: 6
- Appropriate Escalation: 3
- Ownership Gap: 1
Where Did the Time Go
By Product Family
| Family | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Note |
|---|---|---|---|---|---|---|---|
| RE | 2 | 70m 03s | 1.5 | 1.0 | 2.0 | 2.0 | Outlier: 2.9x weekly median handle time |
| MBE | 1 | 49m 41s | 1.8 | 1.0 | 1.0 | 2.0 | Outlier: 2.0x weekly median handle time |
| WHW | 13 | 27m 42s | 2.65 | 2.69 | 2.08 | 2.77 | |
| E | 2 | 25m 15s | 2.3 | 3.0 | 2.0 | 2.0 | |
| SPN | 2 | 24m 28s | 2.2 | 2.0 | 1.5 | 2.5 | |
| MX | 8 | 23m 40s | 2.59 | 3.12 | 2.12 | 2.38 | |
| EA | 3 | 19m 33s | 1.87 | 2.0 | 1.67 | 2.33 | |
| LN | 1 | 19m 23s | 2.8 | 2.0 | 1.0 | 2.0 | |
| MR | 1 | 4m 10s | 1.8 | 4.0 | 1.0 | 2.0 |
By Problem Category
| Category | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Focus? |
|---|---|---|---|---|---|---|---|
| CONNECTIVITY | 10 | 25m 00s | 2.3 | 2.2 | 2.1 | 2.5 | ✓ |
| SETUP | 7 | 26m 40s | 2.6 | 2.7 | 2.3 | 2.7 | |
| ACCESS | 5 | 28m 20s | 2.1 | 2.0 | 2.0 | 2.5 | ✓ |
What You Did Well
- Accurate warranty guidance8 of 24 callsAccurately identified out-of-warranty status and communicated paid-support eligibility across 8 calls, including #LTS00135131 and #LTS00135365.Why this matters: Ensures customers understand support options and avoids mis-selling free support for ineligible issues.
- Clear mesh troubleshooting4 of 8 mesh callsProvided correct 5-press pairing method and guided successful mesh reconfiguration in #LTS00135170 and #LTS00135387.Why this matters: Restores connectivity efficiently and reduces repeat calls for mesh issues.
Growth Focus
- Incomplete model verification7 of 24 callsFailed to confirm product model before troubleshooting in 7 calls (e.g., #LTS00135148, #LTS00135207), leading to mismatched guidance.Why this matters: Risk of providing incorrect instructions, causing customer frustration and repeat calls.Example: In #LTS00135148, the agent skipped model confirmation and provided generic reset steps that did not address the LN11011202's specific power-issue.What better looks like: Always verify product model and serial number before any troubleshooting, using KB-specific steps.
- Inconsistent reset procedures5 of 24 callsProvided conflicting reset instructions (30s vs 15s) and incorrect 5-press guidance on non-supported models in #LTS00135131 and #LTS00135305.Why this matters: Confuses customers, prolongs issue resolution, and may cause hardware damage if misapplied.Example: In #LTS00135131, the agent advised a 30-second reset then later a 15-second reset, contradicting KB guidelines for EA7450.What better looks like: Use KB-documented reset times (10-20s for most models) and confirm model support before suggesting 5-press methods.
Callback Flags
No callback chains detected.
Documentation Accuracy
No documentation mismatches detected this week.
Practice Plan
- Step 1Before guiding any reset procedure, confirm the exact product model and serial number, then reference KB-specific reset times and steps.Why: Prevents incorrect instructions that can confuse customers or damage devices.
- Step 2After any reset or configuration change, verify connectivity on all linked devices (e.g., TV, phones) before closing the call.Why: Ensures full resolution and reduces callbacks for partially fixed issues.This week: #LTS00135131
- Step 3When encountering a solid-red node, immediately check WAN/modem status and ISP connectivity before proceeding with node-level troubleshooting.Why: Avoids wasted time on node resets when the root cause is upstream.This week: #TE00135341
Escalation Lessons
#TE00135341 — MBE7000
Status: resolved · Category: SETUP
What happened on the call: Escalated to Level-2 technician; callback scheduled within an hour.
Why it escalated: L1 could not resolve solid-red MBE7000 node after service restoration and lacked modem model information.
What L2 did:
- Verified modem model SB8200, instructed power cycle of modem and node, reconnected devices, confirmed internet connectivity.
L1 learning points:
- Capture modem model and number of connected devices early in connectivity issues.
- Verify internet connectivity on secondary devices after reset.
- Avoid escalation without full diagnostic data.
#TE00135544 — E8450
Status: resolved · Category: ACCESS
What happened on the call: Case escalated to Level-2 technician; callback scheduled.
Why it escalated: L1 could not resolve missing 2.4 GHz SSID on E8450 despite UI confirmation of broadcast enablement.
What L2 did:
- Performed lab test with actual E8450, confirmed 2.4 GHz functionality, guided customer through mesh parent mode disable and SSID reconfiguration.
L1 learning points:
- When SSID broadcast persists, consider hardware-level issues and escalate for lab validation.
- Document all GUI settings changes and verify post-change status.
- Escalate early for hardware verification when standard steps fail.
Evidence Calls
| Case | Date | Score | V2 | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00135131INBOUND | 2026-06-29 | 3.3 A 4P 2C 3 | 87.7% Meets / Exceeds | EA7450 | CONNECTIVITY | Internet restored on iPad; paid support processed; emailed setup instructions; recommended router upgrade due to end-of-life status. |
| #LTS00135148INBOUND | 2026-06-29 | 2.8 A 2P 1C 2 | 33.4% Needs Improvement | LN11011202 | SETUP | Advised the customer that the product could be returned. |
| #LTS00135170INBOUND | 2026-06-29 | 3 A 3P 2C 3 | 53.7% Needs Improvement | MX2000 | SETUP | Wi-Fi network successfully reconfigured and internet connectivity restored. |
| #LTS00135207INBOUND | 2026-06-29 | 2.8 A 5P 2C 3 | 59.7% Needs Improvement | WHW03 | CONNECTIVITY | Customer to reset the red node and re-add it to the mesh network near the solid-blue node. |
| #LTS00135211INBOUND | 2026-06-29 | 1.4 A 1P 1C 3 | 0.0% Needs Improvement | WHW03 | ACCESS | Advised customer to reset the router and reconfigure; no concrete next steps or follow-up provided. |
| #LTS00135211INBOUND | 2026-06-29 | 2.8 A 1P 2C 3 | 70.3% Developing | WHW03 | ACCESS | No functional resolution; customer declined paid support and may replace hardware. |
| 43530182-7415-11f1-b0c9-42010a623f91INBOUND | 2026-06-29 | 1.8 A 4P 1C 2 | 0.0% Needs Improvement | GENERAL INQUIRY | not_applicable | |
| #LTS00135304INBOUND | 2026-06-30 | 1.4 A 1P 1C 2 | 49.2% Needs Improvement | SPNM60TB | ACCESS | Call was closed with no actual resolution. Customer's underlying issue remains unaddressed. |
| #LTS00135305INBOUND | 2026-06-30 | 2.1 A 2P 2C 3 | 52.6% Needs Improvement | WHW03 | CONNECTIVITY | Continue troubleshooting — recommend full factory reset of all nodes or replacement of the problematic child node; escalate if issue persists. |
| #LTS00135305OUTBOUND | 2026-06-30 | 2.8 A 1P 2C 2 | 60.4% Needs Improvement | WHW03 | CONNECTIVITY | Nodes paired successfully; Wi-Fi name and password updated; customer confirmed network is working. |
| #TE00135341INBOUND | 2026-06-30 | 1.8 A 1P 1C 2 | 60.6% Needs Improvement | MBE7000 | SETUP | Escalated to Level-2 technician; callback scheduled within an hour. |
| #LTS00135365INBOUND | 2026-06-30 | 3.7 A 5P 3C 4 | 87.2% Meets / Exceeds | WHW03 | SETUP | Node appeared online; agent will email receipt request for warranty update and suggested speed test. |
| #LTS00135377INBOUND | 2026-06-30 | 2 A 2P 2C 2 | 82.8% Developing | WHW03 | SETUP | Primary node is online; customer instructed to retry 5-press pairing or add the child node via the web interface later. Agent offered to email the instructions and mentioned paid support. |
| #LTS00135374INBOUND | 2026-06-30 | 1.8 A 4P 1C 2 | — | MR8300 | CONNECTIVITY | Agent promised to resend the email again; no confirmation of receipt was obtained, and no case or escalation was initiated. |
| #LTS00135387INBOUND | 2026-06-30 | 3.5 A 3P 3C 3 | 86.1% Meets / Exceeds | MX6200 | CONNECTIVITY | Node is now solid white and functioning; no further steps required. |
| #LTS00135387OUTBOUND | 2026-06-30 | 1.8 A 4P 2C 1 | 43.5% Needs Improvement | MX6200 | CONNECTIVITY | HomeKit integration toggle attempted; nodes returned to solid blue. No verification of success or next steps provided. |
| #LTS00135387OUTBOUND | 2026-06-30 | 2.1 A 2P 2C 3 | 66.7% Needs Improvement | MX6200 | CONNECTIVITY | Monitor ping test for 24 hours; await LTS follow-up; customer will be emailed detailed instructions. |
| 6f95ede4-74c0-11f1-b16a-42010a623f91INBOUND | 2026-06-30 | 2 A 2P 2C 2 | 57.0% Needs Improvement | MX6200 | CONNECTIVITY | Agent advised trying the web interface to add the nodes; no confirmed resolution. |
| #LTS00135524INBOUND | 2026-07-01 | 1.8 A 1P 2C 2 | 26.3% Needs Improvement | RE9000 | SETUP | Escalate to Level-2 technician; request receipt for warranty verification; advise customer to verify 2.4 GHz network is enabled on router. |
| #TE00135544INBOUND | 2026-07-01 | 1.8 A 1P 2C 2 | 68.3% Needs Improvement | E8450 | ACCESS | Case escalated to Level-2 technician; callback scheduled. |
| #LTS00135524INBOUND | 2026-07-01 | 1.2 A 1P 2C 2 | 17.6% Needs Improvement | RE9000 | SETUP | Call ended without resolution. Node remains unpaired. Customer needs to be informed of incompatibility and advised to return or replace the WHW01P with a compatible model. |
| #LTS00108391 | 2026-07-02 | 2.3 A 3P 2C 2 | — | MX6200 | CONNECTIVITY | Agent will email customer and request purchase receipt for warranty replacement; no immediate fix provided. |
| #LTS00135637INBOUND | 2026-07-02 | 1.3 A 1P 2C 3 | 34.2% Needs Improvement | EA8300 | SETUP | None provided — agent ended call after giving incorrect instructions. |
| #LTS00135651INBOUND | 2026-07-02 | 2.4 A 3P 2C 3 | 69.8% Needs Improvement | MX2000 | ACCESS | No successful resolution. Advised to try a different password but no verification performed. No escalation or follow-up scheduled. |
| #LTS00135669INBOUND | 2026-07-02 | 2.8 A 5P 2C 3 | 85.6% Meets / Exceeds | WHW03 | CONNECTIVITY | Customer to reset child nodes and complete mesh setup; follow‑up email sent with detailed instructions. |
| #LTS00135678INBOUND | 2026-07-02 | 1.1 A 1P 1C 2 | 0.0% Needs Improvement | WHW03 | ACCESS | None confirmed. Email instructions promised but not verified as sent or effective. |
| #LTS00135387INBOUND | 2026-07-02 | 3.6 A 5P 2C 2 | 0.0% Needs Improvement | MX6200 | CONNECTIVITY | Advised that the device is out of warranty and no replacement is available; suggested upgrading to a new system. |
| #LTS00135694INBOUND | 2026-07-02 | 3.3 A 3P 3C 3 | 73.1% Developing | WHW01 | SETUP | Internet restored; customer confirmed connectivity. Offered paid-support option for future issues. |
| #LTS00135694OUTBOUND | 2026-07-02 | 4 A 5P 3C 3 | — | WHW01 | SETUP | Customer will consider the recommended models and purchase a new router. Agent provided guidance on initial setup. |
| #LTS00135699INBOUND | 2026-07-02 | 1 A 1P 1C 1 | 9.8% Needs Improvement | EA8300 | CONNECTIVITY | Agent claimed they would send setup instructions via email, but the email address provided was garbled and invalid. |
| #TE00135544INBOUND | 2026-07-02 | 2.8 A 5P 2C 2 | 31.4% Needs Improvement | E8450 | ACCESS | Technician will contact customer by email and phone after completing device testing. |
| #LTS00135774INBOUND | 2026-07-03 | 2.8 A 1P 2C 2 | 60.1% Needs Improvement | WHW03 | CONNECTIVITY | Customer told to use router password to access the app; no confirmation of success. |
| #LTS00135816INBOUND | 2026-07-03 | 3 A 3P 2C 3 | 41.7% Needs Improvement | SPNM60CF | ACCESS | Factory reset completed; admin access restored; 2.4 GHz and 5 GHz networks separated via Quick-Setup for Ring doorbell compatibility. |
| #LTS00135848INBOUND | 2026-07-03 | 2.8 A 3P 2C 3 | 32.5% Needs Improvement | WHW03 | CONNECTIVITY | Agent recommended purchasing new Atlas Wi-Fi 6 mesh routers/nodes as the red node appears dead. |