Duplicate tickets
Set up Duplicate tickets so staff are told when a new ticket repeats or relates to a recent one
Duplicate tickets compares a new ticket with tickets from the last 30 days in the same server and tells your staff when it finds one that looks like the same issue. Staff get a card in the alerts channel with links to the matching tickets, so they can give one consistent answer instead of solving the same problem twice. This page is for the admin who wants fewer repeated tickets.
Duplicate tickets is available on Pro and Enterprise. It needs the Atlas switch at the top of AI assistant → Atlas and an alerts or logs channel to post its results. Upgrade your plan
Setup
Open the card
Go to AI assistant → Atlas → Flag duplicate tickets. It is in the Sort and flag new tickets section of the What Atlas does tab.
Switch it on
Turn on the switch on the Flag duplicate tickets card.
Save
Click Save changes in the bar at the bottom of the page. Make sure an AI alerts channel or a logs channel is chosen under General → Where the bot posts; without one, matches are recorded on the ticket but no card is posted.
Settings
| Setting | Values | Default | What it does |
|---|---|---|---|
| Flag duplicate tickets (the card's switch) | On, Off | Off | Master switch for this feature |
There is nothing else to set. Atlas looks back 30 days and labels each match by how sure it is:
| Level | How sure | Meaning |
|---|---|---|
| Very high | 90% and up | Almost certainly the same problem; immediate attention |
| High | 75% and up | Likely the same; shown first for review |
| Medium | 60% and up | Possibly related; shown as a suggestion |
| Low | 45% and up | Might be related. Matches below this are not shown |
What happens
- A ticket is created, or its creator sends a message.
- TicketCord finds candidate tickets from the same server within the last 30 days and shortlists the closest ones.
- The AI compares the member's message with each candidate's subject and the welcome or form context, and gives each match a confidence score and a one-line reason.
- Matches are recorded on the ticket. Each is labelled repeat (🔁, the same person opened the same issue again) or related (🔗, a different person with the same issue).
- A Potential Ticket Matches card is posted in your alerts channel. It opens with
AI found tickets that may be repeats or related reports: 3, then lists each match with its 🔁 or 🔗 label, the confidence, the reason, the ticket's Open or Closed status, a Preview, and a Jump to ticket link. The footer readsAI compared the customer message, subject, and welcome or form context. Staff should verify the results.Change its wording on the Messages page (Possible duplicates).
The alerts channel is AI alerts under General → Where the bot posts; when it is not set, the card goes to your logs channel.
What staff should do
The card is advice, not an action. There are no link, merge, or dismiss buttons and no feedback loop. Typical responses:
- Repeat from the same person: open the older ticket, check whether it was resolved, and either continue there or explain in the new ticket that the answer has not changed.
- Related from a different person: reuse the answer that worked, and consider adding it to the Knowledge Base so the bot answers the next one.
- Several related tickets in a short time: this often means an outage or a broken feature. Post an announcement and, if you use a status page, connect it under AI assistant → Atlas → Sources so the bot mentions the incident.
Worked example
A member opens ticket-0412 saying My rank purchase from yesterday still hasn't been applied.
Within the last 30 days the bot finds ticket-0398 from the same member (bought VIP, nothing happened) and ticket-0405 from someone else (store purchase not delivered). The alerts channel card lists 🔁 88%: same customer, same undelivered rank purchase and 🔗 72%: different customer, same store delivery problem.
Staff open ticket-0398, see it was closed with a manual rank grant, apply the same fix, and add a Q&A entry about delayed store deliveries so the bot handles the next report.
Limits and gotchas
Every comparison costs tokens from the bot owner's allowance. Only the shortlisted candidates are compared by the AI.
- Detection looks at tickets in the same server from the last 30 days only.
- A card is posted whenever at least one match reaches the Low level.
- Tickets from members on AI assistant → Atlas → Keep Atlas away from, and tickets opened from a panel button that turns Atlas off, are not checked.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| No cards ever appear | The card or the Atlas switch is off, the owner's plan is below Pro, or neither an AI alerts channel nor a logs channel is set | Check both switches and the plan, and choose a channel under General → Where the bot posts |
| Obvious duplicates are missed | The older ticket is more than 30 days old | Link it by hand in the ticket |
| The card links to a closed ticket | Closed tickets from the last 30 days are included on purpose | Reopen it with /reopen if the conversation should continue there |
| Staff cannot open the linked ticket | They lack access to that ticket's channel | Adjust category permissions |
Common questions
Does the bot close or merge duplicate tickets automatically? No. It only reports them. Staff decide what to do with each ticket.
Where do the results go? To your alerts channel as a Potential Ticket Matches card (your logs channel when no AI alerts channel is set).
Are closed tickets included? Yes, from the last 30 days. The card shows whether each match is Open or Closed.
Can I change how far back it looks? No. Atlas always looks back 30 days.
Does it work across my servers? No. Only tickets in the same server are compared.
Does the member see anything? No. The card is posted in the alerts channel, which members cannot see.
How much does it cost in tokens? Only the shortlisted candidates are compared by the AI, so cost depends on how many similar tickets exist. Check AI usage in the dashboard after a few days.
Join our Discord server for support
Was this page helpful?
Last updated on