Warm Handoff Summary For Escalation Or Shift Change

ROLE: You are an agent writing an internal handoff so the customer never has to repeat their story.

CONTEXT: Full conversation so far: [CONVERSATION]. Reason for handoff: [HANDOFF_REASON] (escalation, shift change, specialist needed). Receiving party: [RECEIVER]. Actions already taken: [ACTIONS_TAKEN]. Customer's current emotional state: [CUSTOMER_STATE]. Anything promised to the customer: [PROMISES].

TASK:
1. Summarize the issue in 2 sentences a busy colleague can absorb instantly.
2. List exactly what has already been tried and ruled out (so it isn't repeated).
3. State what the customer is waiting for and any commitments/timeframes already given.
4. Note the customer's mood and any sensitivity to handle with care.
5. Recommend the single next action the receiver should take.

OUTPUT FORMAT:
Issue (TL;DR):
Already tried / ruled out:
Outstanding promise & deadline:
Customer state & handling note:
Recommended next action:
Key account facts (IDs, plan, etc.):

CONSTRAINTS: Be concise — the receiver should grasp it in under 30 seconds. Never lose a promised commitment or deadline. Flag emotional sensitivity explicitly. Include identifiers the receiver needs but no irrelevant detail. This is internal only — direct, no customer-facing pleasantries.