Discord customer support: answer your community in its own threads, from one inbox
Questions in a busy Discord channel scroll away, and nobody knows who should answer them. How to set up a support forum with tags, roles and AutoMod, and how to answer every thread from one inbox.
Deskwoot Team
9 min read
Contents
A player posts in #help at 23:10 that her save file is gone after 60 hours of play. A moderator reacts with the eyes emoji and goes to bed. By morning her message sits 140 lines up, and nobody on your team has answered it.
This guide sets up Discord's own tools so questions stop getting lost, then shows how to give each one an owner and a clock.
Why questions get lost in a Discord channel
Game studios, software companies, creators and online course sellers end up doing support on Discord for a simple reason: their customers are already there. Sending a player out of the server to a web form feels odd when thousands of people chat in the channel next door.
So the questions arrive where the community is, and the team answers them between everything else.
Discord's Forum Channels FAQ draws the line itself: text channels suit conversation in the moment, forum channels suit longer discussions about one topic. A support question is the second kind, yet many servers still take it in a text channel called #help.
The question scrolls away
In a busy #help channel a refund request competes with bug reports, memes and "anyone else lagging?". Whoever was offline when it came in will rarely scroll back far enough to find it.
Nobody owns it
Every moderator can see every message, so each one assumes another already replied. Discord gives you roles and permissions, but no field that says who is handling a question or how long the person has been waiting.
Phones go quiet
Discord's page on account and server caps lists that servers over 2,500 members get no mobile push notifications for all messages.
In a large server, a new question that mentions nobody waits until someone on your team opens the app and looks.
The history is only a search box
Discord's search filters by from:, in: and has:, so you can pull up everything a member ever wrote.
It cannot show you what your team promised them last month, whether their last problem was solved, or that they emailed you about the same thing yesterday.
Private details end up in public
People paste order numbers, email addresses and license keys into a channel the whole server can read, because that is where the support conversation happens.
Set up a support area with Discord's own tools
Forum channels, threads, roles and AutoMod fix most of this mess if you set them up on purpose. What they leave open is who owns each question and how long it has waited.
Give every question its own forum post
A forum channel holds posts instead of one chat stream. Each post has a title and is its own thread, so one question cannot bury the next.
Forums need a Community server. To turn Community on, Discord requires the following (Enabling Your Community Server):
- a verified email before members can send messages
- the media content filter for all members
- a rules channel
- a channel where Discord sends updates to your moderators
The 4 forum settings that matter most
- Write post guidelines that say what a good question contains (device, app or game version, what happened, a screenshot) and what never to post, like passwords or full card numbers.
- Make a tag required. A forum can hold up to 20 tags and a post can carry up to 5, according to Discord's developer docs. A short list works better: bug, billing, account, how to, plus one status tag such as "solved".
- Set Hide After Inactivity to 1 week. The choices are 1 hour, 24 hours, 3 days (the default) and 1 week. A bug report often waits days for a fix, and 1 week keeps it in the main list while it waits.
- Use the one pinned post a forum allows for known issues, so the 30th person with the same crash reads it before posting.
A post that does hide comes back as soon as someone writes in it, unless it was locked.
Be careful with Close Post. The Forum Channels FAQ says it takes a post out of the new posts list and locks it, so only moderators can open it again.
If you want people to add "it happened again" in the same place, tag the post as solved and let it hide on its own.
If #help stays a text channel, make threads the rule
Some communities prefer the chat feel of a text channel. That can work if every question moves into a thread.
Members need Create Public Threads to open one and Send Messages in Threads to reply in it (Threads Moderation FAQ). Threads hide after inactivity too, after 3 days by default (Threads FAQ).
| What you get | Forum channel | Text channel with threads |
|---|---|---|
| Needs a Community server | Yes | No |
| Each question gets its own thread | Always, every post is one | Only when someone starts one |
| Tags to sort and filter | Up to 20 per forum, 5 per post | None |
| Private threads | Not possible | Possible |
| What members see | A list of questions with titles | A chat, with threads to the side |
Make staff visible and give them Manage Threads
Create a Support role for the people who answer, give it a color, and grant it Manage Threads. Role colors show on usernames in chat, so members can tell that a reply came from your team.
The Threads Moderation FAQ lists what Manage Threads allows:
- rename, archive and unarchive threads
- set slowmode
- view all private threads
- remove people from a thread and delete it
Before you open the forum, use View Server as Role to see it the way a normal member does.
Regulars who like to help can get a Helper role without Manage Threads. They answer questions, and staff decide when one is done.
Plan for the bad day
When an update breaks something and 200 people want to report it, slowmode on the channel lets each member send one message and create one thread per interval you choose.
Inside a single thread, slowmode goes from 5 seconds up to 6 hours (Threads FAQ). Pin the known issue first, then slow things down.
Keep private details out of public threads
AutoMod can block or flag messages that match a pattern, and Discord's regex guide uses email addresses as its own example.
With a Custom Keyword rule that matches email addresses, AutoMod can block the message and show the writer a note of up to 150 characters, for example where to send account details instead (AutoMod FAQ).
Discord allows up to 10 regex patterns of 75 characters each. Members with Administrator or Manage Server are never filtered, so test the rule from a normal account.
Give account questions a private place
Questions about an account or a payment need a place only the person and your team can read. Discord's thread docs say a private thread is visible only to people invited to it and to moderators with Manage Threads.
The same docs say private threads can only be created in text channels. In a forum, ask the person to continue by email or in a private thread under a text channel.
Answer the repeat questions before they are asked
Community servers can turn on a Server Guide under Server Settings > Onboarding. It turns channels where only your team posts into resource pages that new members see when they join.
It also lets you set 3 to 5 New Member To Do's. Make "how to get help" one of them and point it at the support forum. Your FAQ and your known issues fit well as resource pages.
Where Discord's tools stop
A tagged forum and a visible Support role carry a small server a long way. One person filters the forum by the open tags once or twice a day and works down the list.
It gets harder once 3 or 4 people answer, or when the same customers also write by email and through the chat on your website.
A forum post has tags, but no owner and no clock. Discord cannot tell you that the person in one thread opened a chat on your site this morning, or which questions have waited since yesterday. That part needs a help desk.
Read 2 rules before you add a support bot
Discord's Developer Policy sets limits that every support bot has to follow:
- Apps may not contact users without their explicit permission, which includes unsolicited direct messages.
- Apps may not use Discord's API to collect financial or other sensitive information, apart from narrow exceptions Discord allows.
So a support bot should answer in the thread where the person asked and never ask for card details.
Answer Discord from your Deskwoot inbox
Deskwoot is our help desk, and it adds Discord as an inbox. Each question from the channels you pick becomes a conversation in the same list as your email, live chat and WhatsApp.
You assign it to one teammate, sort it with labels and talk it over in private notes. The reply appears in the same Discord thread under the teammate's name.
In a text channel, a question with an order number or an address can move into a private thread that only the person, your team and the server's moderators see. The bot gets no administrator rights and never reads direct messages.
Let Fynn take the first answer
Fynn, our AI agent, can answer in the threads from the Startup plan on, using only what you give him in the Training Hub. For each channel you choose whether he answers in every new thread, only when someone mentions the bot, or never.
He never shares account or order details in Discord. He hands those questions to your team, in a private thread where the channel allows one, and once a teammate answers, Fynn stops.
If your help content is thin, start with how to train an AI support bot on your knowledge base.
Where to start
Set up the forum, the tags and the AutoMod rule first. They help with or without a help desk.
When more than one person answers, or Discord questions start to mix with email and chat, connect the server to Deskwoot. You can read each step in the Discord setup guide before you sign up.
Discord works on every plan at no extra cost, and the free Hacker plan covers 1 server. New workspaces also get a 7 day trial of Enterprise, Fynn included, without a card and for up to 30 seats including yours. Create your account and connect your server today.
