待翻譯：Discord Welcome Bot That Greets Members, Threads and Tickets

AI 服務暫時不可用，以下為來源正文，待恢復後補全翻譯。

How to Make a Discord Welcome Bot That Greets Members, Threads and Tickets Piotr Grudzień on August 20, 2026 • 16 min read ; the original PNG/JPG stays as the fallback and remains the og:image for social scrapers. --> A Discord welcome bot posts a prepared message when something happens in your server: a member joins, a thread opens, a channel is created. Quickchat AI sends those messages from three rules you configure in a dashboard, with no code and no hosting. This tutorial sets up all three, tests each one, and shows what happens when a member replies to the greeting and the AI conversation begins. It covers both ways of connecting Discord to Quickchat AI, including the one extra Developer Portal setting that the member rule needs if you run your own bot. Why this exists: three requests from our own Discord Members of our own Discord server keep asking for the same thing in three different shapes. Each time, our support bot had to tell them it was not possible. Read together, the three are one request: let the bot speak first. Welcome someone who joins. Greet whoever opens a thread. Say hello in a new ticket channel, before the person in it has to work out that a bot is even there. The question has kept arriving all year, in the Discord server and in the widget. As of this week all three exist, as automated message rules you switch on in a dialog, and this post sets up all three, end to end. Why a Discord bot cannot greet anyone by default A Quickchat AI bot in Discord answers when it is mentioned or replied to. The shared one-click bot also supports /ask. That is deliberate: a bot that replied to everything would be unusable in a busy server. The side effect is that in a channel created ten seconds ago, nobody knows the bot is there. It cannot speak first, so it never gets spoken to. That is the cold start, and it is worst in a fresh ticket channel, where the member has a question and no idea that anything in the channel can answer it. An automated message is the bot speaking first. It is fixed text, so it costs nothing and cannot say anything you did not write, and it ends by telling the member how to start a real conversation. The three rules map onto the three requests above: New member joins, New channel, and New thread or forum post. What you will build The demo server is Nebula Lounge, a community server whose agent is called Orbit. By the end it has three greetings running: RuleFires whenPosts in New member joinsA person joins the serverOne channel you choose, #welcome New thread or forum postA public thread or forum post opensInside the new thread New channelA text channel is createdInside the new channel You need a free Quickchat AI account and permission to add a bot to a Discord server. A ticket bot such as Ticket Tool is optional, and only for the ticket workflow in the last section. How automated Discord messages work An automated message is a deterministic pipeline, not a model call. Discord sends the event, Quickchat AI checks it against the rule’s scope, waits the configured delay, fills the placeholders and posts the text. Nothing in that path asks a model what to say. That is what makes the message predictable enough to leave running in a public server, and it is why the message costs no credits. The AI conversation is a separate system that starts afterward, when a member mentions the bot or replies to it. What automated messages are not Four things people reasonably expect from the phrase “welcome bot” are outside this feature. Not verification. There is no CAPTCHA, no age or identity check, and no verified role to grant. Run a dedicated verification bot alongside this one. Not AI-written. The message is your text with placeholders filled in. The model never sees the event and never composes the greeting. Not ticket creation. Quickchat AI does not open the ticket channel. Your ticket bot does that, and Quickchat AI greets the person inside it. Not a broadcast or a scheduler. Each rule fires on one Discord event. There is no “post this every Monday” and no way to message a list of members. Connect the bot to your Discord server Open External Apps in the Quickchat AI dashboard and choose Discord. Set Bot name in the new server if you want the bot to carry your own name, then click Add to your Discord server and authorize it. This is the one-click flow: the shared Quickchat AI bot joins your server and you never create a Discord application or handle a token. Make sure the bot can View Channel and Send Messages everywhere you plan to post. A destination the bot cannot see does not appear in the dropdowns, and a destination it cannot post in is skipped silently at send time. Which setup do you have, and what changes Quickchat AI connects to Discord in two ways, and automated messages work on both. Which one you have changes where the rules live and whether one Developer Portal setting applies to you. One-clickYour own Discord app (Advanced) Which bot postsThe shared Quickchat AI applicationThe application you created Where the rules areAutomated messages on a server under Connected serversAutomated messages on the Discord page, Configure per server New channel and New thread or forum postApply immediatelyRefresh within about one minute New member joinsApplies immediatelyNeeds Server Members Intent, then refreshes within about one minute The reason for that last row is a Discord rule rather than a Quickchat AI one, and it is worth understanding once because it explains the only manual step in this whole tutorial. An intent is Discord’s subscription system. When a bot connects, it declares which categories of event it wants to receive, and Discord sends it only those. Most intents a bot simply asks for. Three are privileged, which means Discord withholds them until the application’s owner switches them on by hand, and one of those three covers the members of a server. So an application receives member join events only if Server Members Intent is switched on for it in the Developer Portal, and it is off by default on every new application. Channel creation and thread creation are not privileged, which is why the other two rules need nothing at all. The shared one-click application already has the intent enabled, so if you connected in one click, none of this applies to you. If you run your own app, Quickchat AI checks the setting for you. Open the New member joins rule and it tells you when the intent is off, and shows nothing at all once it is on. To switch it on, open your application in the Discord Developer Portal, go to Bot → Privileged Gateway Intents, turn on Server Members Intent, save, then save the rule again in Quickchat AI. Your bot keeps replying normally throughout, and only this one rule waits. One limit worth knowing before you build on it: if your own bot is in more than 100 servers, Discord requires your application to be verified before it will grant the intent. Open Automated messages Find your server and open Automated messages: under Connected servers on the one-click setup, or via Configure in the Automated messages section if you use your own app. All three rules are listed, each with its own switch, and all three start switched off. Two things about this screen are worth knowing before you start, because they change how you work in it. Each rule saves on its own. Opening a rule, editing it and clicking Save stores that one rule and returns you to this list. The other two are untouched. The switches on the list save immediately. There is nothing else to press. One-click settings apply immediately, while a bot connected through Advanced setup refreshes its rules within about one minute. If a greeting turns out to be noisier than you expected, one click starts that change. Welcome each new member Select New member joins. The rule opens with its own switch, a destination, a message template and a delay. Set Welcome channel to #welcome. Then set the Message template: Welcome to {server_name}, {username}! I'm {bot_name}. Mention me or use /ask whenever you need help. Leave Delay at 2 seconds, turn the rule on with Turn this message on, and click Save. If you run your own Discord app rather than the one-click bot, drop the /ask half of that sentence. The slash command only exists on the shared Quickchat AI application. The chips under the template insert a placeholder where your cursor is, so you do not have to remember the exact spelling. {username} is the member who joined, {server_name} is the server, and {bot_name} is whatever the bot is called in this server, including the name you set during connect. To test it, join with a second Discord account. The gap between Discord’s own join notice and the greeting underneath it is the delay doing its job. Every rule has one, and you can set it anywhere from none to thirty seconds. The negative control: invite another bot to the server. Nothing is posted. The rule ignores bot accounts on purpose, so an app install or a webhook does not produce a greeting addressed to software. Greet new threads and forum posts Select New thread or forum post and set Parent channel to your help forum. The rule fires for public threads and forum posts created under that parent, and ignores private threads. Parent channel is the channel that new threads appear under, and two kinds of channel can hold them. A normal text channel, where a thread branches off an existing message, and a forum channel, where every post is a thread and the channel has no ordinary message history of its own. Forum channels only become available once Community is enabled in your server settings. Either kind works here, but a help forum is the natural fit, because every question already arrives as its own thread. A forum channel also cannot contain private threads, so under a forum parent every post qualifies. Hi {username}, I'm {bot_name}. Mention me in this thread if you'd like help. If you prefer a human, leave your question here and they'll follow up. Here {username} is the person who opened the thread, which Discord reports directly, so it is always correct. {channel_name} is the thread itself. This is the rule that answers the “only reply in threads it creates for each question” pattern people ask about: every new question thread starts with the bot already in it, saying how to use it. The negative control: open a private thread under the same parent channel. Nothing is posted. Private threads are excluded, so a moderator conversation started under a public forum stays quiet. Greet every new channel, or only your ticket category Select New channel. By default it posts in every new text channel in the server, which is the setting most people want for a small community: any channel that appears has the bot introducing itself. Hi {username}, I'm {bot_name}. Reply to me or mention me if you need help. If you'd rather wait for a human, share your question and they'll get back to you as soon as possible. To narrow it, change Any category to Only in this category and pick one. A category in Discord is the collapsible group that channels sit under in the left sidebar: the grey heading with its channels indented beneath it. Ticket bots almost always create their channels under one, usually named something like Tickets or Support, and that is exactly what makes it a useful filter here. This is the ticket workflow. Point the rule at the category your ticket bot creates channels in, and channels created anywhere else in the server are ignored. The negative control: with the rule scoped to Active Tickets, create a channel in a different category. Nothing is posted there, and a ticket opened a moment later still gets its greeting. How the ticket greeting lands Ticket Tool creates ticket-0042 under your Active Tickets category and posts its own panel. A few seconds later, Quickchat AI posts the greeting underneath it. That ordering is [truncated for AI cost control]