Introduction

Ticket Nexus

A modular Discord.js v14 ticket bot built for high-performance support environments. Multi-category routing, per-category intake forms, staff analytics, full transcripts, and a dashboard you run entirely from inside Discord — no web panel required.

What's in this guide

  • Getting Started — requirements, installation, and a five-minute first-panel setup.
  • Core Reference — every slash command, who can run it, and every dashboard button.
  • Features & Modules — panels, categories, intake forms, claiming, closing and reopening, auto-close, transcripts, blacklist, analytics, and logging.
  • Configuration.env settings, database setup, support roles, naming variables, and Discord permissions.
  • Integrations — BusyBee panel licensing and white-label bot instances.
  • Advanced Optimization — SQLite vs. MySQL, health monitoring, and troubleshooting.
  • Support — FAQ, common issues, and how to get help.

Key features

  • Dashboard-driven setup/ticket-dashboard configures departments, roles, logging, and the public panel. Every change auto-saves.
  • Two panel styles — a Classic embed with one Create Ticket button, or the newer Components layout with a Select button and blurb per category.
  • Multi-department routing — each category gets its own Discord category (or thread parent), support roles, intake questions, naming scheme, and welcome message.
  • Channel or thread tickets — choose private channels or private threads per category.
  • Claiming and tiered closing — optional claim button, instant /close for elevated roles, delayed /closerequest for everyone else, and inactivity auto-close.
  • Reopen by number — admins can bring back a closed ticket with /reopen ticket:<number>, even after its channel was deleted.
  • Transcripts — full-history text transcripts stored in the database, sent to the log channel, and optionally DMed to the opener.
  • Staff analytics — First Response Time and Average Resolution Time via /stats.
  • SQLite or MySQL — zero-config SQLite by default, MySQL for scale.
  • Health endpoint — a /health route for uptime monitors.