Duplicate tickets from one customer merged into a single reply
Reads the separate tickets one customer opened by email, chat, phone and social media about the same issue, builds one timeline, and writes a single reply that answers everything and closes the duplicates cleanly. Use it when a frustrated customer has contacted support several times and got different answers.
The output this prompt produced, unedited.
The prompt
Constraints first
One reply to the customer, sent from one owner, on the channel they used last.
Where earlier answers conflict, the correct one is stated once and the wrong one is corrected openly.
Use only facts in the tickets; mark anything unclear as [check].
Inputs
Every ticket about this issue, with channel, date and replies: [paste]
Correct policy or fix: [paste]
Agent who now owns the case: [Name]
Steps
Put every contact in one timeline by date and channel.
List each question the customer asked and whether it was answered.
Note every promise made, and whether it was kept.
Note answers that contradict each other.
Output format
| Date | Channel | Customer said | Support said | Promise made |
Open questions and broken promises.
The combined reply, under 180 words: one apology for the repeated contact, every open answer, the fix with a date, and one direct way to reach the owner.
A one-line internal closing note for each duplicate ticket, pointing to the main one.
duplicate support ticketsmerge ticketsomnichannel supportcustomer contacted multiple timessingle support replyticket clean up
How to run this
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.