MRI BOTMRI BOTHelp

Tickets

Private support on Discord, with subject types, an opening form, a panel and the history of every conversation.

With tickets, each person opens a private channel of their own with the team. Staff reply there, and when the support ends the history is saved.

Everything is set up in Tickets > Settings. Each block has its own save button.

Start with the basics ready

If the module doesn't have any ticket type yet, the top of the screen shows Want the bot to set it up for you?. Click Set it up for me and the bot creates:

  • the Support role, which sees and answers tickets;
  • the #open-a-ticket channel, with the panel already posted;
  • the private TICKETS category, where tickets open, with the #ticket-history channel;
  • three subjects: Support, Report and Something else.

If a role or channel with the same name already exists, it's reused. Nothing that already existed is deleted. Then just give the Support role to whoever will answer and open a test ticket.

Changed your mind? The Undo link deletes what the bot created, except channels with messages and roles that were already given to someone. Prefer to build it all by hand: click I'd rather start from scratch.

1. Defaults

  • Default category: the Discord category where ticket channels are created.
  • Staff role: who sees and handles every ticket.
  • History channel: when a ticket closes, the bot posts here who opened it, who handled it, how long it lasted and a button with the full history. Make this channel visible to staff only.

2. Ticket types

Types are the subjects the person picks when opening (for example Support, Reports, Donations, Bugs). For each type:

  • Label, emoji and description, shown on the panel.
  • Staff role (override): besides the general staff, who takes care of that subject.
  • Ping role on open: gets a mention when a ticket of this type opens.
  • Opening form: up to 5 questions the person answers before opening. The answers show at the top of the ticket, so staff don't need to ask again.
  • Welcome message and a limit of open tickets of this type per person.
  • Category for this type, if you want to split subjects into different categories.

3. Ticket behavior

  • Open tickets per user limit, adding up all types.
  • Auto-close on inactivity: closes the ticket after a while without a reply.
  • Automatic claim: the first staff member to reply becomes the ticket's handler.

4. Ticket panels

The panel is the message with the button or list to open a ticket.

  • Dropdown (recommended): a single panel, with every type in one list. It stays clean even with many subjects.
  • Buttons: one button per type.

Pick the channel, save and publish. Use a channel where members can read but not write.

Changed the text or the types after publishing? Publish the panel again so it reflects the changes.

Canned responses, hours and blocks

  • Canned responses: texts staff send with the /reply command inside the ticket, like "ask for proof" or "under review".
  • Support hours: whoever opens a ticket outside those hours gets a notice of when the team is back.
  • Blacklist: stops a person from opening tickets.

When the ticket closes

  1. The conversation history is saved and gets a link.
  2. The person who opened it gets a direct message with the history link and can rate the support from 1 to 5.
  3. If there's a history channel, the summary is posted there.
  4. The ticket channel is archived, and staff can reopen or delete it.

The support queue and the numbers (response time, ratings, who handled the most) are in Tickets > Requests and Tickets > Overview.

Common problems

  • The ticket doesn't open: check that the bot can create channels in the chosen category and that its role has Manage Channels.
  • Staff can't see the ticket: check the Staff role in Defaults and the Staff role (override) on the type.
  • The message with the history doesn't arrive: the person has direct messages closed for the server. The history is still in the history channel and in the dashboard.

On this page