Quick Start
From an empty Developer Portal to a working ticket panel in about ten minutes
This is the shortest path to a bot that opens tickets. Each step links to the page with the full details.
You need Administrator (or ownership) on the Discord server, and Discord requires Manage Server to add any bot. Every new TicketCord account starts a 14-day Enterprise trial with no card required, so every feature is available while you set up.
Create the Discord application
Go to discord.dev, click New Application, and name it. On the Bot tab: turn Public Bot off, then click Reset Token and copy the token. TicketCord turns on the privileged intents it needs (Server Members Intent and Message Content Intent) when it checks the token; if Discord refuses, the check tells you to turn them on here.
Never share the token. Anyone who has it controls your bot.
Connect the bot to TicketCord
Sign in at ticketcord.com/dashboard with Discord. The first time you sign in, a guided setup opens ("Let's set up your ticket bot."). Click Get started, paste the token on Connect your bot., and click Check token. While Discord checks it the setup says "Checking your token with Discord…", then shows the bot's name and avatar with "Discord confirmed your token."; if they look right, click Connect bot.
If the check says the privileged intents are off, the two intents from step 1 are still off.
Invite it to your server
On Add your bot to a server., press Add bot next to your server and approve it in Discord. The setup notices when the bot joins.
The list shows the servers you own or have Administrator in; made a server or got Administrator after signing in? Click Refresh the list (once every 5 minutes).
The link requests exactly the permissions the bot needs plus the slash command scope. Do not build your own invite link; see Installation for why.
Go to Invite to a serverChoose where tickets go
Back in the guided setup, Choose where tickets land. asks for:
- a Panel title (members see it at the top of your ticket panel; left empty, it is Support)
- the Staff roles and the Ticket categories
- Move closed tickets to (optional)
- the Transcripts channel and the Logs channel
The setup first picks matching ones from your server ("Choosing for you…"; click Pick myself to choose them yourself).
A new server usually has none of these yet. Click Create them for me at the top of the form. It lists what it will create:
- the Ticket Admin and Ticket Support roles (named TicketCord Admin and TicketCord Support on the Free plan)
- the 🎫 Tickets and 📁 Closed Tickets categories
#ticket-transcriptsand#ticket-logsin a private 📝 Ticket Logs category
Click Create them: the bot creates them in your server and fills in the form. It only creates what is still empty, so you can pick your own staff roles and let it create the rest.
Check the choices, click Save and continue, and give the staff roles to your team in Discord. If imported panels already fill your plan's limit, use an existing newer-style panel's exact name as the Panel title to reuse it; setup cannot add another panel over that limit.
Created a role or channel in Discord yourself, or ran /setup there (it creates the same set)? Click Refresh at the top of the form; the lists also update on their own within about a minute.
Tickets do not open until these choices are saved. For a server you set up later, open your server: the same form opens there (Set up tickets for this server, then Finish setup).
Optional: set up the AI
The next two steps, Add your help docs. and Choose what the AI does., are optional and need the trial, Pro, or Enterprise. Click Skip AI setup to leave them for later.
On Add your help docs., pick what to add at the top:
- Website: the link to your docs, How many pages to read (up to your plan's limit), and Check for changes.
- Discord: a channel the bot can read, and Check for changes.
- GitHub: connect GitHub, then pick a repository and branch; it updates on every push (Enterprise, including the trial).
- File: a
.txt,.md, or.docxfile with up to 50,000 characters of text. AI also turns it into Q&A entries. - Q&A: a question and its answer.
Everything except Q&A entries counts toward your plan's sources ("2 of 15 used"). The preview on the right shows an example of you asking a question and the bot answering the way it does in tickets. Remove anything with the bin icon next to it. The same sources, with more options, are described in Adding Sources.
On Choose what the AI does., Answer questions in tickets is on when you added help docs in the step before. Without help docs, it and Answer in public help channels stay off, with the note "Add help docs in the previous step to turn these on." Changes on this step are kept if you go back a step, and saved when you click Save and continue.
Post a ticket panel and open a test ticket
On Try your first ticket., pick the Panel channel (such as #support) and click Post ticket panel. The list shows the channels your bot can post in, without the ticket, transcripts and logs channels your members cannot see.
Then click Open Discord and press the ticket button on your new panel. When the setup detects your test ticket, it finishes and opens the dashboard. Close the test ticket with /close.
To change the panel first, click Customize next to Post ticket panel. The editor shows the panel as it looks in Discord: click any part of it to change it, or describe what you want to the assistant (on the trial, Pro, or Enterprise). Click Save panel to keep your changes.
- The editor's controls are locked while saving; if saving fails, your draft stays open so you can retry.
- While an image is uploading, wait for it to finish before saving or closing the editor.
- Resizing the window or rotating your device keeps your unsaved customization.
- After posting, Customize is still there, and saving also updates the panel you posted.
The switch at the top of the editor moves between Ticket panel and Welcome message, the first message the bot sends in every new ticket; each has its own save button, and switching with unsaved changes asks before discarding them.
The setup gives your server a welcome message design named Welcome; change it and click Save welcome message. If the server already had a welcome message, the editor shows it turned into a design, and saving makes new tickets use that design (the old message stays available on Messages).
If a test ticket is detected while Customize is open, setup waits for you to save or close the editor before finishing. Unsaved edits are not discarded by the test ticket.
You can also post the panel yourself with /embed name:<panel title> channel:#support; the step shows the embed name to use under Post it yourself in Discord instead.
Later panels are made on Panels → Ticket panels.
Check it worked
- The dashboard home shows your server with the status Working, and the bot is online in your member list.
/diagnosein the server reports All Checks Passed.- Pressing the panel button creates
ticket-0001that only you, staff, and the bot can see. /closerenames it toclosed-0001and moves it to the closed category. Press Transcript on the closed ticket (or run/transcript) to post its transcript in#ticket-transcripts.
Common questions
The bot is online but /setup is not in my command list.
Discord hides /setup unless you have Administrator, or Manage Channels and Manage Roles. Reload Discord with Ctrl+R (Cmd+R on Mac) if you just invited the bot.
The panel button says the server is not set up (TC011). Complete the Choose where tickets go step: select the roles, categories, and channels and save. If you already left the guided setup, open your server and fill in the setup form there.
I skipped or closed the guided setup. How do I continue? If you only closed the page, the setup continues where you left off the next time you open the dashboard. If you chose Skip setup and then Skip forever, it does not come back. Do the same from the dashboard instead:
- Add the bot with Add a bot under Your bots in the sidebar.
- Invite it from the dashboard home (Invite a bot, or the Add TicketCord to another server tile once you have a server).
- Open your server to fill in its setup form.
Pressing the button does nothing, or shows TC002.
The bot is missing permissions in the ticket category. Run /diagnose, then fix the category's permission overwrites for the bot's role.
Can I use my existing categories and roles?
Yes. Pick them in the setup form. Create them for me and /setup are conveniences, not requirements.
Create them for me says the bot needs a permission. Creating roles needs Manage Roles, and creating categories and channels needs Manage Channels. In Discord, open Server Settings → Roles, give the bot's role the permission the form names, and try again. The invite link from step 3 asks for both.
What should I do after the first ticket works? Decide who may close tickets, enable auto-close and transcripts, and write a welcome message. Configuration walks through each setting.
Tune who can close tickets, transcripts, auto-close, and panels
Join the support Discord and ask the team
Was this page helpful?
Last updated on