Ticket Systems
Chapter 11 — How to handle support tickets professionally, from first response to close.
Ticket Tool (or an equivalent ticket bot) gives members a private channel to reach staff for support, reports, appeals, or purchases without cluttering public chat. As staff, tickets are one of your most regular responsibilities.
Handling a Ticket
- Claim the ticket if your team uses a claim system, so members aren't waiting on multiple staff members at once.
- Greet the member and ask clarifying questions if their initial message is unclear.
- Resolve what you can directly; escalate what you can't (see Chapter 19, Chain of Command).
- Keep the conversation professional and on-topic — tickets are not the place for casual chat unrelated to the request.
- Close the ticket once resolved, and log a summary if your setup requires it (common for ban appeals and reports).
Common Ticket Categories
| Category | Typical Handler |
|---|---|
| General support / questions | Any staff member |
| Player reports | Moderator+ |
| Ban appeals | Moderator+ (see Chapter 17) |
| Purchases / store issues | Designated staff or Admin |
| Bug reports | Any staff member — forward to developers/Admins |
GOLDEN RULE
Never leave a ticket open with no response for an extended period. Even a short "we're looking into this" keeps the member from feeling ignored.
Quick Review — Q&A
Q: What is the first step when handling a ticket, if your team uses a claim system?
A: Claim it, so the member isn't waiting on multiple staff members simultaneously.
Q: What should you do with a request you can't resolve yourself?
A: Escalate it through the proper chain of command rather than guessing or ignoring it.
Q: Why shouldn't a ticket be left unanswered for a long stretch?
A: The member may feel ignored — even a brief acknowledgment keeps trust while the issue is being looked into.