edgarianmark.catulong@concentrix.com — Coaching Report

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


At a Glance

Calls HandledAvg Handle TimeTop ProductTop ProblemCases DocumentedCases Escalated
1033m 27sMBE7000CONNECTIVITY55

Scorecard

DimensionThis WeekCalls Reviewed
Accuracy2.0010
Protocol1.3010
Communication2.1010
Overall1.9810

Score range this week: 1.1 – 3.0


Where Time Goes

Product Families

FamilyCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationNote
MBE368m 15s1.301.001.332.00Outlier: 1.5x weekly median handle time
MX721m 42s2.442.711.292.43

Key Pattern:

MBE calls dominate both volume and duration, with significantly lower accuracy and protocol scores. This suggests complex mesh troubleshooting scenarios requiring deeper product-specific guidance and structured problem-solving.

Problem Categories

CategoryCallsAvg Handle TimeAvg OverallAvg AccuracyAvg ProtocolAvg CommunicationFocus Area?
CONNECTIVITY730m 32s1.811.861.292.14
ACCESS323m 04s2.272.331.332.33

Drill-Down Insights:


Week-over-Week Movement

Focus Points: Prioritize accuracy recovery while maintaining communication gains.


What Went Well

  1. Proactive Log Collection

> “Agent attempted to capture logs from child nodes, which may provide useful diagnostic data for senior tier review.”

#TE00128179

  1. Callback Discipline

Scheduled concrete follow-ups with specific timelines (e.g., “callback within 2–3 hours”) and captured customer availability, ensuring accountability.

#TE00130759

  1. Empathy in Frustration

Acknowledged customer dissatisfaction calmly and apologized for inconvenience, maintaining professionalism during escalated conversations.

#TE00130759


Growth Opportunities

  1. Technical Accuracy in Guidance

> “Provided incorrect router web UI URL ([REDACTED_PHONE] instead of [REDACTED_PHONE]) at [60:00], contradicting KB.”

#TE00128179

Next Step: Always verify URLs and credentials against the latest KB before issuing instructions. Use the official myrouter.local or http://[REDACTED_PHONE] format for MBE7000.

  1. Product Information Collection

> “Failed to collect product model, serial number, or warranty status despite troubleshooting a hardware-specific issue.”

#TE00130759

Next Step: Start every call by confirming the exact product model, serial number, and warranty status. This enables accurate troubleshooting and eligibility checks.


Next Week's Focus


Technical Accuracy

Improvement

Agent provided incorrect web UI URL for MBE7000, leading to access failure and customer frustration.

#TE00128179

Improvement

Agent provided incorrect login credentials for MBE7000, violating KB and causing customer access issues.

#TE00128179

Improvement

Agent provided materially false information about product discontinuation, violating KB and misleading the customer.

#TE00130759

Improvement

Agent used unauthorized remote access tool, violating security and support protocol.

#TE00128179

Improvement

Agent provided materially incorrect information about firmware support for discontinued hardware.

#TE00128179


Escalation Lessons: What L2 Did

#TE00128179 — Resolved by Level 2

- Performed full mesh reset and rebuild per universal_mesh_full_rebuild.md.

- Verified firmware versions across nodes and addressed cloud-service discontinuation artifacts.

- Conducted remote session using supported tools to analyze logs and confirm hardware health.

1. Always validate URLs/credentials against KB before instructing customers.

2. For mesh instability, guide through full factory reset and Pair-button rebuild.

3. Use only authorized remote-access tools; document all steps for handoff.


Coach Appendix

Weekly Trend Summary:

Accuracy dipped due to inconsistent technical guidance (URLs, credentials, product discontinuation claims). Handle time increased as MBE cases required deeper troubleshooting. Key focus: reinforce KB adherence, strict product-info collection, and authorized tool usage to regain accuracy while preserving communication gains.

Recurring Pattern:

Calls involving discontinued products or cloud-service changes triggered misinformation and unresolved issues. Ensure clear eligibility criteria are communicated upfront, and avoid speculative statements about product lifecycles.

(No additional quotes introduced beyond those surfaced in main report sections.)


This Week's Calls

CaseDateScoreDirectionProductCategoryOutcome
#TE001281792026-05-261.7OUTBOUNDMBE7000CONNECTIVITYCallback_or_followup_set
#TE001307592026-05-261.8OUTBOUNDMX2000CONNECTIVITYCallback_or_followup_set
#TE001281792026-05-261.1OUTBOUNDMBE7000CONNECTIVITYPending_resolution
#TE001309942026-05-273.0OUTBOUNDMX6200ACCESSAbandoned_or_vague
#TE000924292026-05-271.8OUTBOUNDMX8500ACCESSAbandoned_or_vague
#TE001307592026-05-273.0OUTBOUNDMX2000CONNECTIVITYCallback_or_followup_set
#TE001307592026-05-273.0OUTBOUNDMX2000CONNECTIVITYPending_resolution
#TE001278122026-05-291.5INBOUNDMX6200CONNECTIVITYAbandoned_or_vague
#TE001281792026-05-291.1OUTBOUNDMBE7000CONNECTIVITYAbandoned_or_vague
#TE001307592026-05-283.0OUTBOUNDMX2000CONNECTIVITYPending_resolution