/denysuggestion command lets you handle rejections with transparency, updating the original embed with a Denied status and giving you space to explain the reasoning so members understand the decision rather than feeling ignored.
Description
The/denysuggestion command marks a pending suggestion as denied by referencing its unique numeric ID. Burger Bot updates the original suggestion embed in the suggestions channel to reflect the new Denied status. An optional reason can be included to provide context for the decision. Handling denials respectfully and clearly goes a long way toward maintaining trust and encouraging continued community participation.
Usage
Parameters
The numeric ID of the suggestion you want to deny. This ID is displayed on the original suggestion embed (e.g.,
42 for suggestion #42).An optional reason explaining why the suggestion is being denied. While this is optional, providing a reason is strongly encouraged — it keeps the process transparent and helps members understand what kind of suggestions are more likely to be accepted in the future.
Permissions Required
| Role | Access |
|---|---|
| Administrator | ✅ Full access |
| Configured Admin Role | ✅ Full access |
| Staff Role | ✅ Full access |
| Regular Members | ❌ No access |
What Changes on the Embed
After running/denysuggestion, the original suggestion embed is updated with:
- ❌ Status — Changes from
PendingtoDenied - 💬 Reason — Your optional denial reason (if provided)
- 👤 Reviewed By — The staff member who denied it
You can only deny suggestions that are currently in
Pending status. Attempting to deny an already-reviewed suggestion will return an error. If a decision needs to be reversed, contact your server administrator.Example Usage
#42’s embed to show Denied, attributes the review to you, and displays the reason for the community to see.