🎫 Ticket Types

Ticket types are the heart of the bot. Each type represents a support category with its own channel, roles, and welcome message. You can define 1 to 9 types.

---

Full example

{
  "ticketTypes": [
    {
      "id": "general",
      "label": "General Inquiry",
      "description": "Ask a general question or get help",
      "emoji": "❓",
      "color": "5865F2",
      "categoryId": "123456789012345678",
      "supportRoles": ["987654321098765432"],
      "welcomeMessage": "Welcome! Please describe your question in detail and a team member will be with you shortly."
    },
    {
      "id": "billing",
      "label": "Billing",
      "description": "Payment and subscription questions",
      "emoji": "💳",
      "color": "57F287",
      "categoryId": "123456789012345678",
      "supportRoles": ["111222333444555666", "777888999000111222"],
      "welcomeMessage": "Thanks for reaching out about billing. Please include any relevant order or transaction IDs."
    }
  ]
}

---

Field reference

id (required)

A unique short identifier used in channel names and internal routing.

• Format: lowercase letters, digits, and hyphens only
• Length: 2–32 characters
• Example: "general", "bug-report", "vip-support"

caution

Once you have live tickets using a type ID, avoid renaming it — it will break the type lookup for any in-progress tickets.

---

label (required)

The human-readable display name shown in the panel embed and ticket channel.

"label": "General Inquiry"

---

categoryId (required)

The Fluxer category (channel group) where new ticket channels will be created.

"categoryId": "123456789012345678"

How to get it: Enable Developer Mode → right-click the category → Copy ID.

Each ticket type can point to the same category, or use different categories per type (e.g., a dedicated billing category with restricted visibility).

---

supportRoles (required)

An array of role IDs whose members are automatically granted access to this ticket type's channels and are mentioned when a new ticket opens.

"supportRoles": ["987654321098765432", "111222333444555666"]

• At least one role ID is required per ticket type.
• Each member of these roles will be pinged when a new ticket is created.
• Role IDs must be 17–20 digit numbers.

---

description

Short text shown in the panel embed under the ticket type's name. Keep it to one sentence.

"description": "Ask a general question or get help"

---

emoji

An emoji shown next to the ticket type in the panel embed and inside the ticket channel.

"emoji": "❓"

Standard Unicode emojis work. Custom server emojis are not supported.

---

color

A 6-character hex colour code (without the #) used for the embed sidebar and other UI elements.

"color": "5865F2"

Suggested colours	Hex
Blurple (default)	5865F2
Green	57F287
Red	ED4245
Yellow	FEE75C
White	FFFFFF

---

welcomeMessage

The text shown in the welcome embed when a ticket channel is created. Supports Discord-style markdown (bold, italics, bullet lists with •).

"welcomeMessage": "Welcome! Describe your issue and we'll be right with you.\n\n**Please include:**\n• What you expected\n• What actually happened"

---

Reaction order

The numbered reactions on the panel (1️⃣, 2️⃣, 3️⃣…) correspond to the order of entries in the ticketTypes array. Reordering the array will change which number opens which ticket type.

Maximum types

The reaction panel supports a maximum of 9 ticket types (one per number emoji 1️⃣–9️⃣). Attempting to configure more will cause a startup error.

Global staff roles

If you have roles that need read/write access to all ticket types without being pinged, use globalStaffRoles at the top level instead of adding them to every ticket type's supportRoles.

{
  "globalStaffRoles": ["999888777666555444"],
  "ticketTypes": [...]
}