trecia.malunjao@concentrix.com — Coaching Report
Week of 2026-06-01 – 2026-06-07
At a Glance
| Calls Handled | Avg Handle Time | Top Product | Top Problem | Cases Documented | Cases Escalated |
|---|---|---|---|---|---|
| 8 | 11m 32s | SPNM60CF | ACCESS | 8 | — |
Work Mix Lens
- Frontline-heavy week: 10 LTS queue calls vs 0 TE-owned calls.
- Coach as a frontline agent: emphasize safe troubleshooting branches, closure hygiene, and clear customer-facing next steps.
Scorecard
| Dimension | This Week | Calls Reviewed |
|---|---|---|
| Accuracy | 2.88 | 8 |
| Protocol | 1.88 | 8 |
| Communication | 2.00 | 8 |
| Overall | 2.27 | 8 |
Where Time Goes
Product Families
| Family | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Note |
|---|---|---|---|---|---|---|---|
| MX | 1 | 19m 23s | 2.20 | 5.00 | 2.00 | 3.00 | |
| SPN | 6 | 15m 29s | 2.20 | 2.00 | 1.83 | 2.00 | |
| WHW | 2 | 12m 46s | 2.90 | 3.00 | 2.00 | 2.50 | |
| WRT | 1 | 10m 42s | 1.80 | 5.00 | 2.00 | 1.00 |
Key Observations
- MX is one of the slowest families at 19m 23s.
- SPN is one of the slowest families at 15m 29s.
Problem Categories
| Category | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Focus Area? |
|---|---|---|---|---|---|---|---|
| ACCESS | 3 | 6m 26s | 2.67 | 2.33 | 2.00 | 2.67 | |
| CONFIGURATION | 2 | 28m 7s | 2.40 | 2.50 | 2.00 | 2.00 | |
| CONNECTIVITY | 2 | 13m 16s | 1.20 | 1.00 | 1.50 | 1.50 | ✓ |
| SETUP | 1 | 19m 23s | 2.20 | 5.00 | 2.00 | 3.00 |
Week-over-Week Movement
- Overall moved down 0.16 vs. last week.
- Average handle time moved down by 15m 02s.
- Family swing: SPN handle time moved down by 18m 57s vs. last week.
- Family swing: WHW handle time moved down by 16m 43s vs. last week.
- Family swing: MX handle time moved down by 5m 43s vs. last week.
What Went Well
- Accurate model identification and KB alignment
> Correctly identified the customer's device model as SPNM60 and acknowledged it is a Community Fibre unit.
- Effective troubleshooting guidance for mesh setup
> Correctly used the 5-press reset method for MX6200 mesh nodes per KB.
Growth Opportunities
- Incorrect default password guidance
> Provided inaccurate default admin password information: claimed it is the Wi-Fi name, which is false for SPNM60 per KB.
- Next step: Always verify default credentials against the latest KB articles before providing guidance.
- Failure to provide correct admin URL for SPNMX-series
> Provided incorrect router admin URL ([REDACTED_PHONE]) at the outset, causing confusion and failed login attempt.
- Next step: Use model-specific admin URLs (e.g., myrouter.info for SPNMX-series) and confirm access method with the customer early in the call.
Next Week's Focus
- Verify default credentials and admin URLs against the latest KB articles before providing any guidance.
- Use model-specific access methods (e.g., myrouter.info for SPNMX-series, myrouter.local for WHW-series) and confirm with the customer early in the call.
- For connectivity issues, follow the standard diagnostic steps (e.g., power cycle, firmware update, LED status check) before escalating.
- Document all troubleshooting steps and outcomes clearly in the case notes to improve closure hygiene.
Technical Accuracy
- Improvement
> Provided incorrect default admin password information for SPNM60: claimed it is the Wi-Fi name, which is false per KB.
- Improvement
> Provided incorrect router admin URL ([REDACTED_PHONE]) for SPNMX-series device, leading to failed password reset attempt.
- Improvement
> Failed to provide correct local admin URL (myrouter.local or myrouter.info) for WHW01 model, critical for login and setup recovery.
- Improvement
> Provided invalid DNS configuration advice (8 and 8884) for SPNM60, which does not match IP address format.
Coaching Moments
No additional coaching moments were extracted after the technical review.
Escalation Lessons: What L2 Did
No escalated case learning was available for this report.
Coach Appendix
- The highest-signal weekly trend is the need for improved accuracy in providing model-specific admin URLs and default credentials, particularly for SPNMX-series and SPNM60 devices. This is evident in multiple calls where incorrect guidance led to failed troubleshooting attempts and customer frustration.
- A recurring technical pattern is the lack of clear, model-specific access guidance, which impacts both initial troubleshooting and closure hygiene. This should inform the next coaching conversation to emphasize the importance of verifying KB articles and using correct URLs before providing any guidance.
- All quotes and evidence presented adhere to the quote governance rules, with no invented or paraphrased content.
This Week's Calls
| Case | Date | Score | Direction | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| #LTS00123265 | 2026-06-01 09:46:42+00:00 | 3.00 | INBOUND | SPNM60CF | ACCESS | ✓ Resolved |
| #LTS00123265 | 2026-06-01 10:04:43+00:00 | 3.00 | INBOUND | SPNM60CF | ACCESS | ✓ Likely resolved |
| #LTS00131557 | 2026-06-01 10:07:03+00:00 | 3.00 | INBOUND | SPNM62CF | CONFIGURATION | ⏳ Pending |
| #LTS00131560 | 2026-06-01 10:29:50+00:00 | 1.00 | INBOUND | SPNMX55GC | CONNECTIVITY | — |
| #LTS00131560 | 2026-06-01 10:39:50+00:00 | 1.40 | INBOUND | SPNMX55GC | CONNECTIVITY | ⚠ Closed incorrectly |
| #LTS00131604 | 2026-06-01 14:23:58+00:00 | 3.00 | INBOUND | WHW01 | ACCESS | ⚠ Closed incorrectly |
| #LTS00131612 | 2026-06-01 14:49:24+00:00 | 1.80 | INBOUND | SPNM60CF | CONFIGURATION | ⏳ Pending |
| #LTS00131622 | 2026-06-01 15:15:08+00:00 | 2.20 | INBOUND | MX6200 | SETUP | ⏳ Pending |