< > = Required
[ ] = Optional
Note: The above placeholders are not required. They are simply to show you what the required fields are. The bot will tell you what fields are required.
| = Means "or"
administrator = A user with the Manage Server permission
Managing suggestions is simple. Each suggestion is assigned a Suggestion ID (sID). From there, staff members can either approve, reject, or add a note to a suggestion with the sID. The sID is located in the footer of each suggestion:
You can also find the sID in the message the bot sends after you send a suggestion.
Alternatively, you can use the message ID of the suggestion message to manage a suggestion, especially if you're using the bot on mobile. Click here to check out a tutorial on how to find a message ID.
However, you won't have to worry too much about trying to remember IDs. The bot will autocomplete the suggestion ID as you type it out!
Slash Command Permissions
If you haven't already done so, please refer to the Getting Started section to set up slash command permissions. By default, only administrators can manage suggestions. However, if you want other staff members to have access to these commands, please refer to the aforementioned section.
DM responses are sent to the suggestion submitter based on various actions. DM responses may be toggled by running
/config dm <enable/disable>. This means DMs to the suggestion submitter will or won't be sent via these actions based on how you configure the bot for your server:
- suggestion submitted
- suggestion approved
- suggestion rejected
- suggestion note added
By default, DM responses are enabled. This can be configured by an administrator.
Users can also individually choose if they wish to receive DM responses. This can be configured by running
/dm <enable|disable>. This will override the server-wide setting unless the server has disabled DM responses.
Suggestions are approved via either the sID or message ID. Once you have it, run the command
/approve <sID|message ID>. Afterward, series of actions will happen:
- The suggestion will update as "Approved" in the suggestions channel and its results will be logged.
- The user will receive a DM that you approved their suggestion.
- The results of that suggestion will be posted to the suggestion logs channel.
- An optional response can be added by running
/approve <sID|message ID> [response].
An optional response may also be left on suggestions when approving:
If you enabled DM responses and the user has enabled them, they will receive a DM that their suggestion has been approved.
It seems like a lot, doesn't it? It really isn't, because it all happens in the matter of seconds!
Rejecting suggestions work the same way as approving suggestions. Once you run the command
/reject <sID|message ID> [response], the same series of actions will happen as stated above, but information of the suggestion being rejected will be posted instead.
Just like with approving suggestions, you can add an optional response to the rejection and receive a DM from the bot (if applicable).
When a suggestion is approved or rejected, the following information will be logged:
- the results (this is from the reaction count)
- the suggestion
- the submitter
- the staff member that approved or rejected the suggestion
- the sID
- the response (if one was given)
If you wish to set up the suggestion logs channel, you may refer to the steps below:
- Create a new channel and give it a name such as
- Add the bot to your newly created channel and give it the Send Messages permission.
- Add additional permissions depending on what the bot has assigned in your server.
- Disable Send Messages and Add Reactions for
@everyoneto only allow the bot to send messages and to prevent unnecessary message reactions.