girlyjoy.pocot@concentrix.com — Coaching Report

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


At a Glance

Calls HandledAvg Handle TimeTop ProductTop ProblemCases DocumentedCases Escalated
2613m 13sWHW03CONNECTIVITY263

Work Mix Lens

Scorecard

DimensionThis WeekCalls Reviewed
Accuracy2.3026
Protocol1.7026
Communication2.4026
Overall2.2026

Where Time Goes

Product Families

FamilyCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationNote
LN154m 33s2.802.002.003.00Outlier: 2.9x weekly median handle time
MX635m 34s2.623.501.832.67Outlier: 1.9x weekly median handle time
E318m 51s1.931.331.332.33
MR218m 42s3.204.502.502.50
WHW916m 18s2.302.331.562.22
SPN16m 58s3.002.002.002.00
EA76m 27s2.001.861.432.29

Key Observations

Problem Categories

CategoryCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationFocus Area?
CONNECTIVITY1217m 1s2.102.301.702.30
SETUP913m 31s2.302.701.802.40
ACCESS310m 30s2.704.002.302.70
CONFIGURATION113m 47s2.903.002.003.00

Week-over-Week Movement

What Went Well

Growth Opportunities

Next Week's Focus

Technical Accuracy

Improvement

Provided factually incorrect support-end date (August 9, 2025) for EA6350, materially misrepresenting Linksys policy (Call ID: 337a4bb4-583e-11f1-a03a-42010a62006f).

Improvement

Incorrectly instructed 30-second factory reset for EA7300 instead of 10–15 seconds, risking incomplete reset (Call ID: 80b8e19a-5854-11f1-961e-42010a62006f).

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

Incorrect URL guidance could mislead customer and prevent access to router admin interface.

Improvement

Materially incorrect advice could lead to customer purchasing incompatible hardware.

Coaching Moments

No additional coaching moments were extracted after the technical review.

Escalation Lessons: What L2 Did

— — Resolved

— — Resolved

— — Resolved

Coach Appendix

Weekly pattern unavailable.

Focus points: Improve accuracy in reset procedures and model-specific guidance; Enforce protocol for collecting model/serial numbers in every call; Reduce premature escalation to paid support without basic troubleshooting

This Week's Calls

