Every community handles the same three conversations over and over: I need help, I want to appeal a ban, and I want to report someone. Handled in DMs, they land on whichever staff member is unlucky enough to be online, with no record afterwards.
Need help?
Pick a category and we will get the details up front.
Ban appeal
opened by Nova
Report a player
opened by Kestrel
General support
opened by Ash
Transcripts kept after closing
Guildbase gives those conversations a home. Ticket panels with categories, a form up front so you get the details first time, transcripts kept afterwards, and a staff team that can see the whole queue rather than one person's inbox.
Publish a panel where members open a ticket by category, so support, appeals and reports arrive separated rather than mixed together.
Ask for the details up front — ban date, username, what happened — instead of spending the first four replies gathering basics.
Each category can carry its own form and its own staff, so appeals reach the people who handle appeals.
Conversations are kept after the ticket closes, so a repeat appeal can be checked against what was said the first time.
Your whole team sees open tickets and who is handling them, rather than support depending on one person being awake.
See volume by category and how quickly tickets are handled, which is usually the first evidence you need more staff.
Create the categories your community actually gets
Attach a form to each so details arrive up front
Publish a panel where members can open one
Handle tickets as a team, with transcripts kept
Yes, and it is one of the most common uses. An appeals category with a form asking for the ban date, the reason given and the applicant's account of it means the first reply can be a decision rather than a request for basics.
Yes. Closed tickets keep their transcript, which matters when the same person appeals twice or when a staff decision is questioned later.
Yes. Categories can route to different teams, so appeals, reports and general support each reach the right people.
They sign in the same way applicants do, which is what ties a ticket to a real identity and to that person's history with your community.
Yes. Ticket analytics cover volume and handling, which tends to be the evidence behind a decision to recruit more staff.
How communities in these games use it, with the application types they typically run.
Garry's Mod applications
Staff, gamemaster and job applications for Garry's Mod servers running DarkRP, MilitaryRP, SCP-RP and more.
Rust applications
Clan recruitment, whitelist and admin applications for Rust servers and competitive teams.
DayZ applications
Whitelist, group and staff applications for DayZ roleplay and hardcore survival servers.
Free to start, no card required. Bring your Discord server and set it up this afternoon.