paolo.ebora@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 |
|---|---|---|---|---|---|
| 5 | 28m 4s | MR2000 | CONNECTIVITY | 5 | 5 |
Work Mix Lens
- Escalation-heavy week: 5 TE-owned calls vs 0 LTS queue calls.
- Coach as an escalation owner: emphasize case progression, diagnostics, documentation, and L2-ready handoffs.
Scorecard
| Dimension | This Week | Calls Reviewed |
|---|---|---|
| Accuracy | 2.40 | 5 |
| Protocol | 1.80 | 5 |
| Communication | 2.00 | 5 |
| Overall | 2.12 | 5 |
Where Time Goes
Product Families
| Family | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Note |
|---|---|---|---|---|---|---|---|
| MR | 1 | 46m 21s | 1.40 | 1.00 | 2.00 | 2.00 | Outlier: 1.6x weekly median handle time |
| EA | 1 | 44m 20s | 1.30 | 1.00 | 1.00 | 2.00 | Outlier: 1.5x weekly median handle time |
| WRT | 1 | 28m 54s | 3.00 | 4.00 | 2.00 | 2.00 | |
| MBE | 1 | 16m 8s | 1.30 | 1.00 | 1.00 | 2.00 | |
| MX | 1 | 4m 36s | 3.60 | 5.00 | 3.00 | 2.00 |
Key Observations
- MR is the slowest family at 46m 21s; outlier: 1.6x weekly median handle time.
- EA is the slowest family at 44m 20s; outlier: 1.5x weekly median handle time.
Problem Categories
| Category | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Focus Area? |
|---|---|---|---|---|---|---|---|
| SETUP | 1 | 46m 21s | 1.40 | 1.00 | 2.00 | 2.00 | ✓ |
| CONNECTIVITY | 3 | 29m 47s | 1.87 | 2.00 | 1.33 | 2.00 | ✓ |
| ACCESS | 1 | 4m 36s | 3.60 | 5.00 | 3.00 | 2.00 |
Week-over-Week Movement
- Protocol moved up 0.33 vs. last week.
- Average handle time moved down by 7m 45s.
- Family swing: MX handle time moved down by 46m 55s vs. last week.
- Family swing: WRT handle time moved up by 16m 48s vs. last week.
What Went Well
- Effective appointment rescheduling
> “Do you want to do it earlier? Like how early? Oh, 4:00 p.m. tomorrow afternoon. Um, you have nothing in between that? 4:00 is good for me. I can make that work.”
- Correct router admin access guidance
> “Accessed router admin interface at http://[REDACTED_PHONE]… Verified network status showing two green checkmarks indicating internet and LAN connectivity.”
Growth Opportunities
- Technical accuracy in troubleshooting
> “Lead status right there is that red purple right now. or what's it called sir? okay. just be careful sir, ok? Just check the light. you can step down from the ladder. okay. Before I give the next instructions. okay. to go. Red, you're talking about the spectrum modem right?”
Next step: Use KB-verified URLs (e.g., myrouter.local), avoid unsupported reset methods, and confirm WAN status before proceeding.
- Resolution verification & self-help resources
> “Claimed firmware reflash could take 24 hours to ‘sink in’… Misdefined Mbps as megabytes per second… No self-help resources or follow-up path provided.”
Next step: Verify internet connectivity post-troubleshooting, provide KB articles, and confirm customer understanding of next steps.
Next Week's Focus
- Collect essential device details (serial number, warranty status, firmware version) on every call to inform troubleshooting and escalation decisions.
- Implement post-resolution validation – confirm wired/wireless connectivity and provide self-help resources (e.g., KB articles, setup guides).
- Practice structured escalation handoffs – document L1 steps clearly and ensure L2 has all context to avoid repeat contacts.
Technical Accuracy
Improvement
“Lead status right there is that red purple right now. or what's it called sir? okay. just be careful sir, ok? Just check the light. you can step down from the ladder. okay. Before I give the next instructions. okay. to go. Red, you're talking about the spectrum modem right?”
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
Note: Performed a firmware reflash on the EA7450 without verifying internet connectivity afterward and provided materially incorrect technical information (e.g., reflash takes 24 hours, Mbps = megabytes per second). No self-help resources or follow-up path provided.
Strength
Note: Correctly identified and guided access to router admin via http://[REDACTED_PHONE], aligned with KB for WRT Series.
Coaching Moments
No additional coaching moments were extracted after the technical review.
Escalation Lessons: What L2 Did
#TE00130897 — Resolved by Level 2
- What L1 saw: MR2000 router not receiving internet from Spectrum modem; unable to access router admin page.
- Why it escalated: L1 provided incorrect URLs, suggested unsupported reset method, and failed to verify WAN connectivity.
- Related call chain: 4 prior contacts with inconsistent guidance and no resolution.
- What L2 did:
1. Verified physical connections and modem status.
2. Guided customer to correct router admin URL and login.
3. Confirmed WAN connectivity and reconfigured Wi-Fi settings.
- Current state: Resolved.
- L1 learning points:
1. Always verify modem WAN status before router troubleshooting.
2. Use only KB-validated URLs for router access.
3. Confirm resolution with customer and provide self-help resources.
#TE00131280 — Resolved by Level 2
- What L1 saw: EA7450 unable to access websites; extender functional but main router showing “no internet.”
- Why it escalated: L1 performed firmware reflash without verifying connectivity and provided incorrect technical information.
- Related call chain: 1 prior contact with unresolved issue.
- What L2 did:
1. Diagnosed DNS and firewall misconfiguration.
2. Reverted to factory settings and reconfigured Wi-Fi.
3. Validated internet access post-fix.
- Current state: Resolved.
- L1 learning points:
1. Verify internet connectivity immediately after firmware updates.
2. Avoid misleading statements about update durations.
3. Collect serial number and warranty status for hardware issues.
Coach Appendix
Highest-signal trend: Technical inaccuracies in troubleshooting (incorrect URLs, unsupported reset methods, unresolved connectivity) caused repeated escalations. Focus next week on KB validation, resolution verification, and structured escalation documentation to reduce repeat contacts and improve first-contact resolution.*
This Week's Calls
| Case | Date | Score | Direction | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #TE00130897 | 2026-05-26 23:43:57+00:00 | 1.40 | OUTBOUND | MR2000 | SETUP | No fix achieved; advised customer to contact ISP and provided ticket number TE00130897. |
| #TE00131280 | 2026-05-28 19:49:58+00:00 | 1.30 | OUTBOUND | EA7450 | CONNECTIVITY | Advised customer to consider purchasing a new MX6202 mesh system as replacement for EA7450; no self-help resources, KB articles, or follow-up path provided. |
| #TE00127677 | 2026-05-28 22:56:35+00:00 | 1.30 | INBOUND | MBE7000 | CONNECTIVITY | Suggested purchasing additional mesh nodes (MX series, 'MPE 7000') without providing configuration steps, compatibility verification, or support path. |
| #TE00131348 | 2026-05-29 01:55:31+00:00 | 3.60 | OUTBOUND | MX4200 | ACCESS | Appointment rescheduled to 4:00 PM PST tomorrow. |
| #TE00131346 | 2026-05-29 20:18:28+00:00 | 3.00 | OUTBOUND | WRT3200ACM | CONNECTIVITY | Wired internet restored via switch; customer advised to reconnect Wi-Fi later but no further support provided. |