Docs

Ticket System

Professional support ticket management

🎫 What is the Ticket System?

The ticket system lets your members create private support channels to get help from your staff team. Think of it like a help desk - members click a button, and a private channel is created just for them and your staff.

How to Set Up Tickets (Step-by-Step)

Follow these steps exactly. Each step tells you exactly where to click in the dashboard.

01

Open the Dashboard

Go to modora.gg/dashboard and log in with Discord. On the 'Your Servers' page, click on your server name to open it.

Dashboard → Your Servers → [Click your server]
02

Enable the Ticket Module

If you see a 'Modules' tab, open it. Find 'Tickets' in the module list. If it has a disabled/off switch, turn it ON. Then click the Tickets card to open it.

Server Overview → Modules → Tickets (enable if off) → Click Tickets
03

Go to Panels and Create One

In the Tickets section you'll see tabs like Overview, Panels, Logs. Click 'Panels'. Then click the 'Create Panel' or '+ New Panel' button.

Tickets → Panels tab → Create Panel
04

Choose the Channel

In the create/edit panel form, find 'Channel' or 'Panel Channel'. Click the dropdown and select the text channel where you want the ticket button to appear (e.g. #support or #create-ticket).

Panel form → Channel dropdown → Select your channel
05

Add Categories (Optional)

Categories let you have different buttons (Support, Billing, etc.). In the panel editor, look for 'Categories' or 'Buttons'. Add categories like 'General Support', 'Billing', 'Technical'. Each becomes a separate button.

Panel form → Categories/Buttons → Add category
06

Select Staff Roles

Find 'Staff Roles' or 'Support Roles' in the form. Add the Discord roles that should be able to see and respond to tickets (e.g. Moderator, Admin). Anyone with these roles can help in tickets.

Panel form → Staff Roles → Select your mod/admin roles
07

Customize the Panel Message

Edit the 'Message' or 'Description' field. This is the text that appears above the button. Example: 'Need help? Click the button below to create a support ticket!'

Panel form → Message/Description field
08

Save and Deploy

Click 'Save' or 'Deploy'. The panel will be sent to your chosen channel. Members will see the message and a button. When they click it, a private ticket channel is created automatically.

Panel form → Save / Deploy button

✅ That's it!

Members can now click the button in that channel to create a ticket. A private channel will be created automatically for them and your staff.

What Can Tickets Do?

Multiple Categories

Organize tickets by type - support, billing, technical, etc.

Automatic Transcripts

When a ticket closes, a full transcript is saved automatically

Ticket Claiming

Staff can 'claim' tickets so everyone knows who's handling it

Priority Levels

Mark tickets as low, medium, high, or urgent priority

Rating System

Members can rate their experience after the ticket closes

Analytics Dashboard

See stats like average response time, tickets per day, etc.

Claim Emoji System

Each staff member picks a personal emoji that auto-reacts when they claim a ticket — see who's handling what at a glance.

Staff Overview Page

Public live page (token-protected) showing the ticket queue, claim status, and response times.

Auto Reminders

Automatically nudge staff or the opener when a ticket goes quiet, with configurable thresholds.

Verification Gate

Optionally make the opener verify themselves before they get access to their own ticket, so staff know who they are helping. Off by default.

Setting Up an Admin Role (Optional)

By default, only staff roles assigned to specific panels can manage tickets. But you can set up an "Admin Role" that can manage ALL tickets, no matter which panel they're from.

How to Set It Up:

01

Go to **Dashboard → Tickets → Settings**

02

Find the "Ticket Admin Role" field. It accepts more than one role.

03

Select the role you want (usually your Admin or Owner role)

04

Click "Save"

Info

**What this means:** Anyone with this role can use ticket commands (like /ticket close, /ticket assign, etc.) in ANY ticket, even if they're not assigned to that specific panel.

Claim Emoji System

Each staff member can pick a personal unicode emoji. When they claim a ticket, the bot auto-reacts on the welcome message — so at a glance anyone can see who's on which ticket without opening each channel.

How to configure

01

Set your own emoji: run /claimemoji me and pick one from the list. Your emoji only appears on tickets you claim.

02

Set someone else's emoji: admins with Manage Server can run /claimemoji set @staff to assign emojis in bulk.

03

Two toggles per user — react (auto-react on claim, default on) and rename (also prepend the emoji to the channel name, default off).

04

Review everyone's emojis with /claimemoji list, or clear a user's emoji with /claimemoji clear.

Rules & limits

  • Unicode emojis only — Nitro/custom server emojis are not allowed so reactions work consistently for all staff.
  • Each emoji can be used by only one staff member. Already-claimed emojis are hidden from the picker.
  • Channel renames are limited by Discord to 2 per 10 minutes. On very busy channels a rename may be skipped, but the reaction always applies.

Ticket Commands

Here are all the commands you can use in ticket channels:

👥 Commands for Staff Members

Only staff members (or people with the Admin Role) can use these commands

/ticket claim

Claim this ticket so other staff know you're handling it. Also flips the welcome button to Unclaim and applies your claim emoji.

/ticket unclaim

Release a claim — your own as the claimer, or any claim if you have admin / Manage Channels.

/ticket close [reason]

Close the ticket. You can add an optional reason like 'Issue resolved'

/ticket close Problem fixed!

/ticket assign [user]

Assign this ticket to a specific staff member so everyone knows who's handling it

/ticket assign @Moderator

/ticket priority [level]

Set how urgent this ticket is: low, medium, high, or urgent

/ticket priority high

/ticket escalate [reason]

Escalate the ticket (mark it as needing higher-level attention)

/ticket escalate Needs admin review

/ticket note [staff] [user]

Open a private notes thread for internal staff discussion. Optionally ping staff roles and/or include a specific user.

/ticket info

Show ticket details: category, opener, priority, claimer, SLA, created/claimed timestamps.

/ticket add [user]

Add another person to the ticket so they can see and respond

/ticket add @Helper

/ticket remove [user]

Remove someone from the ticket

/ticket remove @Helper

/ticket rename [name]

Rename the ticket channel. Respects Discord's 2-renames-per-10-minutes limit.

/ticket move [category]

Move the ticket to another Discord channel category.

/ticket transfer [panel]

Move this ticket to a different panel (like moving from General to Technical)

/ticket transfer Technical Support

/ticket reply [quick_reply] [format]

Send a pre-configured quick reply / canned response. Format: plain or embed.

/ticket rate

Send (or re-send) the rating request to the ticket opener.

/ticket requestclose

Ask the member if they want to close the ticket. They'll get a button to confirm.

🎨 Personal Settings

Commands every staff member can run for themselves. /claimemoji me is open to any staff; set and clear require Manage Server.

/claimemoji me [emoji] [react] [rename]

Set your personal claim emoji. Autocomplete shows available unicode emojis with already-claimed ones filtered out.

/claimemoji me 🔥

/claimemoji set [user] [emoji] [react] [rename]

(Admin) Assign a claim emoji to another staff member.

/claimemoji set @Alice 💙

/claimemoji list

Show everyone's current claim emoji and react/rename settings.

/claimemoji clear [user]

(Admin) Remove a staff member's claim emoji configuration.

📜 History Commands

View past tickets and activity

/userhistory tickets [user] [range]

See all tickets you've created. Range: 1d, 7d, 2w, 30d, 3m, 1y, or all (e.g. /userhistory tickets 1d)

/staffhistory tickets [user] [range]

See how many tickets a staff member has handled (staff only). Range: today, 1d, 7d, 2w, 30d, 3m, 1y, or all

/staffhistory tickets @Moderator 7d

Common Questions

Was this page helpful?