Start with one working ticket
Follow the ProTickete setup guide to invite the bot, run /auto-setup and test a complete ticket. Use the command reference when you need a command name or permission requirement.
Get the basic workflow working first. Then add the questions, routes and extra panels your server actually needs.
How panels, forms and routing fit together
A panel is the Discord message members use to start a request. Ticket panel controls the main panel. Panel library lets you create separate panels and give their buttons different jobs.
- Create a ticket: choose the opening category and staff roles. Add questions if members should complete a form first.
- Route by a form selection: add menu choices, then give each choice its own ticket category, submission channel or role action.
- Send a submission: collect a form and optional files in a selected channel without creating a ticket.
- Assign roles: offer ordinary community roles below the bot’s role. Managed roles and roles with moderation or administrator permissions are excluded.
Forms support short text, paragraphs, selections and file uploads. A form has at most five fields, including its route or role selector. Name your fields clearly and ask only for information staff need.
Save before publishing. Publishing creates a Discord message; updating a published copy changes that message. Review its destination channel before confirming.
Who handles the ticket?
Choose support roles and opening, claimed and closed categories for each workflow. Staff claim and close tickets using Discord controls. A channel’s permission overrides still decide who can read it.
For inactivity closing, check the timeout and make sure the bot can read and manage the channel. Start with a test ticket before enabling automation across your server.
Where settings live in the dashboard
Sign in to the dashboard with Discord and choose a server you own or administer. Voting is optional; dashboard access depends on your Discord server permissions. It does not lock ticket creation or slash commands.
- Overview / Tickets: view conversations, rename tickets and move them.
- Ticket panel / Panel library: edit panel messages, buttons, forms and destinations.
- Channels & categories / Roles & access: set up destinations and staff access.
- Transcripts: filter saved records by owner, dates, keywords and staff.
- Activity & logs: review ticket activity and the latest dashboard changes.
- General settings: change ticket names, enable numbering, select the bot language or reset the system.
The in-dashboard User guide explains each section while you work. For public answers, use the ticket bot FAQ.
Ticket numbers keep counting when names change
Each new ticket gets a persistent number, whether its channel uses a username, a number or a fixed name. In General settings, enable Use ticket numbers in channel names and keep id or {id} in the template.
Existing channels keep their names. All panels in the server share the counter. Resetting the ticket system restarts it at 1, so old and new tickets can share display numbers. Read the confirmation before resetting.
Transcript access, expiry and recovery
A transcript is an HTML copy of a ticket conversation. New hosted copies expire after 24 hours by default, or the duration selected by a server administrator. Existing copies keep their original expiry. The exporter reads up to 2,500 messages; a very long ticket or unavailable media can leave the export incomplete.
Use Transcripts → View to try restoring an expired copy. Recovery needs either the saved HTML attachment in Discord or a ticket channel the bot can still read. Keep the attachment in a restricted staff channel if you need a longer record.
Anyone with the hosted link can open it. Share it carefully. The privacy policy explains the data stored with tickets and transcripts.
Send us a useful bug report
Check live service status first. Then contact ProTickete support with the command or dashboard action, the error message and the steps that led to it. Remove private conversation details and tokens from screenshots.
Looking for your own bot name and avatar? See the custom bot wishlist. To follow changes to the regular bot, read the latest ProTickete updates.