User reports
Collect the reported member, reason, evidence, channel, and incident details.
FromFlow Get Started Discord report workflows
Turn vague pings and scattered DMs into structured reports with the context, evidence, ownership, and follow-up your staff needs.
What you can run
A good report flow collects the facts once, protects sensitive context, and gives staff an actionable case instead of another unstructured message.
Collect the reported member, reason, evidence, channel, and incident details.
Route sensitive reports to a restricted staff group with controlled visibility.
Connect report categories to the moderators responsible for each policy area.
Use the same structured intake pattern for account, access, or community support.
Built around your process
Build the exact path from member submission to staff action, including records, notifications, escalation, and resolution messages.
Ask only the questions required for the selected report category.
Store message links, descriptions, attachments, and relevant member details.
Send cases to restricted channels or staff roles based on severity and category.
Track open, investigating, escalated, and resolved states with clear ownership.
How it works
Launch a private intake form from a command or button.
Save the report and post a complete staff-facing summary.
Route, escalate, comment, and update the case through connected actions.
Record the outcome and send the appropriate follow-up to the reporter.
FAQ
Yes. FromFlow lets you build the full Discord report bot visually with Discord triggers, conditions, actions, stored data, and hosted deployment.
Yes. Route submissions to restricted staff channels and control which roles can view or act on each report.
Yes. Store the report, evidence, status, assigned staff member, notes, and resolution as structured data.
Yes. Branch by category, severity, server, role, or form answer and notify the correct staff group.