Discord Ticket Bot Staff Pings: Who Gets Notified, and When

Ask a support team why a ticket sat unanswered all afternoon and the honest answer is often that nobody knew it was there. Which pings go out is a handful of settings, and on most servers nobody has looked at them since the bot was added.

This guide lists every moment our bot pings your staff, which role it pings, the cases where it stays silent, and one Discord rule that makes a ping look sent when nobody heard it. The same questions are worth asking of any Discord ticket bot you run, because a ping nobody receives looks exactly like a slow team.

Every time the bot pings your staff

Six moments, and only one of them is the ticket opening.

The first four rows work on every plan. The fourth also covers a conversation that grows longer than your own connected AI can read.

Every one of these is a short message in the ticket, or in the web chat's thread, where your team can see who was called and when. The AI's own replies can never ping anybody: they are sent with every mention switched off, and it is told to write names as plain text.

Which role gets pinged?

One role, chosen by you, resolved the same way every time: the staff role set on the ticket's category, otherwise the one set on the panel, otherwise nobody. There are no hard-coded pings. The escalation guide covers which role should receive a handover, and ticket categories covers giving each category its own.

Three details catch people out:

• It has to be one of your staff roles. The picker only lists roles you added under Settings, Staff, which is also where you decide what the role may do.
• A deleted role pings nobody. The bot checks the role still exists each time, so a deleted one is treated as no role at all rather than shown as "@unknown-role". Pick a new one.
• Moving a ticket pings nobody. The move is announced in the ticket with no role mentioned, so tell the new team yourself. Later reminders go to the new category's role.

Web chats have their own Ping role, set where you choose where chats go, because a chat on your website belongs to no panel.

This one is easy to miss, because everything looks right in the ticket. There are two fixes, each with a trade-off. In Server Settings, Roles, you can turn on "Allow anyone to @mention this role" for your staff role, which also lets any member ping your staff. Or you can give the bot's role "Mention @everyone, @here, and All Roles", which lets it mention any role. Ours never uses that to ping everyone: every message it sends has those mentions switched off, and the only role it ever mentions is the one you chose.

Why is the new-ticket ping off by default?

Because on a panel where the AI answers first, the ping that matters is the one when it hands over. A good share of tickets end without a person, and pinging the whole role for each of those teaches your team that the role ping means nothing. The handover ping fires whether or not the new-ticket switch is on, so a person is called in exactly when one is needed.

/setup follows the same logic. It creates or reuses a staff role, sets it as the category's staff role, and leaves the new-ticket ping off. The panel it builds opens tickets as channels, and that role can see each one from the moment it opens, because the category's staff role is written into the channel's permissions.

Three common setups break that default.

When should you turn it on?

The AI is off for that category. Then the handover, the reply limit and the allowance rows can never fire, because the AI never speaks. On the free plan, which has no reminders, the new-ticket ping is the only ping those tickets will ever get. If you switched the AI off for billing or reports, switch this on for the same category.

Your panel opens tickets as threads. A private thread shows only to its members and to people with Manage Threads. The opener is added when it opens. Staff are added when the bot mentions their role inside it, so with the new-ticket ping off, staff without Manage Threads first join at the AI's handover, and never see a ticket the AI resolved alone. There is also a size limit: Discord only adds a role's members this way when the role is small, around a hundred members, and past that it adds nobody and reports nothing. Threads or channels covers the rest of that choice.

Your team works from phones. A new channel is easy to spot on a monitor and invisible on a phone, where only mentions light up. Ticket bots on mobile explains why the ping matters most there.

In Discord, the same two settings sit on the panel's AI card in /panel, and each category's card carries its own ping setting. All of it is free on every plan.

The reminder when a reply is overdue

On paid plans, smart inactivity watches which side owes the next message. When the member spoke last and your team has not answered for longer than it usually takes, the Ping staff switch posts a reminder, then one follow-up if that goes unanswered. With working hours on, the wait only counts hours you are open.

The detail worth knowing is who it names. A claimed ticket pings the claimer, not the role. Pressing Claim is how you take the reminder on yourself, and claiming covers the rest of what it changes. What happens at the follow-up depends on when the claim was made:

When does nobody get pinged?

These are the silent cases, and each one is a setting or a limit rather than a fault.

Two of these are deliberate. An outage is usually over in minutes, and paging every staff role for one would cost more than the outage itself (what a bad day looks like). A ticket where the AI never spoke is treated as a human one from the start, because a notice about a service the member never met explains nothing.

What pings cannot do

Read this before you build a rota on top of them.

Two notes on those limits. A log channel is a record rather than a ping: its posts carry no mention, so they only reach people who read that channel or set Discord to notify them of every message in it. Ticket log channels covers what goes there. And ticket priority explains why an Urgent ticket pings the same role as a Low one: priority sorts the queue, it is not an alarm.

The bot does send your admins a few direct messages, about setting it up, about their plan, or about a problem such as losing access to a channel, but never one telling staff about a ticket. Every DM the bot sends lists them, along with the ones members get.