Frequently Asked Questions

Complete, verified answers to the questions people ask about setup, permissions, commands, plans, billing, AI, privacy, and troubleshooting

Every answer on this page stands on its own. Dashboard paths are written as Page → Block, for example Staff → Claiming: click one to open that block (the dashboard asks which server), or open the server, pick the page in the sidebar under Settings, and go to the block. If your question is not here, ask in the support Discord or browse the help centre.

About TicketCord

What is TicketCord?

TicketCord is a hosted ticket system for Discord. You bring your own Discord bot (you create the application in the Discord Developer Portal and give TicketCord its token), TicketCord runs it, and your members open support tickets with buttons, dropdowns, forms, or by sending the bot a DM (ModMail). Staff work tickets in Discord with slash commands or in the web dashboard, which also holds stats, transcripts, a knowledge base, and AI features on paid plans.

Is TicketCord a bot I invite, or do I need my own bot?

You need your own bot. TicketCord does not have a single public bot to invite. You create a Discord application, paste its bot token into the dashboard (the guided setup on your first sign-in, or Add a bot under Your bots in the sidebar), and TicketCord runs it under your bot's name and avatar. This is why branding, status, and permissions are yours to control.

How many bots and servers can I have?

The bot limit depends on your plan: Free 1, Basic 3, Pro 3, Enterprise 6. Each bot can be added to as many servers as you like; the limit counts bots, not servers. A single server can also have more than one of your bots, for example one per department.

Can I self-host TicketCord?

No. TicketCord is a hosted service only.

What languages does TicketCord support?

The website and dashboard are available in 12 languages: English, Czech, German, Dutch, Spanish, French, Italian, Japanese, Polish, Portuguese, Russian, and Turkish (language switcher in the top bar, or Language in the account menu).

Bot messages in Discord are set per server under General → Bot language and support 19 languages: Arabic, Chinese (Simplified and Traditional), Czech, Dutch, English, French, German, Hindi, Italian, Japanese, Korean, Polish, Portuguese, Russian, Spanish, Swedish, Turkish, and Vietnamese.

AI answers reply in the language the user wrote in.

Setup and installation

How do I set up my first bot?
  1. Create an application at the Discord Developer Portal, open its Bot page, and turn Public Bot off. TicketCord turns on the two privileged intents it needs when it checks your token.
  2. Click Reset Token and copy the token.
  3. Sign in at ticketcord.com/dashboard. The guided setup opens on your first sign-in: paste the token, click Check token, then Connect bot. (Without the guided setup: Add a bot under Your bots, paste the token, Continue, then Add this bot.)
  4. Press Add bot next to your server and approve it in Discord. Inviting from the dashboard sets all required permissions.
  5. Back in the guided setup, choose the staff roles, categories, and channels. Anything your server does not have yet, Create them for me creates (the ticket categories, the transcripts and logs channels, and the staff roles). /setup in Discord creates the same set, if you prefer it.
  6. Post your ticket panel and open a test ticket. For a server you set up later, click its tile on the dashboard home and fill in the setup form there.

The Quick Start and Installation pages walk through each step with screenshots.

Where do I get a bot token?

From the Discord Developer Portal: create an application, open the Bot page, click Reset Token, and copy it. Keep it secret; anyone with the token controls your bot. If you reset the token later, your bot goes offline until you paste the new one with Update token on the bot's Bot profile page (open the bot under Your bots).

Which Privileged Gateway Intents do I need?

Two: Server Members Intent and Message Content Intent, both on the Bot page of your application in the Discord Developer Portal. TicketCord switches both on for you when it checks your token, so usually you do not touch them. If it cannot (Discord refuses that for a bot whose servers have more than 10,000 members together until it approves the intents), the token check says so: apply for them, turn both on once approved, save, and check the token again.

If they are turned off later, Discord rejects the connection with a "disallowed intent" error (code 4014) and the bot cannot start. TicketCord makes one automatic attempt to enable them again when that error occurs. Discord refuses that attempt for a bot whose servers have more than 10,000 members together until it approves the intents; the dashboard then says so, and you apply for them in the Developer Portal and turn them on once approved. Restart the bot from its Bot profile page afterwards. 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.

