Issue-to-Resolution

Issue resolved, customer retained, and lesson captured for prevention

A customer complained. You fixed it. It will happen again.

• Area: Operations
• Time savings: Typical run: Hours to days depending on severity
• Try it: "Customer reports a problem, complaint, or service failure"
• Compounding: Each run refines templates and context — 2 automated steps improve with accumulated data
• Frequency: Per trigger event
• Published: 2026-08-01

Inputs

• 🏢 Customer name and client_id
• 📋 Issue description (what happened, when, impact)
• 📋 Severity assessment (critical / major / minor)
• 📋 Any prior communication about the issue
• 📦 Desired outcome from customer's perspective

What BOB does

1. escalation-routing → assess severity, classify issue, determine routing and urgency
2. Acknowledge issue to customer within SLA window — confirm receipt and expected timeline
3. Implement fix or workaround — resolve the immediate problem
4. Confirm resolution with customer — verify satisfaction, document what was done
5. client-health-tracker → update health score, flag if at-risk, log recovery action

Outputs

• 📋 Severity Decision.md
• 📄 RCA Document.md
• 📋 Resolution Record.md
• 📊 Health Score.md
• 📋 Lessons Log.md