Bot Management

Add your Discord bots to TicketCord, keep them online, customise their status and footer, and disconnect them safely

Your bots in the dashboard sidebar lists the custom Discord bots you have connected to TicketCord. Each bot is your own Discord application, running under TicketCord's management, and can serve several servers. Every bot has two pages:

  • its dashboard (ticket numbers, a daily chart, recent tickets and activity, and its servers);
  • its Bot profile, where you change its name, picture, and banner, restart it, update a revoked token, set its activity status and message footer, and disconnect it from TicketCord.

It is for bot owners; dashboard staff work with servers and tickets, not bots.

The number of bots you can run depends on your plan: Free 1, Basic 3, Pro 3, Enterprise 6. The 14-day signup trial allows 1 bot. Bots above the limit are stopped with the Plan limited status until you upgrade or disconnect a bot.

Go to Your bots Go to Add a bot

Adding a bot

The first time you sign in, the guided setup adds your first bot for you. To add another bot later:

Create the application in Discord

In the Discord Developer Portal, create an application, add a bot, and copy its token. TicketCord turns on the Server Members Intent and Message Content Intent for you during the token check, and blocks adding the bot if Discord refuses (then turn them on yourself and check again). See Installation.

Click Add a bot

Go to Add a bot, under Your bots in the sidebar. The page shows three steps, Paste your token, Check your bot, and Done, with a short How to get your bot token guide. Paste the token into Bot token. Tokens are up to 200 characters.

Check the token

Click Continue. TicketCord checks the token with Discord and reads the bot's name, ID, and client ID; you never type those. If the check fails, the page says why:

  • "Discord did not accept this token." for a wrong, reset, or mistyped token;
  • "Turn on Server Members Intent and Message Content Intent" when the intents are off and TicketCord could not turn them on;
  • "This bot is already in your account." when you added it before.

Only "Unable to verify bot status. Please try again." means Discord could not be reached, so trying again can help.

Confirm

Is this your bot? shows the bot's name and picture. If they look right, click Add this bot. The token is encrypted before it is stored and is never shown again.

Invite it to a server

The last step lists the Discord servers you can add the bot to, each with Invite. Later, open the bot under Your bots and use Invite to a server, or use the Add TicketCord to another server tile on the dashboard home.

The invite link requests the ticket-related permissions the bot needs (channels, threads, roles, pins, webhooks) and, since October 2026, Administrator, so the bot works whatever your channel permissions are; you can untick it in Discord. See Why the invite asks for Administrator.

If the bot is added but Discord does not let it start, the last step says "Bot name needs attention": the credentials are saved and you can retry from the bot's Bot profile page.

Bot status

The status pill on each bot means:

StatusMeaningWhat to do
OnlineConnected to DiscordNothing
ConnectingStarting up, restarting after a TicketCord update, or reconnecting because Discord asked it toWait a moment; it comes back on its own
OfflineStoppedClick Start on the bot's Bot profile page
ErrorFailed to startFix the cause (often intents or a revoked token) and click Restart on the Bot profile page
Token invalidDiscord rejected the tokenClick Update token on the Bot profile page
Plan limitedStopped because you have more bots than your plan allowsUpgrade or disconnect a bot
BannedDisabled by TicketCordContact support
Disconnect incompleteA disconnect did not finishDisconnect the bot again

TicketCord emails the bot's owner once, in the language of their account, when Discord rejects a bot's token, when Discord refuses its login because the privileged intents are off, or when the plan's bot limit stops it. A bot can't message you once it is offline, so the email is how you find out when you aren't on the dashboard. It goes to the email on your TicketCord account; an account without one gets no email.

