Ticket Tool Next
Ticket Tool Next
Everything your ticket bot does today, and the things it never shipped.
Free to start, and there is no card to enter. Sign in with Discord, pick a server, post a panel.
- Panels
- Ticket forms
- Thread tickets
- Tickets from your website
- Auto-close with a warning
- Claiming
- Transcripts that keep the files
- A queue with a position in it
- Ratings after close
- Custom commands
- Automations
- 33 languages
Someone asks a question in the busiest channel you have, and either a stranger answers it or it scrolls away. Instead they press a button on a message you wrote, and land in a channel only they and your team can see.
Nobody has to be awake for that to happen. The form asks your questions before the channel opens, so the first thing your staff read is the answer, not the greeting.
Everything a server needs, set from the same place.
A member arrives with a problem, and you already decided the rest.
Somewhere to ask
You post one message, and each button on it opens a different kind of ticket.
It is 3am and you are asleep
The channel still opens, and the form has already asked the questions you would have asked.
Your staff, and nobody else
Support roles decide who is in the channel before it opens, and blacklists decide who cannot open one.
The question you answer twice a day
A custom command, matched by exact word, wildcard or regular expression, answers it once.
Nobody has to remember
The conversation is saved as one HTML file when it closes, with the attachments still in it.
In the language the server speaks
The bot's own messages ship in 33 languages, one chosen per server.
Two people answering the same ticket is worse than nobody answering it. Claiming puts one name on it. The queue puts the rest in an order, and tells the member where they are in it.
Add someone who should see it, rename it, move it to the panel it should have been, leave a note only staff can read, or set a priority. The record shows what actually happened rather than what everyone remembers.
The conversation leaves as one HTML file, and the files people sent are inside it, not linked from it.
Discord's own links to an attachment stop working. A transcript that stored links is a page of dead images six months later, found at the moment somebody needed it as evidence. This copies the bytes while the links are still alive, then files the transcript where the people who need it can reach it.
- A channel in your server
- A link your staff can open later
- The member who opened it Premium
Free runs a real support desk, on its own, for as long as you want. Premium is what a server buys when the volume arrives and the work needs sharing out.
- Claiming, so one name is on a ticket
- Tickets that open as threads
- Transcripts saved without anyone pressing a button
- Direct messages on ticket events
- The automation engine, including the auto-close warning
- Scheduled support hours, and ratings after close
Five steps, and only one of them is something you have to decide. At the end of it the server can take its first ticket.
- Add the bot The invite asks for what a ticket channel needs, and leave the list as it is.
- Pick a support role The one step that is yours to decide. Everything after it is a screen.
- Open the dashboard Administrator in the server is what gets you in.
- Build a panel One message, and a button for each kind of ticket you take.
- Post it to a channel Past here you are customising rather than setting up.
Give your members somewhere to ask. Somebody arrives needing help today, and somebody else will tomorrow.
Panels, forms, transcripts, support roles, custom commands and the queue are free. Nothing expires, and there is no card to enter to find that out.
Add Ticket Tool Next