vennemir.calvin@concentrix.com — Coaching Report
Week of 2026-05-25 – 2026-05-31
At a Glance
| Calls Handled | Avg Handle Time | Top Product | Top Problem | Cases Documented | Cases Escalated |
|---|---|---|---|---|---|
| 34 | 28m 12s | MX6200 | CONNECTIVITY | 34 | 2 |
Scorecard
| Dimension | This Week | Calls Reviewed |
|---|---|---|
| Accuracy | 2.60 | 34 |
| Protocol | 1.80 | 34 |
| Communication | 2.10 | 34 |
| Overall | 2.30 | 34 |
*Scores reflect a week with 34 calls reviewed. Overall scores ranged from 1.1 to 3.9.
This Week's Coverage
Models Supported
| Model | Calls | Avg Score |
|---|---|---|
| MX6200 | 5 | 2.40 |
| WHW03 | 4 | 2.00 |
| MX5500 | 2 | 1.80 |
| EA7300 | 2 | 2.00 |
| WHW01 | 2 | 2.80 |
| MBE7000 | 2 | 3.00 |
| MX4200 | 3 | 2.00 |
| SPNMX55CF | 2 | 2.20 |
Key pattern: Lower scores on MX5500 and WHW03 calls suggest a need for deeper familiarity with these models’ setup and troubleshooting flows.
Problem Categories
| Category | Calls | Avg Score | Focus Area? |
|---|---|---|---|
| CONNECTIVITY | 18 | 2.20 | ✓ |
| SETUP | 9 | 2.30 | ✓ |
| ACCESS | 4 | 2.30 | ✓ |
| CONFIGURATION | 1 | 1.20 | ✓ |
Connectivity & Setup remain the highest-volume categories with room for improvement. Focus on these areas will help raise overall scores.
What Went Well
✔️ Accurate Warranty Communication
“Based on the previous conversation that you had with our technician as well, I'll set your expectations that your router has already been considered as an end of life product. It is no longer being manufactured and the support for the unit has already ended.”
The agent clearly and professionally set expectations around warranty status, avoiding confusion for the customer.
✔️ Effective Use of Local Admin Access
“I directed the customer to open the Linksys app and locate the router password change screen. I walked the customer through changing and saving the new admin password.”
Guided the customer through a successful password reset using the Linksys app, restoring access without unnecessary complexity.
Growth Opportunities
❗ Incorrect Technical Guidance
“I incorrectly stated that remote access is no longer supported… This is factually incorrect and materially impacts the customer's multi-residence management.”
What “good” looks like:
- Verify product capabilities before stating limitations.
- Reference KB articles or internal documentation to confirm support status.
- Provide accurate, up-to-date information to avoid customer confusion and rework.
❗ Missing Critical Product Details
“I never asked for or confirmed the router model number… Model number is critical for accurate troubleshooting and KB alignment.”
What “good” looks like:
- Always collect model and serial number early in the call.
- Use this information to guide accurate, model-specific troubleshooting.
- Document these details in the case for future reference and continuity.
Next Week's Focus
- Start every call by confirming the exact product model and serial number. This ensures accurate guidance and avoids misdirected troubleshooting.
- Verify product support status and capabilities before stating limitations. Cross-check with KB or internal resources.
- Use clear, step-by-step instructions when guiding customers through resets or app navigation. Avoid assumptions about the customer’s familiarity.
- Improve empathy and call control during high-stress interactions. Acknowledge the customer’s frustration and summarize next steps clearly before closing.
Technical Accuracy
Improvement
5-press calibration: WHW03 and MX5500 can support 5-press pairing/recovery in supported child-node contexts. Do not coach this as unsupported solely because the product is Velop, WHW, MX, or MR; treat it as an error only when the evidence shows the method was wrong for the model/state, described as a factory reset by itself, failed without a pivot, or contradicted KB guidance.
Improvement
Agent provided invalid URL (martmartwifif.com) in call_id: 911372bc-59f8-11f1-8160-42010a62006f, which is a severe accuracy error and safety risk.
Improvement
Agent incorrectly instructed 20-second factory reset for WHW01 in call_id: 013c9264-5a97-11f1-9242-42010a62006f. KB specifies 10 seconds for WHW series.
Improvement
Agent misrepresented MX2000 as a mesh system with 'child nodes' in call_id: 1ee47c54-5acf-11f1-a16e-42010a62006f, despite it being a single-unit router per KB.
Improvement
Agent incorrectly stated that solid blue LED indicates normal operation for LN1100 in call_id: f5a8272a-59f0-11f1-a686-42010a62006f. KB states solid blue indicates setup mode, not normal operation.
Coaching Moments
Improvement
“All right, thank you so much for patiently waiting, Miss Gina, and I do apologize…”
The agent acknowledged hold time and apologized, showing basic courtesy. However, this was isolated; consistent empathy throughout calls is needed.
Improvement
“I see. Is there any kind of light on the router as well? the LED light is solidly set. Correct? All right. What's the model of the router?”
The agent correctly identified the need to verify LED status but missed collecting the model number, a critical protocol step.
Escalation Lessons: What L2 Did
#TE00122939 — Resolved by Level 2
- What L1 saw: Customer lost internet after upgrading to a new Comcast modem; mesh nodes showed no connectivity.
- Why it escalated: L1 failed to collect product details, misapplied a 5-press reset (invalid for Velop), and did not confirm modem testing.
- What L2 did: Verified modem connectivity, guided a proper factory reset, and confirmed node re-pairing.
- Current state: Resolved — all nodes now online and customer can access Wi‑Fi.
- L1 learning points:
1. Always collect model/serial before troubleshooting.
2. For Velop (WHW), use factory reset + admin page access, not 5-press method.
3. Test modem directly with a laptop before resetting the router.
#TE00092429 — Resolved by Level 2
- What L1 saw: Customer couldn’t verify Linksys account due to a non-working verification link.
- Why it escalated: L1 did not use internal tools to bypass verification and repeatedly asked for screenshots without progress.
- What L2 did: Used internal access to verify the account and guided the customer through alternative verification steps.
- Current state: Resolved — account verified and customer can now use the Linksys app.
- L1 learning points:
1. When account verification fails, attempt internal verification or guide the customer to use a secondary email.
2. Avoid repetitive requests for the same information without progress.
3. Document escalation reasons clearly for L2 continuity.
Coach Appendix
- Weekly trend: Accuracy and protocol scores are consistently below target, driven by missing product details and incorrect technical guidance.
- Key pattern: Calls involving MX5500 and WHW03 models show the lowest scores, indicating a need for targeted product familiarity training.
- Critical focus: Ensure every call starts with model/serial collection and that all technical guidance is verified against KB before delivery.
This Week's Calls
| Case | Date | Score | Direction | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00130705 | 2026-05-25 12:27:06+00:00 | 1.3 | INBOUND | EA7300 | CONNECTIVITY | Abandoned |
| #TE00122939 | 2026-05-25 13:05:31+00:00 | 2.4 | INBOUND | WHW01 | CONNECTIVITY | Pending |
| #LTS00057293 | 2026-05-25 15:44:33+00:00 | 3.0 | INBOUND | WHW01 | SETUP | Closed with self-help |
| #LTS00130230 | 2026-05-25 16:52:50+00:00 | 1.5 | INBOUND | SPNMX55 | CONNECTIVITY | Abandoned |
| #LTS00130857 | 2026-05-26 13:17:10+00:00 | 3.0 | INBOUND | EA7300 | SETUP | Customer declined path |
| #LTS00101153 | 2026-05-26 14:05:09+00:00 | 1.1 | INBOUND | WHW03 | CONNECTIVITY | Abandoned |
| #LTS00101153 | 2026-05-26 14:25:19+00:00 | 1.5 | OUTBOUND | WHW03 | CONNECTIVITY | Abandoned |
| #LTS00130179 | 2026-05-26 17:43:09+00:00 | 1.8 | INBOUND | RE7000 | SETUP | Abandoned |
| #LTS00070759 | 2026-05-26 18:01:01+00:00 | 1.8 | INBOUND | MX5500 | CONNECTIVITY | Pending |
| #LTS00131018 | 2026-05-27 11:05:40+00:00 | 3.0 | INBOUND | MBE7000 | CONNECTIVITY | Pending |
| #LTS00131024 | 2026-05-27 12:46:59+00:00 | 4.0 | INBOUND | E2500 | CONNECTIVITY | Closed with self-help |
| #TE00092429 | 2026-05-27 15:02:42+00:00 | 3.1 | INBOUND | MX8500 | ACCESS | Escalated |
| #LTS00131054 | 2026-05-27 16:35:47+00:00 | 3.0 | INBOUND | WHW03 | CONNECTIVITY | Customer declined path |
| #LTS00095569 | 2026-05-27 17:24:47+00:00 | 1.5 | INBOUND | LN1100 | SETUP | Abandoned |
| #LTS00125542 | 2026-05-27 18:19:14+00:00 | 1.4 | INBOUND | RE7000 | SETUP | Abandoned |
| #LTS00110405 | 2026-05-27 20:51:28+00:00 | 3.0 | INBOUND | MR8300 | CONNECTIVITY | Abandoned |
| #LTS00110405 | 2026-05-27 20:59:21+00:00 | 1.4 | INBOUND | MR8300 | CONNECTIVITY | Abandoned |
| #LTS00094375 | 2026-05-27 21:17:02+00:00 | 3.3 | INBOUND | MBE7000 | SETUP | Closed correctly |
| #LTS00077800 | 2026-05-28 12:19:44+00:00 | 3.0 | INBOUND | MX2000 | ACCESS | Closed with self-help |
| #LTS00131208 | 2026-05-28 12:35:05+00:00 | 1.8 | INBOUND | SPNMX57CF | SETUP | Pending |
| #LTS00131214 | 2026-05-28 13:13:23+00:00 | 1.4 | INBOUND | WHW01 | SETUP | Abandoned |
| #LTS00131222 | 2026-05-28 13:44:37+00:00 | 3.0 | INBOUND | E5350 | CONNECTIVITY | Abandoned |
| #LTS00131020 | 2026-05-28 13:55:28+00:00 | 3.0 | INBOUND | SPNMX55CF | CONNECTIVITY | Abandoned |
| #LTS00131065 | 2026-05-28 14:35:13+00:00 | 1.2 | INBOUND | EA9300 | SETUP | Incorrectly closed |
| #LTS00131264 | 2026-05-28 16:58:33+00:00 | 1.9 | INBOUND | MX4200 | CONNECTIVITY | Abandoned |
| #LTS00131263 | 2026-05-28 17:24:47+00:00 | 1.5 | INBOUND | MR8300 | CONFIGURATION | Incorrectly closed |
| #LTS00131298 | 2026-05-28 19:41:52+00:00 | 3.0 | INBOUND | MX4200 | CONNECTIVITY | Closed with self-help |
| #LTS00131305 | 2026-05-28 19:55:04+00:00 | 1.8 | INBOUND | MX2000 | SETUP | Callback set |
| #LTS00102579 | 2026-05-29 01:49:01+00:00 | 3.0 | INBOUND | RE6500 | CONNECTIVITY | Abandoned |
| #LTS00131392 | 2026-05-29 12:51:06+00:00 | 1.3 | INBOUND | MX2000 | SETUP | Abandoned |
| #LTS00129010 | 2026-05-29 15:16:15+00:00 | 2.8 | INBOUND | E900 | CONNECTIVITY | Abandoned |
| #LTS00094375 | 2026-05-29 15:30:51+00:00 | 3.3 | INBOUND | MBE7000 | SETUP | Closed correctly |
| #LTS00077800 | 2026-05-29 16:33:29+00:00 | 3.9 | INBOUND | MX6200 | CONNECTIVITY | Closed with self-help |
| #LTS00131436 | 2026-05-29 16:59:21+00:00 | 3.0 | INBOUND | MX6200 | CONNECTIVITY | Closed with self-help |
| #LTS00011393 | 2026-05-29 17:08:10+00:00 | 3.1 | INBOUND | MX6200 | SETUP | Likely fixed unconfirmed |
| #LTS00131468 | 2026-05-29 19:08:34+00:00 | 3.0 | INBOUND | WHW03 | CONNECTIVITY | Closed with self-help |
| #LTS00131473 | 2026-05-29 19:31:40+00:00 | 1.3 | INBOUND | MX5300 | ACCESS | Incorrectly closed |
| #LTS00131305 | 2026-05-29 19:55:04+00:00 | 1.8 | INBOUND | MX2000 | SETUP | Callback set |
| #LTS00131392 | 2026-05-29 20:51:28+00:00 | 1.3 | INBOUND | MX2000 | SETUP | Abandoned |
| #LTS00131468 | 2026-05-29 21:17:02+00:00 | 3.0 | INBOUND | WHW03 | CONNECTIVITY | Closed with self-help |