By SupportHQ Team · October 13, 2026 · Channels

Discord Ticket Bot vs AI Support Agent: Which Do You Need?

A Discord ticket bot turns a support request into a private channel. A member clicks a button, the bot opens a channel that only the member and your staff can see, and a staff member works the case until someone closes it. That model is right for private cases. It is slow for the question your #help channel gets ten times a day.

This post compares four well-known ticket bots on what the free plan includes and what you pay for. Then it explains what an AI support agent does differently, where it does not replace a ticket bot, and how to run both in one server. Every ticket bot price and limit below comes from the bot’s own website, checked on October 1, 2026.

How a Discord ticket bot works

Most ticket bots share the same five parts.

1. The panel. The bot posts a message with one or more buttons in a channel such as #open-a-ticket. Each button can map to a category: billing, bug report, appeal.
2. The form (optional). Some bots ask a few questions before they open the ticket. Tickets and TicketerBot both list forms.
3. The private channel. The bot creates a new channel. Only the member and your support roles can view it.
4. Staff roles and claiming. Everyone with a support role gets access to each new ticket. One staff member claims it, so two people do not answer the same case.
5. Close and transcript. When the case ends, the bot closes the channel and saves a transcript: a text or HTML copy of the messages.

Step 3 is the important one. Every request becomes a channel that a person must read and answer, from “where do I download the client?” to “my payment failed”. A ticket bot organizes support work. It does not reduce it.

Four Discord ticket bots compared: free vs paid

Confirm prices on each bot’s page before you buy.

Three quick reads of the table:

• Most free capacity: Tickets and Helper.gg list unlimited tickets on the free plan. Ticket Tool’s free plan has unlimited panels and a limit of 10 tickets a minute.
• Staff who prefer a browser to Discord: Helper.gg has a web panel on its free plan. TicketerBot adds an inbox view on Pro.
• A multilingual community: Helper.gg Premium lists ticket translation.

All four are cheap. The cost of a ticket bot is not the subscription. It is the staff time behind each ticket.

What an AI support agent does differently

Follow one question, “How do I link my account?”, through each tool.

With a ticket bot. The member finds #open-a-ticket and clicks the button. A private channel opens. The member waits until a staff member is online. The staff member types the answer they typed yesterday, then closes the ticket. The answer lives in a private transcript, so the next member asks again.

With an AI support agent. The member posts the question in your #help forum. The agent, a Discord AI chatbot trained on your docs, replies in that post within seconds. The answer comes from your knowledge base and stays visible in the forum for the next member. If the docs do not cover the question, or the member needs an account change, the agent escalates. It writes a reason, an urgency, and a summary, and your team gets an alert by email, Telegram, or SMS. A teammate replies from the SupportHQ inbox, and the reply posts back to Discord.

Three mechanics decide how you set up channels for the agent:

• Each thread or forum post is its own conversation. A plain channel is one running conversation. An inbox reply pauses the agent on that conversation, so a reply in a plain #help channel pauses the agent for the whole channel. A forum channel gives you per-question handoff.
• Only a reply from the SupportHQ inbox pauses the agent. A mod who answers directly in Discord does not pause it. Add a rule that tells the agent to stay out when a person is already helping. Our post on when an AI agent should stay quiet has rules that work in busy servers.
• You bring your own bot. You create a bot in the Discord Developer Portal and paste its token into SupportHQ.

The full setup is on the Discord support bot page. The numbers to watch after launch are in an AI support agent for your Discord server.

Where an AI agent does not replace a ticket bot

An AI agent is a support tool, not a server bot.

• Private cases. The agent answers where the member asks, so in a public channel the question and the answer are public. Use a ticket bot for private cases. A report about another member often needs several mods in one room with the evidence. A private ticket channel does that.
• Moderation. SupportHQ does not kick, ban, time out, or change roles.
• Role gating and verification. SupportHQ does not hand out roles or verify members. TicketerBot Pro lists auto-role on join and moderation lite, if you want one bot for both jobs.
• Account and order lookups. The agent cannot look up a purchase or an account. A ticket form can collect an order ID before staff see the case.
• Staff who work only in Discord. A ticket bot keeps every case inside Discord. With SupportHQ, handoffs land in an inbox outside Discord.

