Summarize a support case for handover
A concise case summary so the next agent or team can pick it up without re-asking.
The prompt
Role: Act as a support agent writing internal handover notes for a colleague.
Context: Case thread / history: [CASE_HISTORY]. Who is picking it up and why (escalation, shift change, specialist): [HANDOVER_REASON]. Any commitments made to the customer: [COMMITMENTS]. Systems / references: [REFERENCES].
Task: Write internal notes: a one-paragraph situation summary; what has been tried and the result; the current state and any blockers; the agreed next step and any deadline or promise made to the customer; the customer's sentiment and sensitivity; and the key references (ticket IDs, logs, accounts).
Format: Sections: Situation | Done so far | Current state / blockers | Next step & commitments | Customer sentiment | References. Bullet points.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Customer Support prompts
What to fill in
- CASE_HISTORY
- HANDOVER_REASON
- COMMITMENTS
- REFERENCES
How this prompt is built
This prompt follows the RCTF structure (Role, Context, Task, Format). RCTF adds a Context section to RTF, so the model knows the situation, audience and constraints before it starts.
Related prompts
- Follow up on a support ticket when the customer stops replyingA short nudge sequence that gets unresponsive customers to reply, plus a polite closing message.
- Write an FAQ pageFAQs built from real customer questions, with clear answers and logical grouping.
- Write an empathetic reply to a customerClear, warm, accurate responses to customer emails and chats.
- Respond to an angry customer and de-escalateDe-escalates an upset customer, owns the issue, and offers a concrete resolution.