Home › Workflows › Support ticket: handoff note then customer reply
Turn a support thread into a handoff note and a customer reply
Last checked
Use this when a ticket is messy and you need a clean internal handoff plus one careful message back to the customer — without inventing refunds or deadlines.
Cost: each step works on the free ChatGPT, Claude, Gemini or Perplexity plans we list for these tasks. Paid plans raise limits — for example ChatGPT Go is $8/mo in the US (OpenAI, checked Oct 23, 2026), Claude Pro is $20/mo or $200/yr (claude.com/pricing, checked Oct 24, 2026), Google AI Plus is $4.99/mo (Google AI plans, checked Oct 23, 2026), and Perplexity Pro is $17/mo billed annually (Perplexity pricing, checked Oct 24, 2026). See each brand page and the cost calculator.
Steps
Step 1: Write the internal handoff note
ChatGPT or Claude Both are listed for ticket summary on free plans we verified for this task.
Summarise this support thread as an internal handoff note with these headings: Issue (1 line), What the customer wants, What we've tried (each with the date and a short quote), Current status, Next step, Promises made to the customer (with dates), Open questions. Don't invent anything that isn't in the thread. [paste thread, oldest first]
From Summarize a ticket thread. Strip personal data you do not need.
Step 2: List every promise before you reply
ChatGPT or Claude A second pass stops you from missing a credit or deadline someone already offered.
List every promise, refund, credit or deadline anyone on our side mentioned in this thread, with who said it and when. If none, say none. [paste thread]
Step 3: Draft the customer reply, then fix the tone
Microsoft Copilot (Outlook/Gmail) or ChatGPT Draft in the mail tool you use day to day; use a tone pass if the first draft is too stiff or too soft.
Summarise this thread in 3 bullets: what the customer is asking for, any deadline, and what's still undecided. Then draft my reply: I agree to [decision], I can't do [thing] because [reason], and I'll follow up by [date]. Use only facts from the thread and the promise list: [paste]. Keep names, amounts and dates unchanged. Optional tone pass: Rewrite this email to sound [warmer / more formal / more direct] for the customer. Keep it under 120 words. Don't change any names, dates, numbers or what I'm offering. [paste draft]
Related: Draft email and Rewrite for tone.
Common pitfalls
- Promising a refund or ship date the thread never authorised.
- Pasting full payment card or ID details into a consumer chat.
- Sending before a human reads the promise list against the CRM.
Related on this site
- Summarize a ticket thread
- Draft email in Outlook/Gmail
- Rewrite for tone
- Compare tools
- ChatGPT for beginners (beginner tutorial)
- Claude for beginners (beginner tutorial)
- All workflow guides
Prompts are adapted from the linked task pages. Tools and free-plan notes follow those pages; we do not invent prices.