1. Confirm which app and command you need
Type / in the intended channel and select the correct app. Compare its available commands with the bot’s current command list. A command from another bot, a retired command or a dashboard-only feature will not appear just because an app is installed.
2. Check server installation and context
Look under Server Settings → Integrations. Installing an app on your user account is different from adding a bot to the server. Some commands are available only in servers, direct messages or particular installation contexts. Check the bot’s supported installation flow before reinstalling anything.
3. Review channel and integration restrictions
Check Use Application Commands in the channel. In Server Settings → Integrations, inspect the app’s command restrictions for roles, members and channels. Compare the affected member’s access with a moderator’s access; seeing a command as an administrator does not prove other members can use it.
4. If the command appears but refuses to run
Read the bot’s response. The invoking member may need moderation permissions, while the bot needs separate permission to carry out the action. In acrO, enabling a command in Integrations cannot bypass those checks. A disabled module or a service problem can also prevent a response.
5. If installation and permissions look correct
Reload Discord and try the supported command in the intended context once more. If it is still absent, give the bot’s support team the command name and where you tried it. Command registration is the developer’s responsibility; do not share a token or repeatedly remove the bot to force an update.
For acrO, start with the public command list or /help. The website demo can show the dashboard before you sign in; it does not install or change anything on your server.