Ticket Tool Documentation
Invite BotDashboardSupport ServerStatus Page
Ticket Tool Docs - English
Ticket Tool Docs - English
  • Ticket Tool Docs
  • Changelog
  • General
    • Setup
    • Commands
    • Refund Policy
    • Terms of Service
  • Debugging
    • Errors
      • Failed to Create
      • Missing Panel
      • Channel Limit
      • Category Issues
      • Category Permission Issues
      • Storage mode error
      • Thread Error
      • Thread Permission Error
      • Rate Limit
      • Invalid Modal
      • Too Many Errors
      • Major Config Mismatch
    • Troubleshooting
    • FAQs
  • Dashboard
    • About
    • Server Info
    • Server Configs
    • Command Configs
    • Panel Configs
      • General Options
      • Category Options
      • Ticket Options
      • Moderator Options
      • Permission Options
      • Button Options
      • Message Options
      • Transcript Options
      • Logging Options
      • Automation Options
      • Limit Options
      • Claiming Options
      • Form Options
      • Integration Options
      • Panel Options
      • Command Style Tickets
      • DropDown Style
      • Thread Style Tickets
      • Supported Variables
    • Custom Commands
    • Dashboard History
    • Statistics
Powered by GitBook
On this page
  • Ticket Tool doesn't answer
  • Ticket Tool leaves my server as soon as I add it
  • Everyone can see my tickets!
  • I can't see my ticket
  1. Debugging

Troubleshooting

Solving the most frequent issues

PreviousMajor Config MismatchNextFAQs

Last updated 6 months ago

This page covers the most common issues you can face while using Ticket Tool

Ticket Tool doesn't answer

  1. Run $debug on the channel you are trying to run Ticket Tool commands, if the bot has minimum perms it will either send a embed marking with ❌ the permissions it's missing to work properly. If it can't send it to the channel due to permissions, but it received the command it will DM you the debug embed.

  2. Go to your and look at your , Ticket Tool will ignore anyone who has any of those roles.

Blacklisting @everyone will result in Ticket Tool being unresponsive to commands to any user.

  1. Within the tab check that the bot you have enabled is the one you have on your server. If you selected the premium bot you must count with an active subscription.

Ticket Tool leaves my server as soon as I add it

The most common cause for this situation is having a security bot target Ticket Tool, which leads to Ticket Tool being removed or having its permissions removed. To solve this, reach out to the support team of your security bot in order to whitelist Ticket Tool.

Everyone can see my tickets!

There are two possible reasons for this issue:

  1. The @everyone role being selected as a , this by default will grant access to the tickets. To fix it you can simply remove the role from this set of roles and new tickets should be private again.

  2. The have granted access to tickets. To fix it mark as ❌ the View Channel permission and new tickets will be private.

I can't see my ticket

Discord's integrated View As Role feature allows you to see the way different set of roles have access to your server's channels. While this is a useful feature, it's not reliable enough for thorough Ticket Tool testing - As tickets are created based on User permissions, while Role permissions are used for , and .

To test Ticket Tool as a user, we suggest you ask a friend to open a ticket for you as a regular member would do, or use an alternative account to simulate the same process to make sure everything is set properly.

Server Configs
Server Configs
premium
Blacklisted Roles
Support Team Role
Support Team Roles
Additional Roles
@everyone role opened permissions