If it still fails, turn them on manually and use Start if the bot is Offline, or Restart if it is in Error, on its Bot profile page.

What permissions does the bot need?

View Channel, Manage Channels, Manage Roles, Manage Webhooks, Send Messages, Send Messages in Threads, Create Public and Private Threads, Manage Threads, Manage Messages, Pin Messages, Embed Links, Attach Files, Read Message History, Add Reactions, Mention Everyone, and Use Application Commands. Inviting the bot from the dashboard grants all of them.

Do not invite the bot by hand from the Developer Portal; manual invites often miss permissions and break ticket creation, transcripts, or role management. Run /diagnose in your server to check what is missing.

What does /setup create?

/setup creates:

  • A 🎫 Tickets category (new tickets).
  • A 📁 Closed Tickets category.
  • A 📝 Ticket Logs category holding #ticket-logs and #ticket-transcripts.
  • Two roles: Ticket Admin (full ticket management) and Ticket Support (basic ticket access). On the Free plan the roles are named TicketCord Admin and TicketCord Support.

If matching categories or roles already exist, /setup offers Create Anyway (New Names), Use Existing (Recommended), or Cancel.

/setup only creates Discord resources; you still finish the configuration in the dashboard. The setup form on your server can create the same set (or only the parts you have not picked) with Create them for me, and picks them for you.

Who can run /setup and /config?

/setup needs Administrator, or Manage Channels plus Manage Roles. /config (the interactive settings panel) needs Administrator or a configured staff role, but only the bot owner or the Discord server owner can change staff roles there. Everything else is configured in the dashboard by the bot owner or by users you grant dashboard access to.

How do I create a ticket panel?

Open Panels → Ticket panels, click New panel, add a button (or dropdown or application form) that opens a ticket, and post it to a channel from the dashboard or with /embed <name> [channel] in Discord (/embed needs Manage Messages). Free accounts can save 2 panels, Basic and Pro 5, Enterprise 15.

Can I copy my configuration to another server or bot?

Yes. Open the server that should receive the settings, click ⋯ next to its name on its home page, and choose Import settings from another server (bot owner only).

It copies all behavioural settings (timers, toggles, AI settings, business hours), custom embeds, and canned responses from another of your servers, also one run by a different bot of yours.

  • Discord-specific IDs (roles, channels, categories) are cleared and must be picked again.
  • Webhooks and status page integrations are not copied.

To move a whole setup to a new bot, invite the new bot and import each server's settings this way.

Staff, roles, and permissions

How do I make someone staff?

Give them one of the staff roles in Discord. Which Discord roles count as staff is set by the bot owner under Staff → Staff roles. Permissions are checked live, so role changes apply immediately. If you ran /setup, select the Ticket Admin and Ticket Support roles it created there.

Can staff use the dashboard?

Yes, if the bot owner grants them dashboard access under Staff → Staff roles, card Dashboard access (pick their staff roles, or turn on Also allow Manage Server). Those users can view and change the bot's settings for that server, but only the owner can change staff roles, dashboard access, and billing.

Can I restrict who can open tickets?

Yes. Opening tickets → Who can open tickets controls who can create tickets with allow and block lists (members and roles).

The same list decides who can contact staff by DM with ModMail. In ModMail mode the block also has Minimum account age and Minimum time in the server, to keep out new accounts.

A single panel button or dropdown option can also block certain roles, or allow only certain roles, on every plan: click it in the panel designer and turn on Who can open this (for a form or application, it is under Ticket settings).

Why can't my staff see ticket channels?

Ticket channels are only visible to the ticket creator, the configured staff roles, and anyone added with /add. Check that the staff member has a role listed under Staff → Staff roles in the dashboard, that the bot's role is above the roles it manages in Discord's role list, and that the bot has Manage Channels and Manage Roles in the ticket category.

Who can close, reopen, or delete a ticket?