A decision rule by server size and question type

First, sort your last 50 support questions into three groups:

1. Public how-to: setup, downloads, features, known issues. Your docs could answer them.
2. Private: payments, account problems, ban appeals, reports about other members.
3. Undocumented: bugs and topics no doc covers yet.

Then use this table. The thresholds are our rule of thumb, not industry data.

Why 20 a week? At about 3 minutes per simple answer, 20 questions take one hour of mod time a week. Below that, an agent saves little time. For a wider view of what to automate first, see support automation: what to automate first.

Worked example: 300 questions a week

This is an example, not a benchmark. The assumptions:

• The server gets 300 support questions a week.
• A sort of 50 recent questions gives this mix: 60% public how-to that the docs cover (180 a week), 15% undocumented (45), and 25% private (75).
• The agent resolves 70% of the covered how-to questions without staff. The other 30% escalate.
• Every undocumented question escalates.
• Each case that reaches staff takes 6 minutes. That is a full case (open, read, reply, close), not a simple answer. In setup A, even a how-to question becomes a full case.

The arithmetic for B and C: 180 × 70% = 126 questions answered by the agent. The other 54 covered questions escalate, plus 45 undocumented ones. That is 99 escalations from public channels. In setup B, the 75 private cases also reach staff, but they start in a public channel. In setup C, they go to the ticket panel.

Setups B and C give the same staff load. The difference is privacy. That is the reason to run both.

The resolution rate is the number to test. At 50%, the agent answers 90 questions and 210 reach staff (21 h). At 85%, it answers 153 and 147 reach staff (14.7 h). The lever is docs coverage. Each time a mod answers an undocumented question, turn the answer into an article. That moves the question into the covered group for next week.

One volume check. 225 public questions a week is about 975 forum posts a month (225 × 52 ÷ 12). Each post is its own conversation. That is well under the 2,000 conversations a month on the Starter plan. Every post in a forum the bot can see counts as a conversation, even when the agent stays quiet. Keep the bot out of showcase or off-topic forums.

How to run both in one server

Give each channel one owner. This splits your Discord customer support into two lanes: public questions go to the agent, private cases go to tickets.

Then set the permissions so the two bots do not overlap:

1. Do not give the SupportHQ bot the Administrator permission. Discord’s permissions documentation says Administrator bypasses channel permission overwrites. A bot with it can read every private ticket.
2. Do not add the SupportHQ bot’s role to the ticket bot’s support roles. If you do, the ticket bot gives it access to each new ticket channel.
3. Scope the agent with Discord permissions. On #help and #general, give the SupportHQ bot’s role View Channel, Read Message History, Send Messages, and Send Messages in Threads. Deny View Channel on every other channel. Forum posts inherit the forum’s permissions, so the bot sees each new post in #help and nothing in staff or ticket channels. Leave Allowed channel IDs in SupportHQ empty. That filter matches the exact channel or thread a message is in, so a forum’s ID does not cover the posts inside it. You can still set Allowed server IDs to your server.
4. Add a rule for #general: “In the channel named general, reply only when the bot is mentioned.”
5. Add one rule as a backstop: “Never reply in a channel whose name starts with ticket-.” Match the prefix your ticket bot uses. The agent checks the channel name against your rules before it writes.
6. Write one routing article. Add this to the knowledge base: “For payments, refunds, account problems, ban appeals, or reports about another member, open a ticket in #open-a-ticket.” When a member raises a private topic in #help, the agent can send them to the panel. If the agent is not sure, it still escalates.

The agent ignores messages from other bots, so a ticket bot’s panel and welcome messages never trigger a reply.

Start with the sort

Sort your last 50 questions this week. If more than half are private, install a free ticket bot from the table and stop there. If more than half are how-to questions your docs answer, set up a forum channel for an agent first, then add a ticket panel for the private rest.

The Discord support bot page has the setup steps for the agent. SupportHQ for Discord communities lists typical questions and handoff cases for servers. To test the worked example on your own server, start a 7-day trial (card required) and give the agent access to one forum channel.