A Discord ticket transcript is a saved copy of everything said in a ticket channel, kept after the channel is deleted so staff and the member can read it later. A good transcript stores the messages, who sent them, timestamps, attachments and images, the close reason and who handled it, and is viewable on the web by the right people only. Noxyr saves an HTML transcript on every close (or on demand), copies the images into its own storage, and shows it privately on a web page. This guide covers why transcripts matter, what to keep, the privacy rules, and how to set it up.

Chat messages and an image drift into a single locked transcript document. Hey, my order is late Order #4821 Checking now Transcript

Why transcripts matter more than the ticket itself

A ticket channel lives for a few hours or days and is deleted on close. Everything that happened in it (the order, the promise, the insult, the payment screenshot) disappears with it unless a transcript was saved. Four situations make that painful:

  • Disputes. "I paid and never got it" or "staff said I could have a refund" is settled in ten seconds with a transcript and never without one.
  • Chargebacks. A PayPal or card dispute wants evidence of delivery. A transcript showing the buyer confirming receipt is exactly that.
  • Staff quality. You cannot coach a support team you cannot read. Transcripts show which answers close tickets and which ones create three more.
  • Moderation appeals. An appeal ticket from six months ago is the only record of what was agreed.

This is also why transcripts are the feature most ticket bots put behind a paywall, and why it should be the first thing you check when choosing one (see Ticket Tool alternatives).

What a ticket transcript should store

  • Every message in order, with the author's name and avatar, not just a user ID that means nothing once they leave.
  • Timestamps, ideally rendered in the reader's timezone.
  • Attachments and images that still open later. This is the one most transcripts get wrong: a transcript that links to Discord's CDN goes blank when the channel is deleted or the link expires.
  • Embeds and bot messages, because the invoice, the cart summary and the "ticket claimed by" notice are all bot messages.
  • Mentions resolved to names, so "@1234567890" reads as the person it was.
  • Ticket metadata: the panel it came from, who opened it, who claimed it, who closed it, the close reason, the message count and the rating if there was one.
  • Form answers the member gave before the ticket opened.

Where transcripts should go

There are three destinations, and a serious setup uses all three:

  • A private transcript channel for staff, so every closed ticket produces one log message with a link. This is your searchable timeline.
  • A DM to the ticket opener, so the member has their own copy of what was agreed. It also cuts "can you send me what you said?" tickets.
  • A web viewer with access control, so a transcript can be opened from anywhere without downloading a file, and only by people entitled to see it.

Privacy rules worth writing down

Transcripts contain personal data: names, payment handles, addresses, sometimes ID photos. Treat them accordingly.

  • Who can read them: the member who opened the ticket, staff who manage the server, and nobody else. Never a public link that anyone with the URL can open.
  • Tell members. A line in the ticket welcome message ("this ticket is logged") is honest and, in many jurisdictions, required.
  • Don't ask for what you won't need. If you need a payment screenshot, ask for one with the card number covered.
  • Retention. Decide how long you keep transcripts and delete the ones past that date. Forever is a policy, but it should be a deliberate one.
  • Deletion requests. If a member asks for their transcript removed, have a way to do it.

How Noxyr saves transcripts

Noxyr writes an HTML transcript automatically when a ticket closes, and staff can snapshot a ticket at any time without closing it using /ticket transcript, which is useful mid-way through a long order. Each transcript stores the messages, embeds, resolved mentions, the close reason and the message count, and the ticket record keeps who opened, claimed and closed it.

Attachments are the part worth spelling out. At save time the bot downloads each attachment (up to 50 MB per file by default) into its own storage, so images in a transcript render inline even after Discord's original upload is gone, and other files are listed with a download link. Emoji whose CDN link has died fall back to their :name: text instead of a broken image icon.

Every transcript gets a private web page. Opening it requires Discord login, and the page is shown only to the member who opened the ticket, users who can manage that server, and the dashboard owner. Anyone else gets a permission error, even with the link. From the page you can download the HTML file for your own records. In the dashboard, staff search transcripts by ticket ID and see the close reason and message count at a glance, and members see their own closed tickets in a personal list.

Setting it up in two minutes

  • 1. Add Noxyr and open the Tickets page, or run /ticket setup in Discord.
  • 2. Set a transcript_channel (private, staff only) so every close logs a link.
  • 3. Turn on dm_transcript so openers get their own copy.
  • 4. Turn on require_close_reason. A reason like "Delivered, order NX-0198" shows next to the transcript in the list, so the right one is easy to spot later.
  • 5. Leave delete_channel_on_close on; the transcript is the record, the channel is clutter.
  • 6. Mention logging in the panel's welcome message.

The rest of the ticket setup (panels, staff roles, auto-close, forms) is covered in how to set up a Discord ticket system, and the full feature list on the ticket bot page.

Transcripts in other ticket bots

  • Ticket Tool: generates transcripts, with some options and branding tied to premium plans. Attachment handling depends on plan and settings; check whether images survive channel deletion.
  • Tickety and Ticketsbot: both save transcripts viewable from their sites; Ticketsbot's are well regarded. Neither copies attachments into its own storage the way Noxyr does, as far as their documentation states, so treat image persistence as something to test.
  • Self-hosted exporters (DiscordChatExporter): the gold standard for a one-off export of any channel, including attachments if you tell it to download them. Manual, not automatic, and it needs a bot token.
  • Discord threads and forums: the thread itself is the record and stays readable as long as nobody deletes it, but it is not exportable, not private by default and not searchable across tickets.

Common questions

Do ticket transcripts include images? In Noxyr, yes. Image attachments are copied into Noxyr's storage when the transcript is saved and shown inline on the web page; other files are listed with a download link. Files over the size limit are noted rather than stored.

Can the member who opened the ticket see the transcript? Yes. The opener can open their own transcript after logging in, and can receive it by DM if you enable that option. Other members cannot.

Can I save a transcript without closing the ticket? Yes, with /ticket transcript. It writes a snapshot and leaves the channel open.

Are transcripts free? Yes. Saving, hosting and searching transcripts is part of Noxyr's free ticket system with no cap.

How long are transcripts kept? Until you delete them. Set a retention policy that suits your server and stick to it.