37Calls
2.66Avg Score
20m 39sAvg Handle Time
33Documented
4Escalated
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.66 | 37 |
| Technical Accuracy | 2.62 | 37 |
| Protocol | 2.11 | 37 |
| Communication | 2.62 | 37 |
Main focus: Warranty eligibility checks
V2 Rubric (Shadow Grading)
V2 overall: 53.92% across 35 v2-scored calls this week1 auto-zero
| Category | Week Average |
|---|---|
| Resolution | 2.14 |
| Technical Accuracy | 2.19 |
| Communication | 3.04 |
| Customer Ownership | 3.7 |
| Escalation Judgment | 3.12 |
| Customer Experience | 3.04 |
- Unresolved: 14
- Partial Resolution: 13
- Successful Resolution: 6
- Appropriate Escalation: 2
Where Did the Time Go
By Product Family
| Family | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Note |
|---|---|---|---|---|---|---|---|
| MX | 6 | 44m 06s | 2.43 | 2.33 | 2.0 | 2.83 | Outlier: 3.4x weekly median handle time |
| MR | 3 | 30m 35s | 2.73 | 2.0 | 2.0 | 3.0 | Outlier: 2.3x weekly median handle time |
| SPN | 9 | 22m 17s | 2.59 | 2.56 | 2.0 | 2.56 | Outlier: 1.7x weekly median handle time |
| MBE | 1 | 16m 56s | 4.0 | 4.0 | 3.0 | 4.0 | |
| WHW | 7 | 13m 08s | 2.24 | 2.14 | 1.86 | 2.0 | |
| RE | 2 | 12m 39s | 3.05 | 4.0 | 3.0 | 3.0 | |
| OTHER | 3 | 11m 55s | 2.87 | 3.33 | 2.67 | 2.33 | |
| E | 1 | 10m 36s | 2.9 | 4.0 | 2.0 | 3.0 | |
| EA | 4 | 5m 44s | 2.53 | 2.0 | 1.25 | 2.25 |
By Problem Category
| Category | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Focus? |
|---|---|---|---|---|---|---|---|
| CONNECTIVITY | 12 | 22m 30s | 2.25 | 1.92 | 1.83 | 2.75 | ✓ |
| SETUP | 9 | 24m 40s | 2.78 | 2.44 | 2.22 | 3.11 | |
| HARDWARE | 6 | 20m 20s | 2.0 | 1.0 | 1.5 | 2.83 | ✓ |
What You Did Well
- Clear ISP scoping1 of 33 callsIdentified ISP responsibility for service transfer in #GI00135083 and provided accurate Community Fibre hotline, repeating numbers as requested for clarity.Why this matters: Prevents misdirected support efforts and ensures customers reach the correct service provider promptly.
- Mesh reset guidance1 of 33 callsCorrectly applied 5-press reset on MX6200 in #TE00038624 and guided child-node addition, achieving solid white LED status.Why this matters: Restores connectivity efficiently for mesh systems without unnecessary escalation.
Growth Focus
- Warranty eligibility checksAppeared in 1 of 33 callsOmitted warranty discussion in #GI00135088 despite customer interest in purchasing a Linksys adapter, missing an opportunity for clear replacement paths.Why this matters: Risk of customer frustration and repeat calls when replacement options are unclear or unavailable.Example: In #GI00135088, after confirming 5V/3A USB-C spec, no warranty or Linksys purchase path was offered, leaving the customer to self-resolve.What better looks like: Before closing hardware issues, confirm warranty status and provide direct Linksys accessory part numbers or purchase links when applicable.
- LED state interpretationAppeared in 1 of 33 callsIncorrectly described WHW-01 LED as solid green for online status in #LTS00135108; KB states solid blue is correct, causing confusion.Why this matters: Misinterpretation can lead to incorrect troubleshooting and prolonged outages.Example: In #LTS00135108, advised 'solid green means online' for WHW-01, contradicting KB documentation and delaying resolution.What better looks like: Reference KB documentation for model-specific LED meanings before providing status guidance.
Callback Flags
No callback chains detected.
Documentation Accuracy
No documentation mismatches detected this week.
Practice Plan
- Step 1Before closing any call involving hardware replacement or accessory purchase, confirm warranty eligibility and provide direct Linksys part numbers or purchase links.Why: Avoids customer frustration and repeat calls when replacement options are unclear.
- Step 2Review KB documentation for all mesh device LED states before guiding customers on status interpretation.Why: Prevents misdiagnosis and incorrect troubleshooting steps that prolong outages.
- Step 3When discussing firmware or band steering, verify the exact model and consult the compatibility matrix to avoid cross-generation errors.Why: Mixing mesh generations can cause pairing failures and network instability.
Escalation Lessons
#TE00038624 — MX6200
Status: resolved · Category: CONNECTIVITY
What happened on the call: New parent node shows solid white (online). Agent scheduled a callback to finish child-node configuration.
Why it escalated: Complex mesh setup with multiple nodes and internet outage after ISP modem change; L1 unable to confirm WAN connectivity before mesh troubleshooting.
What L2 did:
- Claimed parent node from TE queue
- Performed callback to verify new modem functionality
- Guided WiFi name/password change via web UI
- Initiated firmware update
L1 learning points:
- Verify WAN/internet connectivity at modem level before troubleshooting mesh nodes
- Confirm ISP modem replacement was successful before proceeding with node configuration
- Use myrouter.local or [REDACTED_PHONE] for direct access instead of relying solely on app
#TE00135461 — SPNM60TB
Status: resolved · Category: CONNECTIVITY
What happened on the call: Escalated to Level 2 technical team; customer will receive a callback within 24-48 business hours.
Why it escalated: Ring Video Doorbell 4 failing to connect at 95% with error P777/P707; L1 provided contradictory band guidance and invalid URL path.
What L2 did:
- Verified MAC address and model information
- Corrected band guidance to use 2.4GHz for Ring devices
- Provided valid support URL path
- Escalated for further investigation
L1 learning points:
- Always recommend 2.4GHz for IoT devices like Ring doorbells
- Use only documented URLs (myrouter.local or [REDACTED_PHONE]) for router access
- Avoid contradictory band instructions; clarify band requirements per device
#TE00105631 — MX55EC3
Status: resolved · Category: CONNECTIVITY
What happened on the call: Sent step‑by‑step reset instructions to the customer's email.
#LTS00130279 — MX4200
Status: resolved · Category: CONFIGURATION
What happened on the call: Customer advised to contact TP-Link business support for compatibility/configuration; ticket #130279 logged.
Evidence Calls
| Case | Date | Score | V2 | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #GI00135083INBOUND | 2026-06-29 | 5 A 5P 5C 5 | 100.0% Meets / Exceeds | GENERAL INQUIRY | Provided Community Fibre hotline number (0800-0820-770) for the customer to arrange service transfer. | |
| #GI00135088INBOUND | 2026-06-29 | 2.8 A 4P 2C 3 | 51.7% Needs Improvement | SF600 | HARDWARE | Suggested purchasing a compatible third-party 5V/3A USB-C adapter or testing the node with an adapter at a local store. |
| #LTS00135101INBOUND | 2026-06-29 | 3.6 A 4P 2C 4 | 89.0% Meets / Exceeds | SPNM60CF | ACCESS | Static DNS updated to correct OpenDNS filtering IPs; blocking restored. Customer advised to change admin password to prevent unauthorized changes. |
| #LTS00135108INBOUND | 2026-06-29 | 2.8 A 1P 2C 3 | 74.8% Developing | WHW01 | CONNECTIVITY | Both nodes now show solid green in the app; customer can relocate them to their permanent locations. |
| 1c98f9d2-73ae-11f1-bd0d-42010a62006fINBOUND | 2026-06-29 | 1.3 A 1P 1C 2 | 54.2% Needs Improvement | SPNM62 | HARDWARE | No actionable resolution or next step provided. Call ended with vague suggestion to call back if needed. |
| #TE00038624INBOUND | 2026-06-29 | 1.8 A 1P 2C 3 | 85.4% Meets / Exceeds | MX6200 | CONNECTIVITY | New parent node shows solid white (online). Agent scheduled a callback to finish child-node configuration. |
| 3e152ce8-73c2-11f1-8f8a-42010a660053OUTBOUND | 2026-06-29 | 2.6 A 3P 2C 2 | 66.5% Needs Improvement | MX6200 | SETUP | Escalated to second‑level support; callback scheduled for 1:30 ET. |
| #LTS00135156INBOUND | 2026-06-29 | 3.4 A 3P 4C 3 | 65.6% Needs Improvement | MR9600 | CONNECTIVITY | Router reset and reconfigured; extender reset and reconnected. Customer confirmed laptop internet connectivity. |
| #LTS00135274INBOUND | 2026-06-30 | 1.8 A 1P 2C 2 | 38.6% Needs Improvement | WHW01 | SETUP | Ensure parent node is wired to modem, wait for solid blue/green LED, then re-add child nodes. If still flashing, schedule further troubleshooting or replacement. |
| #GI00135281INBOUND | 2026-06-30 | 1.4 A 1P 2C 2 | 0.0% Needs Improvement | MX5300 | CONFIGURATION | None; call ended without resolution or next steps. |
| #LTS00135284INBOUND | 2026-06-30 | 3.4 A 5P 3C 3 | 59.7% Needs Improvement | SPNMX42GC | SETUP | Customer successfully logged into the Linksys app/web interface and can now manage the network. |
| #LTS00135291INBOUND | 2026-06-30 | 3.1 A 3P 4C 3 | 78.6% Developing | RE6300 | SETUP | Extender configured successfully; solid green LED confirmed operational. Internet access not validated. |
| #LTS00135297INBOUND | 2026-06-30 | 1.6 A 3P 1C 1 | 20.6% Needs Improvement | EA7250 | CONNECTIVITY | None provided. Call ended abruptly with off-topic remark. |
| #LTS00135299INBOUND | 2026-06-30 | 2.9 A 4P 2C 3 | 67.5% Needs Improvement | E2500 | CONNECTIVITY | Agent recommended purchasing a newer router (Wi-Fi 6) and will email step-by-step instructions for accessing the router’s web UI to adjust wireless settings. |
| #LTS00135303INBOUND | 2026-06-30 | 3 A 5P 2C 3 | 55.9% Needs Improvement | RE7000 | SETUP | Agent will email step-by-step reset and re-configuration instructions to the customer. |
| #LTS00135312INBOUND | 2026-06-30 | 2 A 2P 1C 3 | 76.1% Developing | MR75WH | NO TROUBLESHOOTING NEEDED | Agent will email instructions; customer must manually configure the new router and reply with purchase receipt for warranty review. |
| #LTS00135316INBOUND | 2026-06-30 | 1.8 A 1P 1C 2 | 59.5% Needs Improvement | WUSB6300 | SETUP | Agent promised to email driver and setup wizard, but provided incorrect information and did not confirm email address. |
| #LTS00135458INBOUND | 2026-07-01 | 2.8 A 5P 2C 2 | 36.2% Needs Improvement | SPNMX42GC | CONNECTIVITY | Ticket #135458 opened; customer advised to call back for a sequence reboot and possible node relocation. |
| #TE00135461INBOUND | 2026-07-01 | 2.1 A 1P 3C 2 | 59.0% Needs Improvement | SPNM60TB | CONNECTIVITY | Escalated to Level 2 technical team; customer will receive a callback within 24-48 business hours. |
| #LTS00135465INBOUND | 2026-07-01 | 2.8 A 1P 2C 2 | 55.8% Needs Improvement | SPNMX55GC | SETUP | Node now shows solid blue; monitor for stability. If the node drops again, repeat reset and pairing or consider repositioning/additional nodes. |
| #LTS00135470INBOUND | 2026-07-01 | 2.7 A 4P 2C 3 | 66.2% Needs Improvement | SPNMX56CF | CONFIGURATION | Offered a callback to continue the web‑UI walkthrough; no further action taken during the call. |
| #LTS00135472INBOUND | 2026-07-01 | 2.8 A 1P 2C 3 | 71.5% Developing | SPNMX57CF | CONNECTIVITY | Both nodes are now solid blue; mesh connectivity likely restored. |
| #LTS00135474INBOUND | 2026-07-01 | 2.8 A 1P 1C 2 | — | EA6900 | CONNECTIVITY | Offered to email step-by-step reset and re-configuration instructions. |
| #LTS00135478INBOUND | 2026-07-01 | 2.9 A 3P 2C 3 | 49.9% Needs Improvement | EA8300 | CONNECTIVITY | Agent will email self-help instructions for router configuration (UPnP/port forwarding). Customer declined paid support. |
| #LTS00135499INBOUND | 2026-07-01 | 2.8 A 1P 1C 3 | — | EA7500 | ACCESS | Agent will email step-by-step instructions for changing the Wi-Fi password. |
| #GI00135496INBOUND | 2026-07-01 | 4 A 5P 5C 2 | 57.6% Needs Improvement | DECOS4R | GENERAL INQUIRY | Provided TP-Link support phone number (1-866-225-8139). |
| #LTS00135490INBOUND | 2026-07-01 | 3.4 A 3P 3C 3 | 67.4% Needs Improvement | MX4200FM | SETUP | Node configured successfully; customer can keep default SSID/password or customize via web UI. |
| #LTS00135618INBOUND | 2026-07-02 | 1.8 A 1P 1C 2 | 60.2% Needs Improvement | SPNMX42CF | SETUP | Agent told the customer to relocate the node once solid blue, falsely claiming it was paired. No confirmation of solid white or internet connectivity was obtained. |
| #TE00105631INBOUND | 2026-07-02 | 3.6 A 5P 2C 4 | 54.2% Needs Improvement | MX55EC3 | CONNECTIVITY | Sent step‑by‑step reset instructions to the customer's email. |
| #LTS00029317INBOUND | 2026-07-02 | 4 A 4P 3C 4 | 87.5% Meets / Exceeds | MBE7000 | ACCESS | Password reset completed; customer confirmed access to router settings. |
| #LTS00135274INBOUND | 2026-07-02 | 1.4 A 1P 2C 2 | 16.4% Needs Improvement | WHW01 | SETUP | Agent recommended purchasing MX6200, falsely claiming compatibility. |
| #LTS00135626INBOUND | 2026-07-02 | 1 A 1P 1C 1 | 20.4% Needs Improvement | WHW03 | CONNECTIVITY | not_fixed |
| #LTS00135754INBOUND | 2026-07-03 | 3.1 A 4P 4C 2 | 17.3% Needs Improvement | WHW03 | SETUP | Node connectivity restored; advise to position child node permanently and optionally configure Wi-Fi name/password. Internet connectivity not confirmed. |
| #LTS00135626INBOUND | 2026-07-03 | 2.8 A 3P 1C 2 | 0.0% Needs Improvement | WHW03 | CONNECTIVITY | Offered paid support at $15 per incident; no technical fix provided. |
| #LTS00135761INBOUND | 2026-07-03 | 2.8 A 4P 1C 2 | 24.7% Needs Improvement | WHW03 | CONNECTIVITY | Sent email with step-by-step reconfiguration instructions; offered paid support if needed. |
| #LTS00135768INBOUND | 2026-07-03 | 2.8 A 1P 1C 3 | 47.3% Needs Improvement | MR7350 | CONNECTIVITY | Agent will email step-by-step factory reset instructions to the customer. |
| #LTS00130279INBOUND | 2026-07-03 | 1.8 A 1P 1C 3 | 52.1% Needs Improvement | MX4200 | CONFIGURATION | Customer advised to contact TP-Link business support for compatibility/configuration; ticket #130279 logged. |