trecia.malunjao@concentrix.com — Coaching Report

Week of 2026-06-01 – 2026-06-07


At a Glance

Calls HandledAvg Handle TimeTop ProductTop ProblemCases DocumentedCases Escalated
811m 33sSPNM60CFACCESS8

Work Mix Lens

Scorecard

DimensionThis WeekCalls Reviewed
Accuracy2.888
Protocol1.888
Communication2.008
Overall2.288

Where Time Goes

Product Families

FamilyCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationNote
MX119m 23s2.205.002.003.00
SPN615m 29s2.202.001.832.00
WHW212m 46s2.903.002.002.50
WRT110m 42s1.805.002.001.00

Key Observations

Problem Categories

CategoryCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationFocus Area?
ACCESS36m 26s3.002.332.002.67
CONFIGURATION228m 7s2.402.502.002.00
CONNECTIVITY212m 56s1.201.001.501.50
SETUP119m 23s2.205.002.003.00

Week-over-Week Movement

What Went Well

  1. Accurate device identification

> “All right. Who is your internet service provider, sir? So I see, sir, that the model number of your router is SP-NM-60, right?”

#LTS00131557

  1. KB-aligned technical guidance

> “Performed 5-press reset on parent node… Connected phone to default Velop Setup SSID (Velop Setup EFA).”

#LTS00131622

  1. Clear warranty/communication framing

> “Accurately communicated warranty status and explained paid-support option with clear pricing ($15 for one hour).”

#LTS00131604


Growth Opportunities

  1. Use model-specific admin URLs

What went well: Guided SPNM60 users to [REDACTED_PHONE].

What to improve: For SPNMX-series devices, always use myrouter.info per KB.

> “Instructed customer to open a browser and navigate to incorrect IP addresses ([REDACTED_PHONE] and [REDACTED_PHONE])”

#LTS00131560

  1. Validate resolution before closure

What to improve: Confirm network functionality and set clear follow-up paths.

> “Call ended without confirming resolution or setting follow-up path.”

#LTS00131622


Next Week's Focus

  1. Verify admin URL by device family

- SPNM/SPNMX → myrouter.info

- WHW → myrouter.local or myrouter.info

- MX → myrouter.info

  1. Implement resolution confirmation checklist

- “Can you confirm the 2.4 GHz network is now visible?”

- “Is the Ring doorbell now connected and stable?”

  1. Document serial numbers and warranty status

- Capture early, verify eligibility, and note in HappyFox.


Technical Accuracy

> Provided incorrect admin URLs ([REDACTED_PHONE], [REDACTED_PHONE]) for SPNMX-series device; correct URL is myrouter.info per KB.

#LTS00131560

> Incorrectly advised DNS entries ('8' and '8884') which are invalid IP formats; led to 'invalid parameters' error.

#LTS00131612

> Failed to validate network functionality after firmware update on MX6200; call ended without confirmation.

#LTS00131622

> Correctly guided customer through 5-press reset for MX6200 and connection to 'Velop Setup' SSID, aligning with KB procedures.

#LTS00131622


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


This Week's Calls

CaseDateScoreDirectionProductCategoryOutcome
#LTS001232652026-06-01 09:46:42+00:003.00INBOUNDSPNM60CFACCESSCustomer logged in successfully after resetting the admin password.
#LTS001232652026-06-01 10:04:43+00:003.00INBOUNDSPNM60CFACCESSCustomer independently located the Instant-Privacy setting and confirmed resolution. No agent validation or follow-up performed.
#LTS001315572026-06-01 10:07:03+00:003.00INBOUNDSPNM62CFCONFIGURATION2.4 GHz network now visible and Ring doorbell connected; monitor for future drops and call back if issue recurs.
#LTS001315602026-06-01 10:29:50+00:001.00INBOUNDSPNMX55GCCONNECTIVITYNone – no information available.
#LTS001315602026-06-01 10:39:50+00:001.40INBOUNDSPNMX55GCCONNECTIVITYNone – password reset failed and no follow-up action was agreed upon.
#LTS001316042026-06-01 14:23:58+00:003.00INBOUNDWHW01ACCESSAgent suggested using the router password to log in via the app; no further steps were taken.
#LTS001316122026-06-01 14:49:24+00:001.80INBOUNDSPNM60CFCONFIGURATIONAgent will send an email with further instructions; customer advised to try a different browser on a PC.
#LTS001316222026-06-01 15:15:08+00:002.20INBOUNDMX6200SETUPCustomer instructed to run firmware update and complete setup; no confirmed resolution or follow-up path established.
#LTS001021562026-06-03 14:05:06+00:002.80INBOUNDWHW03CONNECTIVITYOffered paid‑support or a self‑help link; customer declined.
#LTS001264132026-06-04 14:23:06+00:001.80INBOUNDWRT1200ACACCESSAdvised customer to contact T-Mobile support for the VOIP adapter. No additional resources or case documentation provided.