#Eğlence #Moderasyon #Yardımcı Araç #Müzik #Sosyal #Ekonomi #Oyun #Mizah #Seviye #Anime

Modern Tickets

•

Genel bakış

Komutlar

Karşılaştır

Support tickets that start in a direct message. Every ticket becomes a forum thread your team can claim, answer and close.

Tickets without the channel clutter

Support that starts in a direct message.

Members write to the bot, pick a category and answer a short form. Every ticket becomes a forum thread your team claims and answers — and, where you allow it, neither side has to give a name.

Add to Server Open your dashboard

Free, nothing to install, no account to make. Set up in about five minutes, or read the docs first.

@ Modern Tickets APP

MaraToday at 5:42 PM

hey, I can’t get back into my account

Modern TicketsAPPToday at 5:43 PM

🎫 Aurora · Support Pick the category that fits best. You’ll be asked a few short questions next.

🔑Account 🚩Report a member 💳Billing ⚖️Appeal

Cancel

Server Aurora · Expires in 5 minutes · Your message is saved as the description draft

A member writes, gets the panel, and the category they pick opens its own form. The bot’s real messages, redrawn.

31 Slash commands

7 Steps to set up

16 Categories per forum

0 Messages lost offline

How it works

One ticket, end to end

From the first message to the transcript. Nobody has to learn a command.

A member writes to the bot

Any direct message opens the panel. The first thing they typed becomes the draft of their answer.

In the member’s DMs

They fill in a short form

Each category asks its own questions, in a form you build. Oversized files are caught before anything is created.

In the popup a category opens

The team claims it

A forum post shows who opened it and what they answered, with controls only the right roles can use.

In your ticket forum

Closed, with a transcript

Both sides get a summary. The thread is locked and archived, never deleted, and the member can rate it.

Back in the member’s DMs

Features

Everything a support team keeps asking for

All of it free, with no paywall.

Tickets start in a DM

No channel to clutter and no button to hunt for. A member writes to the bot, picks a category and fills in a short form.
A queue you read at a glance

Every ticket is a forum post with its category tag and one of four states: unclaimed, claimed, awaiting user, closed.
Reply by name, or as the team

Staff choose their face when they claim and can switch later. Every message keeps the label it was sent with.
Notes, edits and retractions

Start a line with // and the member never sees it. Fix a sent message in both copies, or pull it back out of their DMs.
Nothing typed is lost

Messages sent while the bot is offline are relayed afterwards and marked as late. Anything typed during a prompt is queued, not dropped.
Files in both directions

Attachments travel both ways. A file too large for the server is caught, and the member decides what happens before anything is sent.
One inbox, many servers

Members keep one DM thread however many of their servers use the bot. Every message says which server and which ticket it belongs to.
Transcripts that stay current

Every closed ticket gets a private web page, built fresh on each visit. The team’s copy keeps its notes, the member’s never shows them.
Ratings on close

One to five stars and an optional comment, counted per person, for the whole team and posted to your log channel.
A team hub that updates itself

Pinned in your forum: open tickets, the claim queue, the oldest unclaimed one, a leaderboard and the average rating.
Priorities, hand-overs, close requests

Mark a ticket high or urgent, transfer it, move it to another category, or ask the member whether it can be closed.
Only the commands each person can use

Members see their own commands, your team sees ticket commands inside tickets, admins see the rest. Approve it once and it follows your roles.

Anonymity

Names are optional, on both sides

For reports, appeals and anything about a person with a role.

Your team decides what the member sees

Claiming asks once: your name, or Team member. Moderators handling a report stay unnamed, the community manager answering a question does not.

By name

Alex Team member · Aurora

As Team member

Team member Aurora

Answering as Team member is its own permission. Only administrators have it until you name the roles that may.

The member can stay unnamed too

Switch it on for a category and its form grows a tick box. A ticket opened that way carries a code instead of a name: no mention, no avatar, no roles, no history.

🎫 Ticket q8Zt4m · #131 Anonymous #A7F3C 🕶️ Opened anonymously — this server cannot see who it is, and neither can its admins

Require a name

Nobody on your server can look behind the code, administrators included. Same person, same code on one server: you spot a repeat reporter without a name. Abuse it and lose it. What they already wrote stays anonymous.

No code

