Claiming a Discord ticket means one staff member takes ownership of it, so the rest of the team knows it's being handled and (optionally) loses access to it. Without claiming, three staff members can answer the same customer at once, contradict each other, or all assume someone else already replied. Noxyr's ticket system has a built-in claim/unclaim command, a setting that restricts access to the claimer once claimed, and a claimed-by column on both the ticket channel and the dashboard. This guide covers how to turn it on and how to use it without staff stepping on each other.
What claiming actually does
When staff run /ticketadmin claim inside a ticket, three things happen:
- The ticket is marked claimed by that staff member, with a timestamp, visible in the channel and on the dashboard's ticket list.
- Other staff can see who owns it instead of guessing from scroll history who replied last.
- Access can lock to just the claimer and the ticket opener, if you've turned that on (see below).
/ticketadmin unclaim releases it, which matters more than it sounds - a staff member who claims a ticket and then goes offline for the night without unclaiming it can accidentally block everyone else from touching it, if lock-on-claim is enabled.
Turning on "claim locks ticket"
On the dashboard's Tickets page there's a toggle called Claim locks ticket: when a staff member claims a ticket, other staff roles lose access to that channel. Only the claimer and the ticket's creator keep it, and server admins always keep access regardless of the setting. It's off by default in some setups because small teams don't need it - if you have two staff and both should always be able to jump in, leave it off and just use claiming as a visible "who's on this" marker.
Turn it on once your team grows past a handful of people, or once you notice two staff answering the same ticket differently. It's the difference between claiming being a courtesy and claiming being enforced.
Setting it up
- 1. Open the dashboard, go to your server's Tickets page, and confirm a staff role is set - claiming is restricted to ticket staff, checked the same way as who can see a ticket at all.
- 2. Decide on Claim locks ticket. Small teams: leave off. Teams big enough to duplicate work: turn on.
- 3. Tell staff to run
/ticketadmin claimthe moment they start answering a ticket, and/ticketadmin unclaimif they hand it off or go offline before it's resolved.
There's no dashboard button for claiming itself - it's a Discord command run from inside the ticket channel, since that's where staff already are when they decide to take it.
What claiming doesn't do
Claiming isn't a priority system and isn't a queue. A claimed ticket doesn't move to the top of anything, and Noxyr doesn't auto-assign tickets round-robin to staff. It's a manual "I've got this" flag, which is deliberately simple - automatic assignment sounds nice until it hands a billing question to someone who only knows technical support, and a human picking their own tickets avoids that entirely.
It also doesn't stop the ticket opener from talking to other staff in a different channel, or stop admins from stepping in on a claimed ticket - admin override exists so a claim can never fully lock a server owner out of their own server.
Seeing who claimed what
Two places show claim status without opening every channel: the Tickets page in the dashboard lists open tickets with a Claimed By column ("Unclaimed" if nobody has), and /ticket info run inside any ticket shows who claimed it plus its priority and status in one ephemeral reply. If you're trying to answer "is anyone actually on this," those two are faster than scrolling a channel.
For a wider view of who's closing the most tickets and how fast, the Tickets docs and the ticket analytics dashboard (see our guide on ticket analytics and response time) break claims down per staff member over a period, not just per ticket.
Common mistakes with claiming
- Claiming and forgetting to unclaim. With lock-on-claim enabled, this quietly strands a ticket. Set an expectation that staff unclaim before ending a shift, or leave lock-on-claim off if that discipline is unlikely.
- Turning on lock-on-claim before staff know it exists. A staff member who tries to open a ticket they used to see and can't will assume something is broken. Announce the change.
- Treating claim as a promise to reply immediately. It only marks ownership - it doesn't send a notification to the member or start a timer. Reply first, claim as you go if you need the marker.
Common questions
Can more than one staff member claim the same ticket? No. Once claimed, running claim again either fails or has no effect until it's unclaimed - the point is exactly one owner at a time.
Does claiming notify the ticket opener? No, it's a staff-side marker. If you want the member to know someone's on it, say so in the ticket itself.
Can admins see a locked ticket they didn't claim? Yes. Lock-on-claim never removes access from server admins, only from other ticket staff roles.
Is claiming free? Yes, it's part of Noxyr's ticket system with no paid tier.
What if a claimed ticket needs to be handed to someone else? Unclaim it, or have the new staff member claim it directly, which reassigns ownership.
Ready to set it up? Add Noxyr or open the ticket bot page for the full feature list.