Private Claimed Tickets in Discord: One Staff Member, One Ticket

On most servers a claim is a name tag. It says who is handling a ticket, and the whole team can still read along. That is fine for "how do I link my account". It is not fine for a harassment report, a payment dispute or a staff application, where ten people reading is ten too many. This setting turns a claim into a closed door.

Who can see a claimed ticket?

By default, the same staff who could see it before the claim. Claiming marks the ticket as yours. Whether it also hides the ticket is your choice, role by role.

The permission does not hand out access by itself. It only decides whether a role that could already see the ticket keeps seeing it once a teammate claims it.

How do you make claimed tickets private?

Turn off See claimed tickets for the roles that should step back. It needs Manage Server.

The change applies to tickets that are already open as well as new ones, so test at a quiet time.

Staff roles are built from presets, and the presets differ here. A role added today as a support agent starts without the permission. A support lead or moderator role starts with it. That matches how most teams want it: agents see their own work, leads see everything.

What happens when a ticket is unclaimed?

The team gets it back. The roles that lost the ticket can see it again, and anyone may claim it.

This is what keeps a private claim from becoming a stuck ticket. If the claimer goes offline, they release the claim, or a senior colleague takes it over. /ticket claim on a colleague's ticket takes it over in one step when your staff role is at the same level or higher. A lower role cannot close a ticket a higher role has claimed.

The conversation is never trimmed. Staff who get the ticket back can read what was said while they were out of it. So this is privacy while the work is being done. It is not secrecy afterwards.

When is a private claim the right choice?

There is a cost. When staff cannot see each other's tickets, they also cannot help, learn from or spot mistakes in them. A team of three usually works better with everything open. A team of thirty handling sensitive cases usually does not.

You do not have to pick one for the whole server. The permission is per role, so the common setup is a large agent role without it and a small lead role with it.

How is this different from transferring a ticket?

Both narrow who sees a ticket. They do it differently.

Use a claim when one person on the same team should handle it alone. Use a transfer when a different team should own it, such as HR or billing. They also work together: transfer to the small team, then one of them claims.

What should members be told?

The truth about who can read their ticket. If your server promises that a report is private, be exact about what private means.

A saved copy of the ticket is kept after it closes, and whoever may read saved tickets on your server can read that one. Ticket history covers who that is.

Where private claims stop

The honest list.

If a ticket has to be private from the first message, before anyone claims it, a claim is too late. Give that kind of ticket its own category with a small staff role, so only that team sees it when it opens. Ticket categories shows how.