Tickets
Tickets give members a structured way to reach staff privately. AIO creates a dedicated channel per ticket, tracks status, and supports transcripts when a ticket closes.
What it does#
Members open tickets through panel buttons in a channel or via slash commands (when panels are configured). Each ticket gets its own channel visible to the opener and staff roles you define. Staff can claim, respond, and close tickets; closing can generate a plain-text transcript for your records.
Feedback prompts (optional) let members rate support after closure. Dashboard stats summarize volume and outcomes over time.
Dashboard path#
Dashboard → Servers → {Guild} → Tickets
Turn tickets on, configure categories and staff roles, and create at least one panel. Panels are the buttons members click to open a ticket type (support, bug report, suggestion, and others depending on your setup).
Key settings#
| Setting | Free | Pro |
|---|---|---|
| Active panels | 1 | More panels |
| Open tickets per member | 1 | Higher limits |
| Transcript format | Plain text | HTML transcripts on Pro |
| Staff roles & categories | Yes | Yes |
| Ticket stats in dashboard | Yes | Yes |
Assign staff roles that can view ticket channels but keep them below AIO’s role so the bot can manage channels and permissions.
Related features#
- Guide: Ticket panel — step-by-step panel setup
- Logging — audit ticket-related moderation in log channels
- Moderation — escalate from a ticket to a formal case if needed
- Welcome — point new members to your ticket panel in welcome text
Staff workflow#
Define who may claim tickets—usually @Support or @Moderator. Pin internal guidelines in your staff room: response time targets, when to escalate to Moderation, and how to label bug vs suggestion tickets. Closed tickets lock the channel and schedule deletion; download transcripts before cleanup if your policy requires long-term storage.
On Free, plain-text transcripts suit most teams. Pro HTML transcripts help if you paste records into external tools. Either way, treat transcripts like sensitive member data; restrict access to staff roles.
Common issues#
- Panel button does nothing — confirm tickets are enabled and the panel is active; see Guide: Ticket panel
- Member cannot open a second ticket — Free tier allows one open ticket per user; close the existing ticket first
- Staff cannot see the channel — check category permissions and that staff roles were selected on the panel
Feature overview: Tickets.