Configuration
Turn a freshly invited bot into a working ticket system: pick or create the roles and channels in the dashboard, post a panel, and tune automation
Configuration happens in the dashboard. Its setup form asks how members open tickets (a ticket panel or ModMail) and which staff roles, categories, and channels the bot should use, and can create the ones you do not have yet in your Discord server. (/setup in Discord creates the same set, if you prefer to start there.) The bot does not create tickets until the setup is saved.
You must be the bot owner to set up a server in the dashboard, or hold a role granted dashboard access to change its settings afterwards. Running /setup in Discord needs Administrator, or Manage Channels and Manage Roles.
Setup flow
Pick or create the roles and channels
Go to your server and, in the setup form, pick the staff roles, ticket categories, transcripts channel, and logs channel you already have. Create them for me creates the ones you are missing.
Save the essentials
Save the form. The guided setup asks for these the first time; for any other server, click it on the dashboard home and fill in its setup form.
Post a ticket panel
Go to Panels → Ticket panels, design a panel with an Open Ticket button, and post it to a public channel.
Tune the lifecycle
Decide who can close tickets, whether transcripts are kept, and when tickets auto-close.
Step 1: Pick or create the roles and channels
The setup form shows in two places:
- On your first sign-in, as part of the guided setup (Choose where tickets land.).
- For any other server, on its home page (your server) until it is set up (Set up tickets for this server).
Pick what you already have. While a required choice is empty, the form offers Create them for me: it lists exactly what it will create, and when you click Create them, the bot creates it in your server and picks it in the form.
| Created in your server | When | Purpose |
|---|---|---|
| Ticket Admin and Ticket Support roles | No staff role is picked | Staff roles for your team (named TicketCord Admin and TicketCord Support on the Free plan). Give them to your team in Discord |
| 🎫 Tickets category | No ticket category is picked | New ticket channels open here |
| 📁 Closed Tickets category | Move closed tickets to is empty | Closed tickets move here |
#ticket-transcripts | No transcripts channel is picked | Transcripts are posted here |
#ticket-logs | No logs channel is picked | Ticket events and staff actions are logged here |
The two channels go in a private 📝 Ticket Logs category. Everything created is hidden from @everyone and open to the bot and your staff roles (the ones created with it, or the ones you picked); staff can read the transcripts and logs channels but not post in them.
To create roles the bot needs Manage Roles in your server, and to create categories and channels Manage Channels; if one is missing, the form says which.
If another setup tab has already created the requested resources, creation stops instead of making another set. Reload the Discord lists and select the existing roles and channels. If creation times out or is interrupted, TicketCord stops further creation and tries to remove what it created; the error lists any known resources that could not be removed. Check Discord before retrying if the outcome is unclear.
From the settings pages
After setup, each of these choices has its own picker on the settings pages, and the picker can create one for you. Open it and click the create row, for example Create a ticket category for me. A line under the picker says exactly what will appear in your server; click Create it and the bot creates it and picks it. Click Save to keep the change. Only the bot owner sees these rows.
| Picker | Row | What it creates |
|---|---|---|
| Staff → Staff roles → Roles | Create staff roles for me | The Ticket Admin and Ticket Support roles (TicketCord Admin and TicketCord Support on the Free plan). Offered only while no staff role is picked |
| Opening tickets → Ticket categories → Categories | Create a ticket category for me | A private 🎫 Tickets category |
| Closing tickets → Closing rules → Move closed tickets to | Create a closed tickets category for me | A private 📁 Closed Tickets category |
| General → Where the bot posts → Transcripts | Create a transcripts channel for me | A private #ticket-transcripts channel |
| General → Where the bot posts → Staff logs | Create a logs channel for me | A private #ticket-logs channel |
- If your server already has one with that name from an earlier setup, it is picked instead of created twice. If it appears while your form is open, creation stops and asks you to reload Discord and select it.
- The two channels go in the 📝 Ticket Logs category. The second one joins the category the first one made instead of creating another.
- If no staff role is picked yet, the staff roles are created along with it, since only your staff and the bot can see what it creates.
- When a picker says the bot cannot use any of your channels or categories, or that the saved one no longer works, the same action appears as a button below that message. On phones it fills the notice width, and the confirmation buttons are stacked below the explanation.
With /setup in Discord
/setup creates the whole set above in one go. The bot needs Manage Channels and Manage Roles at the server level to do this (TC002 otherwise). If the server already has categories, channels, or roles with names like these, it offers Create Anyway (New Names), Use Existing (Recommended), or Cancel; the first option creates a second set with TicketCord-prefixed names. Full details are on the /setup reference.
/setup creates Discord resources only. Nothing is selected in the dashboard for you, and tickets will not open until you pick them in the setup form and save it (Step 2).
Step 2: Save the essentials
Open your server (the server's tile on the dashboard home). Until the server is set up, its home page shows the setup form (Set up tickets for this server): fill it in and click Finish setup. Required fields have a red asterisk after their name; the others say Optional. The guided setup you see on your first sign-in asks for the same choices for a ticket panel.
The setup form starts with How members open tickets:
- Ticket panel: members click a button on a message the bot posts in a channel. The form asks for a Ticket panel name and Ticket categories. Saving turns ModMail off if it was on, so the panel's button opens tickets.
- ModMail: members send the bot a direct message. The form does not ask for a panel name or ticket categories; instead it asks Create ModMail tickets in (optional: left empty, ModMail ticket channels are created at the top of your server, outside any category).
- Saving turns ModMail on, and while it is on, panel buttons, dropdowns, and forms in this server do not open tickets.
- In this mode, Create them for me puts the category it creates in Create ModMail tickets in.
To keep ModMail tickets in a private staff server that members are not in, turn ModMail on there and select your public servers under Also take DMs from: see ModMail From Other Servers.
You can switch later with Members open tickets with on Opening tickets → How members open tickets. The settings pages then show only what the chosen way uses: see Settings that follow ModMail.
In Ticket panel mode, setup also creates the panel named in Ticket panel name (Panel title in the guided setup), or reuses a newer-style panel with that exact name.
Existing and imported panels count toward your plan's limit: 2 on Free, 5 on Basic and Pro, and 15 on Enterprise. If you are at the limit, reuse an existing newer-style panel name or make room before creating another. Reaching the limit leaves your existing panels and saved settings unchanged.
Afterwards, each choice lives on its own settings page, in the sidebar under Settings:
| Where | Setting | What to choose |
|---|---|---|
| Staff → Staff roles | Roles | The Ticket Admin and Ticket Support roles (or your own). Required, up to 10 roles. Members with these roles can use staff commands and see every ticket |
| Staff → Staff roles | Dashboard access | Optional, bot owner only. Roles lists only your staff roles: members with the ones you pick can also open this server's dashboard and change its settings. Removing a role from the staff roles also removes its dashboard access and its Supervisor roles entry. Also allow Manage Server gives the same access to anyone with Discord's Manage Server permission. Let staff read transcripts online (off by default) lets a ticket's staff open its transcript from the View online button after signing in, without any dashboard access |
| Opening tickets → Ticket categories | Categories | The 🎫 Tickets category. Required for panel tickets that open as channels. You can select several; each holds up to 50 channels, and when one is full (or was deleted from Discord) the next one is used. In ModMail mode the block shows Create tickets in instead, the one category for ModMail tickets. With thread tickets it shows a note instead, because threads open in a channel, not a category |
| Closing tickets → Closing rules | Move closed tickets to | The 📁 Closed Tickets category. Optional: leave it empty to keep closed tickets where they are. You can select up to 10; each holds up to 50 channels, and when one is full the next one is used. Shown while After closing is Move the channel |
| General → Where the bot posts | Staff logs | #ticket-logs. Receives ticket events and staff actions, plus everything below it on that block that is left at Same as logs. Required |
| General → Where the bot posts | Transcripts | #ticket-transcripts. Used by /transcript and automatic transcripts. Optional on the settings page: left at Same as logs, transcripts go to the logs channel. The setup form asks for one |
Save (Finish setup on the setup form, or Save changes in the bar at the bottom of a settings page, also Ctrl/⌘ + S), then assign the staff roles to your team in Discord. Run /diagnose in the server to confirm the bot can see every selected channel and category.
Only the bot owner sees and changes the Staff roles block; it is hidden from dashboard staff. Changing staff roles in Discord alone does nothing: the role must be selected here.
Step 3: Post a ticket panel
Ticket panels are messages with buttons or a dropdown. Open Panels → Ticket panels and click New panel (or Edit on a panel you have). In the designer:
- New buttons open a ticket out of the box (their When clicked is Ticket); add a dropdown instead if members should pick a topic first.
- Set When clicked to Form (or Application) to ask questions before the ticket opens: short or paragraph text, file uploads, or a dropdown whose options can each have an emoji.
- To rename a button, click its text in the preview and type, or click the gear on the button and change Label at the top.
Click Save changes when it looks right. To send it, click Post at the top of the designer, pick a channel such as #support, and click Post panel, or run /embed name:<panel name> channel:#support in Discord.
Each button or dropdown option can point at its own ticket category (with thread tickets, its own thread channel) and use its own welcome message, so one panel can serve support, sales, and applications. Panels cannot be posted inside ticket channels.
Changing a button's or option's When clicked to a new Ticket, Form or Application carries its current settings (category, channel name, ping, welcome message, who can open it and which staff roles see its tickets) into the new choice. Switching back to a choice you set up earlier without leaving the designer can bring back that choice's own settings instead, so check them before you save.
A new button's ticket settings start from the server's choices, and each field shows what it uses until you change it:
-
Ticket category shows Server default (category name): your first ticket category, or the next one when it is full. Only the categories selected under Opening tickets → Ticket categories can be picked; add a category there first to use it on a button. A button that still points at another category from before is flagged, and its tickets go to the server default.
-
Once a button has its own category, Add a category for when it's full adds more categories for it (up to 10 in all). A button with its own categories places its tickets in this order:
- Its own categories, in the order listed, moving to the next one when a category holds 50 channels.
- An automatic copy. When all of them are full, TicketCord creates a copy of the button's last category right below it, named after it with a number (Support 2, then Support 3), with exactly the same permissions, and adds it to the button's categories and to your ticket categories. Later tickets use the copy while it has room. Before each ticket is placed in a copy, the copy's permissions are matched to the original again, so a permission change on the original carries over. When a copy's last ticket channel is deleted, TicketCord deletes the empty copy. It only ever deletes copies it made, never a category you created.
- A spare ticket category, one of your ticket categories that no button or option uses, when no copy can be made: the bot lacks Manage Channels, the original's permissions set something the bot does not have itself (a copy is never made with weaker privacy than the original, so then none is made; Discord lets only a bot with Administrator copy a category whose permissions set Manage Roles), or the server has reached Discord's 500-channel limit.
- The full error. If no spare category has room either, the member is told the categories are full (TC019).
Tickets never go to a category another button or option uses, so each ticket type stays in its own place. A button left on Server default uses your ticket categories in order, as before.
-
Ticket channel name shows Server default (example), the name from Opening tickets → New ticket defaults. Type a name to give this button its own.
-
Ping staff, while off, says which ping the server default sends. Turn it on to choose this button's own ping. When the server default pings someone, Ping nobody for this button turns off the ping for this button only, and later escalation pings for its tickets too.
To copy a message you built in Discohook, click Import in the designer and paste its JSON or a share link (see Copying a message from Discohook); its buttons and dropdown options come in as ticket buttons and options, and link buttons stay links.
New panels are always Components V2 panels; a panel made in the old classic designer keeps working and can be converted with Convert and edit in the designer.
Panel limits
- Panel limits by plan: 2 on Free, 5 on Basic and Pro, 15 on Enterprise.
- Panel names cannot contain a dot (
.) or a dollar sign ($). - All the text in one panel can be at most 4,000 characters, including its footer and TicketCord branding (the counter under the preview shows how much is used).
- A panel can also hold at most 40 components, counting every container, block, button row, button, and dropdown, as Discord does.
Within those two limits (characters and components) you can add as many containers, blocks, and buttons as you like.
Saving, renaming, and deleting panels
- You can keep editing while a save is in progress; changes made after you start saving remain unsaved.
- Leaving the designer through dashboard navigation asks you to confirm before discarding an unsaved draft.
- To rename a panel, open the ⋯ menu on its card and click Rename. Panels you already posted keep working, and
/embeduses the new name from then on. Two panels cannot share a name, even with different capital letters. - Deleting a panel does not remove the messages you already posted; their buttons stop working, so delete those messages in Discord too.
If the panel is saved somewhere else while you have it open (by another staff member, by you in another tab, or by importing another server's settings), your save is stopped instead of overwriting that change: click Reload latest version to open the newest version, then make your change again. Unsaved edits in the stopped tab are lost.
Step 4: Tune the ticket lifecycle
These live on the Opening tickets, Staff, Closing tickets, and General settings pages of the server, one block under the other.
| Where (page → block) | Setting | Effect | Plan |
|---|---|---|---|
| Opening tickets → Ticket options | Ticket limits → Open at the same time | How many tickets one member may have open at once, up to 50 (empty means no limit). On Free it is 1 to 5 (empty means 5); higher limits need Basic. For Total, including closed (Basic+), see below the table | Free: 1 to 5. Basic+: up to 50 |
| Staff → Claiming | Exclusive claims | When a staff member claims a ticket, the rest of the team loses access until it is unclaimed. Channel tickets only: thread tickets keep every staff member, and ModMail tickets are not affected | All |
| Staff → Claiming | Supervisor roles | Members with these staff roles keep access to exclusively claimed tickets and cannot be removed with /remove | All |
| Staff → Claiming | Claim mark in channel names | Claimed tickets get a 👤 in front of their channel name, so staff see in the channel list which tickets are still unclaimed. Off by default. See Channel name markers | All |
| Staff → Claiming | Auto-unclaim | Release a claim when the member has waited too long for a staff reply, so another staff member can take the ticket. 15 minutes to 30 days. Off by default. See Auto-unclaim | Basic+ |
| Opening tickets → New ticket defaults | Channel name | How new ticket channels are named, for every panel button without its own Ticket channel name and for ModMail. See New ticket defaults | All |
| Opening tickets → New ticket defaults | Who gets pinged | Nobody, Staff roles, or Chosen roles when a ticket opens, for every panel button without its own ping and for ModMail. Nobody only skips the ping when a ticket opens | All |
| Closing tickets → Closing rules | Only staff can close | Members cannot close their own tickets, in ticket channels or in ModMail DMs, and Atlas does not close tickets for members. Panels and ModMail each keep their own setting: the switch changes the one for the mode your server uses, so check it again after switching modes | All |
| Closing tickets → Closing rules | Close without asking first | /close and the close button act immediately without a confirmation card | All |
| Closing tickets → Closing rules | After closing | Move the channel (to Move closed tickets to, or left where it is when that is empty) or Delete the channel. Deleting skips the move, so Move closed tickets to is hidden then | All |
| Closing tickets → Closing rules | Message the member | The member gets a DM when their ticket closes. Change its wording on Messages | All |
| Closing tickets → Transcripts | Transcripts (card switch) | Every close posts a transcript, whether the channel is kept or deleted; when the channel is deleted, the transcript is posted first. Post transcripts in shows where it goes (the logs channel while it is Same as logs) and links to General → Where the bot posts, where you change it | All |
| Closing tickets → Transcripts | Also send it to the member | Attaches the transcript to the DM the member gets when the ticket closes. Needs Message the member | All |
| Closing tickets → Auto-close and reminders | Auto-close | Close tickets after a period with no messages. 15 minutes to 30 days; also settable with /auto-close | Basic+ |
| Closing tickets → Auto-close and reminders | Reminders | Post a reminder in quiet tickets before they auto-close, optionally mentioning the creator. Change its wording on Messages (Inactivity reminder) | Basic+ |
| Closing tickets → Auto-close and reminders | Also close when the member leaves | Close a member's open tickets when they leave the server. It is a switch inside the Auto-close card, so it shows while auto-close is on | Basic+ |
| Closing tickets → Auto-close and reminders | Pause on closed days | On by default. While business hours say you are closed, auto-close, reminders and Auto-unclaim wait and run once you open. See Pause on closed days | Enterprise |
| Closing tickets → Ratings | Ratings (card switch) | Ask creators for a 1 to 5 rating when tickets close and via /feedback | All |
| Staff → Tags | Suggested tags and Tags per ticket | Suggestions for /tag add; limit 10 by default, 1 to 25 | All |
| General → Privacy and data | Keep closed tickets for | How long TicketCord keeps a closed ticket's saved messages, file links, transcript links, what Atlas learned from it, and the member memory facts that came only from it. Copies in Discord and downloaded transcripts stay | All (up to 90 days on Free) |
In Ticket limits, Total, including closed caps every ticket a member has had in the server (deleted tickets do not count): 0 or empty means no limit, otherwise 5 to 200 and not below the open limit.
The other pages cover Panels (ticket panels) or, in ModMail mode, ModMail, Messages (the wording of everything the bot sends), Staff (also quick replies, response targets, and approvals), Opening tickets (also how members open tickets and who can open them), AI assistant, Email inbox and Website widget (bot owner only, Pro or Enterprise), and General (where the bot posts, business hours, bot language, privacy and data, game accounts, webhooks, scheduled reports). Business hours, response targets, approvals, webhooks, and scheduled reports need Enterprise.
New ticket defaults
Opening tickets → New ticket defaults sets how a new ticket's channel is named and who is pinged when it opens. Every panel button and dropdown option uses it unless you give that button its own Ticket channel name or Ping staff in the designer; ModMail tickets always use it.
Go to Opening tickets → New ticket defaults| Setting | Values |
|---|---|
| Channel name | username-1234 (name and number), username (name only), ticket-1234 (ticket and number), 1234-username (number first), or 1234 (number only) |
| Who gets pinged | Nobody, Staff roles (every role under Staff → Staff roles), or Chosen roles (pick at least one under Roles to ping) |
A server that never saved this block keeps what it did before: panel tickets are named like ticket-0042 and are pinged only by buttons that have their own ping, and ModMail keeps its earlier name format and ping roles.
How each name looks for member john-doe and ticket number 42:
| Channel name | Panel ticket | ModMail ticket |
|---|---|---|
username-1234 | john-doe-42 | john-doe-42 |
username | john-doe | john-doe |
ticket-1234 | ticket-0042 | ticket-42 |
1234-username | 42-john-doe | 42-john-doe |
1234 | 42 | 42 |
About the ping:
- Nobody means nobody is pinged when a ticket opens. Later escalation pings in that ticket, such as when Atlas hands the ticket to staff, still go to your staff roles, as on a server that never set a default. Only a button's Ping nobody for this button (offered while the server default pings someone) also turns those off for its tickets.
- With Chosen roles, roles that no longer exist in Discord are skipped; if none are left, nobody is pinged.
- Outside business hours the ping when a ticket opens is skipped.
- In ModMail, the same roles are pinged by the staff reminder while no staff member has claimed the ticket or replied to it (the ModMail reminders card on ModMail → ModMail). After the last reminder, it also pings Roles to ping when reminders run out from that card.
Channel name markers
The bot shows a ticket's state in front of its channel name, so staff can read it in the channel list without opening the ticket.
| Marker | Meaning | Set by |
|---|---|---|
| 📌 | Pinned | The Pin button on the welcome message |
| 👤 | Claimed | Claiming the ticket, when Claim mark in channel names is on |
| 🔴 🟠 🟡 🟢 | Urgent, High, Medium, or Low priority | /priority, Priority support, or Automatic priority |
The markers always appear in this order: pin, claim, priority. A ticket with one marker reads 👤-ticket-0042. With more than one they are grouped in front of a single hyphen, for example 📌👤🔴-ticket-0042, whichever was set first. /rename changes the name and keeps the markers, and a reopened ticket gets its pin and claim markers back.
Claim mark in channel names is off by default. Turn it on under Staff → Claiming:
Go to Staff → Claiming- A ticket gets the 👤 when it is claimed and loses it when it is unclaimed or handed to another team. Tickets without the mark are unclaimed.
- It works for channel tickets, thread tickets, and ModMail tickets, and it does not change who can see a ticket. To hide claimed tickets from the rest of the team instead, use Exclusive claims.
- Turning it on does not rename tickets that are already claimed: each one gets the mark the next time its claim, pin, or priority changes. After you turn it off, a mark already on a channel can stay until that ticket is closed.
- Nothing is posted in the ticket when the name changes.
Discord allows two renames per channel every 10 minutes. When a ticket has used both, a pin, a claim mark, or an automatic priority emoji is not lost: the bot updates the name on its own once the limit resets, so a marker can lag a few minutes behind. /priority and /rename ask you to try again instead (TC001).
Auto-unclaim
A claimed ticket can sit unanswered when the staff member who claimed it is away. Auto-unclaim releases such a claim on its own, so the ticket is free for the rest of the team again. It needs Basic or higher and is off by default. Turn it on under Staff → Claiming:
Go to Staff → Claiming- Release after is how long the member may wait: 15 minutes to 30 days, entered in minutes (1440 is 24 hours, the value it starts with).
- The wait is counted from the member's last message that no staff member has answered, or from the claim if the ticket was claimed after that message. A ticket that was claimed and never answered counts from the claim. A ticket that was closed and reopened starts counting again at the reopen.
- A reply from any staff member answers the ticket, not only a reply from the member who claimed it. Messages from the bot and from Atlas do not count as staff replies. A server owner or administrator without a staff role counts when they reply in a ticket they claimed themselves.
- When the time is up, the claim is removed exactly as with
/unclaim: the claim card is deleted, the Unclaim button turns back into Claim, the 👤 claim mark leaves the channel name, and with Exclusive claims on the rest of the team gets its access back. The bot posts Claim released in the ticket, mentioning the staff member who had it and saying how long nobody replied. Change its wording on Messages under In a ticket. - Also release when the member goes quiet (off by default) covers the opposite case: staff replied last and the member has not answered for the same time. The claim is released then too, so whoever is around can pick the ticket up when the member comes back.
- Claims are checked every 5 minutes, so a release can come up to 5 minutes after the time is up. A ticket with a message in the last 30 seconds is looked at again half a minute later.
- It works for channel tickets, thread tickets, and ModMail tickets. A ticket that is waiting for another team to accept a transfer keeps its claim.
- On Enterprise, while business hours say you are closed and Pause on closed days is on for auto-close, no claim is released. The wait keeps counting, so claims that are due are released when you open.
- Turning it on applies to tickets that are already claimed: claims that have waited longer than your time are released at the next check.
- Released tickets show up in
/unclaimedand under Filters → Claimed by → Nobody yet on the Tickets page. On the Stats page they count as handoffs released automatically for the staff member who had the claim. Releases after the member went quiet are not counted as handoffs. - With compensation reports that credit the claimer, a ticket is credited to whoever holds the claim when it closes. A staff member whose claim was released is no longer that person unless they claim the ticket again.
What happens once configured
- A member presses the panel button (or picks a dropdown option, or fills in the form if one is attached).
- The bot checks the firewall, the button's Who can open this rule, business hours, and the member's open ticket count, then creates the ticket channel (named by the button's Ticket channel name, else by New ticket defaults,
ticket-0042unless you change it) in the ticket category with permissions for the creator, staff roles, and the bot. - The welcome message is posted, the button's ping (or the New ticket defaults ping) is sent, and the logs channel records the event.
- Staff work the ticket with the commands. When it closes, the channel is renamed
closed-XXXXand moved (or deleted), the transcript is posted, the creator is DMed if Message the member is on, and feedback is requested if enabled.
If Transcripts is on but there is neither a transcripts channel nor a logs channel, the transcript cannot be posted anywhere. The close then counts as a failed transcript: a channel set to be deleted is kept instead, so the conversation is not lost. Set a logs channel under General → Where the bot posts to fix it.
A panel button or dropdown option can have its own rule for which roles may use it, while the other buttons keep working, for example so a role cannot open Pre-sale tickets but can still open Support ones. Click it in the designer and turn on Who can open this (for a form or application, it is under Ticket settings), then pick a rule and the roles:
- Block selected roles: a member who holds any one of the roles cannot open a ticket with it.
- Only selected roles: only members who hold at least one of the roles can open a ticket with it.
A member who is turned away gets a TC002 error instead of a ticket, before a form opens; the bot checks again when a form or application is sent. The rule is available on every plan, only the bot owner can change it, and @everyone cannot be picked. It works alongside Opening tickets → Who can open tickets, which still applies to every button.
Deleted roles and categories
Deleting a role or a category in Discord does not change your settings: a setting that named it keeps pointing at it. The bot owner sees a notice on your server's home page when that happens. It counts the settings affected and sorts them in two groups:
- Safe to remove. The setting has other roles or categories left, or it works the same with none (a list of blocked roles, for example). Remove them takes the deleted ones out of all of these settings in one click, panels included. Nothing else is changed.
- Needs a replacement. The deleted role or category was the setting's only one, or the last one left. The notice links to each of these settings so you can pick a new one. They are never emptied for you: a button whose staff roles are all gone stays closed to staff rather than opening to every staff role.
The notice reads your server's current roles and categories from Discord, and shows nothing when Discord cannot be reached or when the bot is offline.
When every staff role of the server, or every staff role picked for a panel button or form, has been deleted, staff cannot see its new tickets. The bot then posts a warning in your logs channel (TC004), not for every ticket: normally once every 6 hours for the same roles, and only if a logs channel is set.
Thread tickets
With thread tickets, the bot opens a thread instead of a channel. Choose Thread under Each ticket is a on Opening tickets → How members open tickets; a Thread tickets card then appears in Opening tickets → Ticket options, where you pick the channel the threads open in. Thread tickets do not use ticket categories.
A panel button or dropdown option can send its tickets to a different channel: click it in the designer and pick a channel in Thread channel (for a form or application, it is under Ticket settings). It takes the place of Ticket category while thread tickets are on.
- Private threads need a text channel; public threads can also open in an announcement channel.
- If the button's channel is deleted or the bot cannot create threads there, its tickets open in the server's thread channel instead.
Discord only shows a private thread to people who are in it and to members with Manage Threads in the channel it is in; threads cannot have role permissions of their own.
For thread tickets to work best, give each staff role View Channel, Read Message History, Send Messages in Threads and Manage Threads in every channel tickets open in. Those roles then see every ticket in the channel, including tickets opened before someone got the role.
Manage Threads also lets them archive, lock or delete any thread in that channel. Public threads can be seen by anyone who can see the channel, so for them the first three permissions are enough.
With private threads, the member who opens a ticket must be able to see the channel to see their thread. If they cannot, the bot gives them their own access to that channel (View Channel, Read Message History and Send Messages in Threads, with Send Messages, Create Threads and Manage Threads denied), the same way a channel ticket gives its opener access.
They still see only the private threads they were added to, never other members' tickets, and the access is removed when their last open ticket there closes. Any permissions you had set for that member in the channel before (for example a block or a mute) are put back then. This needs the bot's Manage Permissions in that channel, and because it gives members access, only the bot owner can choose the thread channel, for the server or for a panel button.
To avoid giving each member their own access, let your member role (or @everyone) see the channel instead: allow View Channel, Read Message History and Send Messages in Threads, and deny Send Messages, Create Public Threads and Create Private Threads. Members still see only the private threads they are in, and nobody can post in the channel itself. Keep the channel for ticket threads only, because anyone who can see it can read messages posted directly in it.
Taking that access away later, for example by syncing the channel's permissions with its category, hides open tickets from the members who opened them until they open a new one.
With public threads the bot does not do this, because anyone who can see the channel can read every public thread in it: a member who cannot see the channel is told so and no ticket is opened.
In the Thread tickets card, Staff access lists each of those channels (the server's thread channel and any button's own) with the staff roles that still lack this access. The bot owner can click Give access to have the bot set it, which needs the bot's Manage Roles and those permissions in that channel.
It also warns when:
- Your members cannot see the channel (private threads), so each member who opens a ticket gets their own access, with how many have it now. If the bot is also not allowed to give that access (it needs Manage Permissions there, and every permission it hands out), members cannot open tickets in that channel at all.
- Such a hidden channel has messages of its own, which every member given access can read.
- A staff role has 100 or more members, or the bot may not mention it, so new tickets do not ping it, and unless the role can see every ticket in the channel, adding its members is slow.
Give access is not offered in a channel where a button's Allowed staff roles share the channel with other tickets, because Manage Threads would show every ticket there to every listed role; give that button its own thread channel first.
The bot always adds the ticket's creator. For your staff roles (or the button's Allowed staff roles when the button sets them):
- When the ticket's staff ping (the button's own, or New ticket defaults) pings a role, the bot mentions it in a short line at the top of the new ticket, including roles that have Manage Threads, so the ticket shows up in their channel list. Discord then adds all of the role's members at once and pings them. A role the ping does not cover is not mentioned: that is every role when the ping is off or the ticket opens outside business hours, and every role you did not choose with Roles I choose.
- Discord only adds members this way for a role of fewer than 100 members that the bot may mention: the role allows anyone to mention it, or the bot has Mention @everyone, @here and All Roles in the channel. For any other role that cannot already see every ticket in the channel (through Manage Threads in a private thread channel, or by seeing a public one), including one that is not pinged, the bot adds the members one by one, without a ping, which in a large server can take a few minutes after the thread opens. A role that already sees every ticket and is not mentioned is neither pinged nor added, but still sees every ticket.
- Members who are given a role without Manage Threads later are added to every open ticket the role can see. With many open tickets this can take a few minutes, because Discord limits how fast members can be added.
- Members who lose that role are taken out of the open tickets the bot added them to, unless they still have another of the roles the ticket was opened for, or Manage Threads in its channel. Members you added with
/addstay.
A button's Allowed staff roles cannot hide a ticket from a role that has Manage Threads in its channel, so give a team that should only see some tickets its own thread channel.
Mentioning a role in a private thread adds its members to the thread, so every staff ping the bot sends in a private thread only mentions roles that may see the ticket: the button's Allowed staff roles, otherwise your staff roles. This covers the ping in a new ticket and later ones, such as Talk to Staff, Atlas handing the ticket over, a member asking for a human, and the staff ping from Ask for details. An approval request from /approval still mentions your Approver role, which adds its members so they can approve. A role chosen with Roles I choose outside them is not mentioned there. To ping it in private thread tickets, add it to the button's Allowed staff roles when the button sets them, otherwise to your staff roles. The button's staff ping setting warns about such roles. A role already mentioned at the top of the ticket is not pinged a second time.
A public thread can be read by everyone who can see its channel, so removing someone from it or closing the ticket does not hide it from them; use private threads to keep tickets between the member and your staff.
With Archive when the ticket closes on, a closed thread is archived and locked, so nobody can post in it until it is reopened (without the bot's Manage Threads permission it is only archived). Exclusive claims do not apply to thread tickets.
Deleting a thread ticket needs the bot's Manage Threads permission in its thread channel. Without it, deleting from the dashboard or with the Delete button archives the thread instead, the ticket stays closed, and the bot says it needs Manage Threads; /purge leaves those threads in place and counts them in its results. Give the bot Manage Threads in that channel, then delete again. /diagnose warns when it is missing.
Quick changes from Discord
/config opens a panel where administrators and staff can change the transcript and logs channels and ticket categories, and toggle auto-close, DM on close (the same setting as Message the member), and auto-delete without opening the dashboard. Turning auto-close on there sets it to 1 day (1,440 minutes); change the time with /auto-close or in the dashboard. Staff roles can be changed there only by the bot owner or the Discord server owner. Everything else is dashboard-only. See /config.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| "This server hasn't been set up yet" (TC011) | The essentials were never saved | Open your server and complete its setup form (staff roles, categories, and channels) |
| Button pressed, no ticket, TC002 | The bot lacks View Channel, Manage Channels, Manage Permissions, Send Messages, or Embed Links in the ticket category | Fix the category permission overwrites for the bot's role, then run /diagnose |
| "The ticket category was deleted" (TC004) | None of the selected categories exists any more | Select another under Opening tickets → Ticket categories |
| "The ticket categories for this ticket type are full" (TC019) | Every category of that button or option is full, no copy could be made, and every spare ticket category holds 50 channels | Give the bot Manage Channels and the permissions the category's overwrites set, so it can copy the category (a category whose permissions set Manage Roles needs Administrator); or set After closing to Delete the channel, close old tickets, add another category to the button, or add a ticket category no button uses |
| Staff cannot see tickets | Their role is not selected under Staff → Staff roles | Select it and save; the change applies to new and existing tickets |
| Staff cannot see new tickets, and the logs channel shows a TC004 warning about deleted staff roles | Every staff role of the server, or of the panel button or form, was deleted in Discord | Pick new staff roles under Staff → Staff roles, or for that button or form in the panel designer. The notice on your server's home page links to the right place, see Deleted roles and categories |
/transcript says no transcript channel is configured (TC011) | The server has neither a transcripts channel nor a logs channel | Select a channel for Staff logs (or Transcripts) under General → Where the bot posts |
| A closed ticket was kept even though After closing is Delete the channel | Transcripts is on and the transcript failed, for example because there is neither a transcripts channel nor a logs channel. TicketCord keeps the channel rather than lose the conversation | Set a logs channel under General → Where the bot posts, and check the bot can post there |
Common questions
Do I have to use the roles and categories TicketCord creates?
No. Any category or role works. Creating them (with Create them for me or /setup) just saves you the work; select whatever you want under Staff → Staff roles and Opening tickets → Ticket categories.
Can I have separate categories for support and sales tickets? Yes. Select several ticket categories under Opening tickets → Ticket categories, then point each panel button or dropdown option at the category it should use.
Why can members open only five tickets? Five open tickets per member is the most the Free plan allows (you can lower it). From Basic you can set any limit for Open at the same time under Opening tickets → Ticket options.
Where do I set who is allowed to close tickets?
Closing tickets → Closing rules → Only staff can close. When it is on, creators can still request closure through staff, and staff can send a close request with /closerequest.
Does changing a setting affect tickets that are already open? Yes for permissions and staff roles. Auto-close and reminders apply to open tickets from the next inactivity check onward. New ticket defaults apply to tickets opened after you save.
How do I move the bot to a different transcript channel later?
Change Transcripts under General → Where the bot posts, or press Change next to the transcript channel in /config. Leave it at Same as logs to post transcripts in the logs channel. Existing transcripts stay where they were posted.
How do I stop pinging staff on every new ticket? Set Who gets pinged to Nobody under Opening tickets → New ticket defaults. Buttons that have their own Ping staff turned on keep pinging; open them in the designer to change them. Nobody does not turn off later escalation pings, such as when Atlas hands a ticket to staff; those still go to your staff roles.
First category, panel, and staff roles, step by step in the help center
Join the support Discord and ask the team
Was this page helpful?
Last updated on