# How to escalate a support ticket without making the customer repeat themselves Escalating to tier 2, engineering or the account manager? What context to pass so the customer never has to explain twice, with a copyable escalation note. ## The short answer To escalate a support ticket without making the customer repeat themselves, pass an escalation note with the ticket: who the customer is, what they are trying to do, what happened, what you already tried, what they were told, how urgent it is, and what you need from the next person. The receiver should act without rereading the thread. Customers rarely mind being passed on. They mind being asked the same questions again. Every repeated question tells them the company does not talk to itself. Below you will find what to include, a note you can copy, what each destination needs, and how to do it from your AI assistant. ## Why context gets lost on escalation The first-line agent spent twenty minutes with the customer. They know the order number, the error message, the three things that did not work and the fact that the customer has a launch on Friday. Then the ticket moves, and what travels is often a one-line comment: “Customer still has the issue, please check.” Three things cause this: - **The thread is long.** The receiver has to read forty messages to find the facts. - **The agent worked it out somewhere else.** Notes in a scratch file, a chat with an AI assistant, a conversation with a colleague. None of it is in the ticket. - **Nobody says what is needed.** “Please check” could mean diagnose, fix, call the customer or approve a refund. This is the support version of a wider problem: work done with an assistant that has to pass to a person. We cover the general case in [AI to human handoff: what has to travel](/blog/ai-to-human-handoff/). ## What to pass: eight fields - [ ] Customer: name, account, plan, and anything special (key account, renewal soon). - [ ] Goal: what the customer is trying to do, in their words. - [ ] Problem: what happens instead, with the exact error, order number or reference. - [ ] Already tried: steps taken and their results, so nobody repeats them. - [ ] What the customer was told: promises, timelines, workarounds offered. - [ ] Impact and urgency: who is affected and by when it matters. - [ ] Ask: what you need from the receiver (diagnose, fix, approve, call). - [ ] Attachments: screenshots, logs or files, named so they make sense. The fifth field is the one people skip, and it causes the most trouble. If the customer was told “we will call you back today”, the next person has to know, or the promise breaks. ## An escalation note you can copy ESCALATION: [short description] Ticket: [number] From: [agent] To: [team or person] Urgency: [low / normal / high], needed by [date and time] Customer [Name, account, plan. Key account? Renewal soon?] Goal [What they are trying to do] Problem [What happens instead. Exact error, order or reference number] Already tried - [Step]: [result] Told the customer [What we promised, and by when] Ask [What I need from you] Attachments - [file]: [what it shows] ## What each destination needs The eight fields stay the same. The emphasis changes with who receives the ticket. ### Tier 2 or a specialist team They need the steps already tried and their exact results, so they start where the first line stopped. Include the environment details your product needs: browser, version, account settings. ### Engineering They need a reproducible case: steps, expected result, actual result, the time it happened and any logs. Keep the customer’s emotions out of the bug description and put the business impact in the urgency line instead. If several customers report the same thing, say so. ### The account manager They need the commercial picture: how upset the customer is, what was promised, whether a renewal or an upsell is at stake, and whether a call from them would help. They do not need the technical detail, only the outcome so far. ## A worked example Sara, a first-line agent at a made-up online shop, has a customer whose order arrived damaged for the second time. She has checked the order history, offered a replacement and been told the customer wants a refund instead, which she cannot approve. She escalates to the logistics team, which also handles damage claims: ESCALATION: Damaged delivery, second time Ticket: 48213 From: Sara To: Logistics Urgency: high, needed by Thu 22 Oct, 12:00 Customer Emma Ward, account since 2023. Second damaged delivery in a month. Goal Refund for order 77120 instead of another replacement. Problem Parcel arrived with a crushed box and a broken lamp base. Photos attached. Already tried - Offered a replacement: declined - Checked previous claim (order 76544): replaced on 2 Oct Told the customer Someone from logistics will reply by Thursday noon. Ask Approve the refund, and check the packaging for this product. Attachments - damage-photos.zip: three photos of box and lamp The logistics team can answer Emma without a single question back to her or to Sara. ## Doing it from your assistant with Colle If Sara worked the case with Claude or ChatGPT, her assistant already has most of the note. With Colle she says: > Hand this complaint to logistics with the order number. The customer expects an answer by Thursday noon. Her assistant writes the summary, records the facts (order number, deadline, what was promised) and attaches the photos. Logistics can be a team space: every member except Sara gets a notification, and one of them picks the case up. When someone accepts it, Sara sees that it has been taken. If logistics needs more, they return it with a reason, such as “please add the delivery date”. If Thursday noon passes, both sides see the case as overdue. Colle does not replace your helpdesk; the ticket stays there. Colle carries the context from one person’s assistant to the next. The general method for any handoff, with or without a tool, is in [how to hand off work to a colleague with Claude and ChatGPT](/blog/hand-off-work-to-a-colleague-with-claude-and-chatgpt/). See how this works for [support teams](/use-cases/support/). [Join the Colle pilot](https://www.trycolle.com/#pilot) ## When you do not need Colle If your helpdesk already has a good escalation form, your agents fill it in, and nobody works the case in an AI assistant, keep using it. The eight fields above will improve the form. Colle helps when the investigation happens in assistants and the context has to move between people, not only between queues. For how this differs from a chatbot passing a customer to an agent, see [AI handoff vs agent handoff vs team handoff](/blog/ai-handoff-vs-agent-handoff-vs-team-handoff/). --- Canonical page: https://www.trycolle.com/blog/support-ticket-escalation-context/ · Last updated: 2026-10-18