Ticket System

#12-Creating & Publishing a Native Ticket Panel

Learn how to create and publish Novus native ticket panels, map ticket categories to Discord channels, configure panel content and buttons, organize single-panel or multi-panel layouts, and test the complete member ticket creation flow.

Updated 8/28/2026, 11:19:47 PM

A Ticket Panel is the member-facing entry point for Novus In-House Ticketing.

It is the Discord message members interact with when they need to create a support ticket.

A well-designed panel should make three things immediately clear:

What the ticket is for
When the member should use it
What button they should select

The native Novus Panel Builder supports panel title, content, button text, Discord button style, optional emoji, and live preview before publishing.

How a Ticket Panel Works

A basic native ticket flow looks like:

Discord Panel

↓

Member selects Create Ticket

↓

Novus identifies the Ticket Category

↓

Ticket Form is shown when configured

↓

Member submits the required information

↓

Native ticket workflow begins

↓

Assigned support team and AI can assist

The panel therefore acts as the bridge between your public Discord support area and your internal ticket workflow.

Ticket Panel vs Ticket Category

These two should not be confused.

Ticket Category

Defines how that type of ticket behaves.

It may contain settings such as:

Discord Category
Ticket prefix
Handler role
Welcome message
Ticket Form
Transcript configuration

Ticket Panel

Provides the Discord interface members use to start that ticket.

Think of it as:

Category = workflow

Panel = entry point

Step 1 — Choose the Ticket Category

Before publishing a panel, make sure its Ticket Category already exists.

For example:

Ticket Category

Technical Support

with:

Discord Category

SUPPORT TICKETS

Prefix

tech

Handler Role

@Technical Staff

Form

Technical Support Form

Once the category is configured, you can create the panel that members will use to access it.

Step 2 — Choose the Discord Panel Channel

Select where the panel should appear.

Common examples include:

#create-ticket
#support
#help-center
#technical-support
#applications
#report-a-bug

Choose a channel members can easily find.

Example Mapping

You may configure:

Technical Support

→ #create-ticket

This means:

Ticket Category

Technical Support

Panel Destination

#create-ticket

When the panel is published, members can create Technical Support tickets from that location.

One Panel Channel for Multiple Categories

A common setup is to use one central channel.

For example:

#create-ticket

Inside that channel you could publish:

General Support

Technical Support

Payment Support

Applications

Each panel has its own button but shares the same Discord channel.

This works well for smaller or medium-sized communities.

Multiple Panel Channels

Larger communities may prefer dedicated panel channels.

For example:

General Support

→ #support-center

Payment Support

→ #billing-help

Bug Reports

→ #report-a-bug

Streamer Applications

→ #streamer-program

This can make large support systems easier to navigate.

Which Panel Structure Should You Use?

Use a single panel channel when:

Your server is small
You only have a few categories
You want one obvious support destination
Members should not need to search for different support channels

Use multiple panel channels when:

You have many departments
Support categories are very different
Certain panels need restricted visibility
Different sections of the server have different audiences

Step 3 — Configure the Panel Title

The panel title should describe the action or purpose clearly.

Good examples include:

Technical Support

Need Help?

Payment Support

Report a Bug

Streamer Application

Avoid unclear titles such as:

Ticket #1

or:

Click Here

The member should understand what they are creating before pressing the button.

Step 4 — Write the Panel Content

Panel content should briefly explain the ticket type.

For example:

Technical Support

Title

Technical Support

Content

Having trouble with the launcher, game client, installation, patching, or connection?

Create a Technical Support ticket and provide the requested information so Novus AI and our support team can assist you.

This is enough information without overwhelming the member.

Panel Content Should Stay Short

Avoid placing:

Full troubleshooting guides
Entire server rules
Detailed refund policies
Long FAQs
Complete application requirements

inside the ticket panel.

Those belong in your Knowledge Base, documentation, or Ticket Form.

The panel should focus on helping the member choose the correct ticket.

Step 5 — Configure the Button Text

Use action-oriented button labels.

Good examples:

Create Ticket

Get Support

Open Technical Ticket

Report Bug

Apply Now

Poor examples:

Click Me

Button

Clear button text reduces accidental ticket creation.

Step 6 — Add an Optional Emoji

The native panel configuration supports an optional emoji.

For example:

General Support

🎫

Technical Support

🛠️

Payment Support

💳

Bug Report

🐞

Application

📝

The emoji should support the meaning of the button rather than replace the label.

Step 7 — Choose a Discord Button Style

The panel builder supports Discord button style configuration.

Use styles consistently.

For example:

General Support

Primary

Application

Success

Important Account Issue

Primary

Avoid using different styles randomly across similar support panels.

The button label and panel text are more important than color alone.

