1) Create a Discord bot
Create an application and a bot in the Discord Developer Portal. Turn on Message Content Intent so the bot can read messages.
SupportHQ runs an AI agent inside your Discord server. It answers from your docs in the channels you allow, stays quiet in general chat, and hands the hard questions to your team with a summary. Every conversation lands in one inbox outside Discord.
Three steps run on every message in the channels the bot can read.
It sees messages in the channels its Discord role can read.
It checks the channel name, whether it was mentioned, and recent messages against your rules.
It replies from your knowledge base, or flags the conversation for your team with a reason and an urgency.
Ticket bot vs AI support agent
Most people who search for a Discord ticket bot want something like Ticket Tool: a button that opens a private channel, staff who claim it, and a record when it closes. SupportHQ does not create ticket channels. It is an AI agent that answers questions where members ask them, and hands off to a human inbox when a person is needed.
| Aspect | Discord ticket bot | SupportHQ AI support agent |
|---|---|---|
| Who answers first | A staff member, every time. | The agent, from your knowledge base. |
| Where the conversation happens | A new private channel per ticket. | The channel, thread, or forum post where the member asked. |
| Privacy | Private to the member and staff by design. | Public channels stay public. Use a ticket bot for private cases. |
| Staff workflow | Claim and close tickets inside Discord. | Work from the SupportHQ inbox, with alerts by email, Telegram, or SMS. |
| Repeat questions | Each one becomes a ticket for a person. | Answered in seconds from your docs. |
| History | Often a transcript when the ticket closes. | Full history in the inbox, next to your website and Telegram conversations. |
| Best for | Private cases: payments, appeals, reports. | Public how-to, setup, and product questions. |
A ticket bot is the right tool when every request is private. An AI agent is the right tool when the same public questions come in every day. The two work well together: keep your ticket bot for payment problems and ban appeals, and give the SupportHQ bot your #help and forum channels, so the repeat questions never become tickets.
Setup
No bot code to write and nothing to host.
Create an application and a bot in the Discord Developer Portal. Turn on Message Content Intent so the bot can read messages.
Paste the bot token and client ID into your project's integrations tab, then test the connection.
Add the bot to your server. Give its role access only to the channels where it should help.
Upload your docs, sync your website, and add your pinned FAQ and release notes.
Start strict: reply when mentioned or when a message is a clear product question. Loosen the rules as trust builds.
Choose who gets an alert by email, Telegram, or SMS when the agent escalates.
For a longer walkthrough and the numbers to watch after launch, read an AI support agent for your Discord server.
In depth
A Discord AI chatbot that replies to everything gets muted. These are the controls that keep it useful.
The bot reads messages in the channels its Discord role can see. That is the simplest way to scope it: give it #help, #support, and your forum channels, and keep it out of staff and off-topic channels.
Advanced settings also let you limit the bot to specific server IDs. Scope channels with Discord role permissions, not the channel ID filter. That filter matches the exact channel or thread a message is in, so a forum or parent channel ID does not cover its threads and posts.
Response rules are plain English. Before it writes anything, the agent checks the message against your rules, with the channel name, whether the bot was mentioned, and the recent conversation as context. A starting set: answer product questions in #help, reply in #general only when mentioned, never post in #announcements.
When a rule says stay quiet, the agent stays quiet. Read when your AI agent should stay quiet for rules that work in busy servers.
In server channels, threads, and forum posts, the agent posts a native Discord reply to the member's message and mentions them. The answer is easy to find in a busy channel. You can turn off the reply style and the mention in settings.
Answers come from your knowledge base, in the language the member wrote in. If your docs do not cover the question, the agent says so instead of guessing.
Each thread and each forum post becomes its own conversation in the SupportHQ inbox. A regular channel is one running conversation.
That makes a forum channel the closest thing to a ticket queue: one post per question, and one conversation per post, each with its own history in the unified inbox.
The agent escalates when it is not confident, when a member asks for a person, or when the request needs an action it cannot take, such as a refund or an account change. It writes a reason, sets an urgency, and summarizes the thread.
Your team gets an alert by email, Telegram, or SMS and replies from the inbox. The reply posts back to Discord, and the agent pauses on that conversation. In a regular channel, the whole channel is one conversation, so an inbox reply pauses the agent in that channel until you resume it. Use forum channels or threads for per-question handoff. If your mods answer directly in Discord, add a rule that tells the agent to stay out when a person is already helping. See how human handoff works.
It is a support agent, not an all-in-one server bot. Running a community? SupportHQ for Discord communities shows example questions and handoff cases.
No. It does not open private ticket channels. It is an AI support agent that answers in the channels, threads, and forum posts where members ask, and hands off to your team through the SupportHQ inbox. You can run it next to a ticket bot.
Yes. Give the SupportHQ bot access to your help channels and keep it out of the private ticket channels your other bot creates. Each bot only reads the channels its role can see.
No. You create a bot in the Discord Developer Portal and paste its token and client ID into SupportHQ. SupportHQ keeps the bot connected and runs the agent. There is no code to write.
SupportHQ reads member messages through the Discord Gateway. Discord hides message text from bots unless Message Content Intent is on, so without it the agent cannot read most questions. Turn it on for your bot in the Developer Portal before you connect it.
Yes. The bot is yours, so it only joins the servers you invite it to. Advanced settings in SupportHQ also take a list of allowed server IDs, and messages from any other server are ignored.
Discord is included on every plan. Starter is $29 per month with 2,000 conversations. Growth is $49 per month with 3,000 conversations. No per-seat fees, no per-resolution fees, and a 7-day trial to start (card required).