jeneth.villanil@concentrix.com — Coaching Report

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

## At a Glance

## Scorecard

Scores reflect 1 calls reviewed. Overall score range: 3.00 (lowest) to 3.00 (highest).

## This Week's Coverage

Models Supported

Problem Categories

The single call this week involved an MX8500 Velop mesh setup issue. While the overall score is mid-range, accuracy and protocol scores highlight room for improvement in technical troubleshooting and process adherence.

## What Went Well

No transcript highlights available for this week. The call summary indicates the agent acknowledged the customer's frustration and attempted to guide through resets, which is a positive starting point.

## Growth Opportunities

1. Use the correct pairing method for MX8500 Velop devices

The MX8500 Velop does not support the 5‑press pairing method. Instead, use the Velop web UI or mobile app to add child nodes. This ensures reliable mesh setup and avoids unnecessary loops.

Next step: Review the official Linksys knowledge base article on adding nodes via the Velop app for MX8500 models.

1. Verify warranty and collect serial numbers before troubleshooting

Warranty status and serial numbers are essential for determining support options and appropriate troubleshooting paths. Collecting this information early helps avoid misdirected efforts and ensures you can offer the right solution (e.g., warranty repair vs. self‑help).

Next step: Add a quick checklist at the start of every Velop/mesh call: ask for model, serial number, and warranty status, and confirm the customer can access the admin interface.

## Next Week's Focus

• Practice the correct node‑addition flow for MX8500 using the Velop app — locate the step-by-step guide and rehearse the key prompts you’ll give customers.
• Create a brief warranty/serial‑number verification script — 30 seconds at the start of the call to capture essential details.
• When a node is flashing red, confirm power and internet connectivity first before moving to resets or pairing.
• If a call remains unresolved after initial troubleshooting, document the exact steps tried and escalate promptly — avoid “pending resolution” closures unless a clear next action is set.

## Technical Accuracy

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.

#LTS00067263

Improvement

Agent did not verify warranty status or collect serial numbers, which are critical for troubleshooting and escalation.

#LTS00067263

Improvement

Call closed with operational_closure_status 'pending_resolution' and technical_resolution_status 'not_fixed', indicating unresolved technical issue.

#LTS00067263

No dedicated technical accuracy signals were extracted this week beyond the items above. Review the Growth Opportunities and Escalation Lessons sections for technical coaching patterns.

## Coaching Moments

Improvement

Provided incorrect pairing method (5‑press) for MX8500 Velop.

Note: The 5‑press pairing method is not supported on MX8500 Velop devices. Use the Velop web UI or app to add child nodes.

#LTS00067263

Improvement

Failed to verify or collect warranty information or serial number.

Note: Warranty and serial numbers are required before proceeding with advanced troubleshooting or escalation.

#LTS00067263

Improvement

Did not create or reference a case/ticket number.

Note: Always create a HappyFox ticket for unresolved or complex issues to maintain a clear audit trail and ensure continuity of care.

#LTS00067263

## Escalation Lessons: What L2 Did

No escalations occurred this week. The single call was closed as “pending_resolution,” indicating an unresolved technical issue that may require escalation next time. When similar cases arise, consider escalating early if:

• The customer cannot access the Velop admin interface or app.
• Nodes remain offline after basic power cycling and proximity checks.
• The customer expresses frustration or uncertainty about next steps.

## Coach Appendix

Internal use only — not for agent distribution.

Highest-signal weekly trend: The sole call involved an MX8500 Velop mesh setup failure where the agent used an unsupported 5‑press pairing method and did not collect warranty/serial information, resulting in an unresolved “pending_resolution” closure. This pattern suggests a need for targeted training on Velop-specific troubleshooting flows and the importance of early warranty verification.

Recurring technical/process pattern: Calls involving mesh node pairing often require strict adherence to model-specific procedures (e.g., app-based addition for MX8500) and upfront collection of device identifiers. Ensure future calls capture these details before proceeding with troubleshooting to reduce repeat contacts and escalation needs.

## This Week's Calls