24Calls
2.47Avg Score
16m 55sAvg Handle Time
17Documented
2Escalated
Week-over-Week Progress
Scorecard
| Dimension | Week Average | Calls Reviewed |
|---|---|---|
| Overall | 2.47 | 24 |
| Technical Accuracy | 2.42 | 24 |
| Protocol | 1.79 | 24 |
| Communication | 2.5 | 24 |
Main focus: Model/serial collection
V2 Rubric (Shadow Grading)
V2 overall: 43.25% across 20 v2-scored calls this week5 auto-zeros
| Category | Week Average |
|---|---|
| Resolution | 1.98 |
| Technical Accuracy | 2.47 |
| Communication | 2.69 |
| Customer Ownership | 3.46 |
| Escalation Judgment | 2.62 |
| Customer Experience | 1.62 |
- Unresolved: 12
- Successful Resolution: 4
- Partial Resolution: 3
- Appropriate Escalation: 1
Where Did the Time Go
By Product Family
| Family | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Note |
|---|---|---|---|---|---|---|---|
| E | 3 | 25m 30s | 1.23 | 1.67 | 1.0 | 1.33 | Outlier: 1.7x weekly median handle time |
| WHW | 1 | 24m 29s | 1.4 | 1.0 | 1.0 | 3.0 | Outlier: 1.7x weekly median handle time |
| MX | 9 | 18m 29s | 3.28 | 3.33 | 2.56 | 2.89 | |
| SPN | 1 | 14m 50s | 1.8 | 1.0 | 1.0 | 2.0 | |
| OTHER | 2 | 10m 10s | 2.05 | 1.0 | 1.0 | 2.0 | |
| EA | 2 | 8m 33s | 3.0 | 4.0 | 2.0 | 2.5 | |
| MR | 5 | 8m 06s | 2.08 | 1.6 | 1.4 | 2.6 |
By Problem Category
| Category | Calls | Avg Handle Time | Overall | Accuracy | Protocol | Comms | Focus? |
|---|---|---|---|---|---|---|---|
| CONNECTIVITY | 7 | 27m 52s | 2.4 | 1.86 | 1.43 | 2.14 | ✓ |
| SETUP | 3 | 31m 03s | 2.97 | 3.0 | 2.33 | 2.67 | |
| CONFIGURATION | 3 | 23m 48s | 2.0 | 1.67 | 1.67 | 2.67 | |
| ACCESS | 2 | 20m 22s | 2.4 | 2.5 | 1.0 | 3.0 | |
| NO TROUBLESHOOTING NEEDED | 1 | 24m 29s | 1.0 | 1.0 | 1.0 | 3.0 | |
| GENERAL INQUIRY | 1 | 10m 09s | 2.9 | 5.0 | 2.0 | 2.0 |
What You Did Well
- Polite and patient tonePresent across multiple callsAgent maintained a polite and patient tone throughout interactions, acknowledged customer concerns, and provided clear next steps where appropriate.Why this matters: Enhances customer experience and builds trust, encouraging customers to follow through on troubleshooting steps.
- Correct factory reset guidanceUsed in setup callsAgent correctly instructed the 5-press reset procedure for MX6200 and MR7310 models, aligning with KB documentation.Why this matters: Ensures devices are properly reset to factory defaults, resolving configuration issues effectively.
Growth Focus
- Model/serial collectionOccurred in 8 of 17 callsFailed to collect product model and serial number on multiple calls, critical for warranty verification and model-specific troubleshooting.Why this matters: Without model/serial, agents cannot access warranty info, apply correct procedures, or escalate appropriately, leading to misdiagnosis and repeat calls.Example: Call #LTS00134231: Agent never identified the router model despite multiple prompts, leading to incomplete troubleshooting.What better looks like: Always confirm product model and serial number within the first 2 minutes of the call, using KB prompts.
- Incorrect technical guidanceOccurred in 5 critical callsProvided factually incorrect information about mesh compatibility, LED states, and password reset methods, contradicting KB documentation.Why this matters: Incorrect guidance leads to unresolved issues, customer frustration, and potential hardware damage if misconfigured.Example: Call #LTS00134253: Advised WHW01 cannot mix with newer mesh nodes, violating velop_mesh_compatibility.md.What better looks like: Reference KB articles before providing technical advice; verify mesh compatibility charts and LED definitions.
Callback Flags
No callback chains detected.
Documentation Accuracy
No documentation mismatches detected this week.
Practice Plan
- Step 1Before closing any call where the issue is not confirmed fixed, ask the customer to test the fix on the call and confirm it worksWhy: Prevents callbacks due to unconfirmed resolutions and ensures customer satisfaction
- Step 2Always collect and verify product model and serial number within the first 2 minutes of every callWhy: Enables accurate troubleshooting, warranty checks, and proper escalation pathsThis week: #LTS00134231
- Step 3Reference KB articles before providing technical guidance on mesh compatibility, LED states, and password reset methodsWhy: Ensures accuracy and prevents misinformation that could cause hardware issues or misconfigurationThis week: #LTS00134253
- Step 4When advising factory resets, clearly state the correct duration (10-20 seconds) and expected LED behavior per KBWhy: Prevents incomplete resets and customer confusion about reset successThis week: #LTS00134950
- Step 5Verify internet connectivity at the modem with a direct Ethernet test before recommending router resetsWhy: Isolates ISP issues from router problems, reducing unnecessary troubleshooting steps
Escalation Lessons
#TE00134332 — MX6200
Status: pending_with_level_2_or_followup · Category: CONFIGURATION
What happened on the call: Escalated to Level-2 support; callback promised within 24-48 hours.
Why it escalated: Customer reported persistent DHCP duplication issue on MX6200 after exhaustive L1 troubleshooting
What L2 did:
- 1. Collected network logs from parent and affected child nodes
- 2. Verified firmware versions on all mesh nodes
- 3. Checked DHCP server configuration for IP reservation conflicts
- 4. Advised customer to monitor DHCP leases after reboot
L1 learning points:
- 1. Always verify firmware version when troubleshooting DHCP issues
- 2. Check DHCP server for IP reservation conflicts before escalating
- 3. Document customer-executed troubleshooting steps clearly
#LTS00132316 — MX8500
Status: resolved · Category: ACCESS
What happened on the call: Customer to power-cycle router and, if needed, perform a factory reset; no further verification or recovery-key guidance provided.
Evidence Calls
| Case | Date | Score | V2 | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00134231INBOUND | 2026-06-22 | 1.3 A 2P 1C 1 | 52.7% Needs Improvement | E5400 | CONNECTIVITY | Advised customer to contact ISP and call back if needed. No fix confirmed or actionable path provided. |
| #LTS00134253INBOUND | 2026-06-22 | 1.4 A 1P 1C 3 | 0.0% Needs Improvement | WHW01 | NO TROUBLESHOOTING NEEDED | Agent promised to email setup instructions and suggested customer call back for assistance. No valid technical resolution provided. |
| #LTS00134231INBOUND | 2026-06-22 | 1 A 1P 1C 1 | 0.0% Needs Improvement | E5400 | CONNECTIVITY | Agent advised purchasing a new router; no technical fix confirmed. |
| #LTS00134305INBOUND | 2026-06-22 | 2 A 1P 2C 3 | 0.0% Needs Improvement | MR7350 | CONNECTIVITY | Ticket created; customer will follow up after checking router settings locally. |
| #TE00134332INBOUND | 2026-06-22 | 2.8 A 5P 2C 3 | 39.3% Needs Improvement | MX6200 | CONFIGURATION | Escalated to Level-2 support; callback promised within 24-48 hours. |
| #LTS00134341INBOUND | 2026-06-22 | 2.9 A 5P 2C 2 | 14.6% Needs Improvement | EA8100 | SETUP | Provided correct setup instructions but did not confirm success; offered paid support; call ended without resolution. |
| #LTS00134492INBOUND | 2026-06-23 | 1.3 A 1P 1C 1 | 16.0% Needs Improvement | MR8300 | ACCESS | Admin password reset completed via recovery key; no further verification or next steps provided. |
| #LTS00134506INBOUND | 2026-06-23 | 2.9 A 4P 2C 3 | 66.5% Needs Improvement | MR7310 | SETUP | Provided reset instructions; offered email follow-up (incorrect address). No confirmed fix. |
| #LTS00079429INBOUND | 2026-06-23 | 2.8 A 2P 2C 2 | 78.7% Developing | MX6200 | SETUP | Customer confirmed internet is working; no further action required. Firmware update recommended for later. |
| #LTS00134602INBOUND | 2026-06-24 | 2.9 A 3P 2C 2 | 91.9% Meets / Exceeds | MX2000 | SETUP | Internet restored; advise to place child nodes 2‑3 ft from the parent, wait for them to turn solid blue, then configure SSID/password if desired. |
| dc03d50e-6ff7-11f1-890e-42010a62006fINBOUND | 2026-06-24 | 3.2 A 2P 3C 3 | — | MX4200 | GENERAL INQUIRY | Confirmed compatibility; incorrectly advised that MX-20MS3 nodes would display solid purple LED when ready to be added (should be solid blue per KB). |
| #LTS00134657INBOUND | 2026-06-24 | 2.8 A 1P 1C 2 | 58.8% Needs Improvement | A0303 | CONNECTIVITY | Agent will email step-by-step instructions for resetting and re-adding the extenders; optional paid support offered. |
| fecce5ba-7012-11f1-9b72-42010a62006fINBOUND | 2026-06-24 | 2.4 A 3P 2C 3 | 37.6% Needs Improvement | CONNECTIVITY | Node briefly came online but reverted to blinking red. Issue unresolved; customer advised to call back if problem persists. | |
| #LTS00132316INBOUND | 2026-06-24 | 2.8 A 1P 1C 3 | — | MX8500 | ACCESS | Customer to power-cycle router and, if needed, perform a factory reset; no further verification or recovery-key guidance provided. |
| #LTS00134815INBOUND | 2026-06-25 | 3.1 A 3P 2C 3 | 0.0% Needs Improvement | EA7200 | CONNECTIVITY | Email with reset/setup instructions to be sent; customer may opt for paid support if needed. |
| #LTS00134842INBOUND | 2026-06-25 | 3.4 A 5P 3C 3 | 82.3% Developing | MX6200 | SETUP | Agent will email setup instructions; customer to perform setup and reset child nodes if needed. Customer instructed to call back if issues persist. |
| 0ba3d0be-70e0-11f1-b894-42010a623f91INBOUND | 2026-06-25 | 4.8 A 5P 4C 4 | 95.2% Meets / Exceeds | MX6200 | CONNECTIVITY | Customer successfully reconnected to Wi-Fi and confirmed internet is working. No further steps needed. |
| #LTS00134942INBOUND | 2026-06-26 | 1.8 A 1P 1C 2 | 63.2% Needs Improvement | SPNMX57CF | ACCESS | Customer instructed to remove unknown devices and re-add them after identifying via MAC address; no confirmation of success or model verification. |
| #LTS00134950INBOUND | 2026-06-26 | 2.8 A 2P 2C 3 | 57.5% Needs Improvement | MX4200 | SETUP | Agent will email step-by-step reset and setup instructions; customer to perform reset and re-configure the mesh. |
| 0f9c086c-718a-11f1-8a62-42010a623f91INBOUND | 2026-06-26 | 4 A 5P 4C 3 | 94.1% Meets / Exceeds | MX2000 | CONNECTIVITY | TV reconnected to Wi-Fi; streaming apps now perform normally. |
| #LTS00134991INBOUND | 2026-06-26 | 1.4 A 1P 1C 3 | — | MR7350 | CONFIGURATION | None provided; call ended without actionable guidance or explanation of incompatibility. |
| #LTS00134991OUTBOUND | 2026-06-26 | 2.8 A 1P 1C 3 | — | MR7350 | CONFIGURATION | Agent will email detailed bridge‑mode and child‑node setup instructions to the customer. |
| 79ab89c6-7194-11f1-bd58-42010a62006fINBOUND | 2026-06-26 | 1.3 A 1P 1C 2 | 0.0% Needs Improvement | AE6000 | CONNECTIVITY | Agent stated the device is no longer supported; no further action or guidance provided. |
| #LTS00135003INBOUND | 2026-06-26 | 1.4 A 2P 1C 2 | 16.7% Needs Improvement | E7350 | CONNECTIVITY | Agent sent email with factory-reset and setup instructions; call ended without confirmation of resolution or next steps. |