# zither.calvin@linksys.com — Coaching Report
## Week of 2026-05-25 – 2026-05-31

---

## At a Glance
| Calls Handled | Avg Handle Time | Top Product | Top Problem | Cases Documented | Cases Escalated |
| --- | --- | --- | --- | --- | --- |
| 1 | 5m 23s | MBE7000 | SETUP | 1 | — |

## Scorecard
| Dimension | This Week | Calls Reviewed |
| --- | --- | --- |
| Accuracy | 5.00 | 1 |
| Protocol | 4.00 | 1 |
| Communication | 3.00 | 1 |
| Overall | 3.90 | 1 |

## Where Time Goes
**Product Families**
| Family | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Note |
| --- | --- | --- | --- | --- | --- | --- | --- |
| MBE | 1 | 5m 23s | 3.90 | 5.00 | 4.00 | 3.00 |  |

**Key Observations**
- MBE is one of the slowest families at 5m 23s.

**Problem Categories**
| Category | Calls | Avg Handle Time | Avg Overall | Avg Accuracy | Avg Protocol | Avg Communication | Focus Area? |
| --- | --- | --- | --- | --- | --- | --- | --- |
| SETUP | 1 | 5m 23s | 3.90 | 5.00 | 4.00 | 3.00 |  |

## Week-over-Week Movement
- Improve call closure protocols and provide self-help resources to customers.

## What Went Well

zither.calvin demonstrated strong technical foundations this week:

> **Accurate product identification**  
> Correctly identified the MBE7000 as a standalone router and not a mesh child node, avoiding unnecessary troubleshooting steps.  
> [#LTS00087422](https://linksys.happyfox.com/staff/ticket/87422/)

> **Protocol adherence**  
> Collected both model and serial numbers for the new and existing devices, fulfilling basic protocol requirements and gathering essential information for accurate assessment.  
> [#LTS00087422](https://linksys.happyfox.com/staff/ticket/87422/)

> **Technically accurate solutioning**  
> Provided a valid alternative solution (MX6200) for the customer's mesh expansion need, showing good product knowledge and problem-solving approach.  
> [#LTS00087422](https://linksys.happyfox.com/staff/ticket/87422/)

---

## Growth Opportunities

### Incomplete call closure
The call ended abruptly without confirming customer understanding, offering self-help resources, or setting clear next steps. Good looks like:  
- **Recap & confirm**: Always summarize the issue and solution, then ask "Does that make sense?" or "Do you have any other questions?"  
- **Offer resources**: Provide a KB article, product comparison page, or email summary when appropriate  
- **Set expectations**: Clearly state next steps (e.g., "Please return the device and we'll process your exchange")  
- **Close politely**: Use a friendly closing phrase and invite further contact if needed  

> Did not confirm customer understanding of the issue or next steps before ending the call at [05:00]. Allowed call to end abruptly with minimal closing protocol — no recap, no confirmation of action items, no offer of further assistance.  
> [#LTS00087422](https://linksys.happyfox.com/staff/ticket/87422/)

### Lack of self-help resources
The customer was left without written guidance or easy access to product information. Good looks like:  
- **Proactively share**: Offer links to product specs, compatibility matrices, or setup guides  
- **Follow-up email**: When possible, send a summary email with key details and resources  
- **Direct to self-help**: Guide customers to relevant support articles or product pages  

> Did not offer any self-help path such as a KB article, product comparison page, or email with details.  
> [#LTS00087422](https://linksys.happyfox.com/staff/ticket/87422/)

---

## Next Week's Focus

- **Implement the 3R Close**: Before ending any call, run through Recap, Resources, and Request (for confirmation). Practice this on every call.
- **Resource readiness**: Keep top 3 product comparison KB articles bookmarked for quick sharing during mesh/setup calls.
- **Confirm understanding**: After explaining a solution, always ask a closed-ended question ("Does that resolve your issue?" or "Is there anything else I can help with?").
- **Document next steps**: When directing customers to return items or order replacements, note exact steps in the case and offer to email them.

---

## Technical Accuracy

### **Strength**
> Correctly identified the MBE7000 as a standalone router and provided a technically accurate alternative solution (MX6200) for the customer's mesh expansion need.  
> [#LTS00087422](https://linksys.happyfox.com/staff/ticket/87422/)

### **Improvement**
> Call ended without confirming customer understanding, offering self-help resources, or setting a follow-up. No case was created or follow-up scheduled despite unresolved setup need.  
> [#LTS00087422](https://linksys.happyfox.com/staff/ticket/87422/)

---

## Coaching Moments

### **Improvement**
> Oh, man, I didn't know there is a such thing. So what do I need to  
> [#LTS00087422](https://linksys.happyfox.com/staff/ticket/87422/)

*Note: The agent missed an opportunity to acknowledge the customer's frustration here. When customers express surprise or disappointment (e.g., "Oh man, I didn't know..."), validate their feelings ("I understand this can be frustrating") before explaining constraints. This builds rapport and makes the solution easier to accept.*

---

## Escalation Lessons: What L2 Did

*No escalation cases were processed this week, so there are no Level 2 resolution patterns to learn from.*

---

## Coach Appendix

*Highest-signal weekly trend:* With perfect accuracy but lower communication scores, the key opportunity is enhancing customer engagement during constraint explanations. The agent excels at technical assessment but needs to pair this with clearer communication protocols—especially during call closure—to ensure customers leave feeling informed and supported. Focus next week on implementing the 3R Close framework to bridge this gap.

---

## This Week's Calls

| Case | Date | Score | Direction | Product | Category | Outcome |
|---|---|---|---|---|---|---|
| [#LTS00087422](https://linksys.happyfox.com/staff/ticket/87422/) | 2026-05-26 | 3.9 | INBOUND | MBE7000 | SETUP | ⏳ Pending |