Why ticket chaos kills RP servers faster than bad RP does
Most server owners think their problem is "players don't play seriously". Talk to a struggling server's staff for an hour and you'll find the real problem: tickets live in DMs, three mods independently "handle" the same player report, the whitelist queue has 40 unread applications, and the bug-report channel is buried under "why don't you ban X" messages. That's not a player problem. That's an ops problem.
A clean ticket structure does three things: it routes the right work to the right person, it gives players a paper trail when they feel ignored, and it surfaces metrics so you can see when SLAs are slipping before players churn.
What the generator above produces
- Category table: typically 6–9 ticket categories (whitelist-apply, player-report, bug-report, support, ban-appeal, comp-request, suggestions, partnerships) with handler role and priority level for each.
- ASCII routing flowchart: player opens ticket → bot asks type → routes to correct staff queue.
- Ticket lifecycle: OPEN → CLAIMED → IN PROGRESS → RESOLVED → CLOSED, with rules for each transition (e.g. "don't work on unclaimed tickets", "handler must respond within SLA before escalation").
- Priority levels: critical / high / normal / low with specific examples per level (exploit/harassment = critical, whitelist app = normal).
- SLA targets per category: critical 5 min, high 30 min, normal 24 h, low 72 h — adjusted to your staff size.
- Escalation rules: who to ping if SLA missed, how to hand off, anti-pattern list ("don't handle tickets in DMs", "don't solo-ban").
Best practices we encode
One ticket category per logical workflow
Don't mix "player report" and "bug report" in the same channel. They're different teams (staff vs. dev), different SLAs (urgent vs. async), and different evidence requirements. Each category should map to one queue.
Staff size determines depth, not breadth
A 3-person team can't maintain 12 ticket categories — half will rot. Better to have 4 broad categories with sub-types via bot dropdown than 12 channels with one stale message each. The generator scales depth to your staffCount.
Auto-claim on first response
Configure Ticket Tool / Carl-bot to auto-claim a ticket when a staff member sends the first message. Without this, two staff "handle" the same ticket independently — wasted time and inconsistent verdicts.
Public SLA, private metrics
Post your SLA targets in #how-to-open-a-ticket so players know what to expect. Track actual response times privately (KeepGrid Pro does this automatically via Tickets SLA in weekly reports). The gap between posted SLA and actual SLA is your operational debt.
Escalation with a clock
Every escalation rule needs a time component: "If a critical ticket has no response in 15 minutes, ping @Head Admin." Without the clock, escalation is a polite suggestion, not a process.
Common mistakes to avoid
- Tickets in DMs. Players DM individual staff, conversations get lost, no audit trail. Forbid this in your Staff SOP and route everything through the ticket system.
- One mega-channel for "all support". New players don't know if their question is bug, RP, or admin. Two mods take it; nobody owns it. Split into specific categories.
- No closing protocol. Tickets stay "open" for weeks. Set a rule: a ticket that's been resolved-but-not-closed for 48h auto-closes with a satisfaction prompt.
- Whitelist applications mixed with general support. Whitelist has its own SLA, its own reviewers, its own outcome (accept/deny). Always separate.
- No comp-request channel for paid VIP servers. If players can pay for VIP and lose items, they need a clear path to compensation requests. Otherwise refunds happen via Stripe disputes.
FAQ
Which Discord ticket bot should I use?
For most RP servers under 500 members, Ticket Tool is the easiest setup with a generous free tier. Carl-bot has more sophisticated routing rules but requires Premium for advanced features. Dyno is similar to Carl-bot. The generator above produces output that works with all three — it specifies categories, channel names, and routing logic, not bot-specific configs.
How fast should we respond to player reports?
Critical reports (active exploit, harassment, slur usage) should be acknowledged in 5 minutes. Normal reports (general rule violation, RP dispute) get 30 minutes during active hours, up to 24 hours overnight. Posting an explicit SLA in #how-to-open-a-ticket sets expectations and reduces 'why are you ignoring me' messages.
Should ban appeals go through the same system as new whitelist apps?
No. Ban appeals need different reviewers (typically Head Admin+, not Mod), different evidence (the ban itself plus the appeal), and a different verdict format (overturn / reduce / uphold). Always a separate ticket category with its own SLA — usually 48h since these need careful review.
Can I run this without paying for Ticket Tool Premium?
Yes. The generator's output uses only free-tier features: numbered categories, basic routing, single-message close logic. Premium adds nice-to-haves like auto-archive and detailed analytics, but the core flow works on free. KeepGrid Pro adds Tickets SLA tracking on top of whatever bot you use.
How do I keep tickets organized when staff turnover is high?
Two things: (1) Document the lifecycle in your Staff SOP so a new mod can read 5 minutes and start working tickets correctly. (2) Use role-based ticket access, not user-based — when a mod leaves, you remove their role and they lose access automatically. Don't tie ticket permissions to specific people.
Related tools
- Staff SOP Generator — define who handles which ticket category and the response SLAs.
- Discord Permission Matrix — make sure ticket channels have the right view/send permissions per role.
- Whitelist Rubric — formalize the most common ticket type so reviewers don't score inconsistently.
Want all 13 docs + Launch OS install?
Ticket Routing is one of 13 documents in the full KeepGrid pack. The full pack also installs the Tickets category (whitelist-apply, player-report, bug-report, ban-appeal, etc.), wires them with the right permissions, and pins your #how-to-open-a-ticket guide. See all plans — from Docs Pack $19 to Launch OS + Pro $59 + $19/mo.