Transcripts

How transcripts work

When a ticket is closed — either via the /ticket-close command or the Close Ticket button — Docket:

1. Paginates all messages in the ticket thread
2. Builds a structured JSON document with the full conversation, embeds, attachments, and ticket metadata
3. Uploads the file to secure cloud storage
4. Posts a closing embed in the ticket thread containing a link to view the transcript
5. Locks and archives the thread

Tip: Anyone with the link can view the transcript in a browser — share it with other team members or save it for records without needing to re-open the thread. Links stay valid for the server's retention period (see below), and sensitive transcripts can be password protected.

How long transcripts are kept

Retention is counted from when the transcript was first uploaded (normally when the ticket closed). Re-generating a transcript does not extend it.

• Free servers — 90 days
• Premium servers — up to 365 days (default 365, minimum 90), set in the dashboard under Settings

After that the transcript is permanently deleted and its link shows "This transcript has expired". The Transcripts tab shows each transcript's expiry date.

Warning: Shortening retention, or Premium ending, applies to existing transcripts too: anything older than the new limit expires immediately and cannot be restored by upgrading again.

Password protection

Server administrators can lock any transcript with a password from the Transcripts tab in the dashboard (lock, change, or remove). Viewers then see a password prompt instead of the conversation until they enter it; access lasts 12 hours on that browser. Changing the password signs out everyone who unlocked it with the old one.

Tip: Passwords are never stored in readable form. If you forget one, an administrator can simply set a new password in the dashboard.

Accessing a transcript

The easiest way to access a transcript is the link posted in the closing embed at the bottom of the archived ticket thread. You can also find transcripts via the Docket dashboard — navigate to the Transcripts tab for your server to see a list of all closed tickets with their IDs and view links.

Tip: If a transcript link is missing or broken, an admin can run /force-transcript inside the ticket thread to re-generate and re-upload the transcript without changing any ticket data.

What's included

Transcripts capture the full content of the ticket thread:

• All messages in chronological order
• Message embeds and attachment references
• Interactive component data (buttons, selects)
• Ticket metadata: creator, type, ticket ID, status, opening reason, closure reason, and timestamps

What's not included

• Deleted messages — Discord does not expose deleted message content to bots
• Attachment files — links to attachments are captured but the files themselves are not re-hosted
• Reaction emojis

Re-generating a transcript

If a transcript link is missing or the upload failed at close time, use the /force-transcript admin command inside the ticket thread. It re-runs the full generation and upload process and returns a fresh link without modifying any database state.

Warning: /force-transcript is only available in the primary Nøyra server and will not appear in other guilds.

Feedback on close

If your server has feedback collection enabled with auto-send on close, Docket also sends a feedback request DM to the ticket creator at the same time the transcript is generated. See the Feedback collection page for details.