Setting up a ticket system on Discord

Why DMs stop working

At first, server support runs through DMs to moderators. That works up to roughly two hundred members, then three problems appear at once.

The first is distribution: the same question reaches three moderators, who answer it three times, differently. The second is continuity: the moderator handling a case goes on holiday, and nobody knows where it stood. The third is evidence: when a sanction or a purchase is disputed, there is no record the team can consult.

A ticket system solves all three at once, because it moves the conversation from a private space to one the team shares.

The five pieces of a ticket system

Whatever tool you use, a ticket system always comes down to the same parts. Knowing them lets you judge any solution.

• An entry point: a message with a button or a menu, in a public channel, to open a ticket. A command alone is not enough — too many members will never find it.
• Categories: “report a member”, “purchase problem”, “application”. They route the ticket to the right people and tell you, over time, what actually occupies your team.
• A private channel created on opening, visible to the author and the relevant staff, and to nobody else.
• A claim: a way for a staff member to say “I’ve got this”, so that three people do not answer or none do.
• Closing with a transcript: the channel disappears, the content stays readable. That is the part people forget, and the one that matters in a dispute.

The settings that make the difference

A badly set ticket system creates more work than it saves. Three settings decide almost everything.

1. Limit to one open ticket per person. Without that limit, an unhappy member opens twelve and your channel category becomes unreadable.
2. Close inactive tickets automatically. Half of all tickets are abandoned by their author once they have their answer. Without auto-closing they pile up and hide the real ones.
3. Ask a question on opening. A two-field form — subject and detail — avoids the ticket that says only “hi” and saves one round trip every time.

Discord caps a category at 50 channels and a server at 500. A system without auto-closing hits that ceiling sooner than you would think, and Discord then refuses to create the next ticket — with no useful explanation for the member.

What belongs in a ticket, and what does not

Not everything should become a ticket. A question whose answer interests everyone belongs in a public channel: handled as a ticket, it will be asked fifty more times.

Keep tickets for what is personal (a dispute, an application, a payment issue), confidential (a report about another member), or long (a request needing several exchanges).

How Kuratos helps

Kuratos’ Tickets module provides the five pieces above: a button panel, customisable categories, an automatic private channel, named claiming, and closing with a readable transcript.

The one-ticket-per-person limit and auto-closing after inactivity are set from the dashboard, with no command to remember. A statistics page shows tickets per category and average first-response time — so you can see a category overflowing before the team complains about it.

The Reports module connects to it: a report can open a ticket, which avoids two parallel queues that nobody watches in full.