General support
One open category for questions, routed to all mod roles with transcripts on.
Home / Rust Console Ticket Bot
Rust Console Feature PageRust Console Ticket Bot and Support Panel
Helios gives Rust Console Edition server owners a Discord support ticket panel so players can open private tickets and staff can respond in dedicated channels. Set ticket categories, mod roles, and transcript routing once, then run player support from one place across PlayStation and Xbox communities.
The ticket system keeps support organized: one open ticket per user, private channels under the category you choose, close confirmation, and saved transcripts so nothing gets lost.
Configure categories and mod roles first, then test the panel with a non-admin account before you announce it to players.
Quick take
A Rust Console ticket panel works best when owners define clear categories, restrict sensitive ones with required roles, route transcripts to a staff channel, and test the full open-to-close flow with a non-admin account before launch.
At a glance
- This page explains how the Helios ticket panel works and how to roll it out.
- It covers categories, required roles, mod access, transcripts, and close behavior.
- Use the linked docs to configure the panel before announcing it to players.
What this feature solves
- Replaces scattered DMs and public help requests with structured private tickets.
- Routes each ticket to the right staff with mod roles and category permissions.
- Keeps a record of every resolved issue with saved transcripts.
Who this is for
- Owners who need an organized support flow instead of ad-hoc help channels.
- Moderators handling reports, appeals, purchases, and player questions.
- Servers that want auditable support history through transcripts.
What the ticket panel includes
- Public ticket creation panel posted in a channel you choose.
- Ticket categories with descriptions and optional required roles.
- Private ticket channels created under a Discord category you select.
- Ticket mod roles that can view and respond, plus transcript channel routing.
- One open ticket per user, close confirmation, manual delete, and auto-delete after 30 minutes.
Recommended rollout sequence
- Confirm premium is active, then pick the channel for the public panel.
- Create categories, set descriptions and optional required roles, and choose where private channels are created.
- Add mod roles and a transcript channel, then test open-to-close with a non-admin account.
Common server-owner scenarios
Purchases and store
A category gated by a buyer or supporter role so only relevant players open it.
Player reports
A reports category routed to senior staff, with transcripts kept for review.
Appeals
A restricted appeals category so bans and disputes stay private and documented.
Validation and troubleshooting checkpoints
- Test with a non-admin account so you see exactly what players experience.
- Confirm private channels are created under the right Discord category.
- Check that transcripts route to your chosen channel after a ticket closes.
Related setup docs and cluster pages
Share-ready talking points
Quick summary to share
Share this when teammates ask how the ticket panel should be set up.
- Lead with clear categories and required roles on sensitive ones.
- Include the setup link so the reader can act immediately.
- Tie wording to real controls: categories, mod roles, transcripts, close behavior.
Useful next links
Use these follow-up links based on what the team needs next.
- Setup path: Ticket Panel Guide and Start Here.
- Roles path: Permissions and Roles.
- Comparison path: Comparison Guide.
Built for Rust Console owner workflows
Linked setup path
This page points back to the ticket panel setup guide so owners move from overview into the exact configuration steps.
Daily staff use
The ticket system is tuned around real support work: categories, mod access, and transcripts.
Role-aware rollout
Helios points owners toward required roles on sensitive categories and dedicated mod access.
Clear next steps
This cluster links back to setup docs, roles, and troubleshooting paths when tickets misbehave.
Frequently asked questions
- What does the Rust Console ticket panel do?
- It posts a public ticket panel in Discord so players can open private support tickets. Helios creates a private channel per ticket, routes it to your mod roles, and saves a transcript when the ticket closes.
- Can I limit who can open certain tickets?
- Yes. Each ticket category can have optional required roles, and you choose which Discord category the private channels are created under.
- What happens when a ticket is closed?
- Closing a ticket removes it from the open list, posts a delete prompt, and builds a text transcript routed to your transcript channel. Closed tickets can be deleted manually or automatically after 30 minutes.
- Is the ticket panel premium?
- Yes. The Helios ticket system is a premium feature and requires premium active on the Discord server.
Ready to run Rust Console support through a clean ticket panel?
Set categories and mod roles first, route transcripts to staff, then test the full flow with a non-admin account before you announce it.