Suggestions
Multiple suggestion boards with voting, an optional staff review queue, and nine statuses to say what happened — decided without necessarily being closed.
A board is a channel plus its rules. Feature requests, event ideas and bug reports can each have their own board, their own voting style and their own statuses.
Setting up a board
Switch it on
Community → Suggestions.
Create a board and pick its channel
One board per channel — two boards in one channel would make channel submissions ambiguous.
Choose how members submit
The
/suggestcommand, or by simply typing in the board's channel, which Arclo converts into a suggestion card.Choose the voting style
Buttons or reactions.
Save
There is no publish step — a board has no panel message of its own.
ArcloBOTToday at 14:32
Nebula Collective – Suggestions
User
@mira
Votes
Yes: 24 (86%) | No: 4
Suggestion
Add a channel for sharing what everyone is playing this week.
Suggestion Status
Pending
Suggestion #142
Voting
| Style | Behaviour |
|---|---|
| Buttons | The default. Supports anonymous votes, a confirmation before switching sides, and a View votes browser. |
| Reactions | Simpler and more familiar. Cannot be anonymous — Discord shows who reacted — so Arclo forces those options off rather than pretending. |
- Voting can be single-sided or allow both, with an optional confirmation when somebody switches.
- Pressing your own side again removes your vote.
- A per-member cooldown per board limits vote spam.
Statuses
Nine of them, each with its own color and message: pending, queued, approved, denied, considered, in progress, implemented, duplicate and a custom status where staff type the label.
Decided does not have to mean closed
Whether a decided suggestion keeps collecting votes is your call, not the bot's. Some servers want approved to keep gathering support; others want it frozen.
- Thresholds can set a status automatically — “net +20 becomes Considered”, “net −10 becomes Denied” — but only while the suggestion is undecided.
- Decisions can be announced in the board, in a separate decisions channel, as a reply, in the suggestion's thread, and as a DM to the author.
The review queue
With require approval on, a submission is held and posted as a card in your review channel. Staff approve it, which publishes it as a normal pending suggestion, or reject it, which is an ordinary denial.
The queue is post or reject, never edit
Staff cannot rewrite somebody's suggestion into something else before publishing it. A suggestion published under a member's name has to be their suggestion.
Placeholders
{user}, {suggestion}, {number}, {yes}, {no}, {yes_percent}, {bar}, {status} and {status_emoji} — the last two split deliberately, because the default design prints the status inside a code block, where a custom emoji's raw form would show through.
Commands
/suggestion create <suggestion> [board] [anonymous] [image]EveryonePosts a suggestion to one of the server's boards.
/suggestion status <suggestion> <status> [response] [label]Suggestion managersDecides a suggestion — approved, denied, considered, implemented, in progress, duplicate or a status of your own.
/suggestion votes <suggestion>EveryoneShows who voted on a suggestion, and how it stands.
/suggestion edit <suggestion>Author or managersRewrites a suggestion — yours, or any of them if you manage suggestions.
/suggestion delete <suggestion>Author or managersRemoves a suggestion and its message.
Note
Five commands is the whole set on purpose. Everything else staff need is on the Staff Options menu attached to each suggestion card.
Still stuck? Ask in the support server — somebody there has almost certainly configured this before.