Discord Ticket History: How Members Find Their Own Past Tickets

Closing a ticket deletes the room it happened in. That is the right default, because a server carrying four hundred dead ticket channels is unusable, and it is what nearly every Discord ticket bot does. It also means the member walks away holding nothing they can point at.

They do get the transcript link, by direct message, the moment the ticket closes. Two weeks later that message sits above a game invite and three friend requests, and the member is back in your server asking whether anyone remembers what they were told in June. Somebody on your team then goes and finds it, which is a support ticket about a support ticket.

What a Discord ticket history is

Three things get used interchangeably and are not the same, so it is worth separating them before anything else.

A transcript is a document. A history is a list. A product can have the first without the second, and it is worth checking on any bot you are comparing, because "we save transcripts" and "your members can find their transcripts" are different promises with very different day-to-day consequences.

The staff-side equivalent here is /ticket search, which filters every ticket in the server by status, priority, opener, panel and period. That one is gated on staff permissions and it answers a different question. Support analytics covers the staff view properly.

How a member finds their own past tickets

Two surfaces, the same data underneath, and neither of them asks for a permission.

/mytickets is the only ticket command that works outside a server, and that is structural rather than incidental: a subcommand of a server-only group can never appear in a direct message, so this one sits at the top level on its own. There is nothing to grant, either. It only ever returns tickets that member opened, so no permission would make sense attached to it.

Picking one ticket opens a detail view with up to two buttons: a jump back into the channel while the ticket is still live, and the transcript once there is one. A closed ticket has no channel left to jump to, so that button is absent rather than broken.

Tickets are listed by their channel name, not their number. Ticket 137 identifies nothing to the person who was inside it. A name like support-137 does, and it is stored at close so it survives the channel being deleted.

What the history shows, and what it leaves out

The member's view is a deliberate subset of the row your staff see. Each omission has a reason, and the reasons are the interesting part.

One rule covers the whole table: the member sees what they already experienced, and nothing your team wrote about it afterwards. Everything in the lower half is a note taken by staff, for staff, and handing it back to the member changes what it is.

Why hiding the staff name is the load-bearing one

Every line in that lower half is a judgement call. One of them is more than that.

Staff replies on this bot can be sent under a shared Staff label, so the member never learns which person answered. Servers turn it on for good reasons: it stops one helper being direct messaged for months over a decision they only relayed, and it keeps a refusal from becoming personal. Replying as Staff goes through when that is worth doing.

Now put the claimer's name on a self-service history page. Every ticket ever answered anonymously has just been de-anonymised, retroactively, in a single release. Not one ticket: all of them, on every server, as far back as the records go.

For a large share of tickets there is no staff name to hide in the first place. Roughly half of all tickets across every server running this bot close with no human replying at any point. The live figures sit at /api/stats/global if you would rather check than take our word for it.

Does it still work after somebody leaves your server?

Yes, and it is worth knowing before the day you need it.

The check on a transcript is whether the reader is the person who opened that ticket, compared by Discord account, and it runs before anything looks up server membership. A member who left, or who you banned, can still list their own tickets and read their own transcripts.

Staff access runs the other way. A staff member's right to read somebody else's transcript comes from holding a role in your server, so it ends when they leave it. The record follows the person who opened it. The access to everyone else's follows the role.

Both halves are deliberate and both are worth being able to say out loud. A departing moderator does not keep a window into your ticket archive. A member you removed does not lose the record of what you told them before you did.

The gate on a leaked link is unchanged by any of this: the URL alone is not enough, and anyone who is neither the opener nor current staff of that server is refused. Transcripts, retention and privacy is the full version.

How long a member can read their history for

The ticket outlives the transcript. Once the body is purged the ticket still appears in the member's history and says the record is no longer available, rather than offering a button that fails. Small thing, and it saves a support ticket every time it happens.

Two ways a history ends up thinner than you expect. A server can switch transcripts off entirely, which is free and has no plan gate: closing then stores nothing at all, and the member's list has rows with nothing to open. And tickets opened through somebody else's bot, using the connect feature, keep no messages with us, so they carry no transcript either. What a close actually deletes has the rest of that sequence.

Website chats from a visitor who never signed in appear nowhere in this, because there is no account to attach them to.

Where a ticket history is the wrong answer

That last one is the real ceiling. A ticket history is a record, not a relationship. There is no email address, no phone number, and no way to start a conversation with somebody who is no longer in your server, which running a helpdesk on Discord is honest about at more length.

What it does do is take a recurring class of work off your team without anybody configuring anything. It is on now, on every plan, and the only reason your members are not using it is that nobody has told them it exists. One line in your rules channel, or in the description on your ticket panel, is the whole rollout.