Give your members a private place to talk to your staff. They press a button, answer a few questions, and get their own ticket. Your staff claim it, the bot chases the replies, and every ticket ends with a rating and a transcript. Free, no coding, and your bot.
Pick what you need help with and we will open a private ticket for you.
Your ticket is ready: #support-0042
Only you can see this
The panel in its Card look. Tom pressed Support, and only he sees the reply.
Follow Tom's ticket from the moment he presses Support to the transcript in your staff channel, and see what the bot did at each step.
Pick what you need help with and we will open a private ticket for you.
Tom pressed Support.
Every step runs through one of five ticket events. Switch on only the parts your server needs.
Start from a preset, pick one of four looks, and see the panel the bot posts. Every button opens its own kind of ticket.
Card: A box in your colour, with buttons or a dropdown.
Pick what you need help with and we will open a private ticket for you.
Before a ticket opens, the bot checks the member. Pick a reason to see the reply only they see. You can change every reply, or switch any check off.
Pick what you need help with and we will open a private ticket for you.
Tom pressed Support.
You already have a ticket open: #support-0042
Only you can see this
A limit per member sets how many tickets of a type one member can have open at once, 1 by default and up to 10. The reply links to the ticket they already have.
Members always hear why, so nobody presses the button again and again wondering what went wrong.
Members never see them. Pick a tool to see what it does in the ticket.
Hey @Tom, thanks for reaching out. Someone from @Support team will be with you soon.
Jayce is looking after this ticket now.
You choose what the other staff can do once it is claimed: still reply, only read, or not see it at all.
Staff find their tools as buttons on the first message, in a Staff tools menu, or both.
All of it lives on one Tickets page in your dashboard, in the order a ticket happens. Pick a part to see every setting on it and what it does in Discord.
Pick the channel and how the panel looks: a Card, a List, a classic Embed, or a Custom message you write yourself. Post it, and later Update it changes the message that is already there.
PremiumMore than 1 panel in each server needs Premium.
Pick what you need help with and we will open a private ticket for you.
Every setting on the Panel tab, 20 in all
Each panel is a message in a channel.
Where it is posted and what it says.
One button for each ticket type.
Each reason has its own reply, and each can be switched off.
Every button on the panel is a ticket type. Choose whether it opens as a private channel, a private thread or a forum post, who answers it, and the questions members fill in first.
PremiumMore than 3 ticket types needs Premium.
Hey @Tom, thanks for reaching out. Someone from @Support team will be with you soon.
You are number 3 in line. The usual wait is about 20 minutes.
Every setting on the Opening tab, 25 in all
Each button on the panel is a ticket type with its own settings.
How the type shows on the panel.
And who answers it.
What they fill in and what they see first.
So nobody opens too many.
Its name and what members can post.
Pings, priority and claiming.
Staff find their tools as buttons on the first message, in a Staff tools menu, or both. Switch on the ones your team uses and press one to change how it works.
PremiumReply as the bot needs Premium.
Hey @Tom, thanks for reaching out. Someone from @Support team will be with you soon.
Every setting on the Staff tools tab, 21 in all
Members never see them.
Who has it and how urgent it is.
People, notes and saved replies.
For now and then.
Reminders nudge the right people at the right time, and quiet tickets close by themselves. Set your support hours and the clocks stop while you are closed. With On duty, pings only reach staff who are on.
Can you send me the newest error from your Error Logs page?
@Tom This ticket closes soon if we don't hear back. Reply here to keep it open.
Every setting on the Automations tab, 11 in all
Press one to change its waits and what it says.
When your staff are around.
Staff go on and off with /ticket duty.
Keep closed tickets so they can be reopened, or delete them. The member gets your closing message by DM, and the bot can save a transcript, ask for a rating and tell your log. A low rating reaches your seniors while it is fresh.
Every setting on the Closing tab, 20 in all
Kept tickets can be reopened.
Confirm, a reason, and who can close.
Transcript, rating and log.
Reopening and clean up.
For the endings that need something different.
The Transcripts tab lists every ticket with what they asked and its transcript. Search and filter, press one to read it word for word, and see your stats under it.
PremiumExport your tickets as a spreadsheet with Premium.
Every setting on the Transcripts tab, 11 in all
Every closed ticket, word for word.
How many tickets, how fast staff answer, and the ratings.
Set on the Closing tab.
Besides the panel, members can type a command, right click a message, or mention the bot, and staff can open a ticket with a member.
PremiumDM the bot and Say a keyword need Premium.
i need help with my bot, it keeps going offline
Need a hand? Open a ticket and our staff will help.
Only you can see this
Every setting on the Other ways in tab, 8 in all
Besides the panel.
Open a ticket with a member.
Everything on the page runs through five events in the builder, with a path for each thing that can happen. A path you leave empty does what the page says, so you only add blocks where you want something different.
PremiumAdding your own blocks to the ticket events needs Premium.
Every path in the five ticket events, 33 in all
Someone asked for a ticket.
Staff did something in a ticket.
A timer from Automations ran out.
It closed, reopened or was deleted.
The member rated a closed ticket.
Every ticket is saved when it closes. Pick a look to see Tom's ticket in it.
Looks just like the channel it came from
Hey Tom! Does it go off at the same time each night?
Yeah, around 3am every night.
That is the nightly restart. It should stay online from now on.
That fixed it, thanks!
Every look is free. Find any past ticket later on the Transcripts tab.
Ticket Tool, Tickets, Ticket King and the rest do tickets well. The difference is whose bot it is and what else it can do.
| Feature | Your BotGhost bot | Dedicated ticket bots | Coding your own |
|---|---|---|---|
| Runs under your own bot name and avatar | Yes | Paid plan | Yes |
| Panels with buttons or a dropdown | Yes | Yes | Code |
| Questions before the ticket opens | Yes | Varies | Code |
| Claim, priority, notes and saved replies | Yes | Varies | Code |
| Reminders and auto close | Yes | Varies | Code |
| Ratings after a ticket closes | Yes | Varies | Code |
| Transcripts | 16 looks | Varies | Code |
| Welcomes, moderation and custom commands in the same bot | Yes | No | Code |
| Cost | Free, Premium for more | Free tiers and paid tiers | Server bills and your time |
Dedicated ticket bots means Ticket Tool, Tickets, Ticket King and similar, whose features vary by bot and plan. White labelling is a paid tier on the major ones.
How to set it up
From a fresh bot to a panel in your support channel
Every tab of the Tickets page, step by step with pictures, plus what to check when something isn't working.
What a ticket bot does, how the panel works, what makes a good ticket system, and what else tickets are good for.
A ticket bot turns "can someone DM me?" into a private room with a record. A member presses a button, answers a few questions, and gets a channel or thread that only they and your staff can see. Staff claim it, help, and close it, and the conversation is saved as a transcript.
Doing that by hand means making channels, fixing permissions and chasing people. A ticket bot does all of it, the same way every time, and a BotGhost bot does it under your own name.
The panel is the message members press to open a ticket. Make it a Card in your colour, a List with an Open button for each type, a classic Embed, or a Custom message you write yourself. Each button opens a different ticket type, so billing goes to one team and reports go to your moderators.
A good support desk answers fast and tidies up after itself. A few things that help:
The same tickets work for reports, shop orders and staff applications. The Shop and orders preset asks for the order number on every ticket, and Staff applications gives members a form, keeps every application as a transcript, and lets them apply once every 30 days.
Under the page, Tickets is five ordinary events: Ticket Requested, Ticket Changed, Ticket Needs Attention, Ticket Closed and Ticket Rated, with a path for each thing that can happen. You can open them in the builder at any time and see exactly what runs. With Premium you can add your own blocks under any path, so a ticket can also check a database, call an API, or give a role.
Tickets are one part of your bot. Here is the rest of it.

Create a bot, switch on Tickets, and have a panel in your support channel in minutes. Free, no code, nothing to install.