Describe your server rules and moderation process. Makeform builds a Discord report form for reported account IDs, message links, timelines, categories, witnesses, and evidence.
Route reports to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a flow, adapt it to your rules, or send the prompt into the builder.
Audience
Members reporting behavior in a community Discord
Format
Multi-section report with identity, timeline, and evidence
Prompt size
237 chars
Example form structure
Multi-section report with identity, timeline, and evidence
Your Discord username and user ID
Reported username and user ID
Which rule category fits best?
Describe what happened in order
Upload screenshots or supporting files
Suggested routing tags
New report
Urgent review
More context needed
Ask for a username and stable user ID because display names can change.
Step 1
Report
account IDs, location, timeline, and rule category
Step 2
Preserve
message links, screenshots, and supporting files
Step 3
Triage
urgency and conflicts route to the right reviewer
Step 4
Review
moderators assess context and record the next step
Better moderation intake
A structured form gathers account IDs, locations, timelines, and evidence without putting sensitive reports in a public channel.
Pair usernames with stable IDs, dates, channels, rule categories, links, and a chronological account.
Keep screenshots, files, witnesses, and links with the narrative and surrounding context.
Separate harassment, scams, staff conduct, and ordinary violations into designated review paths.
Built around server risks
Use conditional sections so each category asks relevant questions and reaches the right reviewers.
Capture channel, date, participants, message references, context, and rule category.
Ask whether conduct is ongoing, where it happened, and what follow-up contact is safe.
Collect account IDs, links, plain-text URLs, screenshots, related accounts, and interaction status.
Record the action, staff role, case links, requested review, and reviewer conflicts.
Report workflow
Generate an editable form, then check it against your current rules and escalation path.
List reportable behavior, identifiers, evidence formats, urgent categories, and reviewer roles.
Use your rule names and set required IDs, dates, locations, timelines, links, and contact choices.
Show scam, safe-contact, and staff-conflict questions conditionally, then route reports privately.
Place the link in rules and help channels, with next-step and external emergency guidance.
Form vs direct message vs ticket
A generated form standardizes initial reports and can feed the workflow your moderators already use.
Field guide
These six sections give moderators enough information to identify accounts, find the relevant conversation, understand the sequence, examine supporting material, triage the report, and follow up responsibly.
People & accounts
Collect display names and stable IDs separately. If anonymous reports are allowed, make reporter contact optional and explain its limits.
Location & time
Ask where and when the incident occurred, including time zone, message links, and whether it extended to voice or direct messages.
Category & timeline
Pair a rule category with a chronological account. Ask for observable actions and relevant context instead of assumptions about motive.
Evidence & context
Keep screenshots, files, message links, and witness details together. Ask reporters to retain timestamps and surrounding context.
Urgency & routing
Use ongoing behavior, account compromise, and staff involvement to notify the designated reviewers without promising automatic action.
Follow-up & acknowledgment
Collect a safe contact method and accuracy acknowledgment. Explain the next review step without promising a sanction or response time.
Related tools
Use related tools for incidents, anonymous complaints, bullying, security, feedback, or customer complaints.
Collect bullying accounts with optional reporter identity.
Open toolCollect account-compromise, suspicious-link, and access details for a separate security review workflow.
Open toolInvite broader suggestions about rules, events, channels, and community experience outside incident reporting.
Open toolStructure service complaints when your Discord server supports customers, subscribers, or product users.
Open toolFAQ
Practical answers for server owners, community managers, and volunteer moderation teams building a consistent report intake process.
A Discord report form privately collects a reported username and user ID, location, timeline, rule category, message links, and evidence. It gives moderators one organized submission for review; it does not decide the outcome.
Include both account IDs, incident date and location, message links, rule category, factual timeline, witnesses, uploads, ongoing-behavior status, and a safe follow-up method. Add conditional fields for scams, voice incidents, or staff involvement.
Display names can change or look alike. A stable user ID identifies the intended account. Give members copying instructions, let them say when it is unavailable, and keep reporter and reported-account fields separate.
Yes, if your process permits it. Make identity optional and explain that missing contact details can limit follow-up. Do not promise anonymity if required fields or integrations reveal identity to reviewers.
Accept message links, screenshots, and files. Ask members to retain usernames, timestamps, and surrounding context, then caption each item. Use a plain-text field for suspicious URLs and discourage gathering unauthorized material.
Yes. Makeform provides unlimited free forms and responses, including generation, editing, publishing, and submissions. The paid tier only removes the Makeform badge. Review the generated form against your current server rules before sharing it.
Design conditional paths and connect submissions to email, Slack, Google Sheets, or Zapier. Route ordinary violations, security concerns, and staff reports to their designated private destinations, with an uninvolved reviewer for conflicts.
Confirm receipt, check identifiers and links, preserve context, compare the account with server rules, request clarification, and record the next step. Explain update and emergency routes without promising a sanction or result.
Give members one clear place to report rule violations.
