Read what was sampled.
Start with the messages and participants shown in the report. The sample may cover only part of the server’s activity.
Inside GuildAudit
Read an activity sample.
Know what it leaves out.
Run /audit in Discord for a free look at a sample of activity. Bring the report to your moderators before deciding what, if anything, to change.
After /audit
Read it in three passes.
Numbers are useful when their limits are clear. The report does not replace what your staff knows about the community.
Ask what is missing.
Which channels, times or events could explain it? Your moderators know things that a sample alone cannot tell you.
Choose a question to follow up.
You might look at a quiet channel or how newcomers get their first reply. Treat this as a question to investigate, not a proven cause.
Design examples
See the format.
Keep the limits in view.
These are fictional design examples, not screenshots of a connected server. Commands and paid concepts shown here are not a claim that every feature is currently available.
GAGuildAuditAPP
/auditAn activity sample — fictional design
147
Messages in this sample
11
Participants in this sample
A question for the moderators
Which channels and times are represented here? Does the sample match the activity your team expected?
These invented counts describe this example only. They are not a retention rate or a view of every member.
Fictional design example: Nova Gaming Hub. Not a screenshot or a proven customer result.
GAGuildAuditAPP
/reportStaff discussion — design example
Observation
The sample contains messages from a small group of participants.
Context to add
Was this a quiet period, a specialised channel or a conversation around an event?
One question to explore
How do newcomers get their first reply in the channels you want them to use?
This illustrates how staff might discuss a report. It does not verify current /report command availability.
Fictional design example: Nova Gaming Hub. Not a screenshot or a proven customer result.
GAGuildAuditAPP
/historyComparing samples — design example
Example A147 messages · 11 participants
Example BDifferent time or channels
Before comparingCheck the sampling context
What the comparison cannot prove
A different sample does not establish that a staff action improved retention or caused activity to change.
This is a design concept, not a live history view or verification of current /history availability.
Fictional design example: Nova Gaming Hub. Not a screenshot or a proven customer result.
Names, scores and changes are invented for the examples. They do not demonstrate retention, recovery or the effect of a staff action. Check offers and availability in Discord; website checkout is not connected.
Dashboard design preview
A place for the next staff review.
This fictional layout brings server status, sample reports and recent activity into one view. It illustrates the design; it is not connected to Discord.
Every server, score, status and activity item below is invented. These are design examples, not a live dashboard or evidence of recovery. Opening the owner dashboard follows the existing sign-in path.
Owner dashboard
Fictional servers · Design preview
3 connected1 setup needed
Selected server
Nova Gaming Hub
GuildAudit connectedPro Monitoring Check Discord
68/100
Stable
GuildAudit diagnosis
Activity is stable, but most conversations are carried by a small group of regulars.
Main risk
Core-member dependency
Next action
Create weekly prompts that bring newer members into conversations.
History preview
First read42/100
Week 251/100
Week 359/100
Today68/100
Recent bot activity
Audit completed
Nova Gaming Hub finished the latest read
Staff report generated
A summary is ready for moderators
Activity drop detected
Creator Lounge has a lower sampled activity score
Pro monitoring preview
Check offers and availability in Discord
Recommendation created
Bring newer members into weekly prompts
View latest audit
View staff report
View history
Monitoring preview only
Start in Discord
Try the free audit before going further.
Review the requested permissions, run /audit and read the sample with your moderators.