trecia.malunjao@concentrix.com — Coaching Report

Week of 2026-05-25 – 2026-05-31


At a Glance

Calls HandledAvg Handle TimeTop ProductTop ProblemCases DocumentedCases Escalated
1633m 58sWHW03CONNECTIVITY161

Work Mix Lens

Scorecard

DimensionThis WeekCalls Reviewed
Accuracy2.5616
Protocol1.8116
Communication2.0616
Overall2.3816

Where Time Goes

Product Families

FamilyCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationNote
LN162m 22s1.801.002.002.00Outlier: 2.3x weekly median handle time
SPN634m 26s2.402.331.672.33
WHW829m 29s2.472.751.752.12
MX225m 6s3.003.502.002.00
OTHER16m 51s1.803.002.001.00
EA16m 3s3.004.002.002.00

Key Observations

Problem Categories

CategoryCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationFocus Area?
CONNECTIVITY1336m 25s2.232.311.772.08
ACCESS211m 4s2.402.002.501.50
SETUP167m 43s1.401.001.002.00
NO TROUBLESHOOTING NEEDED19m 30s2.805.003.003.00

Week-over-Week Movement

What Went Well

  1. Accurate mesh topology guidance

> "Wired child nodes must connect to the Linksys parent node or a switch attached to it, not the ISP router."

#LTS00130834

  1. Clear password recovery path

> "Use the recovery key on the router label to reset the admin password."

#LTS00131031

  1. Polite closure with self-help

> "I’ve emailed a reset guide — please try these steps and reply if you need further assistance."

#LTS00130852


Growth Opportunities

  1. Technical accuracy in mesh troubleshooting

> "Wi-Fi 5 supports up to 2 Gbps"(Typical max ~866 Mbps on 5 GHz band)

Next step: Always verify product family and reference KB for speed limits before advising.

#LTS00130691

  1. Protocol rigor in case closure

> "Customer advised to relocate nodes without verification of internet connectivity."

Next step: Confirm WAN status and document outcomes before closing.

#LTS00130697


Next Week's Focus


Technical Accuracy

Improvement: Materially incorrect Wi-Fi 5 speed claim

"Wi-Fi 5 supports up to 2 Gbps"

Note: Contradicts KB — typical max ~866 Mbps on 5 GHz band.

#LTS00130691

Improvement: Incorrect Velop LED interpretation

"Nodes turned solid green"

Note: Velop shows solid purple (ready) or white (online), not green.

#LTS00130697

Improvement: Expired warranty denial

"No support available due to expired warranty"

Note: Basic password retrieval and self-help always available regardless of warranty.

#LTS00130727

Improvement: Admin password confusion

"Router admin password is the same as Wi‑Fi password"

Note: LN1600 uses default ‘admin’ or recovery key — never Wi‑Fi password.

#TE00131379


Coaching Moments

No additional coaching moments extracted after technical review.


Escalation Lessons: What L2 Did

#TE00131379 — Resolved by Level 2

1. Verified firmware versions and WAN status.

2. Guided through 5-press pairing (valid for LN1600).

3. Confirmed node LED progression to solid white.

- Confirm product family (LN = Cognitive Mesh) before pairing method.

- Never equate admin password with Wi‑Fi password.

- Validate WAN and LED states after every reset.


Coach Appendix

Highest-signal trend: Inconsistent technical accuracy in mesh node troubleshooting (incorrect speed limits, LED states, password guidance) drives prolonged handle times and low accuracy scores. Focus next week on model-specific KB validation and WAN verification protocols to reduce LN/SPN outliers.


This Week's Calls

CaseDateScoreDirectionProductCategoryOutcome
#LTS001306912026-05-25 09:38:53+00:001.80OUTBOUNDWHW03CONNECTIVITYSchedule a callback to complete the mesh rebuild and verify speed improvement.
#LTS001306912026-05-25 10:11:38+00:003.00OUTBOUNDWHW03CONNECTIVITYSpeed improved after node reboot and repositioning; no further action required.
#LTS001306972026-05-25 10:44:16+00:001.60INBOUNDWHW03CONNECTIVITYNo confirmed resolution. Customer advised to relocate nodes without verification of internet connectivity.
#LTS001307272026-05-25 14:42:10+00:001.80INBOUNDVLP01ACCESSNo resolution or next step provided; customer was incorrectly told no support could be offered due to expired warranty.
#LTS001308342026-05-26 10:04:19+00:003.00OUTBOUNDMX5500CONNECTIVITYCustomer will rewire according to agent's guidance; agent available for callback if issue persists.
#LTS001308462026-05-26 12:42:21+00:003.00INBOUNDEA7200CONNECTIVITYCustomer declined paid support; no self-help or alternative guidance provided.
#LTS001308522026-05-26 13:03:29+00:003.00INBOUNDWHW03CONNECTIVITYCustomer to follow emailed guide: factory reset node, place near parent, use Pair button. No follow-up scheduled.
#LTS000343162026-05-27 10:29:51+00:003.00INBOUNDMX6200CONNECTIVITYTicket created and emailed to the customer; advised to monitor router lights and reopen the case if the problem returns.
#LTS001310202026-05-27 10:58:41+00:003.00INBOUNDSPNMX55CFCONNECTIVITYAgent advised customer to return the unit to Amazon or request a replacement from the ISP without validating compatibility or offering troubleshooting steps.
#LTS001310212026-05-27 12:30:25+00:003.00INBOUNDWHW03CONNECTIVITYAgent will email guide for factory reset and reconfiguration. Customer to attempt proper 10-second reset and verify WAN status if issue persists.
#LTS001310312026-05-27 13:20:14+00:003.00INBOUNDSPNM60CFACCESSCustomer reset router admin password using recovery key and regained access to router settings and internet.
#LTS001310412026-05-27 14:21:46+00:002.80INBOUNDSPNM60CFNO TROUBLESHOOTING NEEDEDInformed customer that WPS is not supported; no further steps provided.
#LTS001311972026-05-28 10:12:13+00:001.70INBOUNDSPNMX56CFCONNECTIVITYAdvised customer to contact ISP (Community Fibre) without validating physical connection or correct troubleshooting path.
#LTS001310642026-05-28 13:02:08+00:003.00INBOUNDWHW03CONNECTIVITYNone provided; call ended without a clear path forward.
#LTS001310642026-05-28 13:07:06+00:003.00INBOUNDWHW03CONNECTIVITYAgent will send a text message to allow the customer to schedule a callback with the appropriate representative.
#LTS001310642026-05-28 13:18:24+00:001.40INBOUNDWHW03CONNECTIVITYNo resolution; agent suggested paid support. Recommend modem activation verification, correct factory reset (10-15s), and topology confirmation per KB.
#LTS001312232026-05-28 13:45:38+00:002.50INBOUNDSPNM60TBCONNECTIVITYAdvised customer to contact Ring support for possible firmware updates and retry connecting the doorbell to the 2.4 GHz network.
#TE001313792026-05-29 08:29:37+00:001.80INBOUNDLN1600CONNECTIVITYEscalated to senior technical support; customer to be contacted within 24–48 hours.
#LTS001313852026-05-29 10:59:36+00:001.40INBOUNDSPNMX55GCSETUPNo fix achieved; recommend Level-2 escalation and full mesh rebuild per KB.