GUIDE · TICKETS

How to Set Up a Discord Ticket Bot (Channels, Roles & Private Support)

A ticket flow gives members a private place to ask for help instead of posting in public channels. You need three things: a public channel where members open tickets, a ticket category where private ticket channels appear, and staff roles that can see and answer them. The steps below use ARK Bot, configured from /settings.

By ArkFlame · Published 2026-10-13 · 4 min read

Before you start

You need Manage Server permission to add the bot and administrator access to run /settings. Create (or pick) a staff role for support helpers and a senior staff role for sensitive reports. Create two channel categories yourself: a ticket category for general requests and a staff-report category for reports about staff. ARK Bot creates ticket channels inside your existing categories — it does not create categories.

Choose a public ticket-opening channel

Pick a channel every member can read, such as #support or #help. Members should be able to view it and click buttons, but not send messages there — keep the channel clean so the ticket panel stays visible. You will post the ticket panel here in a later step.

Configure the private ticket category

Run /settings → Tickets. Set the ticket category to the category you created, and set the staff role so helpers can see new requests. Set the staff-report category and the senior staff role as well; reports in the Staff report category are visible only to senior staff. Optionally set a transcript channel to receive a transcript file when a ticket closes.

Define who can see staff reports

The Staff report category exists so members can report a staff member without that person reading it. Only the senior staff role should have View Channel in the staff-report category. Deny View Channel for @everyone and for the regular staff role on that category. Double-check with Discord's preview (View as Role) before publishing.

Publish a panel and run a member test

Run /tickets in your public channel, or open /settings → Tickets → Preview/Publish to post the managed ticket panel. The panel heading reads “ARK Bot · Help Desk” and lists the categories Support, Report a player, Bug report, Booster rewards, and Staff report. Then test as a member: pick a category, complete the form, and confirm a private ticket channel opens that only you and staff can see. Reply in the channel, then press Close ticket and confirm the statuses move through open, closing, and closed.

How to avoid public report leaks

Most leaks come from category permissions, not the bot. Keep @everyone denied View Channel on both ticket categories, and grant access through the staff role instead. Remember that members with the Administrator permission bypass channel permission overwrites entirely — never grant Administrator to helpers who only need ticket access; the staff role is enough.

Troubleshooting

• Buttons do nothing. The panel message is stale or setup is incomplete. Re-run /tickets after fixing /settings, then run /setup-check.
• Bot cannot create the channel. The bot role lacks Manage Channels, or it sits below the roles it must manage. Move the bot role above the staff role and grant Manage Channels.
• Wrong staff role sees tickets. You set the staff role but not the senior staff role (or vice versa). Re-open /settings → Tickets and check both fields.

How ARK Bot handles tickets

Members pick a category and complete the form; each submission opens a private ticket channel inside the configured ticket category (or the staff-report category for Staff report). Staff reply in the channel and close it with Close ticket. Only proven behavior is described here: five categories, managed panel with Preview/Publish, private ticket channels, and open / closing / closed statuses.

Common mistakes

• Posting the panel in a channel members cannot see.
• Granting the regular staff role access to the staff-report category.
• Skipping the member test before announcing support.

FAQs

Why did my member's ticket open in the wrong category?

The category is chosen on the panel form, not by the bot. If Support requests land in the staff-report category, a member picked the wrong option — rename the panel buttons with plain verbs (“Get help” vs “Report staff”) and re-test as a member before announcing.

Can helpers see staff reports?

Only if you let them. The staff-report category must deny View Channel to the regular staff role and grant it only to the senior staff role. Audit this with Discord's View as Role preview after every permission change.

What happens to a ticket after Close ticket?

The ticket moves through open, closing, and closed. If you set a transcript channel in /settings → Tickets, a transcript file is delivered there for the record.

Conclusion

Configure the ticket category and staff roles in /settings, publish the ticket panel, and verify with a member test. Keep staff-report permissions tight and you have a support flow members can trust.

Related: Tickets feature · Setup guide