Design every message, and the popup behind every button

Two builders on the website, no embed JSON. What you build is what the bot sends.

The message designer

Every message the bot sends: the info post in your server, the ticket panel and every DM a member gets. Retype titles, texts and buttons right in the picture and see it the way Discord draws it.

Placeholders like {user}, {id} and {staff} One banner and palette, or a colour per message Info messages already posted update when you save

Info message Ticket panel Ticket received Ticket claimed Back in the queue Ticket reopened Still there? Can we close this? Ticket closed

The form builder

The popup a category opens before a ticket exists. Drag blocks into a picture of the Discord popup and type straight into it. The team reads every answer in the ticket.

A form of its own for every category Up to three pages of five, each answer required or optional Length limits, word counts, number ranges and templates

Short answer Paragraph Number Dropdown Single choice Multiple choice Tick box File upload Member picker Role picker Channel picker Text

Dashboard

Run it from Discord, or from your browser

The same settings in both places. A change made on the website is the same change the bot makes in Discord.

In Discord: `/settings`

Ten pages behind one command and around forty settings, without leaving your server. Changes apply the moment you make them.

Overview Categories Forums Access Commands Appearance Behaviour Notifications Health Danger zone

Something looks wrong? /diagnose runs every permission and health check and puts a repair button next to anything that is off.

On the web: your dashboard

Setup The same seven steps, with real text fields and pickers for every role and channel.

Settings, forms and messages Every setting plus both builders, with live previews and a trail of who changed what.

Transcripts Every closed ticket the server kept, searchable by member, handler, category, rating and date.

Statistics First response and handling times, ratings, categories, the busiest days and hours, the team and the trend.

Also built in

Limits per member and per server Cooldowns between tickets Auto-close, with a warning first Reminders for unclaimed tickets Role pings on new tickets A role that blocks tickets Blacklist with an expiry A log channel for everything Thread names you choose How long data is kept Copy a setup with one file Health checks with repairs

Why Modern Tickets

The differences that show up on day two

A channel-based ticket bot Modern Tickets

Where the conversation lives

A new channel per ticket, in everyone’s sidebar The member’s own direct messages

What the team sees

A growing list of channels One forum, sorted by category and status tags

Staff identity

Always the real name Named or anonymous, chosen per ticket

Who has to give a name

Both sides, always Neither, if you allow it, and no admin can look behind it

While the bot is offline

Messages are simply gone Relayed afterwards and marked as late

Closing a ticket

The channel is deleted with everything in it Thread locked and archived, transcript kept

Slash commands

Thirty-one commands, and you need three

Members never need one: they just write to the bot. The rest is for your team and your admins.

Members8

/newopen a panel for this server

/ticketslist your own tickets

/closeclose your ticket yourself

/transcriptget a copy of a closed one

Team15

/claimtake it, named or not

/noteleave an internal note

/transferhand it to someone else

/statssee how the team is doing

Admins8

/setuprun or repair the wizard

/settingsopen the dashboard

/infopost the explainer message

/diagnosecheck permissions and health

Every command in the docs →

Good to know

Your bot, your data, your call

Beta

Your own bot, the same system

Your bot’s name, avatar, banner image and status, with everything Modern Tickets does behind it. Transcripts, the dashboard and the setup show your bot, not ours. In beta, for selected people.

Custom branding →

Private by default

Tickets are kept as long as your server decides, ninety days unless you change it. /forget erases one member’s data at any time. Nothing is sold, shared or tracked.

Your choice of permissions

Add it with Administrator, so no channel override can half-break it later, or with only the twelve permissions it actually uses. It never uses more than those twelve.

What each one is for →

Set it up in five minutes. Forget about it after that.

The bot creates its own private forum, walks you through seven steps and renames the forum when you are done. Everything is changeable later.

Add to Server Read the docs

Website Documentation Terms of Service Privacy Policy

Derecelendirme & Değerlendirmeler

0 değerlendirme

Değerlendirmeler sadece kayıt olmuş kullanıcılar tarafından yapılabilir. Tüm değerlendirmeler Top.gg moderatörleri tarafından yönetilir. Paylaşmadan önce lütfen yönergelerimizi okuduğundan emin ol.

5 yıldız

4 yıldız

3 yıldız

2 yıldız

1 yıldız