Your member count tells one story. The conversation can tell another. Run /audit for a free sample of activity: messages, participants and a report to read with your moderators.
The report covers a sample, not necessarily the whole server.
Before changing your events or onboarding, look at who appears in the sample and ask your moderators what might explain it.
Your regulars are active, but you rarely see a new name. More announcements might help — or the issue might be timing, channels or the first conversation. Start by looking.
Situations to explore, not a diagnosis of your server.A sample alone cannot explain why members participate or leave. GuildAudit helps you start the conversation; it does not guarantee more activity.
A report is a starting point for your moderators. Use this fictional example to see what is observed, what needs context and what you could try.
In this fictional example, 147 messages came from 11 participants. These are observations from a sample, not a measure of the whole community.
Run the command in Discord. Review the sample with the people who know your channels.
Shall we look at activity before planning the next event?
/audit↵Activity report
The command /audit stays at the centre of the workflow.
Which channels and times explain this sample?
The report brings observations. Your staff decides what happens next.
Design illustrations, not screenshots of the current interface. People, conversations and numbers are fictional.
Start with the free audit. See what it adds before considering a deeper paid diagnosis.
Need more detail? Compare the available options on the pricing page.
Choose a server you manage and review the requested permissions. The getting started page walks you through the existing installation path.
Open the getting started guide →Run a free /audit, read the sample with your moderators and pick one thing to investigate. Keep the report’s limits in mind when you compare it with the next one.
Review the requested permissions before adding GuildAudit.