History & transcripts
Every closed ticket, its transcript and rating — searchable, exportable, reopenable — and the member's own view of their tickets.
Do this on my dashboardWhen a ticket closes, SUPREO archives it: the messages, the attachments, the internal notes, who opened and closed it, and how long it took. Ticket History (sidebar → Tickets) is where that archive lives.
Archiving must be on
Archive transcripts in the database in Ticket setup → Logging is on by default. Switched off, a closed ticket leaves nothing behind — no history, no transcript, no rating, no analytics.
The list
One row per closed ticket: the member (avatar, name, ticket id and user id), the subject with its message count, the staff who claimed and answered it, the rating, and when it closed with how long it stayed open. Badges mark tickets that were reopened, flagged high or urgent, opened out of hours, or that live in a support server. Click a row to open its transcript.
- Search — a name or a Discord id. It finds the tickets the person opened and the ones where they were staff: they claimed it, closed it, replied or left a note. The name that matched is highlighted in the Staff column.
- Period — last 7, 30 or 90 days, this month, last month, any of the last twelve months, all time, or a custom from–to. Dates follow the server's time zone.
- Sort — newest, oldest, best rated or worst rated.
- Pages — 25, 50 or 100 tickets per page. The page, period, search and sort are part of the address, so a link or a reload keeps them.
- Export CSV — the current list in the current order, with a Staff column, for a spreadsheet.
Premium
Free servers see the last 7 days; Premium keeps everything, for as long as the server uses SUPREO.
The transcript
View opens the conversation as it happened, with the member's messages on one side and staff and bot messages on the other, attachments inline. Files are archived by SUPREO, so they outlive Discord's expiring links.
- Download HTML — a standalone file to keep or forward. HTML with notes includes the internal notes; it is offered to staff only.
- Reopen — creates a new channel with this conversation as its opening card and tells the member by DM. See Reopening.
Ratings
With Ask for a satisfaction rating on in Ticket setup, the member is DM'd a 1–5 star prompt when their ticket closes. The stars show in the History list, on the overview (Average satisfaction) and in Analytics. Ratings are stored on the archived ticket, so they need archiving on.
Read-only access
Log viewer roles in Ticket setup give a role a read-only dashboard: Ticket History and transcripts, nothing else. For a lead who reviews conversations without managing settings. (Premium)
Retention
Transcripts are kept for as long as the server uses SUPREO — the plan changes how much of it you are shown, not how much is stored. Data & privacy covers what is kept, for how long, and how to have it deleted.
The member's side
Members have their own page: My tickets on the dashboard lists every ticket they opened, or were added to, on any server using SUPREO — open ones with where to continue, closed ones with their transcript. In Discord, /mytickets shows their open tickets. They never see internal notes.
DM appearance
How the direct messages a member gets look — the staff reply, the ticket-opened confirmation and the close notice — as a card or plain text, with your colour and signature.
Welcome
Greet every new member with a card — a generated image with their avatar, a message, a button to your ticket panel — and give them roles on join.