Design service recovery strategies that turn failures into loyalty-building moments.
## Service Recovery Paradox Strategy Design service recovery strategies for [COMPANY_NAME]: **Service Failure:** [FAILURE] **Recovery Resources:** [RESOURCES] **Customer Segments:** [SEGMENTS] **The Service Recovery Paradox:** Customers who experience a failure followed by excellent recovery can become MORE loyal than if the failure never occurred. **Recovery Framework:** ### 1. Acknowledge (within minutes) - Detect the failure proactively when possible - Reach out before the customer contacts you - Use empathetic, human language - Take full ownership — never blame the customer ### 2. Apologize (genuine, not scripted) - Specific apology for the exact impact on THEM - "I'm sorry that [SPECIFIC_IMPACT]" not generic "We apologize for any inconvenience" - Match the apology intensity to the failure severity ### 3. Act (fast and decisive) | Failure Type | Immediate Action | Recovery Bonus | Follow-Up | |---|---|---|---| | [Type 1] | [Fix] | [Bonus — upgrade, credit, gift] | [Check-in timing] | | [Type 2] | [Fix] | [Bonus] | [Check-in timing] | | [Type 3] | [Fix] | [Bonus] | [Check-in timing] | ### 4. Exceed Expectations - Fix the problem + give something unexpected - Personalize the recovery (not a generic coupon) - Make it memorable: handwritten note, personal call from manager - Follow up to ensure the recovery landed well ### 5. Learn and Prevent - Root cause analysis for every P1/P2 failure - Share learnings with the team - Update processes to prevent recurrence - Track: Did the recovered customer become an advocate? **ROI of Great Recovery:** - Recovered customers have [X]% higher lifetime value - They tell [X] people about great recovery (vs [X] about the failure) - Repeat purchase rate after recovery: [X]%
Free to copy and use. Compatible with Claude 4 Opus, GPT-5, Gemini 2.5 Pro, Llama 4.
Describe the service failure in [FAILURE] and recovery resources.
Initial release
Sign in and download this prompt to leave a review.