Support Tickets
Let members open tickets with your support team, with panels, transcripts, ratings and staff tools.
Overview
Make sure that Cakey Bot has the Manage Channels permission and that Cakey Bot's role is above your support staff roles.
Cakey Bot's support ticket system lets your users open tickets and get 1 on 1 support from your support team. You can manage tickets with Discord's buttons and save transcripts of the ticket history.
Panels
A panel is one complete ticket setup: its own staff roles, category, embeds, button and settings. A server can have up to 10 panels, so you can run separate setups for general support, bug reports and staff applications, each with its own staff roles and its own category.
From the Support Tickets page you pick which panel to work on, and everything under Configure Tickets applies to whichever one is selected.
Post Panel sends that panel's embed and button to a channel you choose, without needing /setup createticketembed.
Delete Panel removes the panel and its settings.
Deleting a panel is refused while it still has open tickets. Close them first, otherwise those tickets would be left with nothing behind them.
Ticket Type decides how tickets open for that panel:
- Channel: a normal text channel inside the panel's category. This is the default.
- Private Thread: a private thread. No channel is created, so the category limit doesn't apply.
- Public Thread: a public thread, visible to anyone who can see the parent channel.
Editing a panel's open embed or button rewrites every copy of that panel already posted, so a live panel can't drift from what the dashboard says is saved. A Refresh action is there for panels that were edited while the bot was offline.
Multipanels
A multipanel posts one message with a button for each panel you pick, so members can choose the type of ticket. Each panel gets its own button, using that panel's button label. A server can have up to 10 multipanels, and a multipanel can offer up to 25 panels.
You manage them under Multipanels on the Support Tickets page. Give each one a Multipanel name, choose its Panels to offer, and post it to a channel. Posting it again in the same channel edits the message already there instead of sending a new one. Once a multipanel is posted, saving it updates the posted message.
Delete multipanel removes it from the dashboard, but a message already posted stays in its channel and its buttons keep opening tickets for their panels.
Configure Tickets
- Login to our web dashboard.
- Go to "Support Tickets".
- Pick the panel you want to configure.
- Configure your desired settings
Panel Name: Give the panel a custom name (up to 100 characters). If left blank, it displays as "Panel #1" wherever the panel is referenced, including the /setup createticketembed panel picker.
Support Staff Roles: Select one or more roles to act as support staff for the panel. Members with any of the selected roles can view/access all of the panel's tickets and use the staff-only ticket commands, so you can give access to several teams (for example a Moderators role and a Support role) without putting everyone in one role. If you do not select any support staff roles, only Administrators will have access to tickets.
For thread tickets, Cakey Bot adds the roles to the thread by mentioning them in a message that is edited in and deleted straight away, so nobody gets a notification. Discord only adds a role's members this way if the role is mentionable or Cakey Bot has the Mention Everyone permission. When Ping Staff Roles on Ticket Creation is enabled, the ping itself adds them instead.
Transcript Channel: Selecting a transcript channel unlocks the ability to save ticket history to that channel. This lets staff review old closed/deleted tickets.
Auto Save Transcripts: If enabled, it automatically creates transcripts for all closed tickets. A transcript channel has to be configured for this to function. Premium Only
Initial Embed Message/Color: Customize the message and embed color shown before a user opens a ticket (up to 2,000 characters).
Open Embed Message/Color: Customize the message and embed color shown once the ticket channel has been created (up to 2,000 characters).
Open Embed Title: Customize the title shown on the "Open a Ticket" embed (up to 256 characters). Leave blank to use the default title ("Support Ticket").
Open Button Label: Customize the text shown on the "Open a Ticket" button (up to 80 characters). Leave blank to use the default label ("Open a Ticket").
Ticket Form: Choose the questions members answer in a pop-up before their ticket opens. Each panel can ask up to 5 questions, which is Discord's limit for a pop-up, and each question can have a placeholder, be required or optional, take a short or long answer, and set a minimum and maximum answer length. The answers are shown in the ticket's first message. Turn off Ask questions when a ticket is opened to open tickets as soon as the button is pressed. Panels you haven't changed keep asking for a ticket reason.
Usage/Creating Tickets
Once you have enabled and configured support tickets via the web dashboard, your users can start making tickets after you create an embed using the /setup createticketembed <panel> command. The panel option autocompletes with your panel's name (its custom name if you've set one, otherwise "Panel #1"). Select it to generate an embed with a button that users can click to open a ticket. When users click the button it prompts them to enter a reason for their ticket, or answer the panel's own questions if you've set up a Ticket Form.
You do not need to make/set up a support category. Cakey Bot automatically generates the correct channels and permissions if it has access to do so. The category it creates is named "Support Tickets" by default, or your panel's custom name if you've set one. Once created, Cakey Bot tracks it internally, so you can rename the category afterward without breaking anything. If the category ever gets deleted, Cakey Bot automatically creates a new one the next time someone opens a ticket. If a category fills up (Discord caps a category at 50 channels), Cakey Bot automatically creates an overflow category (e.g. "Support Tickets #2") and starts using that instead.
Cakey Bot needs access to manage channels to create the required category and ticket channels.
Once a user has closed a ticket, Cakey Bot sends an embed with three options:
- Transcript: Selecting this saves the contents of the ticket to a text file and uploads it to your transcript channel.
- If this option is disabled, you will need to configure your transcript channel on the web dashboard.
- Open: This option re-opens the ticket to allow the user to provide more information or to ask more questions.
- Delete: This option deletes the ticket and clears the channel history.
- This option does NOT save a transcript unless auto-save is enabled.
Ticket Manager
The Ticket Manager page on the dashboard lists every ticket across every panel, so staff can work through them without hunting for channels in Discord.
Each row shows the panel it belongs to, who opened it, who has claimed it, its status, the rating it was given and when it was last active. Columns can be sorted, and the list can be filtered by state and by panel or searched.
Staff actions available on a ticket from here:
- Close and Reopen
- Claim, marking yourself as the person handling it
- Add User and Remove User
- Reply, posting into the ticket as the bot
- Remind, nudging the ticket's opener
- Delete
Actions your roles wouldn't be allowed to perform are disabled before you click them, rather than failing afterwards. The same permission check still runs on the server.
The page also groups ticket categories per panel and shows how full each one is against Discord's 50 channel limit, so you can see an overflow coming before it happens.
Anything done from the Ticket Manager reads the same in Discord as if it had been done there: the embeds and DMs use the bot's own wording and colours.
Ratings
If Allow Feedback Ratings is enabled, closing a ticket asks its opener to rate the support they received. Ratings are recorded against the ticket and shown in the Ticket Manager list, so you can see how a panel or a staff member is doing over time.
Ticket Management
Add User
You can add other users to tickets by typing the /ticket adduser <user> command. This allows that user to view the ticket if they were not the one who created it. This command can be run by anyone who can view and send messages within that ticket.
Remove User
You can also remove other users from tickets by typing the /ticket removeuser <user> command. This revokes that user's ability to view the ticket if they were added to it by the previous command or had access by other means. This command can be run by anyone who can view and send messages within that ticket.
Anonymous Replies
By default, any staff members who have view/send access to tickets can respond to them like they would in other channels. However, sometimes staff members may want to reply to a ticket anonymously without showing their username. To do this, run the /ticket anonreply <message> command. It sends a generic anonymous message from Cakey Bot instead of the staff member.
To use the anonymous reply system, the staff member MUST have one of the panel's support staff roles, which can be set on the web dashboard.
Reminders
Staff members with one of the panel's support staff roles can use the /ticket remind command to send a DM reminder to the user who opened the ticket. The DM prompts them to respond if the issue is still unresolved and provides a button link to open the ticket.
Close Requests
The /ticket request-close <reason> command allows staff members with one of the panel's support staff roles to request the closure of a ticket. Instead of immediately closing the ticket, this command notifies the original user that opened the ticket that the staff have requested the ticket to be closed. The user can then review and approve or deny the request. The reason parameter is required and can be up to 255 characters.
Advanced Settings
These advanced settings are configured on the web dashboard.
Ticket Close Confirmation
Defaults to disabled. When enabled, this prompts the user to confirm that they want to close the ticket with a Yes/No button message.
DM User on Ticket Close
Defaults to disabled. When enabled, the bot attempts to send a DM with basic information about the ticket to the user who opened it, once it has been closed.
Note: Sometimes users have DMs blocked or Discord will fail to send the DM. There is nothing Cakey Bot can do about this.
Require Close Reason
Defaults to disabled and is set per panel. When enabled, pressing the Close button opens a pop-up with a Closing Reason box that takes up to 500 characters, and the ticket closes once the reason is sent.
The reason is shown in the message Cakey Bot posts when the ticket is closed, is saved with the ticket and is added to the transcript message that Auto Save Transcripts posts. A transcript saved with the Transcript button does not include the reason. The reason is required, so the pop-up cannot be sent empty.
Auto Delete Tickets On Close
Defaults to disabled. When enabled, the ticket channel is automatically deleted a few seconds after it's closed, so staff don't need to click the "Delete" option manually.
If Auto Save Transcripts is also enabled, the transcript is always fully generated and saved before the channel is deleted, so enabling this setting never causes you to lose ticket history.
Disable Transcript Mentions
Toggles whether transcript channel logs will mention users/roles.
Ping Staff Roles on Ticket Creation
Defaults to disabled. When enabled, it pings every one of the panel's support staff roles when a new ticket is created.
Note: You MUST have at least one support staff role configured on the web dashboard or this setting will not do anything.
Ping User on Ticket Creation
Defaults to disabled. When enabled, it pings the user who opened the ticket when it is created. This is separate from the "Ping Staff Roles on Ticket Creation" setting above.
Allow Feedback Ratings
This allows users to submit feedback ratings on the support they received inside of a ticket.
How it works:
- Ticket is closed, transcript is created. (a transcript channel MUST be set for this feature to work)
- The bot sends a DM to the user notifying them their ticket was closed and asking for feedback.
- The user can then rate their support between 1 and 5 stars.
- This feedback is posted/updated on the transcript message for the ticket in the server for staff to review.
Note: Ticket transcripts must be enabled for this feature to work properly.
Business Hours
Each panel can be limited to business hours by turning on Limit tickets to business hours. Set Opens at, Closes at, the Time zone and the days the hours apply to. A closing time earlier than the opening time runs past midnight into the next day.
Outside business hours decides what happens to a ticket opened outside these hours:
- Refuse new tickets: the ticket is not opened.
- Open the ticket and post a notice in it: the ticket opens as normal with a notice that a reply may take longer.
Notice message sets the text of that notice. Use {hours} to show the business hours, or leave it empty for the default message.
Blacklisted Roles
This allows you to prevent specific roles from creating tickets. This can be useful if you have users who are spamming or abusing the ticket system.
Related Commands
- /setup createticketembed Manage Server
Create an embed to open tickets with a button.
/setup createticketembed <panel>