Open a bot under Your bots to see its dashboard. It is the same dashboard as each server's home page, counted across every server the bot is in:

  • Welcome back, (your name). with "Here's what's happening with (bot) today." under it, and the Bot profile button (bot owner only).
  • A status line only when something needs attention: "Bot name is connecting. Tickets work again in a moment." or "Bot name is offline. Members can't open tickets until it's back.", with the fix for the bot owner (start it again, update its token, or open its Bot profile).
  • Four numbers: Total tickets (every ticket the bot has had), New today (since midnight in your time zone), Active tickets (open right now), and Typical first reply (the median time to the first staff reply for tickets opened in the last 30 days: half were answered faster; No replies yet when staff have not replied, Under a minute when it is shorter than that).
  • Ticket activity: tickets opened and closed per day over the last 7, 14, or 30 days, drawn even when there were none.
  • Recent tickets: the six tickets that moved last, with View all (this bot's tickets), and Recent activity: what happened in the last 24 hours.
  • Servers: a tile for each server the bot is in, plus Add (bot) to another server for the bot owner.
  • Quick access: knowledge base settings, this bot's Bot profile, and its stats.

The numbers and the chart need the Basic plan or higher; on Free a Ticket numbers card with the plan badge takes their place. A bot that is in no server yet shows Invite (bot) to a server. instead of the dashboard.

Bot profile

Open a bot and click Bot profile (inside a server, the bot owner also finds Bot profile at the end of the sidebar). The page starts with Name, picture and banner and the bot's Bot ID. Staff with access to one of the bot's servers see the name and picture; only the bot owner can change them. Changes go straight to Discord and show in every server the bot is in:

  • Picture and banner: click Change picture or Change banner and pick a PNG, JPEG, or GIF image of up to 6 MB (a GIF stays animated). It applies as soon as you pick it. Remove picture and Remove banner take the image off.
  • Name: type the new name (2 to 32 characters) and click Save name. Discord limits how often a bot can change its name and refuses some words, such as "discord" and "everyone"; the page says so when Discord turns a name down or asks you to wait.
  • TicketCord accepts up to four profile changes per bot every two minutes. They cannot be made while the bot's token has stopped working: update the token first.
  • The bot's About Me and other application details are still set in the Discord Developer Portal, linked under the card.

Below are the bot's settings, which apply in every server the bot is in:

Go to Bot profile → Status Go to Bot profile → Footer
SettingAllowed valuesDefaultPlan
Status (card switch), TypePlaying, Watching, Listening to, Competing inPlayingBasic+
Status, Textup to 128 charactersPowered by TicketCord.comBasic+
Footer (card switch), Footer textup to 2,048 characters of footer textnoneEnterprise

Notes on branding:

  • Free bots always show the activity Playing Powered by TicketCord.com and the TicketCord footer on embeds.
  • Basic and Pro can set their own activity and remove the TicketCord footer (embeds then have no footer unless a custom one is allowed by the plan).
  • Enterprise can also set custom footer text.

Save with Save changes in the bar at the bottom of the page. Changes apply live without a restart.

  • You can save up to 4 times per 2 minutes; beyond that the dashboard reports "Rate limit exceeded" and tells you when to retry.
  • Saving with nothing changed returns "Settings have not changed."
  • While the token is invalid or the bot is in Error, saving is blocked until you update the token or restart the bot.

If TicketCord temporarily cannot verify your sign-in, an already-open status or footer draft stays in place. Saving and bot actions are unavailable until your session recovers. Confirmed sign-out or loss of access still closes the editor.

Keeping a bot online

  • Restart: at the top of the Bot profile page. Bots also restart automatically after token updates and plan changes.
  • Start: replaces Restart for an Offline bot.
  • Fix commands: next to Restart. Puts TicketCord's slash commands back after another program using the same token replaced them; see Fixing missing slash commands.
  • Update token: shown at the top of the Bot profile page when a bot is Token invalid. It opens a page, valid for 10 minutes, where you paste the new token, click Continue, then Save new token; the bot restarts with it. The option is only available when the current token is actually invalid; otherwise the dashboard says "This bot already has valid credentials and doesn't need an update."

Bots with no activity

A bot on the Free plan is stopped once it has gone 90 days with no activity. Activity means a ticket message, a ModMail message, a slash command, or a press of one of the bot's buttons; ordinary chat in your server does not count.

After those 90 days TicketCord emails you, and the bot goes offline at least 7 days later. Using the bot, or clicking Restart on its Bot profile page, cancels the stop. If it does stop, you get a second email and the bot shows as Offline. Click Start on the Bot profile page to bring it back; nothing is deleted. If another bot now uses your plan's only slot, stop that one first.

Bots on a paid plan are never stopped this way, including while the subscription is paused or a payment is being retried. Neither are bots whose owner has no email on their account, because the warning could not reach them.

Fixing missing slash commands

If the bot's slash commands are missing, or Discord shows commands that are not TicketCord's (for example /blacklist or /bypass), another program or bot host is running with the same bot token and has replaced TicketCord's commands with its own.

Stop the other program

TicketCord must be the only thing running with this token, or the other program replaces the commands again. If you don't know what else uses it, click Reset Token on the Bot tab in the Discord Developer Portal. The bot then shows Token invalid; click Update token and paste the new token.

Choose Fix commands

Click Fix commands at the top of the Bot profile page, next to Restart. It is also in the ⋯ menu on the bot's tile under Your bots. Read the dialog and click Fix commands.

Reload Discord

TicketCord checks which commands Discord has for the bot, puts its own back, and removes the other program's. Press Ctrl+R (Cmd+R on Mac) in Discord to see them.

If nothing was missing, the dashboard says the bot already has all of TicketCord's commands. Fix commands is not offered while the bot is Token invalid, and it can run 3 times per bot per hour.

Moving your setup to another bot

To replace a bot application but keep your setup:

  1. Add the new bot and invite it to the same servers.
  2. Open each server under the new bot and click ⋯ next to the server name on its home page.
  3. Choose Import settings from another server, and pick the same server under the old bot.

This works before you have run the server's setup, and the setup keeps the imported settings.

Behaviour settings, embeds, and canned responses are copied. Roles, channels, and categories are cleared and must be chosen again, knowledge base sources need a refresh, and webhooks and status page connections are not copied. Thread tickets and approvals stay off until you choose their channel and roles again. The dialog lists exactly what was copied. The old bot keeps its own configuration until you disconnect it. The website widget is not copied: set it up again under the new bot and put its new install code on your website.

Also allow Manage Server, Let staff read transcripts online and Search past Discord conversations are only copied between bots on the same server. Importing from a different server keeps that server's own Also allow Manage Server and Let staff read transcripts online choices and leaves Discord search off until you turn it on there.

Disconnecting a bot

Disconnecting removes a bot from TicketCord. It does not delete the bot from Discord: the application stays in your Discord Developer Portal, and you can add it to TicketCord again later, starting fresh. You can also disconnect a bot from the ⋯ menu on its tile under Your bots.

Choose Disconnect

Go to Bot profile → Disconnect bot. The card at the bottom of the page says what is removed. Click Disconnect.

Type the bot's name

The dialog Disconnect BotName lists what is removed. Type the bot name exactly to confirm; a mismatch returns "Bot name confirmation does not match".

Disconnect

Click Disconnect bot. The bot leaves every Discord server it is in, and TicketCord permanently deletes everything attached to it: tickets, knowledge base, analytics, embeds, and server configurations. If Discord no longer accepts the bot's token, the bot cannot leave on its own: TicketCord still disconnects it, and you remove it from your servers in Discord.

Disconnecting deletes the bot's TicketCord data, not just its connection. Export any tickets you need first from Tickets, and copy the setup to another bot with Import settings from another server if you want to keep it.

Limits and gotchas

  • A Discord bot can be registered with one TicketCord account at a time. Adding a bot that another account already registered fails with "Another TicketCord account already added this bot."; the other account must disconnect it first.
  • Tokens are never displayed after creation. If you lose a token, reset it in the Discord Developer Portal and use Update token once the bot shows Token invalid.
  • The privileged intents are required. Without Server Members Intent and Message Content Intent the bot fails to connect (Discord gateway error 4014) and shows Error. TicketCord tries once to turn them on, but Discord does not allow that for a bot whose servers have more than 10,000 members together until it approves the intents: the bot's notice then says so and offers Open Developer Portal. Apply for both intents there, turn them on once Discord approves, then click Restart. TicketCord cannot run without them. For help with Discord's form, open a ticket in our support Discord: we send you answers you can mostly copy and paste, and mark the few details only you can fill in.
  • Adding a bot counts all your bots, online or not. Starting or restarting one counts only the bots that can run: a bot marked Token invalid or Banned, or one you stopped yourself, does not use a place, and the oldest bots get the places first. Downgrading below your bot count marks the extra bots Plan limited until you disconnect some.
  • Only the bot owner can change a bot. Dashboard staff who open its Bot profile page see "Only the owner can change this bot." with a Back to the bot button.

Troubleshooting

SymptomCauseFix
"Discord did not accept this token."The pasted value is not a working bot token (a client secret, a mistyped token, or one that was reset since)Click Reset Token on the Bot tab in the Developer Portal and paste the new token
"Turn on Server Members Intent and Message Content Intent"The privileged intents are off and TicketCord could not turn them onTurn both on, save, and click Continue again
"This bot is still being disconnected."An earlier disconnect of this bot did not finishClick Disconnect again on its tile under Your bots, then add it
"Bot limit reached" when adding a botYou are at your plan's bot limitDisconnect a bot or upgrade at ticketcord.com/pricing
Status stuck on Error, saying the Server Members and Message Content intents are offPrivileged intents are off (Discord gateway error 4014)Click Open Developer Portal, turn them on, and click Restart on the Bot profile page
Error saying the bot's servers have more than 10,000 members together, so Discord has to approve the intentsDiscord must approve privileged intents for such a bot before they can be turned onClick Open Developer Portal, apply for both intents (open a ticket in our support Discord for answers to Discord's form), turn them on once approved, then click Restart on the Bot profile page
Token invalid after you reset the token in DiscordThe old token was revokedClick Update token and paste the new token
Update token is missingThe current token still worksNothing to update; restart instead
The update link says "This update link is invalid or has expired"Links last 10 minutesClick Update token again for a new one
"Rate limit exceeded. You can update each bot setting 4 times every 2 minutes." or "Rate limit exceeded. Limit is 4 requests per 2 minutes."More than 4 status or footer saves in 2 minutesWait the time the message gives, then save again
"Settings have not changed. No update needed."You saved without changing anythingChange a value first
Custom status reverts to Playing Powered by TicketCord.comThe plan is FreeCustom status needs Basic or higher
Custom footer text is cleared on saveThe plan is not EnterpriseCustom footer text needs Enterprise; Basic and Pro can only remove the footer
Disconnect incomplete on a botA disconnect was interruptedClick Disconnect again on its tile under Your bots
Slash commands are missing, or commands that are not TicketCord's appearAnother program is running with the same bot tokenStop it (or reset the token), then use Fix commands
Invite says "Detection timed out"Discord took too long to report the joinRefresh the page; the server appears once the bot is in it

