Customer support
Prepare an escalation summary for a difficult ticket
Open with the decision you need from the receiving team, then give the customer's goal, the evidence and what has already been tried. State open contradictions plainly. The reader should be able to decide without reopening the full ticket thread.
A text to start with
I'm escalating a ticket to [team or person]. The customer wants [goal]. Ticket history and evidence: [paste]. Actions already taken: [list with dates]. The unresolved issue: [issue]. Facts that conflict with each other: [conflicts]. Write a summary that opens with the decision I need, then gives the customer goal, evidence, prior actions and open issue. Mark assumptions as assumptions, and show each conflict with its sources.
Example request. Change the details to fit your situation.Escalation summary worksheet
Ticket reference: [ ] Escalating to: [ ] Decision needed, as a question: [ ] Deadline for the decision, if any: [ ] Customer goal: [ ] Evidence available and where it is stored: [ ] Actions already taken, with dates: [ ] Unresolved issue: [ ] Facts that conflict: [ ] Source of each conflicting fact: [ ] Assumptions made so far: [ ] What the customer has been told: [ ] Owner until the team accepts: [ ] Follow-up date: [ ]
Hidden conflicts and repeated assumptions
A summary can look tidy because it smoothed over a contradiction, such as two timestamps that disagree or a customer account that differs from the logs. Check that every conflict you know about appears in the text. Look for assumptions inherited from earlier agents that were restated as facts, and for dates or amounts copied without confirming the source. The decision requested should be a clear question, and any evidence referenced should be named so the receiving team can find it.
Ask another agent to check the result
Check whether this escalation summary hides contradictory facts or restates assumptions as confirmed. List each conflict between the ticket evidence and the summary, and each statement that rests on an unverified assumption. Say whether the decision requested is clear enough to answer, and if not, what question it should ask.
Hand off and keep the thread alive
Send the summary through your normal escalation channel and name who owns the ticket until the receiving team accepts it. Tell the customer only what has been decided about their expectations, not what the team might do. Note when you expect a response and check back then. Record the team's decision in the ticket when it arrives.