Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.stellarbot.dev/llms.txt

Use this file to discover all available pages before exploring further.

Stellar’s ticket system gives your members a structured way to reach your staff privately. When a member opens a ticket, Stellar creates a dedicated channel that only they and your support team can see. Staff can add or remove participants, close tickets with an optional reason, and manage a blacklist to prevent abuse — all without leaving Discord. Every ticket is also logged, so your team can review transcripts and stay accountable.
Ticket setup — including choosing the ticket category, support role, log channel, and button embed — is done through the web dashboard at stellarbot.dev. There is no slash command to configure the ticket system at this time.

How tickets work

Once you have configured the ticket system in the dashboard, Stellar posts an embed with an Open Ticket button in the channel you chose. Any member who clicks the button gets a new private channel created for them. Staff members with the designated ticket support role can see all ticket channels and use the commands below to manage them.
Ticket transcripts are available in the dashboard. After a ticket is closed, navigate to the Tickets section on stellarbot.dev to view the full conversation history.

Setup guide

1

Configure the ticket system in the dashboard

Go to stellarbot.dev, select your server, and open the Tickets section. Set the following:
  • Message channel — where the Open Ticket button embed is posted
  • Category — the channel category where ticket channels are created
  • Log channel — where ticket events are logged
  • Support role — the role that can see and manage all ticket channels
  • Embed title and description — what members see before opening a ticket
Save your settings. Stellar will post the ticket embed automatically.
2

Test the ticket flow

Click the Open Ticket button in the embed to confirm a ticket channel is created correctly and that members with the support role can see it.
3

Brief your support team

Share the staff commands below with your team so they know how to close tickets, add collaborators, and manage the blacklist.

Staff workflow

1

Respond inside the ticket channel

Staff with the ticket support role can read and send messages in any open ticket channel.
2

Add or remove participants if needed

Use /ticketadduser or /ticketremoveuser to include other members in the conversation, or to remove someone who was added by mistake.
3

Close the ticket when resolved

Run /ticketclose inside the ticket channel. Optionally provide a closing reason so it appears in the log and transcript.

Commands

/ticketclose [closeReason]

Closes the current ticket channel. Run this command from inside the ticket you want to close. The closeReason parameter is optional. If provided, the reason is recorded with the ticket and appears in the log channel.
This command must be run from inside a ticket channel. Running it in a regular channel will return an error.

/ticketblacklist [user] [sendMessage] [reason]

Prevents a user from opening new tickets in your server.
ParameterRequiredDescription
userYesThe user to blacklist
sendMessageNoWhether to notify the user via DM (defaults to true)
reasonNoReason for the blacklist (max 255 characters, defaults to “No reason”)
If sendMessage is true and the user has DMs disabled, Stellar will note that the notification could not be delivered.

/ticketunblacklist [user]

Removes a user from the ticket blacklist, allowing them to open tickets again.

/ticketgetblacklisted

Displays a paginated list of all users currently blacklisted from tickets in your server. Each entry shows the offender, the staff member who issued the blacklist, the date, and the reason.

/ticketadduser [member]

Adds a member to the current ticket channel, granting them permission to view and send messages. Run this from inside the ticket channel.

/ticketremoveuser [member]

Removes a member from the current ticket channel, revoking their access. Server owners and members with Administrator permissions cannot be removed.
Last modified on May 6, 2026