Discord Bot Not Showing Commands? Every Cause and How to Fix It

This page is for the person who added the bot, not the person who built it. Everything below is checked in Discord's own settings, roughly in the order it turns up, and applies to any bot, from a music bot to a Discord ticket bot. The last two sections cover AI Ticket Bot.

What are you seeing?

Find your symptom first.

Why is a Discord bot not showing slash commands?

Check these five, in this order.

The second check explains the classic "works everywhere except one channel": that channel denies Use Application Commands to @everyone or to the member's role. On forums, the fourth is called the applications.commands scope.

The bot's own role does not decide this. A bot with too few permissions still has its commands listed and fails only when it acts, which ticket bot permissions covers. In a direct message, a bot's server commands never appear.

Why is the bot not showing new commands?

Usually because your Discord app still holds the list it loaded earlier. Discord takes a new or renamed command quickly on its side, but an app left open for days can keep the old picker. Reload first, as above.

Still missing? The command may have a new name, since bots merge and rename commands: run the bot's help command, usually /help, for the current list. Or it follows your limits: if Integrations restricts the bot to some roles or channels, a new command inherits that.

Why is the bot not showing up in the server or member list?

Discord's member list belongs to the channel you are looking at. It lists the people who can see that channel. If the bot's role lacks View Channel there, the bot is left out, while still being in the server.

For the last row, open Server Settings, then Integrations, which lists every bot in the server. If it is not there, the Audit Log shows who removed it. A security bot that removes new bots not on its allowed list is a common cause: allow it there, then invite it again. On the invite page, check the server picker. It only lists servers where you have Manage Server.

To give the bot its own group in the list, open its role under Server Settings, Roles and turn on the option that shows the role's members separately.

Why is the bot not showing online?

Its program is not connected to Discord. Only the people who run the bot can fix that. You can find out which side the problem is on:

• The bot's status page or support server. Ours is /status.
• Discord's own status page, when several bots go offline at once.
• A reload, since an app open for days can still show a returned bot as offline.

One clue: an offline bot keeps its commands in the picker, and running one gets "The application did not respond". So if commands are missing entirely, offline is not the reason. What an outage does to open tickets and when a ticket button fails cover the rest.

Which AI Ticket Bot commands should you see?

It depends on whether you have Manage Server. Start with /setup. It needs Manage Server and runs only on a server with no panel yet, building a staff role, a ticket category, a panel channel and a live panel in one step. After that, /help lists every command by topic.

Discord hides four from anyone without Manage Server: /panel, /language, /whitelabel and /subscription. Everything else shows to everyone, staff commands like /ticket claim included, because Discord cannot hide a command behind a staff permission that belongs to the bot. A member who runs one gets a private reply naming what is missing. Opening a command to a role in Integrations changes who sees it, never what they may do: the bot checks every run.

Our invite already asks for permission to create commands, so on a fresh invite, check Integrations and Use Application Commands first. If you renamed the bot with /whitelabel, look for that name in the member list. The full command list says who may run each one.

Why is a role or channel missing from the dashboard?

Press Refresh from Discord under the picker. The dashboard keeps a copy of your server's roles and channels for a few minutes, so a role made in Discord a moment ago may not be listed yet. The link reloads the list from Discord.

With this release, Settings has it too:

A notice says Lists refreshed when it worked.

Still missing? It may be left out on purpose. The staff role picker skips @everyone, roles a bot or an integration manages, such as a bot's own role or Server Booster, and roles already on staff. Only the server owner and people with Manage Server can open the dashboard at all, as what the dashboard does explains.

What no setting can fix