Ticket commands and panel buttons say Tickets is switched off
Why: The Tickets service is switched off for the server. Commands and panel buttons both answer "The Tickets service is switched off in this server."
Fix: If you have Manage Server, press the Switch on button under that reply. You can also open the dashboard, choose the server and turn on the Tickets switch on the Services page. See Set it up.
Run setup stops before it changes anything
Why: The bot is missing the Manage Channels permission, which it needs to create ticket categories and channels.
Fix: Give the bot's role the Manage Channels permission in Discord, then press Run setup again. The Setup check shows what else the bot lacks.
A member cannot open a ticket
Why: One of the checks the bot runs before a ticket opens refused the member. The first check that refuses decides what the member sees.
Fix: Read the reply the member saw. Then lift the block, change the limit or change the opening hours.
The checks in order and what members see
The bot checks the member in a fixed order:
- the blocked list
- the opening hours
- the panel's wait between tickets
- the panel's limit of open tickets
- the panel's limit for each member
- the daily limit
- your open ticket limit
| The member sees | Why |
|---|---|
| "You are not able to open tickets in this server." | They are on the blocked list. |
| A limit reply, such as "You already have {n} open tickets, which is the limit of {limit} here. Please close one of your tickets before opening a new one." | A limit stopped them. The reply names the count and the limit. |
Members with Manage Server always pass the panel's open rules and skip the hours check. The "Roles that skip these limits" skip the wait and the limits.
A ticket opened outside support hours, or did not open at all
Why: Outside your opening hours, the choice under "Outside these hours" decides. Either no ticket opens and the member sees the closed message, or the ticket opens with a "🕒 Outside support hours" notice saying when the team is back.
Fix: Change "Outside these hours", or add the "Roles that can open tickets at any time".
The panel will not post in the channel
Why: The bot needs View Channel, Send Messages and Embed Links in that channel. When it lacks one, the post does not go out.
Fix: Allow those permissions for the bot in the channel, or pick another channel. Then press Post in Discord again.
Members still see the old text on a panel after you edited it
Why: Button changes reach Discord by themselves, but text and look changes wait for you to press Update in Discord.
Fix: Open the panel on 1 Opening and press Update in Discord. The bar on top of the panel editor says whether members see your latest changes.
Staff cannot close a ticket and are told to claim it first
Why: "Staff must claim a ticket before closing it" is on, so staff who did not open the ticket must claim it before they close it. Without a claim they see "You must claim this ticket before closing it. Click the Claim button first."
Fix: Click Claim, then close the ticket. Or switch off "Staff must claim a ticket before closing it" on 3 Closing. The member who opened the ticket never needs to claim it.
Closing a ticket says it needs a reason
Why: The ticket's panel has "Ask for a reason to close" on. A close with no reason gets "Tickets from this panel need a reason to close. Try again and add one."
Fix: Close the ticket again and add a reason. Or switch off "Ask for a reason to close" for that panel on 3 Closing.
A member who writes to the bot by DM gets no answer
Why: No server they share with the bot takes tickets by DM, so the bot keeps quiet on purpose. Only someone who had a ticket by DM before is told, at most once a day: "I can't pass this on: no server we share takes tickets by DM. Open a ticket in the server instead."
Fix: Open 1 Opening and find the "Tickets by DM" card. Check that "Members can open a ticket by writing to the bot" is on and that its panel is on. On a server with a custom bot, members must write to that bot, not to the shared YourBot.
A staff reply shows a warning mark and "Not delivered"
Why: The ticket came in by DM and your message did not reach the member. For example:
- the member does not accept DMs from the server;
- the member is no longer in the server;
- the ticket is closed.
Fix: Read the reason in the bot's reply under the first failed message. If the member's DMs are closed, they can still read the ticket and its answers on their My tickets page. If the ticket is closed, reopen it to write to the member.
The bot says it cannot add the marks on a ticket by DM
Why: The ✅ and ⚠️ marks are reactions, so the bot needs the Add Reactions permission. Without it the answers still arrive.
Fix: Give the bot Add Reactions. A panel that opens threads also needs Read Message History in the channel its threads open in. The Setup check lists the permission while Tickets by DM is on.
Run setup again posted the first panel twice
Why: "Run setup again" posts your first panel (A to Z by name) again as a new message.
Fix: Delete the older message in Discord.