prompt

Post-Resolution Follow-up Framework

Design a follow-up sequence to verify resolution satisfaction and prevent ticket reopening.

Updated June 2026
The prompt
Resolved ticket summary:
Issue: {{resolved_issue}}
Resolution: {{solution_given}}
Customer type: {{customer_type}}
Resolution time: {{hours_to_resolve}}

Design a post-resolution sequence that:
1. Day 0 (immediate): Confirms resolution receipt, next steps if unsolved
2. Day 3: Quick check-in—is the issue truly resolved?
3. Day 10: Gather satisfaction feedback + CSAT survey
4. Day 30: Verify no regression, offer preventative tips

Include:
- Tone for each touchpoint (warm, brief, scannable)
- Reopen trigger phrases (if customer says X, auto-escalate)
- Knowledge base link to prevent future similar issues

Optimize for mobile readability.
Did it work? Rate this prompt

Variables

Issue Category (technical, billing, feature, account)
Type of Solution (workaround, fix, refund, update)
Customer Segment (free, basic, enterprise)
Hours to First Resolution

Details

Author

AI Khazna

License

Security

Type

prompt

Related assets

More curated picks in Customer Support.

Audit before you install

Run any source through our checks - AI visibility, security, performance, and stack detection.

More in Customer Support