Noyra Docket
Sign in

Viewing Transcription History

Access and manage your ticket history and transcriptions on the Docket website.

What Are Transcripts?

Transcripts are records of all messages and activity in closed tickets. They provide a complete history of support conversations for reference, compliance, and customer service quality assurance.

Automatic Archiving

When a ticket is closed, Docket automatically saves a transcript that you can access anytime from the dashboard.

Accessing Transcripts

  1. Log into the Docket Dashboard
  2. Select your server/guild
  3. Click on the "Transcriptions" tab

You'll see a list of all closed tickets with ticket ID, dates, user who opened it, and message count.

Viewing a Transcript

  1. Find the ticket in the history list
  2. Click on the ticket ID or "View" button
  3. The full conversation will display

In the transcript view:

  • Complete message history in chronological order
  • User avatars and names for easy identification
  • Timestamps for each message
  • Ticket metadata (creator, type, etc.)

Searchable Content

Use your browser's search function (Ctrl+F / Cmd+F) to find specific keywords within a transcript.

Filtering & Searching

The transcripts page includes filters to help you find what you're looking for:

  • Search by ticket ID— Type in the ID (e.g., "ticket-123")
  • Search by user — Find tickets opened by specific users
  • Search by date — Filter tickets from a specific time period
  • Sort by columns — Click headers to sort

Narrow Your Search

Combine multiple filters for more precise results. Filter by date range AND user to find a specific person's tickets in a certain month.

Exporting Transcripts

When viewing a transcript, you can:

  • Copy the transcript URL to share with team members
  • Export as text for record-keeping
  • Use browser functions to print or save as PDF

Browser Save Options

Use your browser's "Print to PDF" feature (Ctrl+P / Cmd+P) to save transcripts as PDF files for long-term archival.

Best Practices

Organization

  • Regularly review transcripts to identify patterns in support issues
  • Use consistent ticket naming/IDs for easy searching
  • Organize completed tickets in logical time periods

Quality Assurance

  • Review transcripts to ensure quality customer service
  • Use transcripts to provide feedback to support team members
  • Identify frequently asked questions from transcripts

Compliance & Records

  • Archive important transcripts for compliance requirements
  • Keep records of support interactions for accountability
  • Export transcripts for external documentation if needed

What's Included

  • All messages sent in the ticket thread
  • User names and avatars
  • Message timestamps
  • Ticket metadata and status changes

What's Not Included

  • Deleted messages (they don't appear in the transcript)
  • Message attachments (links only, not the files themselves)
  • Reaction emojis (may vary by export format)