Step 8 — Review the Live Preview

Before publishing, use the panel preview to check how the message will appear to members.

Verify:

Title is readable
Content is not too long
Button label is clear
Emoji displays correctly
Button style matches the intended action

The implementation includes a live preview specifically so the panel can be reviewed before it is posted.

Step 9 — Publish the Ticket Panel

When the configuration is ready, publish the panel.

Novus can post the actual Discord embed and ticket button into the configured Discord channel.

You do not need to manually create the embed using another Discord bot.

Publishing vs Updating

After a panel has already been published, Novus can update the existing panel when supported by the current configuration.

For example, you may change:

Old

Create Ticket

to:

New

Open Support Ticket

Or change the panel description without publishing an unnecessary duplicate.

The native implementation includes Publish/Update Panel behavior.

Avoid Duplicate Panels

Before publishing another panel, check whether the category already has one.

Multiple identical panels may cause:

Member confusion
Old buttons remaining active
Tickets being created from outdated instructions
Difficulty knowing which panel staff should maintain

When possible, update the existing panel instead.

Complete Example — General Support Panel

Ticket Category

General Support

Panel Channel

#create-ticket

Title

Need Help?

Content

Need assistance with a general server concern?

Create a support ticket and describe your issue. Novus AI may assist you first, and a support staff member can take over when necessary.

Button

Create Support Ticket

Emoji

🎫

Handler Role

@Support Staff

Ticket Prefix

support

Complete Example — Technical Support Panel

Ticket Category

Technical Support

Panel Channel

#create-ticket

Title

Technical Support

Content

Having trouble with the launcher, client, patch, installation, or connection?

Create a Technical Support ticket and complete the troubleshooting form.

Button

Open Technical Ticket

Emoji

🛠️

Handler Role

@Technical Staff

Ticket Prefix

tech

Complete Example — Payment Support Panel

Ticket Category

Payment Support

Panel Channel

#payment-support

Title

Payment Support

Content

Create a private ticket if you need assistance with a payment, transaction verification, or purchase-related concern.

Never share passwords, authentication codes, or other secret credentials.

Button

Open Payment Ticket

Emoji

💳

Handler Role

@Transaction Staff

Ticket Prefix

payment

Complete Example — Bug Report Panel

Ticket Category

Bug Report

Panel Channel

#report-a-bug

Title

Report a Bug

Content

Found a problem?

Create a Bug Report and provide enough information for the team to reproduce the issue.

Button

Report Bug

Emoji

🐞

Handler Role

@Technical Staff

Ticket Prefix

bug

Complete Example — Streamer Application

Ticket Category

Streamer Application

Panel Channel

#applications

Title

Streamer Program

Content

Interested in joining the Streamer Program?

Create an application ticket and complete the requested information for staff review.

Button

Apply Now

Emoji

📹

Handler Role

@Community Team

Ticket Prefix

streamer

Multi-Panel Example

Your #create-ticket channel could contain three separate Novus panels.

Panel 1

General Support

Button:

🎫 Create Support Ticket

Panel 2

Technical Support

Button:

🛠️ Open Technical Ticket

Panel 3

Account Support

Button:

👤 Open Account Ticket

This keeps all standard support options in one location.

Department-Based Panel Example

A larger server might instead use:

#support-center

General Support
Technical Support
Account Support

#transactions

Payment Support
Purchase Support

#community-applications

Guild Application
Streamer Application

#bug-reports

Bug Report

This reduces the number of unrelated options a member sees at once.

Panel Mapping Example

For larger setups, it can help to think in a mapping table:

Ticket Category	Panel Channel	Discord Ticket Category	Handler
General Support	#support-center	GENERAL TICKETS	Support Team
Technical Support	#support-center	TECH TICKETS	Technical Team
Payment Support	#transactions	PRIVATE TICKETS	Transaction Team
Bug Report	#bug-reports	BUG TICKETS	Technical Team
Streamer Application	#applications	APPLICATIONS	Community Team

This makes configuration easier to audit.

Why Mapping Matters

A panel does more than display a button.

It connects several parts of the support workflow:

Discord Panel Channel

↓

Ticket Category

↓

Ticket Form

↓

Discord Ticket Destination

↓

Handler Role

↓

Transcript Destination

If one mapping is wrong, the ticket may still open but go to the wrong location or staff group.

Example Incorrect Mapping

Suppose:

Payment Support Panel

is accidentally connected to:

Technical Support

A member clicks:

Open Payment Ticket

but Novus creates a Technical Support ticket.

The member may receive:

Wrong Ticket Form
Wrong welcome message
Wrong handler role
Wrong transcript destination

Always test each published panel individually.

Mapping Forms to Panels

