Getting Help & Support
Stuck on something? Garrison has a built-in support-ticket system so you can reach a server's staff privately and get a one-to-one answer, no third-party bots required.
💬 Join the Garrison Support server
The official server for help, announcements, bug reports, and feature requests, open the link in the web app or your installed client.
If you need help
Submit a support ticket
On any server that has support enabled, you'll see a life-buoy button (🛟) at the top of the server list. Click it, give a short subject (e.g. "Voice won't connect on desktop") and a description, and submit. Your ticket goes privately to the server's staff, no one else sees it.
A staffer replies in your DMs
When a staff member claims your ticket, Garrison opens a private one-to-one direct message between you and them, and that's where it gets worked out. Keep an eye on the Messages button (the chat-bubble, top-right) for their reply.
See what's been fixed
When a ticket is closed, some servers post a short read-only "resolved" note (the subject and the fix) to a public channel, so the whole community can see common issues and their solutions without anyone's private conversation being exposed.
No life-buoy button on your server? That server hasn't turned on support tickets, ask an owner or admin, or check the FAQ & Troubleshooting and the feature pages in the sidebar, most questions are answered there in depth.
Running support on your server
Support tickets are opt-in per server and take a minute to set up. You'll need a role with Manage Messages to handle tickets.
Turn it on
Create (or pick) a staff-only channel to act as your ticket log, then set it as the server's ticket-log channel in Server Settings. As soon as it's set, the 🛟 submit button appears for members, and every new ticket is logged into that channel as unclaimed. Restrict that channel to your staff roles so only they can see incoming tickets.
Work the queue
Staff get an inbox button next to the life-buoy (shown to anyone with Manage Messages). It lists submitted tickets. Claim a ticket to open a private DM with the person who opened it and sort it out there; when you're done, close it and record the resolution.
Publish resolved tickets (optional)
If you set a resolved-tickets channel, closing a ticket posts a tidy read-only summary (subject + resolution) there for the whole server, a self-building, public knowledge base of fixes. The private DM stays private; only the summary you write is shared. Leave it unset to keep closures fully internal.
Tickets and the staff DM are ordinary private conversations on your own server, the operator can see them, the way any support desk works. They are not end-to-end encrypted; for that, use an encrypted channel.