Set up your first ticket category

What “category” means in TicketCord

We use Discord’s built-in channel categories - there’s no separate concept to learn. Every new ticket becomes a text channel inside the category you choose, and the bot manages permissions per channel so only the requester and staff can see it.

The quick path: let TicketCord create them

In the setup form (the guided setup on your first sign-in, or the server’s home page in the dashboard until it is set up), press Create them for me. It lists exactly what it will create, and creates only what you have not picked yet:

• A Tickets category for open tickets and a Closed Tickets category.
• A private Ticket Logs category with a transcripts channel and a logs channel.
• Two staff roles, Ticket Admin and Ticket Support (named TicketCord Admin and TicketCord Support on the Free plan), unless you picked staff roles of your own.
• Private permissions: @everyone cannot see any of it, the bot and your staff roles can.

It then picks them in the form for you. Save the form, give the roles to your team in Discord, and tickets can open. The bot needs Manage Roles to create the roles and Manage Channels to create the categories and channels (the invite asks for both); if one is missing, the form says which. If your server requires 2FA for moderator actions, the account that created the bot in the Discord Developer Portal must have 2FA on too. That is a Discord rule, not ours.

Or from Discord: /setup

Running /setup in your server creates the same set in one go. It needs the Discord Administrator permission, or Manage Channels and Manage Roles. Before creating anything, it looks for categories, channels, and roles that seem to come from an earlier ticket setup (e.g. “Tickets”, “Closed Tickets”, “Ticket Admin”, “Ticket Support”). If it finds any, you get three buttons:

• Use existing - keep your current resources untouched; you’ll point the dashboard at them yourself.
• Create anyway - make new ones with slightly different names so they don’t collide.
• Cancel - back out without changing anything.

/setup only creates the Discord side. It doesn’t tell TicketCord which categories or roles to use: afterwards, pick them in the setup form. Without that step, tickets still won’t open.

Or: create the categories yourself

1. In your server, create a category called something like Open tickets.
2. Optionally create a second one called Closed tickets - TicketCord can move resolved channels there instead of deleting them, which is useful for audit history.
3. Set both categories to private by default: in the category permissions, deny View Channel for @everyone and grant it for your staff role and the TicketCord bot.

Point TicketCord at them

Pick them in the setup form, or later on the server’s Opening tickets page under Ticket categories. You can pick more than one if you want tickets to spread across them as each fills up (Discord caps each category at 50 channels). If you made a closed category, choose it as Move closed tickets to on the Closing tickets page.

Both settings accept a list, so you can add more categories later without replacing what you already chose.

What the bot does to permissions

When a customer opens a ticket, TicketCord creates a new text channel inside the open category and adds three permission overwrites: deny @everyone View Channel, grant the requester View + Send + Read History, and grant your staff roles the same. The category-level permissions stay untouched.

Next up

With somewhere for tickets to land, you’re ready to create a ticket panel so customers have a button to click.