ποΈ Ticket - Ticket System
Advanced support system with private tickets, AI priority, quick responses, and more.
π Overviewβ
Yume-chan's ticket system allows you to create a professional support system in your server. Users can create private tickets to report issues, request help, or ask questions, and your support team can manage them efficiently from Discord or from the Web Panel.
β¨ Key Featuresβ
- π€ AI Classification: Automatic priority based on ticket content
- π Unlimited Categories: Organize tickets by type (support, report, suggestions, etc.)
- π Notifications: Automatic alerts for the support team
- π Statistics: Real-time metrics of open, closed tickets and response times
- π¨ Customizable Panel: Create panels with buttons or dropdown to create tickets
- π Transcripts: Save complete conversations when closing tickets
Commandsβ
/ticket setupβ
Configure the ticket system
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
categoria | Channel | β Yes | Category where tickets will be created |
soporte | Role | β Yes | Support role |
Configurable from: Tickets > Configuration
Access panel.yumechanbot.com
Example:
/ticket setup categoria:πTickets soporte:@Support
/ticket panelβ
Create a ticket panel
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
titulo | String | β No | Panel title |
Configurable from: Tickets > Create panel
Access panel.yumechanbot.com
Example:
/ticket panel titulo:Yume-chan Support
/ticket cerrarβ
Close the current ticket
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
razon | String | β No | Reason for closing |
Example:
/ticket cerrar razon:Problem resolved
/ticket addβ
Add a user to the ticket
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
usuario | User | β Yes | User |
Example:
/ticket add usuario:@Admin
/ticket removeβ
Remove a user from the ticket
Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
usuario | User | β Yes | User |
Example:
/ticket remove usuario:@User
π Premium Featuresβ
π Auto-Close Inactive Tickets (Starter+)β
Automatically closes tickets that have had no activity for X days.
Features:
- β° Configurable from 3 to 30 days depending on your tier
- π€ Automatic review every 6 hours
- π Automatic close message with reason
- π Transcript saved before closing
Limits per Tier:
- Free: 3 days maximum
- Starter: 7 days maximum
- Pro: 14 days maximum
- Ultra: 30 days maximum
Configuration:
- Go to Web Panel β Tickets β Settings
- Enable "Auto-Close Inactive Tickets"
- Configure the inactivity days
- Save changes
How it works:
- The bot checks all open tickets every 6 hours
- Checks the last message in each ticket
- If more days than configured have passed, it automatically closes
- Sends notification: "Auto-closed due to inactivity (7 days without response)"
π Private Staff Notes (Starter+)β
Add internal notes visible only to the support team.
Features:
- π Notes visible only to staff
- π€ Identifies who wrote each note
- π Timestamp for each note
- π Included in transcripts marked as PRIVATE
- ποΈ Delete notes when needed
Use Cases:
- "User seems to be a troll, check history"
- "Already contacted admin, waiting for response"
- "Third similar ticket, could be a system bug"
- "Temporary solution applied, check in 24h"
How to use:
- Open a ticket from the Web Panel
- Click on the "π Notes" tab
- Write your note (not visible to the user)
- Click "Add Note"
In Transcripts:
---
# π PRIVATE STAFF NOTES
[01/13/2026 20:30] Admin#1234:
User reported this issue 3 times, possible recurring bug.
[01/13/2026 21:15] Support#5678:
Escalated to technical team.
π Quick Response Templates (Starter+)β
Save predefined responses for frequently asked questions.
Features:
- π¬ Saved responses with dynamic variables
- π Organize by categories (General, Technical, FAQ, Policies)
- π Usage counter for each template
- β‘ Quick insertion from chat
- π¨ Real-time preview
Available Variables:
{user}β User mention{username}β User name{ticket}β Ticket number{server}β Server name{category}β Ticket category{date}β Current date{time}β Current time
Limits per Tier:
- Free: 0 templates
- Starter: 5 templates
- Pro: 20 templates
- Ultra: Unlimited
Template Example:
Hi {user}! Thanks for opening a ticket in {server}.
I've received your ticket #{ticket} in the {category} category.
A team member will respond soon.
Date: {date} - Time: {time}
How to use:
-
Create Template:
- Go to Web Panel β Tickets β Settings β Templates
- Click "New Template"
- Write name, choose category and content
- Use dynamic variables
- Save
-
Use Template:
- Open ticket from Web Panel
- In the chat, click "Quick Responses"
- Select your template
- It inserts automatically with replaced variables
- Edit if needed and send
π Transfer Tickets between Staff (Starter+)β
Reassign ticket ownership between team members.
Features:
- π₯ List of staff members with support roles
- π Complete transfer history
- π Discord notification of the change
- π Server log record
Use Cases:
- Specialization: Transfer to technical expert
- Shift Change: Pass tickets to next shift
- Escalation: Transfer to supervisor
- Redistribution: Balance workload
- Absence: Transfer before leaving
How to use:
- Open a claimed ticket from Web Panel
- Go to the "Info" tab
- Click "Transfer to Another Staff" button
- Select the new staff member
- Automatic confirmation
Discord Message:
π Ticket Transferred
@StaffA has transferred this ticket to @StaffB.
From: StaffA#1234
To: StaffB#5678
Transfer History:
Each ticket maintains a complete record:
- Who was the previous staff
- Who is the new staff
- Who made the transfer
- Exact timestamp
π Response Time Analytics (Pro+)β
Detailed metrics on support team performance.
Features:
- β±οΈ Average first response time
- π Average resolution time
- π Time distribution by hour of day
- π₯ Individual staff member performance
- π Metrics by ticket category
- π Period comparison (week/month/year)
- π Bottleneck identification
Available Metrics:
| Metric | Description |
|---|---|
| First Response | Time from creation to first staff message |
| Total Resolution | Time from creation to ticket closure |
| Median | Central value (more reliable than average) |
| Distribution | Tickets by time range (0-1h, 1-4h, etc.) |
| By Staff | Individual performance of each member |
| By Category | Specific times by ticket type |
Use Cases:
- Staff Evaluation: Identify who responds fastest
- Planning: Detect peak ticket hours
- Continuous Improvement: Identify slow categories
- Reports: Generate monthly performance reports
How to use:
- Go to Web Panel β Tickets β Analytics
- Select date range (Last week/month/year)
- Filter by category or staff member (optional)
- Review key metrics:
- β±οΈ First response average
- π Resolution average
- π Distribution chart
- Compare periods to see improvements
Available Filters:
- π Custom date range
- π By specific category
- π€ By staff member
- π― By status (open/closed)
Sample Results:
β±οΈ First Response
- Average: 2h 15m
- Median: 45m
- Fastest: 5m
- Slowest: 12h
π Total Resolution
- Average: 1d 4h
- Median: 8h
- Fastest: 15m
- Slowest: 5d
π Distribution
- 0-1h: 45% (23 tickets)
- 1-4h: 30% (15 tickets)
- 4-12h: 15% (8 tickets)
- +12h: 10% (5 tickets)
β Post-Close Feedback System (Pro+)β
Collect user opinions after closing tickets.
Features:
- β Rating from 1 to 5 stars
- π¬ Optional additional comment
- π Satisfaction analytics
- π Quality trends by period
- π₯ Specific feedback by staff member
- π Received feedback notifications
How it works:
- On ticket close: Staff closes ticket normally
- Automatic DM: User receives a private message with:
- Buttons from 1 to 5 stars
- Option to add comment
- User rates: Click on desired stars
- Optional comment: Modal to leave additional comment
- Saved: Feedback is saved in system
- Notification: Staff receives notification in logs
- Analytics: Data aggregated in satisfaction metrics
Feedback Message:
β How was your experience?
We'd love to know your opinion about ticket #42.
How would you rate the support you received?
[β] [ββ] [βββ] [ββββ] [βββββ]
Feedback Analytics:
The Web Panel displays satisfaction metrics:
- π Rating distribution (% per stars)
- β Overall average rating
- π₯ Rating by staff member
- π Trends over time
- π¬ Featured recent comments
Sample Analytics:
β Average Rating: 4.2/5
π Distribution:
5β: 45% (23 tickets)
4β: 30% (15 tickets)
3β: 15% (8 tickets)
2β: 7% (4 tickets)
1β: 3% (2 tickets)
π¬ Recent Comments:
"Quick response and effective solution" - 5β
"Good service but took a while" - 4β
Use Cases:
- Quality Assessment: Measure user satisfaction
- Process Improvement: Identify areas for improvement
- Recognition: Highlight staff members with best feedback
- Problem Detection: Identify negative patterns
π« User Blacklist System (Pro+)β
Block problematic users from creating new tickets.
Features:
- π« Permanent or temporary blocking
- β° Automatic expiration of temporary blocks
- π Documented reason for each block
- π Blacklist statistics
- π Notification when blocked user attempts to create ticket
- ποΈ Remove users from blacklist
Block Types:
| Type | Duration | Use Case |
|---|---|---|
| Permanent | No expiration | Users with unacceptable behavior |
| Temporary | 1-90 days | Users with temporary bad behavior |
Use Cases:
- Abusive Users: Block users who insult staff
- Ticket Spam: Users who repeatedly create fake tickets
- ToS Violation: Users who violate terms of service
- Cooldown: Temporary block for users who abuse system
- Ban Appeal: Banned user who keeps creating tickets
How to use:
-
Add to Blacklist:
- Go to Web Panel β Tickets β Settings β Blacklist
- Click "Add User"
- Enter user's User ID
- Choose type (Permanent/Temporary)
- If temporary, select duration in days
- Write reason for block
- Click "Block"
-
Remove from Blacklist:
- Go to blocked users list
- Find the user
- Click "Remove Block"
- Automatic confirmation
Message to Blocked User:
When a blocked user attempts to create ticket:
π« You cannot create tickets
You are currently blocked from creating tickets in this server.
Reason: Fake ticket spam
Type: Temporary
Expires: 2026-01-20
If you believe this is an error, contact an administrator.
Blacklist Statistics:
The Web Panel displays:
- π Total blocked users
- π Permanent blocks
- β° Active temporary blocks
- π Expired/removed blocks
- π Block history
Auto-Expiration:
Temporary blocks are automatically deactivated:
- β When expiration date is reached
- β No manual intervention needed
- β User can create tickets again
- β Record remains in history
Sample Statistics:
π Total: 15 blocked users
π Permanent: 5 (33%)
β° Active Temporary: 7 (47%)
π Removed: 3 (20%)
π¨ Web Panel - Advanced Managementβ
Access panel.yumechanbot.com to:
π Dashboardβ
- View real-time statistics
- Open, claimed, closed tickets
- Distribution by priority
- Active tickets with direct access
π« Ticket Managementβ
- View all tickets (filter by status/priority)
- Respond from the web panel
- Claim, close, or change priority
- Use quick response templates
- Add private notes
- Transfer to another staff
π Categoriesβ
- Create unlimited categories (per tier)
- Customize emoji, color, and description
- Configure default priority
- Reorder categories
- Delete obsolete categories
βοΈ Settingsβ
- Configure support roles (up to 5 with Starter)
- Logs and transcripts channel
- Selection mode (buttons/dropdown)
- Auto-close inactive tickets
- AI Priority classification
- Automatic transcript on close
- Response templates
- And more...
π Tier Comparisonβ
| Feature | Free | Starter | Pro | Ultra |
|---|---|---|---|---|
| Categories | 3 | 10 | 25 | β |
| Simultaneous Tickets | 3 | 10 | 25 | β |
| Support Roles | 1 | 5 | 10 | β |
| Dropdown Mode | β | β | β | β |
| Chat from Panel | β | β | β | β |
| Transcripts | β | β Basic | β Complete | β Complete |
| AI Priority | β | β | β | β |
| Auto-Close | β | β 7 days | β 14 days | β 30 days |
| Private Notes | β | β | β | β |
| Templates | β | 5 | 20 | β |
| Transfer Tickets | β | β | β | β |
| User History | β | β | β | β |
| Response Time Analytics | β | β | β | β |
| Post-Close Feedback | β | β | β | β |
| User Blacklist | β | β | β | β |
| Export to CSV | β | β | β | β |
Unlock all premium features from $3.99/month with Server Starter.
View Premium Plans π
π Notesβ
- Tickets are created by clicking a panel button
- An automatic transcript is generated on close
- Only the support team can see tickets
- AI automatically classifies priority
- Private notes are NOT visible to the ticket user
- Templates update in real-time with variables
π FAQβ
How does AI priority classification work?
The bot analyzes the initial message content using keywords:
- π΄ Urgent: "urgent", "emergency", "critical", "hacked"
- π High: "important", "serious problem", "can't"
- π‘ Medium: "problem", "error", "bug", "help"
- π’ Low: "suggestion", "idea", "proposal"
Can I have multiple ticket panels?
Yes, you can create panels in different channels with different configurations.
Do transcripts include private notes?
Yes, but they are clearly marked as "π PRIVATE STAFF NOTES" so they are not confused with regular messages.
What happens if I transfer a ticket that is not claimed?
It's not possible. Only tickets that are already claimed by a staff member can be transferred.
Can templates be edited after creating them?
Yes, you can edit name, content, and category at any time from the Web Panel.
Is feedback mandatory for the user?
No, feedback is completely optional. The user can ignore the DM if they don't wish to rate.
Do analytics show real-time data?
Yes, metrics are automatically updated every time a ticket is closed or responded to.
Are temporary blocks automatically removed?
Yes, when the expiration date is reached, the user can create tickets again automatically.