Make sure that Cakey Bot has the
Manage Channelspermission and that the Cakey Bot's role is above the support staff role.
Cakey Bot's support ticket system allows your users to make tickets and get 1 on 1 support from your support team. You can easily manage tickets via Discord's button system and even save transcripts of the ticket history.
Support Staff Role: Selecting a support staff role will automatically allow users with the selected role to view/access all support tickets. If you do not select a support staff role only Administrators will have access to tickets.
Transcript Channel: Selecting a transcript channel will unlock the ability to save ticket history to the selected channel. Which will allow staff to review old closed/deleted tickets.
Auto Save Transcripts: The option requires premium. If enabled, it will automatically create transcripts for all closed tickets. A transcript channel will have to be configured/set for this to function.
Once you have enabled and configured support tickets via the web dashboard your users can start making tickets using the
/ticket create <description> command. You can also create a embed with a button to create tickets with using this method.
Note: The issue description is optional and a default reason will be filled in if a user does not provide one.
You do not need to make/set up a support category, Cakey Bot will automatically generate the correct channels and permissions if Cakey Bot has access to do so.
Once a user has closed a ticket, Cakey Bot will send an embed with three different options:
You can add other users to tickets by typing the
/ticket adduser <user> command. This will allow that user to view the ticket if they were not the one who created it. This command can be ran by anyone who can view and send messages within that ticket.
You can also remove other users from tickets by typing the
/ticket removeuser <user> command. This will revoke 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 ran by anyone who can view and send messages within that ticket.
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 memebrs may want to reply to a ticket anonymously without showing their username. In order to this all they have to do is run the
/ticket anonreply <message> command. this will send a generic anonymous message from Cakey Bot instead of the staff member.
In order to use the anonymous reply system, the staff member MUST have the Support Team role which can be set on the web dashboard.
These are advanced settings that you can configure via the web dashboard to further customize your support ticket system!
Defaults to disabled. When enabled, this will prompt the user to confirm that they want to close the ticket with a Yes/No button message.
Defaults to disabled. When enabled, this will send attempt to send a DM to the user who opened the ticket once it has been closed with basic information about the ticket.
Note: Sometimes users have DMs blocked or Discord will fail to send the DM. There is nothing Cakey Bot can do about this!
Defaults to disabled. When enabled, it will ping the Support Team staff role when a new ticket is created.
Note: You MUST have a Support Team role configured on the web dashboard or this setting will not do anyhting.
This allows users to submit feedback ratings on the support they received inside of a ticket.
How it works:
Note: Ticket transcripts must be enabled for this feature to work properly.
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. This will blacklist users from creating tickets via the
/ticket new command as well as any ticket embeds.
This will modify the color for the initial embed that is created inside of newly created tickets.
You can also create a fancy embed with a button that users can click to automatically open up tickets instead of using the slash commands as well. You can create this embed using the
/setup createticketembed default command.
You can set a custom message and a custom color for this default embed on the Web Dashboard! You are also able to use Basic Placeholders in this custom message.
You can also create category-specific embeds which will prompt users to select a reason from a dropdown menu to pre-fill the ticket with. You can create these category embeds by typing
/setup createticketembed <type>. You can check out the full list of category types and their pre-filled reasons below: