Bot Overview

What a TicketCord bot is, how a ticket flows from panel to transcript, and what each plan includes

TicketCord runs a Discord ticket bot under your own application, so members see your name and avatar rather than a shared bot. Each bot you create is independent: its own branding, its own configuration per server, and its own ticket history. You configure it from the web dashboard and staff work tickets in Discord with slash commands.

How a ticket flows

A member opens a ticket

They press a button on a panel you posted, pick a dropdown option, fill in a form, or (in ModMail mode) DM the bot. The bot checks the firewall, business hours, and the member's open ticket count first.

A private channel is created

A channel such as ticket-0001 appears in your ticket category, visible only to the creator, staff roles, and the bot, with your welcome message. Its name and who is pinged come from the button, or from New ticket defaults for the whole server.

Staff handle it

Staff claim it, reply (by hand, with /reply, or from an /ai-help draft), add colleagues, set priority and tags, and keep internal notes. Every action is logged to the logs channel (see Where the bot posts).

It closes

The creator or staff close it. The channel becomes closed-0001 and moves to the closed category (or is deleted), the transcript is posted, and, depending on your settings, the creator is DMed and asked for a rating. Auto-close handles tickets that go quiet.

What the bot does

AreaCapabilities
Ticket panelsEmbeds with buttons or dropdowns, each mapped to its own category and welcome message; optional application forms before the ticket opens
Ticket channelsChannel or thread tickets, per-user open limits, priority indicators, tags, claims (optionally exclusive), internal notes, close requests, transcripts
ModMailMembers DM the bot and staff answer from a ticket channel, with evidence tools for moderation
Email inboxEmails to your own addresses open tickets, and staff answer from Discord by email (Pro and higher). See Email Inbox
Website widgetA chat on your own website: every conversation opens a ticket, and staff answer from Discord (Pro and higher). See Website Widget
AutomationAuto-close after inactivity, reminders before closing, auto-close when a member leaves, auto-delete on close, DM on close, feedback collection
AIAuto Support answers from your knowledge base, AI reply drafts, ticket summaries, priority detection, translation, auto-routing, tone detection
Enterprise workflowsBusiness hours, response targets, approval requests, scheduled reports, webhooks
LanguagesThe bot's own messages are available in 19 languages, chosen per server under General → Bot language

Plans at a glance

Plan gates apply to the account that owns the bot. Every new account starts with a 14-day Enterprise trial, no card required.

FreeBasicProEnterprise
Bots1336
TicketsUnlimited, up to 5 open per memberUnlimited, configurable per-member limitUnlimited, configurable per-member limitUnlimited, configurable per-member limit
Custom embeds per server25515
Canned responses02525Unlimited
BrandingTicketCord footerFooter removedFooter removedCustom footer text
Auto-close and reminders before itNoYesYesYes
Application forms, DM on joinNoYesYesYes
AI features and monthly AI tokensNoNo10M tokens30M tokens
Knowledge base sources00215
Email inbox addresses and emails sent per monthNoNo3 addresses, 3,000 emails10 addresses, 5,000 emails
Website widgetNoNoYesYes, and can hide Powered by TicketCord
StatsNoYesYesYes
WebhooksNoNoNo20 per server
Business hours, response targets, approvalsNoNoNoYes

Prices and the full comparison are on Plans.

Where things live

TaskWhere
Add a botAdd a bot under Your bots in the dashboard sidebar
Restart a bot, update its token, set its status and footerThe bot's Bot profile page (open the bot under Your bots)
Configure a serveryour server (the server's tile on the dashboard home), then its settings pages
Design panels and embedsThe server's Panels → Ticket panels
Work ticketsDiscord slash commands, or Tickets
Read transcriptsThe server's transcript channel (the logs channel when it has none), or the ticket under Tickets in the dashboard
Stats and reportsStats; emailed reports under General → Scheduled reports

Common questions

Is TicketCord one shared bot or my own? Your own. You create the application in Discord's Developer Portal and TicketCord runs it. Members never see the TicketCord name unless you keep the default footer on the Free plan.

Does the bot need Administrator? The dashboard invite asks for it, since October 2026, together with the specific permissions the bot uses (channel, role, thread, message, and webhook management). Many servers have channel permission overrides that would otherwise hide channels from the bot; Administrator works past them. You can untick it in Discord and the bot still works, as long as it can see the channels you pick. See Why the invite asks for Administrator.

Can I run different settings in different servers with the same bot? Yes. Every server has its own configuration, staff roles, categories, panels, and automation.

What happens when my trial ends? The account moves to the Free plan. Configuration and tickets are kept; features above Free stop working until you upgrade, and the bot keeps handling tickets within Free limits.

Do members need to install anything? No. They open tickets by pressing a button or sending the bot a DM, inside Discord.

Which languages can the bot speak? The bot's messages are available in 19 languages: Arabic, Chinese (Simplified and Traditional), Czech, Dutch, English, French, German, Hindi, Italian, Japanese, Korean, Polish, Portuguese, Russian, Spanish, Swedish, Turkish, and Vietnamese. Ticket translation between members and staff is a separate Pro feature.

Last updated on

On this page