The form belongs to the Ticket Category rather than simply the visual panel.

For example:

Technical Support Panel

↓

Technical Support Category

↓

Technical Troubleshooting Form

When the member uses that panel, the correct form should appear.

Example Technical Form Mapping

Panel

Open Technical Ticket

↓

Category

Technical Support

↓

Form

Technical Intake

↓

Fields:

Issue Type
Error Message
Problem Description
Troubleshooting Attempted

This provides context before the ticket conversation starts.

Panel Forms and Future Google Sheets Mapping

Consistent panel and form configuration also improves external data mapping.

For example:

Bug Report Panel

↓

Bug Report Form

↓

Google Sheet: Bug Reports

Possible mappings:

Form / Ticket Data	Sheet Column
Ticket ID	Report ID
Ticket Owner	Reporter
Bug Title	Title
Description	Description
Reproduction Steps	Steps
Area	Component
Final Status	Status
Resolution	Resolution

This creates a direct path from member intake to structured records when the relevant Sheets integration is enabled.

Example Application Mapping

Streamer Application Panel

↓

Streamer Application Form

↓

Google Sheet: Streamer Applications

Mapping:

Novus Field	Google Sheets Column
Ticket Owner	Discord User
Streamer Name	Name
Platform	Platform
Channel URL	Channel
Streaming Schedule	Schedule
Ticket Status	Application Status

This is useful because staff no longer needs to manually copy each field from Discord.

Panel Category to Google Drive Mapping

Ticket categories can also provide useful structure for future or enabled Google Drive archiving.

For example:

Technical Support

→ /Novus Archive/Technical/

Payment Support

→ /Novus Archive/Payments/

Streamer Applications

→ /Novus Archive/Applications/Streamer/

Bug Reports

→ /Novus Archive/Bugs/

The ticket panel ultimately determines which category the ticket belongs to, so accurate panel mapping also affects downstream organization.

Example Full Data Flow

A Bug Report workflow could eventually look like:

Member

selects:

🐞 Report Bug

↓

Novus Ticket Panel

maps to:

Bug Report Category

↓

Bug Report Form

collects:

Title
Description
Steps
Area

↓

Native Ticket

opens under:

BUG TICKETS

↓

Technical Team

handles the ticket

↓

Ticket closes

↓

Google Sheets

receives structured report information

↓

Google Drive

receives the transcript

↓

Knowledge Base

receives a reusable verified solution only when appropriate

This is why consistent Ticket Categories are important across the entire system.

Testing the Published Panel

Do not test using only a Discord Administrator account.

Use a normal member account whenever possible.

Test the complete flow:

View the panel.
Select the ticket button.
Complete the form.
Submit it.
Confirm the correct ticket workflow begins.
Verify staff access.
Verify member access.
Test closing.
Check transcript behavior.

Test Wrong or Missing Form Data

If your Ticket Form has required fields, try submitting without completing them.

Verify that the member cannot accidentally bypass required information.

Also test:

Long answers
Short answers
Dropdown options
Single choices
Multiple choices

The current form implementation includes these field concepts, with up to five fields.

Test Panel Updates

After publishing a test panel:

Change its description.
Change its button text.
Update the panel.
Verify the existing Discord panel reflects the new configuration.

This confirms that staff can maintain panels without constantly creating new messages.

Panel Design Best Practices

Keep your ticket panels:

Short
Clear
Purpose-specific
Consistent
Easy to find
Easy to understand on mobile

Avoid excessive emojis, large paragraphs, or several unrelated instructions.

The goal is to get the member into the correct support workflow as quickly as possible.

Security Considerations

Ticket panels should never instruct members to submit:

Passwords
Authentication codes
API keys
Recovery codes
Full payment credentials
Other secret information

A private ticket channel is not a reason to request information that should never be shared.

Publishing Checklist

Before making a panel public, confirm:

The correct Ticket Category is selected.
The correct Discord panel channel is selected.
The panel title clearly identifies its purpose.
The description is concise.
The button label explains the action.
The emoji is appropriate.
The button style is consistent.
The preview looks correct.
The correct Ticket Form is connected.
The correct handler role is assigned.
The correct Discord ticket destination is configured.
The correct ticket prefix is configured.
The panel successfully publishes.
Updating the panel works.
A normal member can use the panel.
Required form fields work.
The ticket starts in the expected workflow.
Staff can access the resulting ticket.
Member permissions are correct.

Next Step

After members can create native tickets from your published panels, the next step is controlling exactly what information Novus collects during ticket creation.

Continue to Native Ticket Forms, Fields & Data Mapping, where we'll cover field types, required and optional fields, reusable form design, category-specific forms, Google Sheets column mapping, Google Drive archive mapping, and practical application, bug-report, and support workflows.