Close: the ticket creator, staff, or an administrator, with /close [reason] [silent] or the Close button. Reopen: staff, with /reopen or the Reopen button. /purge, which bulk-deletes tickets, is limited to the server owner. In the dashboard, Delete soft-deletes a ticket (the channel is removed and the ticket stays under the Closed tab) and Purge permanently removes those deleted tickets and is limited to the bot owner.

Commands and everyday use

Which slash commands exist?

33 slash commands plus two right-click commands.

  • Ticket management: /close, /reopen, /escalate, /claim, /unclaim, /add, /remove, /rename, /closerequest, /transcript, /priority, /tag, /note, /claims, /unclaimed, /feedback.
  • Staff tools: /reply (canned responses), /stats, /staff-stats, /summary, /ai-help, /ai-style, /context, /translation, /modmail, /approval, /diagnose, the Open ticket entry when you right-click a message, and the Find ticket entry when you right-click a user.
  • Admin: /setup, /config, /auto-close, /embed, /purge.
  • Everyone: /help.

The full reference with options and permissions is under Commands.

Which commands need a paid plan?

/escalate, /reply (canned responses), /stats, /staff-stats, and /auto-close need Basic or higher. /ai-help, /ai-style and /summary need Pro or higher. /approval needs Enterprise. Everything else works on Free. A command used on the wrong plan replies with error code TC014.

How do I close a ticket after a delay or without a DM?

/close accepts reason, in (for example 30m, 2h, 1d, which schedules a ModMail close after that delay), and silent (no DM is sent to the user). Staff can also send /closerequest [reason], which asks the ticket creator to confirm the close.

How does auto-close work?

Auto-close closes tickets with no activity after a set time. Configure it under Closing tickets → Auto-close and reminders or with /auto-close <time> (for example 30M, 2H, 1D, or off; minimum 15 minutes, maximum 30 days; needs Administrator).

It requires Basic or higher; existing Free accounts that had it before the change keep it. Reminders that warn the user before closing are configured in the same block and also need Basic or higher; change their wording on Messages (Inactivity reminder). On Enterprise, Pause on closed days holds both back while your business hours say you are closed.

  • ModMail tickets use the ModMail reminders card on ModMail → ModMail instead, which reach the member in their DMs.
  • A reminder counts as a message, so it restarts the timer: a quiet ticket closes one full auto-close time after its last reminder.
  • Pinned tickets get neither auto-close nor reminders, and unpinning a ticket restarts its inactivity timer.
  • Auto-close checks about every 3 minutes and closes up to 10 tickets per server each time, the longest quiet first. A check can take longer when many tickets close, which delays the next one. A bigger pile, for example after upgrading to Basic or while the bot was offline, closes over the next checks.
  • A ticket closed more than an hour after the first moment auto-close could close it (its auto-close time, or your next opening when business hours pause auto-close), for example after the bot was offline or an upgrade to Basic, closes quietly: the close notice, transcript, logs and auto-delete work as usual, but its creator gets no close DM, no transcript copy and no feedback request. This keeps a pile of old tickets from messaging every member at once.
  • If TicketCord restarts while an auto-closed ticket's channel is still being deleted, renamed or moved, that step usually finishes within about 10 minutes, as long as the bot can still manage the channel. A ticket pinned since, or in a server that has turned auto-delete off since, is kept and moved to closed tickets instead of deleted. No notice, DM, transcript or log entry is sent for it; a finished delete still sends the ticket.deleted webhook event.
  • The ticket creator or any staff member can press Extend Time on a reminder. Inactivity auto-close waits until that extra time runs out, even when Time added is longer than the normal auto-close timer. Simultaneous clicks count as one extension; if the ticket changes before your click completes, try again.
What are canned responses and how do I use them?

Saved replies that staff send with /reply <shortcut>; the shortcut option autocompletes. Create them under Staff → Quick replies. Basic and Pro allow 25, Enterprise unlimited, Free none.

How do transcripts work?