CaseDateScoreDirectionProductCategoryOutcome
#LTS001307142026-05-25 13:32:40+00:001.70INBOUNDEA6350ACCESSCustomer to try uninstall/reinstall the app; no further action taken by agent.
#LTS001307462026-05-25 16:12:18+00:001.60INBOUNDEA7300CONNECTIVITYAgent refused further support due to warranty status, offered to email setup instructions, and suggested paid support. No resolution achieved.
#LTS000980762026-05-25 20:53:30+00:003.40INBOUNDMX6200CONNECTIVITY2.4 GHz network restored and child node paired; customer can now connect devices.
#TE001307872026-05-25 21:37:52+00:001.80INBOUNDWHW03SETUPEscalated to Level 2; callback scheduled.
#LTS001308622026-05-26 13:42:23+00:001.80INBOUNDEA8100CONNECTIVITYAgent will email setup instructions; customer to perform another factory reset and reconfigure router. No confirmation of resolution or follow-up scheduled.
#LTS001308952026-05-26 16:04:54+00:003.50INBOUNDMX6200CONNECTIVITYNode LED is solid white; advise to relocate to intended position and verify Wi-Fi connectivity. Recommend follow-up if issues persist.
#LTS001308952026-05-26 16:25:12+00:001.50INBOUNDMX6200CONNECTIVITYAgent falsely claimed prior agent resolved the issue; no resolution or next step provided.
#LTS001309112026-05-26 17:26:02+00:001.80INBOUNDWHW01SETUPAgent offered to email generic setup instructions; no live verification of pairing or connectivity performed. Customer left to self-resolve.
#TE000233482026-05-26 18:54:18+00:001.40OUTBOUNDMX6200CONNECTIVITYNo resolution achieved. Customer advised to monitor and call back if issue persists. No KB article, email, or self-help path provided.
#LTS001242872026-05-26 18:57:23+00:001.50INBOUNDMX5500CONNECTIVITYCustomer decided to order VLP01 nodes based on agent's incorrect advice.
#TE001309632026-05-26 20:46:57+00:001.60INBOUNDEA7430CONNECTIVITYAgent instructed customer to perform a factory reset (30-second press) and offered to send email instructions; no verification, no follow-up scheduled, no case created.
#LTS001011532026-05-26 21:44:20+00:003.00INBOUNDWHW03CONNECTIVITYNodes showed solid blue and new SSID was visible, but connection stability was inconsistent. Customer reported temporary success but signal fluctuations and node reconnection issues. No further escalation or follow-up scheduled.
#LTS001312112026-05-28 12:58:08+00:003.50INBOUNDWHW03ACCESSCustomer will reset the router using the recovery key and then log into the app with the newly created admin password.
#LTS001312152026-05-28 13:10:21+00:002.80INBOUNDEA8300SETUPUse the local web interface at http://192.168.1.1 to finish router setup. No verification was performed.
#LTS001312172026-05-28 13:13:39+00:003.40INBOUNDMR7350SETUPCustomer will connect to the router’s default Wi-Fi network, access http://myrouter.local in a browser, and follow the on-screen setup wizard. Agent will email additional guidance.
#LTS001312382026-05-28 15:04:53+00:003.00INBOUNDE2500CONNECTIVITYAgent claimed to send reset instructions via email to unconfirmed address; no verification of fix or next steps established.
#LTS001304632026-05-28 16:06:10+00:003.00INBOUNDSPNM60CFSETUPAll LEDs are now solid white; network appears functional.
#LTS001312782026-05-28 17:41:28+00:001.30INBOUNDWHW03SETUPNo resolution achieved. Call ended without clear next steps or follow-up plan.
#LTS001312782026-05-28 17:52:29+00:001.60INBOUNDWHW03SETUPCustomer advised to contact ISP (Ry Broadband) to have the new Linksys router registered on their network.
#LTS001312992026-05-28 19:39:19+00:002.90INBOUNDWHW03CONFIGURATIONAgent sent email with KB article titled 'How to log into Linux mesh router surface' (likely typo for 'Linksys') and instructions to access myrouter.local to rename network. Advised to bypass browser security warning and try alternate browsers if needed.
#LTS001313062026-05-28 19:56:41+00:003.00INBOUNDEA7200ACCESSCustomer to perform the hard reset and follow the emailed instructions to set a new admin password.
#LTS001313242026-05-28 21:17:29+00:002.80INBOUNDLN11011202SETUPAll mesh nodes re‑added and internet works on laptop; advise customer to contact ISP regarding the blocked website.
#LTS000697402026-05-29 12:40:49+00:001.30INBOUNDE1000SETUPAdvised customer to purchase a new MR5500 router; no further troubleshooting.
#LTS001314202026-05-29 15:46:50+00:001.50INBOUNDE8450SETUPCustomer advised to contact ISP for WAN provisioning; no technical fix confirmed.
#LTS001314312026-05-29 16:28:33+00:003.00INBOUNDWHW03SETUPCustomer to perform factory reset of all nodes and re‑configure using default credentials; detailed email instructions to be sent.
#LTS000374602026-05-29 17:09:27+00:004.40INBOUNDMX2000SETUPSeparate 2.4 GHz and 5 GHz SSIDs created; customer confirmed both networks are visible.
#LTS001314522026-05-29 17:29:13+00:003.00INBOUNDMR9600CONNECTIVITYOffered to email detailed troubleshooting steps or provide paid support; no technical fix confirmed.
#LTS001314722026-05-29 19:26:07+00:001.50INBOUNDEA8100CONNECTIVITYAgent promised to send generic setup instructions via email and offered paid support ($15/hour).
#LTS001314312026-05-29 19:56:49+00:001.80INBOUNDWHW03SETUPNo payment captured; customer advised to call back later. No clear next step or alternative provided.