how to handle duplicate tickets from the same customer

TL;DR

Duplicate tickets usually mean anxiety, not spam: the customer is worried and trying channels. Acknowledge the duplicates once, link them to the primary ticket, work only the primary, and close the rest with a pointer. Never scold. The customer who opened three tickets wants certainty; give it to them on one thread.

The query

how to handle duplicate tickets from the same customer

Use this when

• Customers open multiple tickets for one issue
• Incident-driven duplicate floods
• Writing queue hygiene rules
• Agents work the same issue twice

Not for

• Spam or abuse
• Ticket fraud
• Merging tickets (separate playbook)
• Different issues from one customer (those are separate tickets)

Steps

1. Identify the primary ticket

The oldest, or the one with the most context. That is the working ticket. All others are duplicates. Decide fast; do not work two in parallel.

Expected output: one primary designated.

2. Link the duplicates to the primary

Use the ticket system's link or parent-child feature. If yours lacks it, note the primary's ticket number on each duplicate. Linked tickets keep the history together.

Expected output: duplicates linked to the primary.

3. Reply once on the duplicates, then close

One message: "I see you also wrote in about [issue]. I am handling it on ticket [number], and I will update you there." Then close the duplicate. Short, warm, no lecture about opening one ticket.

Expected output: duplicates closed with a pointer.

4. Work the primary with extra communication

Duplicate openers are anxious. Update the primary more often than usual. The extra updates prevent the fourth ticket.

Expected output: the primary updated proactively.

5. Note the cause for queue hygiene

Why did they open multiples: no auto-ack, slow first response, confusing channels, incident panic. Log it. Duplicates are a symptom of a communication gap.

Expected output: the cause logged.

Template: the duplicate reply

Hi [Name], I see your messages about [issue]. I am working on it in ticket [number], so let us keep everything there where I have the full picture.

[One line on status or next step.]

I will update you on [ticket number] by [time]. No need to reply here.

Variant phrasings

customer opened multiple tickets

Steps 1 through 3. Primary, link, close with pointer.

duplicate ticket queue hygiene

Steps 1, 2, and 5. Designate, link, log the cause.

same issue multiple tickets incident

Steps 3 and 4. Fast close with pointer, extra updates on the primary.

Why it works

Duplicates come from uncertainty: the customer does not know they were heard. The pointer reply gives them certainty (one ticket, named, with a next update time), and the extra communication on the primary removes the reason for the next duplicate. Linking preserves history so nothing is lost.

Edge cases

• The duplicates contain different details: consolidate the details into the primary before closing.
• Different channels (chat + email + phone): same playbook. Pick the primary, pointer the rest.
• The customer keeps opening new ones after the pointer: call them. Something about the primary is not reassuring them.
• True spam: different playbook. Volume plus no legitimate issue is abuse, not anxiety.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_lLmblfzqOEwLRscD1ZtE4w