Discord & community · 6 min read
Organize community support with website, email and Discord
A community needs a clear way to help. Use the website as a guide, a Discord for public questions and e-mail or a closed form for confidential concerns. The most important decision is where a request is processed and completed. A short page with responsibilities, contact paths and expected response times often helps. Choose only what tasks you want to automate and which one a person should take over.
Split the contact paths by request
Arrange questions to a channel before you set up forms or bots. Frequently asked questions about operation can be answered publicly. If someone wants to restore an account or reports a private incident, the request needs a protected channel. Publish this distinction at the places where members are looking for help. Thus, they need to switch between platforms less often and get an answer faster from the person in charge.
A short overview with concrete examples is useful as a starting point. A link "Questions about the community" leads to the public help channels. "Report account problem" leads to a private way. Give for each channel, who supervises it and when the team usually looks. Formulate these times as an orientation based on your actual occupation.
Show the next step on the website
The help page should be accessible quickly on the smartphone. Place the entry where problems occur, for example when logging in or in the community rules. The contact path must also work for people who currently have no access to their Discord account. A direct link to a contact form or a reachable email address helps in such cases.
You can collect recurring questions in a small help area. Keep each answer aligned to a specific task and link the next step. If the process changes, update the central answer and replace outdated clues in attached posts. Thus, conflicting information becomes less frequent over time. As an example of such a structure, you can use the [dhosty Help Center].](/hilfe/) The European
Organize e-mail for confidential concerns
For e-mail support, a jointly managed mailbox or ticket system with clear responsibilities helps. If several people use the mailbox, determine who takes over new requests, who can represent and how a case is closed. A short status label such as "open", "in preparation" and "waits for feedback" facilitates the transfer and avoids duplicate responses.
Ask for the function concerned, the time and the error message. Please ask the person to remove personal details from screenshots, if these are not needed for processing. Passwords, bot tokens and confirmation codes do not belong in a support message. If a case is passed on internally, only share the information required for processing with the responsible team.
Use Discord for exchange and quick orientation
A channel of help on Discord is suitable for questions from which other members benefit. Keeps the channel description short and makes visible when a request is better reported privately. Moderators should be able to refer public contributions to the appropriate way if necessary, without reciting the confidential part of the request in the channel.
For a common question, a well-kept default answer with a helpful link is often sufficient. If you want to use a bot for it, specify who can change commands and how to test their output.](/discord-bot-hosting/) you can check the offered functions and packages. You should not plan an automatic connection to the website or email until the required interface and its operation have been clarified.
Making transfers between channels comprehensible
A case can start publicly and become confidential later. Then give the person a clear next step and specify what information to specify at the new contact point. If you already work with process numbers, a reference is often enough for the assignment. Copy a complete message only into a system that is intended for this content.
This is where the current status, the person responsible and the next step are located. In other channels, a brief reference to the further processing is sufficient. If several systems exchange status messages, the system is documented which is the decisive factor. Thus, the transfer remains understandable, even if a bot fails or a team member changes the shift.
Test automation in small steps
Start with a process that often occurs and can be clearly answered. This can be a Discord command that points to your contact overview. Test it with the permissions of an ordinary member. Check if the answer appears in the correct channel, the link is accessible and no confidential content is published. Determine who can disable the process if an error occurs.
If you want to transfer requests between platforms later, clarify the required permissions and fields in advance. Test with invented data, which happens in case of double events, delayed answers and an unreachable goal. A new delivery attempt should not open a second process if possible. Keep a simple manual path for important messages, which the team can use without integration.
Checking the quality of support in everyday life
After the launch, look together at some closed cases. What questions ended up in the wrong channel? Where did members have to enter data several times? Which cases remained because no one felt responsible? Such observations usually show better than the pure number of messages, where the sequence is unclear.
First adjusts the contact overview and internal responsibilities. Then check whether the same problems occur again. If you change the team, a second person should be able to take over the process using your documentation. Also, keep track of where technical access data are stored and who manages them. This also keeps support accessible and understandable when you change the team.
Frequently asked questions
Do I need a bot to get started?
A contact page, a managed mailbox and a Discord help channel are enough for many small teams. A bot is worth it if a task occurs often and is clearly defined. For example, start with a command that refers to the relevant help page.
Where do I process reports of a private incident?
Use a protected contact path and restrict access to the responsible persons. In the public channel, provide a reference to the registration path. Please ask the data subject not to publish private messages, access data or unswedged screenshots.
What time should I specify?
Orient yourself to the actual occupation of your team. A reachable contact point and a clear indication of when requests are usually read are more helpful for members than a deadline that the team regularly exceeds.
How do I avoid double processing?
Arrange each case of a person and a leading channel. Use a reference when handing over and determine who will take over the next answer. If the person additionally requests in Discord, refer to the already ongoing process.