ayman.elamin@sutherlandglobal.com — Coaching Report

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


At a Glance

Calls HandledAvg Handle TimeTop ProductTop ProblemCases DocumentedCases Escalated
915m 29sEA7300CONNECTIVITY7

Work Mix Lens

Scorecard

DimensionThis WeekCalls Reviewed
Accuracy2.569
Protocol1.899
Communication2.229
Overall2.319

Where Time Goes

Product Families

FamilyCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationNote
EA322m 8s1.672.331.672.33
MBE119m 56s3.004.003.002.00
MX214m 55s3.103.002.502.50
RE112m 14s1.001.001.001.00
WHW17m 22s1.101.001.002.00

Key Observations

Problem Categories

CategoryCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationFocus Area?
CONNECTIVITY418m 41s2.752.752.002.50
ACCESS210m 20s1.401.501.502.00
HARDWARE215m 49s2.102.502.001.50
SETUP17m 22s1.101.001.002.00

Week-over-Week Movement

What Went Well

  1. Accurate troubleshooting guidance for EA7300 password reset

> Guided customer to perform a 20-second factory reset using the pinhole button. Instructed to connect to the router's default Wi‑Fi network (Linksys). Directed to access http://[REDACTED_PHONE] via mobile browser and complete login. Assisted with setting a new admin password meeting complexity requirements.

#LTS00131992

  1. High accuracy scores in specific calls

Accuracy score of 4.0 in calls with IDs: 8d59dab4-5dac-11f1-ac90-42010a5a3f83, b786a278-5f1d-11f1-91a2-42010a5a3f83, 14d33664-5f3f-11f1-8e5f-42010a5a3f8a, 0c386334-5f4f-11f1-9f77-42010a5a3f83


Growth Opportunities

  1. Protocol adherence and case documentation

> Failed to create or cite a HappyFox case number in multiple calls, violating standard case management protocol.

#LTS00131571 | #LTS00131585 | #LTS00131629

Next step: Always document cases in HappyFox before concluding calls, even for self-help resolutions.

  1. Technical accuracy and troubleshooting completeness

> Provided incorrect or incomplete troubleshooting steps, such as suggesting a 5-press pairing method without confirming the product model, and failing to verify internet connectivity after node recovery.

#LTS00131585 | #GI00132004

Next step: Verify device model/serial before recommending model-specific procedures, and always confirm post-troubleshooting connectivity.


Next Week's Focus

  1. Document every call in HappyFox – Create or cite a case number before ending each call, even for self-help scenarios.
  2. Collect model/serial numbers – Ask for and record these upfront to avoid repeat contacts and enable accurate troubleshooting.
  3. Verify resolutions – After guiding troubleshooting, confirm the customer’s issue is resolved (e.g., “Is your internet working now?”).
  4. Follow KB procedures – Use documented reset durations (e.g., 10–15 seconds for mesh nodes) and avoid guesswork.

Technical Accuracy

Improvement

Agent failed to follow standard troubleshooting flow for RE6400 extender (reset, power-cycle, LED interpretation) and did not verify warranty status. Recommended purchasing a new unit without confirming the fault.

#LTS00131629

Improvement

Agent provided incorrect advice for email-based password reset, stating the customer needed to be physically next to the device, which is not required per KB. Failed to follow documented password-recovery process.

#LTS00131830

Improvement

Agent incorrectly identified model as 'WN03' (non-existent) and failed to perform basic mesh troubleshooting. Provided inaccurate warranty and pricing information.

#LTS00062401

Strength

Agent correctly guided customer through factory reset and password reconfiguration for EA7300, achieving technical resolution.

#LTS00131992

Improvement

Agent provided incorrect reset procedure ('press the space' instead of 10-second hold) and failed to collect model/serial details for mesh node troubleshooting.

#GI00132019


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
#LTS001315712026-06-01 11:25:11+00:003.2INBOUNDMX2000HARDWARE✓ Resolved
#LTS001315852026-06-01 13:05:39+00:003.0INBOUNDMX5500CONNECTIVITY⏳ Pending
#LTS001316292026-06-01 15:34:42+00:001.0INBOUNDRE6400HARDWARE⚠ Closed incorrectly
#LTS001318302026-06-02 15:12:26+00:001.1INBOUNDEA7300ACCESS⏳ Pending
#LTS000624012026-06-02 17:06:56+00:001.1INBOUNDWHW01PSETUP⚠ Closed incorrectly
#LTS001319922026-06-03 07:27:46+00:002.2INBOUNDEA7300ACCESS✓ Likely resolved
#GI001320042026-06-03 11:26:36+00:003.0INBOUNDMBE7000CONNECTIVITY✓ Likely resolved
#GI001320192026-06-03 13:20:53+00:002.8INBOUNDCONNECTIVITY↻ Callback set
#GI001320192026-06-03 14:16:21+00:002.8INBOUNDCONNECTIVITY↻ Callback set
#LTS001322562026-06-04 15:37:21+00:001.7INBOUNDEA7300ACCESS⏳ Pending