Skip to main content

First response time: how to answer faster

Why the first reply in a ticket matters more than closing speed, what slows it down, and how to fix it: topic roles, intake forms, Claim, shifts and templates.

Discord Tickets team6 min read

A member opens a ticket and stares at an empty channel. They do not know whether anyone has seen it, whether they picked the right topic, or whether waiting is worth it. The longer the silence, the more likely they open a second ticket, DM a moderator or complain in general chat.

The first response is the part of support members notice most. Below: what keeps teams from answering quickly, what helps, and a few templates for opening the conversation.

Why the first response matters more than closing speed

A hard question can take a day or two to solve, and that is fine as long as the member knows someone is on it. Silence is not fine. A short “Got it, looking into this” removes the anxiety, and the rest of the conversation goes more calmly.

There is a practical difference too. Time to close depends on the question itself: a refund or a report investigation takes what it takes. First response time depends almost entirely on how your team is set up: who hears about the ticket, who picks it up, who is on at the right hours. That makes it easier to improve, and members feel the change right away.

What slows the first response down

Nobody knows the ticket exists

Ticket channels are private. If nobody is mentioned when a ticket opens, staff only find it by chance while scrolling the channel list. Worse: the mention is there, but the staff member has Suppress @role mentions on, or the server’s notifications set to Nothing, and the ping never arrives.

The wrong people see it

One role for every topic means moderators get pinged about payments they do not handle. They quickly learn to ignore those pings, while the person who handles payments never sees the ticket at all.

Not enough context

“Hi, I have a question.” The first reply goes to “What is it?”, and then the team waits. On paper the first response was fast; in practice the conversation has not started.

Everyone assumes someone else will answer

Five people see the ticket and each expects another to reply. Or the opposite: two answer at once and contradict each other.

What helps

The right roles on every topic

Split topics by who can actually answer them and give each its own roles:

Topic Role
Payments and donations @Billing
Report a member @Moderators
Technical issue @Tech Support
Partnerships @Management

Now the mention on open reaches people who can help, and pings stop being noise. In Discord Tickets this is the topic’s “Admin roles” field: those roles see the topic’s tickets, get mentioned when one opens, and can close them. More on splitting roles in Support team roles and access.

Test it: open a ticket in each topic and confirm the notification actually reaches a staff member. Ask your team not to suppress role mentions for the server.

An intake form instead of “Hi, I have a question”

Let the member share the essentials before the ticket is created. For a Technical issue topic, three fields are enough:

  • “What happened?” as a required paragraph;
  • “When did it start?” as a short line;
  • “What have you already tried?” as an optional paragraph.

The answers land in the ticket, so an admin can reply with substance in the very first message. More on which questions to ask in an intake form.

Claim, so two people do not answer at once

Agree on one rule: whoever sees a ticket first claims it, even if the full answer will take a while. We put a “Claim” button under the welcome message for this: once pressed, the ticket shows “Claimed by …” and a “Close ticket” button. Everyone else sees it is taken and does not double up.

Claiming is not answering. Right after you claim, send the opener at least a short message: they see the channel, not your internal agreements.

Shifts based on real load

“Everyone answers when they can” works while tickets are few. After that you need shifts built on actual load: check which days and hours tickets arrive and put people on the peaks. For hours when nobody is around, say so in the welcome message: a wait with a clear expectation is easier than silence.

A benchmark, not a target at any cost

Pick one clear benchmark and watch the trend, not individual days. The “Overview” tab in our dashboard shows “First response” and “Taken within 30 min”, the share of tickets claimed within the first half hour. Both numbers run from opening to “Claim” — the bot doesn’t read the conversation. Tickets nobody claimed are left out, and claiming late makes the numbers look worse even if someone already replied. “When tickets arrive” sits there too, a weekday by hour grid that makes planning shifts easy. Details in the Tickets section of the docs.

Tip. Do not turn the benchmark into a race. A “Claim” pressed right away, or an empty “Looking into it” with no follow-up, improves the number, not the support. Read first response together with close reasons, covered in Close reasons and the support metrics worth tracking.

First response templates

Keep a few templates pinned in a staff channel. A template is a frame, not an answer: add one sentence about the actual question so you do not sound like an autoresponder.

Claimed, needs time:

Hi. This ticket is mine and I am looking into it. I will post the answer here and mention you, so no need to watch the channel.

Need more details:

Hi, thanks for reaching out. To sort this out, please send a screenshot of the error and your in-game name. I will get back to you as soon as I have them.

Wrong place:

Hi. Another team handles this. Please open a ticket under Payments and donations, they will get to it faster there. I will close this one.

Already in the FAQ:

Hi. This comes up a lot, so here is the short answer: … The full version is in the FAQ channel. If that does not help, reply here and we will dig in.

The welcome message can do part of the first response’s job: the bot posts it the moment a ticket opens, so use it to set expectations. An example with placeholders:

{opener}, ticket #{number} about {topic} is in. The team will see it and reply here. We are around during the day and evening, Central European Time; if you write at night, expect a reply in the morning. While you wait, attach any screenshots you have.

The bot replaces {opener}, {number} and {topic} with a mention of the opener, the ticket number and the topic. More on the builder in Welcome message.

Checklist

  • Every topic has its own roles, and the mention on open reaches people who can answer.
  • A test ticket in each topic confirmed that notifications arrive.
  • The intake form collects the essentials: what happened, when, what was tried.
  • The team follows one rule: see it, claim it, reply.
  • Shifts cover the hours when most tickets arrive.
  • The welcome message is honest about when to expect a reply.
  • First response templates are pinned in a staff channel.
  • Once a week, someone checks first response and the share taken within 30 minutes.

Read next

All posts →