Everything you need to know about TicketByte. Can't find an answer? Join our support server.
Click the Add to Discord button at the top of this page. Make sure you select the right server and grant the requested permissions. TicketByte needs Manage Channels, Manage Roles, and Send Messages at minimum.
Run /setup as a server administrator. The setup wizard walks you through choosing a ticket category, assigning your support role, and configuring log channels. You can fine-tune everything afterwards from the Dashboard.
Use /panel [#channel] to post a button panel in any channel. Users tap the button to open a ticket instantly. You can fully customise the panel colour, title, description, thumbnail, and button label from Dashboard → Panel Embed — changes apply the next time you run /panel.
For full functionality TicketByte needs:
Click the 🔄 Refresh List button on your Dashboard server list. This re-syncs your server list from Discord. If it still doesn't appear, make sure you have Manage Server or Administrator permission in that server.
Users click the button in your ticket panel (created with /panel). They can also type /ticket [reason] or the prefix equivalent !ticket [reason] directly.
Yes! Use /addtype <name> [description] [emoji] to add as many types as you need. When a user opens a ticket they'll see a dropdown to choose the type. Each type gets its own button on the panel automatically.
In the Dashboard under General Settings, set Max open tickets per user to any value from 1 to 10. The default is 1. Users who hit the limit will get an error message asking them to close their existing ticket first.
Click the red Close Ticket button inside the ticket channel, or run /close [reason]. You'll be asked to confirm. After closing, a summary embed is posted in the channel, the user receives a DM (if enabled), and the channel is deleted after a few seconds.
Run /reopen <number> where the number is the ticket's ID (e.g. /reopen 42). This recreates the channel, restores the ticket to open status, and notifies the original user.
Inside any open ticket, staff can run /priority <low|medium|high|critical>. The priority is saved and visible in the Dashboard ticket list and in the ticket info embed (/ticketinfo).
Yes. Staff can run /add @user to grant a member access to the ticket channel, and /remove @user to revoke it. The participant list is tracked and shown in /ticketinfo.
Run /rename <new-name> inside the ticket. Staff only. Channel names are sanitised automatically (spaces become hyphens, special characters are removed).
Staff can use /note <text> to post a yellow internal note that stands out from regular conversation. Notes are also saved to the ticket transcript so they appear in the HTML log when the ticket is closed.
Staff can add short labels to a ticket with /tag add <label> (e.g. billing, urgent, waiting-reply). Use /tag remove <label> to remove one and /tag list to see all current tags. A maximum of 5 tags per ticket is allowed.
Run /ticketinfo inside the ticket channel. This shows the ticket number, opener, type, status, priority, claimed-by, open/close times, tags, and participant list all in one embed.
When a staff member runs /claim inside a ticket, it is assigned to them. This prevents multiple agents from replying to the same ticket. Enable claiming in Dashboard → General → Claim Mode. You can also click the Claim button that appears in every new ticket.
Run /unclaim inside the ticket. This removes the assignment so any staff member can claim it. Only the current claimer or a server admin can unclaim.
Use /transfer @staff. This unclaims the ticket from whoever currently holds it, assigns it to the new staff member, and grants them channel access if they don't already have it.
Enable Claim Mode in the Dashboard under General Settings. When active, the bot will remind staff to /claim if they reply to an unclaimed ticket.
Go to Dashboard → General Settings and update the Prefix field, then save. You can also change it with /config prefix <new_prefix>. The default prefix is !.
In the Dashboard go to Channels and set:
/ticketlog set|transcript|modlog #channel.
Go to Dashboard → Messages → Welcome Message. You can use {user} to mention the ticket opener. The message is sent as the first embed inside every new ticket.
Go to Dashboard → Panel Embed. You can change the colour, title, description, footer text, thumbnail URL, image URL, author name, button style, and button label. A live preview updates as you type. Run /panel again after saving to post the updated panel.
Go to Dashboard → Roles → Support Role and select the role that should have access to all tickets. You can also set an Admin Role (full bot control) and a Manager Role. Roles can be set from Discord with the /ticketlog command.
Yes — enable Ask for reason in Dashboard → General. Users will see a modal asking for a reason before the ticket is created.
Transcripts are complete HTML conversation logs generated when a ticket closes. Enable Save transcripts in Dashboard → General Settings, and set a Transcript Channel. When a ticket closes, a styled HTML file is attached to a message in that channel, showing every message, staff note, and attachment link.
The transcript is a self-contained HTML file with a purple gradient header showing the ticket number, user, type, open/close times, duration, and close reason. Each message is displayed in a card. Staff notes are highlighted in yellow. Attachments appear as clickable links.
Currently transcripts are posted to your configured Transcript Channel. The user receives a DM with the close summary (if DM on Close is enabled) but not the full transcript file directly. You can share the transcript link with the user from the log channel.
Yes. Enable Auto-close inactive tickets in Dashboard → General and set how many days of inactivity trigger a close (1–30 days). The bot checks for inactivity on a schedule and closes tickets that have had no new messages in that time.
Yes — if DM on Close is enabled in General Settings, the user will receive a DM with the ticket summary and close reason (Auto-closed due to inactivity) when their ticket is automatically closed.
TicketByte includes: /ban, /kick, /mute (timeout), /unmute, /unban, /warn, /purge, /slowmode, /lock, /nick, and /role. All commands also work with the ! prefix.
Use /warn add @user <reason> to add a warning. View all warnings with /warn list @user, and clear them with /warn clear @user. Warnings are stored per-server and per-user in the database.
TicketByte uses Discord's built-in Timeout feature. Run /mute @user <duration> [reason] — for example /mute @user 1h Spamming. Valid durations include 10m, 1h, 1d, 7d, or 28d.
Run /blacklist add @user to prevent them from opening tickets. Use /blacklist remove @user to lift the ban, and /blacklist list to see everyone currently blocked. Roles can also be blacklisted.
Click Dashboard in the top navigation and log in with your Discord account. You'll see all servers where you have Manage Server or Administrator permission and TicketByte is installed.
Click the 🔄 Refresh List button on the dashboard server list page. This re-syncs your server list from Discord in real time. If it still doesn't appear, try logging out and back in.
Yes — go to your server's dashboard and click Tickets in the sidebar. You can see all open and closed tickets, filter by status, and close open tickets directly from the browser without using Discord.
The analytics page shows a 30-day overview including: tickets opened & closed per day (line chart), command usage, average tickets per day, peak day, close rate, week-over-week comparison, ticket type and priority breakdowns (doughnut charts), and a top-staff leaderboard.
Click the ☀️ / 🌙 button in the top-right corner of any dashboard page. Your preference is saved to your account and persists across devices.
No. TicketByte authenticates entirely through Discord OAuth2 and never asks for, stores, or processes your email address. We do not send marketing emails, digest emails, or any unsolicited communications of any kind.
TicketByte stores: server configuration settings, ticket metadata (who opened it, when, what type), and optionally message transcripts (only if you enable the feature). Read our full Privacy Policy for details.
Server admins can reset their server's ticket data by removing the bot (all server settings are tied to the guild ID). For personal data requests, join our support server and open a ticket.
TicketByte only stores data necessary for the ticket system to function, does not sell or share data with third parties, and provides data deletion on request. Read our Privacy Policy for the full details.
First check the bot has the correct permissions in your server and in the specific channel. If slash commands aren't showing, try re-inviting the bot using the invite link. If prefix commands don't respond, check your configured prefix hasn't changed (use /config prefix to verify).
Make sure:
Check our Status page to see if there's a known outage. If the status is operational, try using a different command. If the issue persists, join our support server and let us know.
Check that TicketByte's role is positioned above the roles it needs to manage in your server's role list (Server Settings → Roles). Discord requires a bot's role to be higher than any role it modifies or assigns.
Our support team is ready to help you on our Discord server.
Join Support Server