Skip to main content

Close reasons and the support metrics worth tracking

How to build a list of quick close reasons for Discord tickets, why to require a reason, when to DM it to the opener, and which support metrics to act on.

Discord Tickets team6 min read

A ticket is closed. But what actually happened? Was the question solved, did the member vanish, was it a duplicate or in the wrong place? Without a recorded reason, your ticket history is just a counter. With one, you get a map of what people come to you with and where support gets stuck.

Below: how to build a list of close reasons your team will actually use, which support numbers are worth checking, and what to do with them.

Why record a close reason

A close reason is one line, but it answers questions you would otherwise chase in your staff chat:

  • How did it end? “Solved” and “opener never replied” are different outcomes, though both tickets are just closed.
  • What keeps coming back? If ticket after ticket closes with “Answered in the FAQ”, nobody sees your FAQ.
  • What does the next shift need? A moderator logging in at night sees how the day’s tickets ended without rereading them.
  • What does the opener hear? Members want to know their question was closed for a clear reason, not lost.

How to build a list of quick reasons

Quick reasons are ready-made options an admin picks in the close form instead of typing. Our rules:

  1. Say how it ended, not what it was about. The topic is already known: the member picked it when opening. “Payment question” is a poor reason; “Payment confirmed” is a good one.
  2. Short, no staff jargon. If the reason goes to the opener by DM, they should understand it as is.
  3. No overlap. If two options fit the same case, your team picks at random and the numbers drift.
  4. Fewer is faster. Up to five reasons appear as radio buttons, one click each. From the sixth on, they become a dropdown: fine for a longer list, but every close takes an extra step.

Example sets

The right set depends on what the panel handles. A few starting points:

Panel Quick reasons
General support Solved · Answered in the FAQ · Duplicate ticket · No reply from opener · Wrong place
Member reports Violation confirmed, action taken · No violation · Not enough evidence · Report withdrawn
Staff applications Accepted · Declined: requirements not met · Declined: recruitment closed · Candidate stopped responding
Purchases and donations Payment confirmed, delivered · Refund issued · Payment not found · Wrong place

Two of these have their own guides: member reports and staff applications through tickets.

Other is a safety net, not the main road

The last option in the form is always Other, for cases your list does not cover. Whatever the admin types becomes the reason. Leave it empty and the ticket closes as closed without a reason, which tells you nothing.

Two team agreements help:

  • keep Other entries as short as your quick reasons;
  • every couple of weeks, skim closed tickets. If the same custom text keeps showing up, promote it to a quick reason and drop the one nobody uses.

Required reasons: when they kick in

Quick reasons only appear when two settings line up: only admins can close tickets, and a reason is required. If openers can close their own tickets, there is no ready-made list, so factor that in when deciding who closes.

Requiring a reason builds a habit: otherwise tickets get closed with an “I’ll fill it in later” that never happens. Keep the list short so closing does not become paperwork.

Should the opener get the reason by DM

Telling members how their request ended heads off “where did my ticket go” messages. But once it is on, every reason becomes text a member reads, including whatever an admin types into Other. So:

  • phrase reasons neutrally: “Could not reach the opener”, not “Opener ghosted us”;
  • in reports, share nothing about the other member; “Violation confirmed, action taken” is enough;
  • internal staff notes never go into Other.

Which metrics to watch

Reasons tell you how requests end. Metrics tell you how support is running. This set covers most servers:

Metric What it shows A bad value usually means
First response How long a member waits for the team to react Too few people at peak hours, or staff do not hear about new tickets
Time to close How long a ticket lives from open to close Questions arrive without context, or solved tickets are left open
Open now Your current queue Tickets open faster than they close
Share closed with a reason How complete your data is Reasons are not required, or Other is left empty
By topic Where the load comes from One topic is eating the whole queue
When tickets arrive Load by weekday and hour Peaks hit hours when nobody is on

Members feel the first response most. How to bring it down: First response time: how to answer faster.

What to conclude

Numbers alone change nothing. Look at combinations:

  • One topic leads, and its tickets often close with “Answered in the FAQ”. Show the answer before a ticket is opened: in the topic description, panel text or welcome message.
  • Lots of “No reply from opener”. People open a ticket and leave. Ask for a description of the problem in the intake form, so an admin can answer even if the opener is offline.
  • Fast first response, slow time to close. Solved tickets are often left open. Go through the open ones and close what is done.
  • The queue keeps growing. If open tickets climb week after week, the team is falling behind. Check when tickets arrive and reinforce those shifts.
  • Few tickets closed with a reason. Make sure a reason is required on every panel and remind the team about empty Other entries.

Tip. Do not chase a single number. Push for fast closing and tickets get closed before the issue is solved. Push for a fast first response at any cost and you get empty “Looking into it” messages with no follow-up. Read the metrics together and against close reasons. A weekly glance and a monthly review of reasons and topics are usually enough.

How Discord Tickets handles this

In our bot, close reasons live in the panel’s “Advanced settings”. Set “Who can close” to “Admins only”, keep “Require a close reason” on, and “Quick close reasons” appear below, up to 20. The “DM the opener why it was closed” toggle sits there too, off by default. Then click “Update in Discord”. Step by step: Rules, limits and closing.

The “Overview” tab shows “First response” (measured until “Claim”), “Time to close”, “Open now”, “Closed with a reason”, a “Tickets opened” chart for 24 hours, 7 days, 30 days or all time, “Taken within 30 min”, “By topic” for 30 days, and “When tickets arrive” by weekday and hour. The “Tickets” tab filters All, Open and Closed, and each ticket card shows who opened and closed it, first response, duration and close reason, handy for reviewing Other entries. More in Tickets.

Read next

All posts →