Run a structured request board

Choose the right view

• Collect consistent viewer suggestions.
• Moderate their lifecycle.
• Keep point charges and public status clear.
• A channel owner or permitted moderator chooses the channel. That person opens Request boards at /requests to manage boards.
• Open public board copies the viewer route /requests/{channel}/{board-name}. Anyone can read a saved board.
• A viewer signs in with Twitch to submit.
• A viewer signs in with Twitch to vote.
• A viewer signs in with Twitch to withdraw.
• Chat participants can discover boards with !requests.
• Website and chat actions use the same board.
• Website and chat actions use the same limits.
• Website and chat actions use the same votes.
• Website and chat actions use the same request states.

Configure a board

A field uses one of the types below.

1. Select New.
2. Enter a Command and URL name.
3. Enter a title and description.
4. Select whether the board accepts submissions.
5. Set the point cost.
6. Set the refund policy.
7. Set the active-submission limit.
8. Set the submission cooldown.
9. Set the voting switch.
10. Set the per-viewer vote limit.
11. Add only the fields that participants need.
12. Set its label.
13. Set the applicable length limits.
14. Set the applicable choice limits.
15. Set the applicable number limits.
16. Select Save board.
17. Use Open public board.
18. Read the Board rules as a participant.

• The stable public queue order accounts for moderator priority.
• The stable public queue order accounts for votes.
• The stable public queue order accounts for assigned queue position.
• Field type: Text.
• Field type: Link.
• Field type: Choose from a list.
• Field type: Number.
• Field type: Twitch clip link.

Submit and vote

• On the public page, sign in with Twitch.
• Complete Title and the configured fields.
• Select Submit request.
• The page shows the request number and its current public state.
• In chat, use !request <board> <title> | field=value | category=value | tags=a,b. Required field keys come from that board's configuration.
• Use !requestvote <request-number> to vote in chat, or Vote on the public board. A repeated vote does not add another vote.
• A submitter can Withdraw an active request from the public page. The public page never shows private moderator text.

Moderate the lifecycle

Private moderator note and Private rejection reason remain moderator-only. Put public participant context in Public note instead.

The public board keeps the Merged into another request outcome and the target request's combined support.

1. Review the submitted values and any possible-duplicate warning.
2. If participants need them, set the public category and tags.
3. If participants need them, set the priority and Public note.
4. Move Awaiting review to Approved or Rejected.
5. Use Merge with the target request number when two entries are the same request.
6. When the dashboard is not convenient, use one applicable chat action.
7. To merge in chat, use !requestmerge <source-number> <target-number>.

• Approved requests can move to In queue or Accepted.
• In queue or Accepted requests can move to Completed.
• Submitters can select Withdraw.
• BlokeBot gives merged duplicates the Merged into another request state.
• Chat action: !requestapprove followed by one request number.
• Chat action: !requestreject followed by one request number.
• Chat action: !requestqueue followed by one request number.
• Chat action: !requestaccept followed by one request number.
• Chat action: !requestcomplete followed by one request number.

Points and recovery

• When the board accepts the initial submission, it holds the cost from the viewer's available balance before moderator review.
• The reservation starts as No points charged.
• The reservation then moves to Points held.
• The reservation finishes as Points refunded or Points charged.
• Never charge the viewer manually as well.
• Completion charges the held points.
• A closure follows the selected policy:
• Closure policy: Never refund.
• Closure policy: Refund if rejected or withdrawn.
• Closure policy: Refund if not fulfilled.
• If the submission fails, correct the cause that the message identifies.
• A validation error can reject a submission.
• A cooldown can reject a submission.
• A limit can reject a submission.
• The balance can reject a submission.
• Submit once. If an outcome is already visible, reload before you try again.
• If request state and points still disagree after reload, leave the request unchanged.
• Include the channel in the information for the server owner.
• Include the board name in the information for the server owner.
• Include the request number in the information for the server owner.
• Include the approximate time in the information for the server owner.
• Include the visible message in the information for the server owner.
• Do not share Twitch tokens or private notes.