What it does
- Offer several ticket types
- Create multiple panels with buttons or menus, choose labels and support roles, and set an intake form for each option. Welcome messages and controls use the shared message editor.
- Coordinate staff
- Support staff can claim, unclaim, add participants or request closure. Saved settings include cooldowns, close-on-leave behavior and automatic closure after inactivity.
- Keep transcripts private
- Ticket transcripts require Discord sign-in. The opener, people who wrote in the ticket and authorized ticket staff can access them, as can flanker site admins. They are not public search pages and are automatically deleted after one year.
- Limit ticket floods
- Configured AntiRaid checks can detect ticket bursts across distinct accounts, block new tickets during raid mode and remove recent flanker tickets tied to flagged raiders.
Get started
Type the slash command in Discord and fill in its fields, or mention flanker before it. Commands still require their usual permissions.
- Run guided setup with Manage Server access.
/ticket setup - Choose support roles, a log channel and the channel where the panel should appear.
- Review panels and ticket options.
/ticket config - Customize ticket messages, questions and controls from the Tickets page on your server's dashboard.
Common questions
Can a ticket panel have more than one option?
Yes. A panel can include multiple ticket types, each with its own label, support roles, category, welcome message and questions.
Can anyone with a transcript link read it?
No. The website requires Discord sign-in and checks ticket participation or staff access. Possession of the URL alone does not grant access.
Does flanker also support staff applications?
Yes. Applications are a separate configurable feature with forms and staff review controls. The documentation covers both tickets and applications.