Free
Core ticketing, one custom bot, unlimited tickets, two custom embeds, and required TicketCord branding.
Discord ticket bot features for support teams.
Custom bots, ticket operations, and optional AI in one platform. Feature availability is plan-based, so teams can start with core ticketing and add AI or enterprise workflows when needed.
No card required. After 14 days the account moves to Free, which shows TicketCord branding, unless you pick a plan. Basic and up remove the branding.
Core ticketing
The ticketing basics, on every plan.
Panels, buttons, and forms
Members open tickets from buttons, dropdowns, and forms on panels you design and post from the dashboard.
Channel or thread tickets
Each ticket opens as a private channel in the category you choose, or as a thread.
ModMail
Members can DM your bot to open a ticket, and staff replies reach them by DM.
Claims and staff tools
Staff claim tickets, add members, and close them with a reason, from Discord or the dashboard.
Transcripts and exports
Every plan includes ticket transcripts and HTML, JSON, CSV, or PDF exports. Retention follows your policy.
Dashboard replies
Answer tickets from the web dashboard as well as Discord. The bot posts your reply in the ticket.
AI and knowledge
Ground answers, then hand off with context.
Atlas AI
Available on Pro and Enterprise, with monthly token allowances tied to the plan.
Knowledge-base sources
Use up to 2 sources on Pro or 15 on Enterprise to ground assistance. Each website source supports up to 100 pages on Pro or 500 on Enterprise.
Confidence-aware workflows
Priority and duplicate detection are on Pro and Enterprise; smart auto-routing is Enterprise.
Human support
Keep staff in control of the conversation.
Operations and trust
Run several bots from one account.
Account-level bot limits
Free includes 1 bot, Basic and Pro include 3, and Enterprise includes 6.
Retention controls
Free retains closed-ticket content for 90 days; paid plans add 180-day, 365-day, and manual options.
19 bot interface languages
The bot interface is available in 19 languages. Website language coverage is separate.
Tutorials
Set up and run TicketCord, step by step
Video guides
The trickier settings, explained in under two minutes
Short clips
One feature each, in under a minute
Feature reference
Every feature, from panel to closed ticket.
Ticket creation
Ticket panels with buttons or dropdowns
A panel is an embed with an Open Ticket button, or a dropdown whose options each open a different ticket category. Any button or option can carry its own welcome message, so one panel can route support, sales, and applications to the right place.
Forms, modals, and applications
Attach a form to a panel button so members answer a few short or paragraph-length questions before their ticket opens. Applications use the same designer for structured intake, such as staff or partner applications, and need Basic or higher.
Private ticket channels
Every ticket opens as its own channel, visible only to its creator, staff roles, and the bot. With threaded tickets turned on, the bot opens a private thread instead and adds the creator plus every staff role member automatically.
Claiming
/claim records which staff member is handling a ticket, shown in the dashboard and in /claims. Exclusive claim mode can remove other staff members' channel access until the ticket is unclaimed, while configured supervisor roles always keep access.
Roblox, Steam, FiveM and RedM accounts
Show each ticket opener's Roblox account, from your server's Bloxlink key, their linked Steam account, and their player on your FiveM or RedM server, with account age, bans and txAdmin warns. FiveM and RedM players are matched by their Discord account, and the details update while the ticket is open. You can require a linked Roblox or Steam account before a ticket opens. Available on every plan.
Staff workflow
Staff roles and permissions
Select up to 10 Discord roles as ticket staff in the dashboard. Members with a staff role can use staff commands and see every ticket. Only the bot owner can change staff roles; anyone else with dashboard access sees the setting read-only.
Transcripts
/transcript generates an HTML transcript of the current ticket and sends it to the configured transcript channel, another channel, or a DM. Evidence transcripts add Discord IDs and message links, and closing a ticket can post one automatically.
Auto-close
Close quiet tickets automatically after 15 minutes to 30 days of inactivity, with an optional reminder posted first, on Basic and above. Auto-close on user leave, which closes a member's open tickets when they leave the server, is on every plan.
Canned responses
Save reusable replies staff can insert into a ticket in one step. Free has none, Basic and Pro include 25, and Enterprise has no configured limit, useful for repeated billing, setup, or account questions.
ModMail: DM tickets
Members can message the bot directly instead of using a panel. Staff answer from a dedicated ticket channel with evidence tools for moderation, and /close in:2h schedules a close that any new activity cancels.
Automation and AI
Automatic answers with human handoff
Atlas answers members directly and includes source references when knowledge-base material is used. When it cannot help it offers Talk to Staff; requests for a person trigger handover. Staff continue the same conversation in Discord or the web inbox. Private AI Help drafts are also available.
Knowledge base
Ground Atlas in your support content and reusable Q&A. Pro supports up to 2 sources with 100 crawled pages per website source; Enterprise supports up to 15 sources with 500 pages each. Larger source reads can require approval of the AI cost. Learning can publish confident entries automatically or hold every entry for review.
Business hours and SLAs
Enterprise adds business hours, SLA targets, and approval workflows. Outside business hours, new tickets are blocked with a closed notice or opened with an after-hours notice, and SLA timers can pause. SLA breaches are tracked against your response and resolution targets.
Operations
Retention controls
Free retains closed-ticket content for 90 days. Paid plans add 180-day and 365-day options plus manual deletion, so closed tickets are purged automatically once their window passes while ticket metadata and audit fields remain.
Web inbox
Reply to tickets from a dashboard inbox instead of Discord: filter by status, tag, priority, or text search, keep internal notes staff-only, and reply from either surface while the ticket stays connected to Discord.
Analytics
Dashboard analytics summarize ticket volume, response and resolution time, staff performance, and the ratings collected through feedback, available on Basic and above so teams can see where support time actually goes.
19 bot interface languages
Each server picks its own bot language from 19 supported languages, independent of the 12-language dashboard interface. Members using the bot in Discord see menus, buttons, and messages in the language you choose for that server.
Custom bot identity
Every bot is your own Discord application. Its name, avatar, and status are yours to set in the Discord Developer Portal, and TicketCord reads them from Discord, so members see your brand, not TicketCord's.
Basic and Pro
Both include three custom bots, analytics, auto-close, branding controls, and flexible retention. Pro adds AI and knowledge-base sources.
Enterprise
Six custom bots plus larger AI allowances, up to 500 pages per website source, business hours, SLA management, approvals, unlimited canned responses, and webhooks.