Ir al contenido principal

Tickets

ProBot's Tickets system allows you to create a fully-featured support ticket system for your Discord server. Members can open tickets through buttons or dropdowns, and your staff team can manage, claim, and close them — all from the dashboard.

info

The dashboard is where the configurations described here are managed.

  1. Go to the dashboard and log in.
  2. Select your server from the menu on the left.
  3. Choose the module and make sure that it is enabled.

Overview

The Overview tab gives you a quick summary of your ticket activity over a selected time period (e.g., 30 Days). It displays:

  • Total Tickets — The total number of tickets created.
  • Opened Tickets — Currently open tickets.
  • Closed Tickets — Tickets that have been closed.
  • Response Time — Average staff response time.

You will also see a Tickets by Panel breakdown and a Daily Activity chart showing ticket volume over time.

Ticket Panels

Ticket panels are the core of the ticket system. Each panel defines how users create tickets and how those tickets are handled. You can create multiple panels for different purposes (e.g., "General Support", "Bug Reports").

To create a panel, click the Create Panel button. Each panel has an Edit button and a three-dot menu with options to Duplicate or Delete it.

Basic Settings

SettingDescription
Panel NameThe name of the ticket panel (e.g., "Tickets").
Naming SchemeHow ticket channels are named. Use {number} for auto-incrementing numbers (e.g., ticket-{number}).
User Ticket LimitMaximum number of tickets a single user can have open at once.
Cooldown (seconds)Cooldown period before a user can open another ticket.
Attached PanelsLink other panels together so they appear on the same message.
Enable/Disable PanelToggle the panel on or off.

Appearance

Choose how users interact with the ticket panel:

  • Button — Users click a button to create a ticket.

    • Emoji — Optional emoji displayed on the button.
    • Button Style — Choose a color style (e.g., Primary Blue).
    • Button Label — The text on the button (e.g., "Create Ticket").
  • Dropdown — Users select from a dropdown menu.

    • Dropdown Placeholder — The placeholder text shown in the dropdown.
    • Dropdown Options — Each option has an Emoji, Label, and Description.

Categories

Organize tickets into Discord channel categories:

SettingDescription
Ticket Open CategoryThe category where new/open ticket channels are created.
Ticket Closed CategoryThe category where closed ticket channels are moved to.
Ticket Claimed CategoryThe category where claimed ticket channels are moved to.

Permission & Roles

Control who can access and manage tickets:

RoleDescription
Staff RolesRoles that can view and respond to tickets.
Admin RolesRoles with full administrative control over tickets.
Blacklisted RolesRoles that are prevented from creating tickets.
Whitelisted RolesRoles that bypass restrictions (e.g., cooldowns).
Ping RolesRoles that get pinged when a new ticket is created.

Automation

Automate common ticket actions:

SettingDescription
Auto-close After (hours)Automatically close inactive tickets after the specified number of hours. Set to 0 to disable.
Auto-delete After (hours)Automatically delete closed tickets after the specified number of hours. Set to 0 to disable.
Auto-pin First MessageAutomatically pins the first message in the ticket channel.
Require TopicRequire users to provide a topic when opening a ticket.

Form Settings

You can require users to fill out a form when creating a ticket:

  • Require Form — Toggle to enable or disable the form.
  • Form Title — The title displayed at the top of the form.

Form Fields

Each form field has the following options:

OptionDescription
LabelThe name of the field (e.g., "What is your issue?").
Field StyleChoose between Short Text (Single-Line) or Long Text (Multi-Line).
PlaceholderOptional placeholder text shown inside the field.
Min LengthMinimum character length for the response.
Max LengthMaximum character length for the response.
RequiredWhether the field must be filled out.

You can add multiple fields by clicking + Add Field, and remove fields with the delete button.

Panel Messages

Customize the messages sent at various ticket lifecycle events. Each message can be sent as plain text or as an Embed with a color, author, title, description, and images.

MessageWhen it is sent
Greeting MessageWhen a ticket is first opened.
Ticket MessageThe main message displayed in the ticket channel.
Open MessageWhen a ticket is created.
Close MessageWhen a ticket is closed.
Claim MessageWhen a staff member claims a ticket.
Unclaim MessageWhen a staff member unclaims a ticket.

Available Variables

Use these variables in your messages:

VariableDescription
[user]User mention
[username]Username
[ticket]Ticket number
[channel]Channel mention
[topic]User topic

Transcripts

Save ticket conversations for future reference:

SettingDescription
Transcript ChannelThe channel where transcripts are sent.
Transcript FormatChoose between HTML (Discord Style), JSON (Structured Data), or Plain Text.

Claiming Settings

Allow staff members to claim tickets so only they handle them:

SettingDescription
Enable ClaimingToggle claiming on or off.
Claim ModeToggle — Staff must unclaim before another can claim. Reassign — Staff can claim from others directly.

Ticket Logs

The Ticket Logs tab allows you to configure logging for ticket-related events. Set a Log Channel where ticket logs are sent, then toggle individual Log Actions on or off:

Log ActionDescription
CreatedA ticket is created.
ClaimedA ticket is claimed by staff.
UnclaimedA ticket is unclaimed.
ClosedA ticket is closed.
ReopenedA closed ticket is reopened.
LockedA ticket is locked.
UnlockedA ticket is unlocked.
DeletedA ticket is deleted.
Priority ChangedA ticket's priority is changed.
TransferredA ticket is transferred to another panel or staff.
RenamedA ticket channel is renamed.
Permissions ChangedTicket permissions are modified.
Transcript GeneratedA transcript is created for the ticket.
tip

Enable logging for at least Created, Claimed, Closed, and Deleted actions to maintain a clear audit trail of ticket activity.

precaución

Make sure ProBot has the necessary permissions in your ticket categories and log channels, including Manage Channels, Send Messages, and Manage Webhooks.