How to set up a Discord ticket system that lasts

Why this goes wrong

The mistake almost never happens during setup, it happens in week two. At the start curiosity is high, the first requests arrive minute by minute, and three people from the team jump in at once. After a few days that fades: the same person answers every time, the others only read along, and eventually a channel sits untouched overnight. The member waits, sees nothing new the next morning and additionally messages a moderator privately, exactly the situation you wanted to end, only now with an extra channel. The reputation of a support area is decided in its first ten tickets. Anyone who has learned once that nothing happens there will not press the button a second time, even if you fix the problem two weeks later. So the first question is not which categories to create, but how many requests you can genuinely answer on an ordinary Tuesday evening.

What to decide first

Start with the people, not the buttons. Write down who on the team is allowed to answer, and next to each name the hours that person is usually online. If two names are left for the evening, you do not need six categories. You need two you can serve reliably. Without premium the panel shows only the first two anyway, so the decision is made either way. Then settle one single question per category: who is responsible when nobody else reacts? Enter exactly that role for notifications instead of pinging the whole team at large. A message to everyone feels personal to no one. Decide whether the team gets woken by a direct message or whether a ping in the channel is enough. Decide how many tickets one member may keep open at the same time; out of the box it is one. And agree on a promise you can keep on a Sunday too.

Step by step

1. Count first who on the team can answer and when: the number of reliable responders limits everything else.
2. Assign a responsible role to every category you are planning and note which details you need from the person asking.
3. Switch the module on in the dashboard, enter the support roles and set the panel channel.
4. Store a greeting for each category that asks for exactly those details, and decide where closed tickets are filed.
5. Run it for a week, collect the five questions that came up most often and store them as automatic replies.

The mistakes almost everyone makes

The most expensive mistake is copied: someone lifts the category list of a large server that has twenty people on staff. Second, naming from the team’s point of view: “escalation”, “partner requests”, “internal” means nothing to a member; they pick something at random and you sort it out afterwards. Name categories after what the person wants, not after your own division of labour. Third, the silent claim: two staff members read along, neither says “I will take this”, and both wait for the other. Agree that claiming happens visibly and that internal remarks belong in the notes, not in the channel the member is reading. Fourth, permissions on the ticket area: if the Discord category is set so that a new role sees nothing, the bot does open a channel, but the right person never looks inside. And fifth, switching on automatic replies and dumping thirty question-and-answer pairs into them. Matching works on shared words; the vaguer the stored question, the more likely it hits the wrong one.

Frequently asked questions

As many as you can serve on an ordinary evening, usually fewer than the plan assumed. Without premium the panel shows the first two; beyond that, each additional one only pays off once it has a responsible role of its own. Better to add one later than to leave three dead buttons standing.

Treat it as an incident, not as a one-off. Answer the waiting person first with an honest assessment, even if you do not have the solution yet, and afterwards work out in the team why nobody felt responsible. If it keeps happening, the setting is not wrong; the number of categories is too high for your staffing.

In a channel the team opens daily anyway, not in a separate archive area at the bottom of the list. It helps if follow-up questions are allowed there, so a closed ticket can turn into a discussion. File them and you have an archive; read through them once a week and you have a place where answers can be found again.

Take the closed tickets of one week and look for the questions that came up more than once. Phrase the stored question the way a member would type it, and use as the answer the very sentence you would have written anyway. The bot will send at most three such replies per ticket and only reacts to the person who opened it. After that it is your turn again.

How many categories make sense?

As many as you can serve on an ordinary evening, usually fewer than the plan assumed. Without premium the panel shows the first two; beyond that, each additional one only pays off once it has a responsible role of its own. Better to add one later than to leave three dead buttons standing.

What should I do when a ticket sits unanswered for three days?

Treat it as an incident, not as a one-off. Answer the waiting person first with an honest assessment, even if you do not have the solution yet, and afterwards work out in the team why nobody felt responsible. If it keeps happening, the setting is not wrong; the number of categories is too high for your staffing.

Where do transcripts belong?

In a channel the team opens daily anyway, not in a separate archive area at the bottom of the list. It helps if follow-up questions are allowed there, so a closed ticket can turn into a discussion. File them and you have an archive; read through them once a week and you have a place where answers can be found again.

How do answered tickets turn into automatic replies?

Take the closed tickets of one week and look for the questions that came up more than once. Phrase the stored question the way a member would type it, and use as the answer the very sentence you would have written anyway. The bot will send at most three such replies per ticket and only reacts to the person who opened it. After that it is your turn again.