Common questions

How many bots can I add? 1 on Free, 3 on Basic and Pro, 6 on Enterprise, and 1 during the signup trial.

Can I see my bot token again? No. It is encrypted at creation and never shown. Reset it in the Discord Developer Portal if you need a new one, then use Update token on the bot's Bot profile page.

What does Plan limited mean? You have more bots than your plan allows, so the extra ones are stopped. Disconnect a bot or upgrade, and the bot starts again.

Do I have to restart the bot after changing settings? No for bot status, footer, and server configuration; they apply live. Restart only when a bot is in Error or after fixing intents.

Can I change the bot's name or avatar in TicketCord? Yes. The bot owner can change the name, picture, and banner on the Bot profile page, without opening the Discord Developer Portal. See Bot profile. A new name, picture, or banner set in the Developer Portal also shows up in TicketCord. A banner removed in the Developer Portal keeps showing on the Bot profile page until you change or remove it there.

Where did the Bot Settings tab go? It is now the Bot profile page: open the bot under Your bots and click Bot profile. Restart, token updates, status, footer, and disconnect are all there.

How do I move my setup to a new bot application? Add the new bot, invite it to the same servers, then on each server's home page use ⋯ → Import settings from another server and pick the server under the old bot. Roles, channels, and categories must be chosen again. Disconnect the old bot when you are done.

Does disconnecting a bot delete it from Discord? No. The bot stays in your Discord Developer Portal, and you can add it to TicketCord again later. Its TicketCord data does not come back.

Does disconnecting a bot delete my tickets? Yes. Tickets, transcripts, knowledge base, analytics, embeds, and server configurations are all removed, and the bot leaves every server. Export first.

Last updated on

On this page