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, enable Server Members Intent and Message Content Intent under Privileged Gateway Intents, then click Reset Token and copy the token.
Never share the token. Anyone who has it controls your bot.
Add the bot to TicketCord
Sign in at ticketcord.com/dashboard with Discord, click Add Bot, paste the token, and click Validate & Continue. TicketCord reads the bot's name and avatar from Discord. Click Create Bot.
If validation reports a "disallowed intent" (4014) error, the two intents from step 1 are still off.
Invite it to your server
On the bot's page click Invite, pick the server, and authorise. 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.
Run /setup in Discord
In the server, run /setup. With no prompts it creates:
- the 🎫 Tickets and 📁 Closed Tickets categories
- the 📝 Ticket Logs category with
#ticket-logsand#ticket-transcripts - the Ticket Admin and Ticket Support roles (named TicketCord Admin and TicketCord Support on the Free plan)
If matching resources already exist it asks whether to create a second set, use the existing ones, or cancel.
Save the essentials in the dashboard
Open Dashboard → Bots → your bot → Servers → the server. Under Staff select the two roles; under Structure select the Tickets and Closed Tickets categories and the logs channel; under Transcripts select #ticket-transcripts. Save, then give the roles to your team in Discord.
/setup only creates the Discord resources. Tickets do not open until this step is saved.
Post a ticket panel
Under Panels & Embeds, create an embed, add a button with the Open Ticket action, and send it to a channel such as #support (or run /embed name:<embed name> channel:#support). Press the button to open your first ticket, then close it with /close.
Check it worked
- The bot shows online in the dashboard and 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-0001, moves it to the closed category, and posts a 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.
I ran /setup but the button says the server is not set up (TC011).
Complete step 5: select the roles, categories, and channels in the dashboard and save.
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 skip /setup and use my existing categories and roles?
Yes. Select them in the dashboard instead. /setup is a convenience, not a requirement.
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