Limitations
Control who can create tickets and manage ticket volume with role restrictions, user limits, and server-wide capacity controls.
Access Control
White/blacklisted roles
Limit who can create tickets of this subject by setting roles that are allowed or disallowed to create tickets.
Configuration modes:
Whitelist mode - Only users with one of the specified roles can create tickets of this subject.
Blacklist mode - Users with any of the specified roles are prevented from creating tickets of this subject.
Benefits:
- Control access to specific ticket subjects
- Prevent abuse from problematic users or roles
- Create VIP or member-only ticket subjects
- Block new user spam until they're verified
Use cases:
- Whitelist premium member roles for exclusive support subjects
- Blacklist muted or restricted roles to prevent ticket spam
- Require verified member role before opening tickets
- Create department-specific subjects for certain teams
User Limits
Limit amount of tickets per user Premium
Limit how many tickets of this subject a user can have open at the same time.
How it works:
- Set a maximum number of tickets (e.g., 1, 2, or 3) per user for this subject
- When users reach the limit, they must close an existing ticket before creating a new one
- Applies only to this specific subject (other subjects have separate limits)
- Staff members can create tickets on behalf of users regardless of the limit
Benefits:
- Prevents users from flooding your system with multiple tickets
- Encourages users to resolve existing issues before creating new ones
- Keeps ticket queues clean and manageable
Use cases:
- Limit users to 1 ticket at a time for general support
- Allow 2-3 tickets for complex technical issues
- Force users to close resolved tickets before opening new ones
Cooldown between tickets Premium
Set a cooldown on how often a user can create tickets. This setting is a cross-subject cooldown, meaning it applies across all subjects in your server.
How it works:
- When a user creates a ticket, they must wait for the cooldown period before creating another ticket
- If users try to create a ticket during the cooldown, they're notified how long they must wait
- If multiple subjects have different cooldowns, the longest cooldown applies after creating any ticket
TIP
The bot has a minimum cooldown of 10 seconds to prevent extreme spam. Staff members are not affected by this setting and can create tickets regardless of the cooldown.
Benefits:
- Prevents users from rapidly creating multiple tickets
- Encourages users to formulate their issue properly
- Reduces duplicate tickets for the same issue
Use cases:
- Set a 5-minute cooldown for general support to prevent panic spam
- Use a 1-hour cooldown for low-priority subjects to encourage self-help
- Apply 24-hour cooldowns to suggestion subjects to prevent flooding
Server Limits
Limit amount of tickets of subject Premium
Limit how many tickets of this subject can be open at the same time across your entire server.
How it works:
- Set a maximum number of open tickets for this subject (e.g., 10, 50, 100)
- This limit is shared between all users - when the limit is reached, no one can create new tickets until one is closed
- Different subjects can have different limits
- Staff members can create tickets on behalf of users even at the limit
Benefits:
- Prevents your server from being overwhelmed with too many ticket channels
- Ensures you stay within Discord's channel limits (500 channels per server)
- Keeps your ticket system responsive and manageable
- Encourages staff to close resolved tickets to make room for new ones
Use cases:
- Set high limits (100+) for general support subjects with high volume
- Use lower limits (10-20) for specialized subjects requiring intensive support
- Limit suggestion subjects to prevent flooding the development team
- Allocate more capacity to important subjects and less to low-priority ones