Community conversations. Clear ownership.
Separate community discussion from support, moderation, and event operations. Design alerts around the role that can help, not around the number of mentions in a busy channel.
Discord bot permissions and Gateway intents determine available events and message fields. Message-content access is a privileged intent with documented exceptions; verify the approved application configuration.
Official reference: Discord ↗Route the responsibility, not the role mention
A casual mention in general discussion is different from an explicit incident report. Create clear submission paths and give each path an owner. Keep moderation review restricted, direct product issues to support, and send event blockers to the organizer who is actually covering the event. The first label should describe a report awaiting review, not a confirmed finding.
A member reports an issue blocking a scheduled community event.
- Check the report through the authorized server workflow.
- Assign the issue to the active event coordinator.
- Keep subsequent updates together and escalate only material changes.
Keep the preview useful, not excessive
Do not forward a private moderation report into a general operations channel. Review the destination audience as carefully as the bot’s source access.
The notification should identify the work, explain why it needs attention, and name the next responsible role. Keep acceptance separate from delivery and resolution separate from both. The escalation guide shows how to make that response loop explicit.
Before you implement
- Agree on support and moderation reporting paths.
- Review channel access and the application’s intents.
- Name primary and backup roles with real coverage.
- Test an accidental mention and a sensitive report.
Begin with fictional test messages and a small, agreed scope. Confirm that the intended responder can open the source, understand the routing reason, and take the requested action. Use the scope guide to separate access, implementation, provider costs, and human coverage.
Common questions
Is a server mention enough to create an urgent page?
Not by itself. Use the reporting path, consequence of delay, and available owner to determine the response.
Can the same queue handle moderation and support?
The workflow can use consistent states, but sensitive moderation details need an appropriately restricted audience.