When a ticket closes, TicketCord saves the conversation. The transcript is posted to the Transcripts channel under General → Where the bot posts (for example the #ticket-transcripts channel TicketCord creates during setup), or to the logs channel while it is Same as logs:

  • when staff press Transcript on the closed ticket or run /transcript, and
  • automatically on every close when the Transcripts switch is on (under Closing tickets → Transcripts; when the channel is deleted on close, the transcript is posted first). Also send it to the member there attaches it to the member's close DM.

If there is neither a transcripts channel nor a logs channel, an automatic transcript fails, and a ticket set to be deleted on close is kept instead.

In the dashboard every ticket can be exported as HTML, JSON, CSV, or PDF; transcript pages on ticketcord.com require signing in with an account that has access to the ticket.

How long transcript content is kept depends on your retention setting (see Privacy below).

What is ModMail?

ModMail lets members open a ticket by sending your bot a direct message; each DM conversation becomes a ticket channel in the category you choose, and staff replies are relayed back as DMs.

Turn it on with Members open tickets with under Opening tickets → How members open tickets. Its settings then sit with the rest:

/modmail evidence and /modmail message <number> help staff inspect a ModMail ticket.

Text, files, and forwarded messages are relayed in both directions, up to 5 member messages a minute (see TC001 for what happens past that). A sticker on its own has nothing to relay: it gets a ❌ and the other side sees nothing, and staff keep their message in the channel. A sticker sent with text relays the text only. A pin notice is ignored, so pinning a message in a ModMail ticket does not count as a reply.

When the bot restarts, DMs a member with an open ticket sent in the meantime reach that ticket once it is back, up to 5 messages from the last 15 minutes, with a ✅ on each. Anything older stays unsent. A first DM from a member with no open ticket cannot be picked up, so they need to send it again. A staff message sent in the ticket channel while the bot was away is not delivered late: it gets a ❌, so send it again.

If a ModMail ticket's channel is deleted in Discord instead of closing the ticket, the ticket closes the next time the member writes, and they are asked whether to open a new one, as after any close.

Can ModMail tickets open in a private staff server?

Yes. Add the bot to the private server and to your public server, turn ModMail on in the private server, and select the public server under Also take DMs from in ModMail → ModMail.

Members of the public server can then DM the bot, and their tickets open in the private server even though they are not in it. Only the bot owner can change this, and you can select up to 25 servers. See ModMail From Other Servers.

Can the bot DM new members when they join?

Yes, on Basic and higher. Turn on DM to new members under Messages (Automatic messages, Member joins); the default message welcomes the member and tells them to reply to the DM to open a ticket. Supports {server} and {username} placeholders.

Can I limit how many tickets one user can open?

Yes. On Free every user can have up to 5 open tickets at a time, and you can lower that to anything from 1 to 5. On Basic and higher you can set any number under Opening tickets → Ticket options, Open at the same time. When a user hits the limit they see error code TC016.

Plans and billing

What does each plan cost?

Basic €3.50/month or €34.99/year, Pro €6.99/month or €68.99/year, Enterprise €12.99/month or €128.99/year. Free is €0. Yearly billing saves about 17%. Prices are in EUR; the pricing page is the source of truth. Full feature matrix on Plans & Pricing.

What is included in the Free plan?

1 bot, unlimited ticket volume with up to 5 open tickets per user, all the ticket commands that do not need a paid plan, ModMail, the dashboard, transcripts and exports, 2 saved embeds, per-button staff roles, and closed-ticket retention of delete-after-close, 30, or 90 days. The "Powered by TicketCord.com" footer and bot status are required. No AI, no stats, no quick replies, no auto-close, no webhooks.

What is the difference between Basic and Pro?

Pro is Basic plus AI, the email inbox and the website widget. Both have 3 bots, branding removal, custom bot status, stats, auto-close, 25 quick replies, application forms, custom close messages, DM on join, and the full retention options. Pro adds 10M AI tokens a month, a knowledge base with 2 sources, Atlas AI, AI Help and summaries, priority, duplicate, and tone detection, the email inbox (3 addresses, 3,000 emails sent per month), the website widget, and the ability to buy extra tokens.

What does Enterprise add?

6 bots, 30M AI tokens a month, 15 knowledge base sources with up to 500 crawled pages each, 20 outgoing webhooks per server, business hours, response targets, approval workflows, scheduled reports, smart auto-routing, ticket translation, the sentiment journey, unlimited quick replies, 15 saved embeds, custom footer text, an email inbox with 10 addresses and 5,000 emails sent per month with no daily limit, and the option to hide Powered by TicketCord in the website widget.

How does the free trial work?

Every new account automatically gets 14 days of Enterprise. No card is collected and nothing is charged. During the trial you are limited to 1 bot, 2 knowledge base sources, 100 crawled pages per source, and 1,000,000 AI tokens for the whole trial. When it ends the account returns to Free and everything you set up is kept. Details on Free Trial.

How do I upgrade?

Plan & billing → Change your plan: choose Card (monthly or yearly) or Crypto (3, 6, or 12 months), click Upgrade to …, accept the two-checkbox purchase consent, and pay. Card payments go through Stripe Checkout; if you already have a card subscription the plan changes immediately and the prorated difference is charged to your saved payment method right away. Step by step on Manage Subscription.

How do I downgrade or cancel?

To move to a lower paid plan, click Downgrade to … on its card in Change your plan; the change is scheduled for the end of the period you paid for, and nothing is charged or refunded.

To cancel, open the Stripe billing portal with Manage subscription on the Plan & billing page; cancellation also takes effect at the end of the period you paid for. Until then you keep the plan. Nothing is deleted when a plan ends.

What payment methods do you accept?

Cards, Link, and the other payment methods Stripe Checkout offers in your country, and cryptocurrency through NOWPayments (Bitcoin, Ethereum, Litecoin, Solana, Monero, TON, TRON, XRP, Bitcoin Cash, BNB, and USDT or USDC on several networks). Crypto purchases are one-time payments for 3, 6, or 12 months and never renew; they cannot overlap with an active card subscription.

Is there a refund policy?

TicketCord activates the moment you pay. At checkout you tick two separate boxes: a request for immediate access and an acknowledgement that you waive the 14-day EU right of withdrawal once the service begins. After that, subscriptions and token packages are non-refundable. Cancel at any time to stop future charges. For a billing mistake email help@support.ticketcord.com with the invoice number.

What happens to my bots and settings if I downgrade?

Bots above the new limit are stopped (the oldest ones keep running) and show Plan limited until you upgrade or disconnect a bot. Features the new plan does not include are switched off but keep their settings. On Free each user can have at most 5 open tickets (a saved limit from 1 to 5 still applies, a higher one counts as 5) and TicketCord branding comes back. Tickets, transcripts, embeds, and configuration are all kept. Full list on Plans & Pricing.

Where are my invoices?

Plan & billing → Payment history lists every payment; Manage subscription opens the Stripe portal where you download invoice PDFs, update your card, and change the billing name, address, and VAT number. Crypto purchases have no Stripe invoice. See Invoices.

What if my renewal payment fails?

Stripe retries the charge and emails you. While the invoice is unpaid the account is treated as Free (extra bots stop, paid features pause). Update the card and pay the open invoice from Manage subscription and access returns. If all retries fail, the subscription ends and you stay on Free until you subscribe again.

Can I get a custom or larger plan?

Email help@support.ticketcord.com with what you need.

AI features and tokens

What AI features are there and which plan do they need?

Pro and Enterprise: knowledge base answers in tickets, AI Help for staff (/ai-help), AI summaries (/summary), the ticket summary card, Ask for details, priority detection, duplicate detection, tone alerts, and general-knowledge fallback answers. Enterprise only: Sorting (smart auto-routing), ticket translation, and Mood history. Free and Basic have no AI. All of these are part of Atlas, TicketCord's AI.

How many AI tokens do I get?

Pro 10,000,000 per month, Enterprise 30,000,000 per month, Free and Basic none. The trial has 1,000,000 for the whole 14 days. Usage, the refill date, and what you are expected to use by then are shown on the AI usage page (under More tools in the sidebar of the dashboard home, or in the account menu).

Do unused tokens roll over?

Monthly plan tokens do not; they refill every month, on annual plans too. Purchased extra tokens never expire, and whatever is left of them carries over.

Can I buy more tokens?

Pro and Enterprise accounts can, from Extra tokens on the AI usage page: 10M for €4.99, 20M for €8.99, 50M for €21.99. Extra tokens are only spent after the monthly allocation is used up and never expire. Basic and trial accounts cannot buy tokens.

What happens when my tokens run out?

AI features pause until the next reset or until you add tokens. Everything else keeps working. In a ticket the bot tells the user it is connecting them with a team member, and staff see a notice that the AI token quota has been reached so they take over.

How does the knowledge base work?

You add sources (websites that TicketCord crawls, or text and Q&A entries) under AI assistant → Atlas → Sources, on the Help content tab. When a user writes in a ticket, the bot searches those sources and answers with citations when it is confident; otherwise it hands over to staff.

Pro allows 2 sources with up to 100 crawled pages per website source, Enterprise 15 sources with up to 500 pages. A website source can be re-indexed once every 8 hours.

With Learning on, the bot proposes new Q&A entries from resolved tickets for you to approve. See Knowledge Base.

Why isn't the knowledge base giving good answers?

Add or update sources so the information actually exists, check the crawled pages for the source, review and approve the Q&A entries the bot learned from closed tickets under AI assistant → Atlas → Learning, and describe your product and what Atlas should not answer under AI assistant → Atlas → About your server. If the account has run out of tokens, answers stop entirely until tokens are available. See Knowledge Base Feedback.

Can I turn individual AI features off?

Yes. Under AI assistant → Atlas, every job on the What Atlas does tab has its own switch, such as Set priority automatically, Flag duplicate tickets, Alert staff to upset members, Translate tickets, and Move tickets to the right category, and the Atlas switch turns them all off for the server. Answers come from AI assistant → Atlas → Answer questions in tickets and Answer in public help channels. Staff can also toggle translation for a single ticket with /translation.

Privacy and data

How long is ticket content kept?

It depends on the retention policy of the server, set under General → Privacy and data, Keep closed tickets for. Options are Delete right after closing, 30 days, 90 days, 180 days, 365 days, and Until you delete them.

Free servers can choose delete after close, 30, or 90 days (default 90); Basic, Pro, and Enterprise can choose any option (default 365 days).

When the policy runs it removes the stored messages, attachment links, transcript links, compressed history, and any knowledge base learning derived from the ticket. Ticket metadata (such as status, timestamps, reply times, and who handled the ticket) and staff-only internal notes remain, so analytics keep counting the ticket.

The policy applies to tickets created after it took effect; older tickets keep their previous treatment unless you delete them. Copies in Discord or transcripts you exported are not affected.

Is my bot token safe?

Bot tokens and other secrets are stored encrypted. They are never included in data exports and never returned by the dashboard or API. All connections use TLS. If you think a token leaked, reset it in the Discord Developer Portal and paste the new one with Update token on the bot's Bot profile page.

What data does TicketCord collect?

Your Discord account details (ID, username, avatar, email), the bots and servers you connect, ticket content (messages and attachments), configuration, and usage analytics. TicketCord does not sell data. The Privacy Policy lists the processors used for payments and AI and how long each kind of data is kept.

Can I export my data?

Yes, on request. Email hi@ticketcord.com from the address on your account (the Help page in the dashboard has the email under Your data rights).

The export is a JSON file with your profile, your bots (without credentials), and your servers; tickets, transcripts, and knowledge base content for specific servers are included when you ask for them. Billing records are held by Stripe and NOWPayments and are not part of the export.

Replies usually go out within two business days. Individual tickets can also be exported from the dashboard at any time. See Data Export.

How do I delete my account?

Account deletion is not self-serve. Email hi@ticketcord.com from the address on your account, say which account to close, and confirm you understand it is permanent. Requests are processed within two business days.

  • Deleted: your profile, plan, every bot you own, every server configuration, and the tickets and transcripts tied to them.
  • Kept for legal reasons: billing records and operational audit logs.

Back up what you need first; there is no recovery. You can disconnect individual bots (deleting all their data) and delete tickets from the dashboard at any time.

What happens to ticket data when I disconnect a bot?

Disconnecting a bot (at the bottom of its Bot profile page) removes it from TicketCord and permanently deletes everything attached to it: tickets, knowledge base, analytics, embeds, and server configurations. You type the bot's name to confirm. The bot itself is not deleted from Discord and can be added again later, without its old data. Export anything you want to keep first.

Troubleshooting

Why is my bot offline?

The usual causes, in order:

  1. The two Privileged Gateway Intents are off in the Developer Portal (Discord error 4014).
  2. The token was reset and TicketCord still has the old one (status Token invalid: use Update token).
  3. The bot exceeds your plan's bot limit (status Plan limited: upgrade or disconnect a bot).
  4. Discord is having an outage.
  5. The bot was rate limited (wait and retry).

The bot's page (under Your bots) shows the current status and any error. Use Start on its Bot profile page when the status is Offline, or Restart when it is running or in Error.

Slash commands are not showing up

Wait a few minutes after adding the bot; command registration is not instant. Make sure the bot has Use Application Commands in the server, restart the bot with Restart on its Bot profile page, and if commands still do not appear, invite the bot again with Invite to a server in the dashboard.

If another ticket bot is in the server, its commands can be confused with TicketCord's; remove the old bot when you have finished migrating.

Tickets are not being created

Run /diagnose in the server. Common causes:

  • The bot lacks Manage Channels or Manage Roles in the ticket category (error TC002).
  • The category, channel, or role from the configuration no longer exists (TC004).
  • The ticket category already has 50 channels, Discord's maximum (TC019).
  • The server is not fully configured in the dashboard (TC011).
  • The user already has the maximum number of open tickets (TC016).
  • The user is on cooldown or double-clicked (TC013).
  • The feature is disabled or outside business hours (TC018).

Every code is explained on Troubleshooting.

What do the TC error codes mean?

Every error the bot shows carries a code.

  • TC000: unexpected failure on our side
  • TC001: Discord rate limit
  • TC002: missing permission
  • TC004: channel, category, role, ticket, or user no longer exists
  • TC005: Discord returned an error
  • TC008: could not fetch roles, channels, or members
  • TC009: nothing or an invalid option selected
  • TC010: unknown button or menu
  • TC011: server or feature not configured
  • TC012: invalid command input
  • TC013: ticket cooldown or duplicate submission
  • TC014: higher plan needed
  • TC015: action conflicts with the ticket's state
  • TC016: open-ticket limit reached
  • TC017: command used outside a ticket
  • TC018: feature disabled, unsupported, or outside business hours
  • TC019: Discord channel or category limit reached

Details and fixes are on Troubleshooting.

Transcripts are not being posted

Check that:

  • a Transcripts or Staff logs channel is selected under General → Where the bot posts (with Transcripts left at Same as logs, they go to the logs channel);
  • automatic posting is on if you expect it (the Transcripts switch under Closing tickets → Transcripts; otherwise staff press Transcript on the closed ticket);
  • the bot can see the transcript channel and has Send Messages, Embed Links, Attach Files, and Manage Webhooks there; and
  • the retention policy is not Delete right after closing if you expect content to remain available in the dashboard.
The welcome message or embed looks wrong after I changed plans

On Free, the "Powered by TicketCord" footer and the "Powered by TicketCord.com" bot status are enforced and custom footer text is removed. After downgrading, saved embeds above the new limit are kept but cannot be used. Upgrade and the customisations return.

I reset my bot token and now everything is broken

Expected: the old token stops working the moment you reset it. Open the bot under Your bots, go to Bot profile, click Update token, paste the new token, click Continue, then Save new token. The bot restarts automatically.

Where do I get help?

For a quick answer, use Ask AI in these docs or, once signed in, in the top bar of ticketcord.com: it answers from the docs and the website. On the website it answers up to 10 questions a day for each account and for each internet connection; in the docs, up to 10 a day for each internet connection. For anything else: the chat button in the bottom-right corner of ticketcord.com once you are signed in (it opens a conversation with the team), the support Discord, the help centre, or help@support.ticketcord.com. Paid plans get priority support (24-hour target on Basic and Pro, 12-hour on Enterprise). When you ask, include your bot name, the server, what you clicked, and the TC code if one was shown.

Last updated on

On this page