Nexus Logo
Nexus
Configuration

Ticket System

💡 Support without the chaos: With Nexus, members open a private ticket channel with a single click, visible only to them and your support team. When a ticket is closed, Nexus automatically creates a transcript so no conversation gets lost.

The Order: Category → Panel → Settings

The ticket system builds on itself: without a category there's no panel, and without a panel members can't open tickets.

Method 1: Setup via the Dashboard (Recommended)

  1. Open the Nexus Dashboard and select your Discord server.

  2. Go to Tickets in the menu.

  3. Create a category (e.g. "General Support" or "Applications") and choose the support roles that can see tickets in it.

  4. Post the ticket panel in a channel of your choice. It automatically gets one button per category.

  5. Optionally, set when unanswered tickets close automatically and when closed channels are deleted.

The dashboard also shows all currently open tickets at a glance. You can also adopt an existing panel there via its message link.

Method 2: Setup Directly in Discord

With the Manage Server permission, you can also do it right in the chat:

  1. Create a category: Type /add_category, enter a name and then select the support roles.

  2. Post the panel: Type /ticket_panel, choose the channel and enter the panel's title and description.

  3. Set timings (optional): Use /ticket_settings to configure automatic closing and deletion.

You can add more categories at any time with /add_category, and the panel updates automatically. Use /edit_category to rename categories, change their roles or delete them.

Automatic Closing & Deletion

  • Auto-close: Tickets without a response are closed after 12, 24, 48 or 72 hours, or after 1 week.

  • Delete channel: Closed ticket channels are deleted after 1, 12, 24 or 48 hours, or after 1 week.

How a Ticket Works

  1. A member clicks a category in the panel and briefly describes their issue.

  2. Nexus creates a private channel for the member and the category's support roles.

  3. Once the issue is resolved, the team clicks Close Ticket. The member confirms the closure or declines it with a reason.

  4. Nexus creates a transcript, posts it in the ticket and the log channel, and sends it to the member by DM.

If a ticket needs to be closed immediately, e.g. because of spam, the team can use /force_close with a reason, no confirmation needed.

Limits

  • Free: 2 ticket categories.

  • Premium: up to 10 ticket categories.

Tip: You'll find a full list of all chat commands in our command reference for Tickets.