Run a Discord giveaway without creating distrust
Define eligibility, selection and delivery before launch so a giveaway remains transparent and manageable.
Prepared by the Sunatia product team from practical Discord community administration workflows.
Publish the complete conditions first
State the prize, organizer, opening and closing time, eligibility, entry method, selection method and delivery process. Include geographic or age restrictions when they apply and check the laws relevant to the organizer.
Do not change material conditions after entries begin unless safety or legality requires it. If a correction is necessary, announce it visibly and consider restarting the event.
Use entry requirements that match the goal
Requiring dozens of messages encourages spam rather than community participation. Prefer one explicit entry action or a meaningful contribution that can be reviewed fairly.
Avoid asking members to share sensitive information in a public channel. Collect delivery details only from the verified winner through a private, trusted method.
Practical checklist
- Explain whether staff and bots are excluded.
- Prevent duplicate entries using stable account identifiers.
- Warn members about impersonation and fake prize messages.
Make selection auditable
Freeze the eligible entry list at the deadline and record the selection process. A deterministic or reputable random method is easier to explain than an undocumented manual choice.
Publish the winner’s display name only when appropriate and never expose private account data. Keep internal proof long enough to resolve a reasonable dispute.
Close the event properly
Set a response deadline and a clear redraw process. Confirm delivery privately, then mark the event as completed so members are not left wondering whether the prize existed.
Afterward, review spam, support requests and participation quality. A smaller event that creates genuine interaction is usually more valuable than a large event driven by temporary prize hunters.
Write the giveaway record before opening entries
Create a durable record containing the organizer, prize, eligibility rules, opening and closing timestamps with a time zone, selection method, delivery deadline and fallback if the winner cannot be contacted. Publish the essential terms in the same place members enter so they do not depend on an edited announcement or a separate conversation.
Decide how duplicate accounts, staff entries and regional restrictions will be handled before collecting entries. If a sponsor supplies the prize, state the sponsor’s role and who is responsible for delivery. Never ask winners to pay a fee, reveal a password or send a Discord token to claim a prize.
Test the entry control with an account that is eligible and one that is not. Verify that entries stop at the announced deadline and that restarting the bot or dashboard does not erase the participant list. Export or preserve the final eligible set before drawing a winner.
Practical checklist
- Publish exact timestamps, eligibility and the selection method.
- Preserve the final eligible entrant list before drawing.
- State the official contact path and the information staff will never request.
Make selection and delivery auditable
Record the entrant count, the random selection output and the account chosen. If the first winner is ineligible or misses the claim deadline, record the reason before selecting a replacement. This creates a simple chain of evidence without publishing private account details.
Announce winners through the documented channel and repeat the anti-scam warning. Impersonators often contact participants immediately after a popular giveaway. A verification phrase or case identifier in the public winner notice helps members distinguish the real contact from an unsolicited direct message.
Close the record after delivery with the date and confirmation method. Review complaints, failed claims and suspicious entry clusters before the next giveaway. The aim is not only a random draw; it is a process participants can understand and moderators can defend.