Evelina
HomeStatusCommandsFAQInviteSupport Server
  • Overview
    • Introduction
    • Donator Perks
  • Security Setup
    • Antinuke
      • Role creation
      • Role deletion
      • Role editing
      • Role giving
      • Role locking
      • Channel creation
      • Channel deletion
      • Kick
      • Ban
      • Bot adding
    • Join Gate
    • Moderation
    • Auto Moderation
      • Invite
      • Words
      • Spamming
      • Repeat
    • Fake Permissions
  • Server Configuration
    • Roles
      • Vanity Roles
      • Booster Roles
      • Reaction Roles
      • Button Roles
    • Messages
      • System Messages
      • Auto Responders
      • Auto Messages
      • Button Messages
    • Logging
    • Starboard
    • VoiceMaster
    • Level Rewards
    • Bump Reminder
    • Reaction Triggers
    • Command Aliases
  • Miscellaneous
    • Music
    • Tickets
    • Counters
    • Webhook
    • Giveaway
    • Invite Tracker
  • Economy
    • General
  • Business
  • Laboratory
  • Company
  • Cards
  • Games
  • Integrations
    • Last.fm
  • Social Notifications
  • Resources
    • Syntax
    • Scripting
      • Embeds
      • Variables
      • Pagination
    • Permissions
    • Punishments
  • Common Issues
    • iOS Dash
    • Server Removal
Powered by GitBook
On this page
  • Ticket Setup
  • Support Role
  • Category
  • Transcripts
  • Ticket Topics
  • Ticket Embed
  • Ticket Open Embed
  • Ticket Modals
  • Ticket Channel Names
  • Ticket Channel Topic
  1. Miscellaneous

Tickets

Learn how to setup the ticket system

PreviousMusicNextCounters

Last updated 7 days ago

Ticket Setup

Support Role

Define a support role for the ticket system. This role can close tickets, view them and add/remove members from the ticket.

Syntax: ;ticket support add [topic] [role]
Example: ;ticket support add default Staff

Category

Set a category in which Evelina should create all new tickets.

Syntax: ;ticket settings category [topic] [category]
Example: ;ticket settings category [topic] #tickets

If you do not use topics or do not want each topic to have its own category, use "default" to set the default category

Transcripts

Set a channel in which all transcripts of closed tickets should be sent.

Syntax: ;ticket settings logs [channel]
Example: ;ticket settings logs #transcripts

Ticket Topics

Create multiple ticket topics to have a better overview of your tickets.

Syntax: ;ticket topics
Example: ;ticket topics

After you have executed the command, you will receive a message with two buttons with which you can create or delete topics (categories).

To add your topic, click on "add topic" and fill out the modal.

To avoid problems with emoji processing, we recommend using the command ;emoji info [emoji] to find out the Markdown and copy it 1:1 for the ticket system.

You can also edit existing topics or create them manually.

;ticket topic add [name]
;ticket topic remove [name]

;ticket topic name [old] [new]
;ticket topic description [name] [description]
;ticket topic emoji [name] [emoji]

It is important that if you create a category and want to use an emoji, the emoji must be on the same server as the bot.

Ticket Embed

To create a ticket you also need the ticket embed.

Syntax: ;ticket send [channel]
Example: ;ticket send #ticket

After you have finished designing your embed, click on "Generate Embed Code" and copy it with "Copy Embed Code"

Syntax: ;ticket send [channel] [code]
Example: ;ticket send #ticket {embed}$v{description: Create a Ticket}

Ticket Open Embed

Change the message sent when a new ticket is created.

Syntax: ;ticket settings embed [topic] [code]
Example: ;ticket settings embed default {embed}$v{description: Support will be with you shortly}

If you do not use topics or do not want each topic to have its own category, use "default" to set the default category

Ticket Modals

Now you can add a modal that opens before a ticket is opened to have questions answered.

Syntax: ;ticket modal add [topic] [name] [description]
Example: ;ticket modal add Support Question What is your Question?

It is now important to save this code as you will need it to retrieve the user response.

To display in the ticket message what the user has entered in the modal, you have to take the code and insert {code} into your open embed message like this

Syntax: ;ticket settings embed [topic] [code]
Example: ;ticket settings embed Support {embed}$v{content: {user.mention} | {support.role}}$v{description: ## :support: Support}$v{color: #729bb0}$v{author: name: {user.name} ({user.id}) && icon: {user.avatar}}$v{field: name: > Question && value: ```{lNp6A5kA}```}

Here is an example of what it would look like if a user wants to open a ticket:

Here is an example of what it would look like if a user opened a support ticket and filled out the modal:

Ticket Channel Names

If you want you can change the default ticket channel name with these commands.

Syntax: ;ticket topic channelname [name] [channelname]
Example: ;ticket topic channelname Support 💰-{user.name}

To remove a channelname from a topic you can do it with this command. Just leave the [channelname] variable empty.

Syntax: ;ticket topic channelname [name]
Example: ;ticket topic channelname Support

Ticket Channel Topic

If you want you can change the default ticket channel topic with these commands.

Syntax: ;ticket topic channeltopic [name] [channeltopic]
Example: ;ticket topic channeltopic Support 💰-{user.name}

To remove a channeltopic from a topic you can do it with this command. Just leave the [channeltopic] variable empty.

Syntax: ;ticket topic channeltopic [name]
Example: ;ticket topic channeltopic Support

If you don't want the standard ticket embed, you can create one yourself. Go to .

https://evelina.bot/embed
Tickets | Evelina
Logo