Documentation

Learn TicketsX faster

Setup guides, the full command reference, Premium features, and the REST API in one place.

Deep Search on Transcripts

Deep Search lets you search inside every archived ticket from the Transcripts page, not just its metadata. When a ticket closes, TicketsX indexes who messaged and what was said alongside the encrypted HTML transcript, and the dashboard search runs entirely against that index so the bot never slows down.

What you can search


  • Message content - Words or phrases said anywhere in the ticket, with matching snippets shown in the results.
  • Said by - Combine a content search with the user who said it.
  • Participants - Tickets where specific users messaged. Enter several users and choose whether *all* of them (a group) or *any* of them must have messaged.
  • Opened / closed date ranges - Narrow results to tickets opened or closed between specific dates.
  • Channel ID - Find the transcript for a specific Discord channel or thread ID.
  • Opened by, rating, and bot messages - Filter by the ticket creator, a minimum feedback rating, and optionally include bot messages.

Results respect the same permissions as the rest of the transcripts page: admins see everything, staff see what their teams allow, and everyone can always find their own tickets.

Indexing follows your Premium subscription: while Premium is active every ticket close is indexed automatically, and when you first upgrade your existing transcript archive is backfilled into the index in the background. If Premium ends, the index is removed (your HTML transcripts are untouched); re-upgrading rebuilds it. The search panel shows how many of your archived tickets are covered.

To make message text searchable, deep search stores message content and participant metadata in a database index alongside the encrypted transcript file. Index entries are deleted together with transcripts and through the GDPR/CCPA erasure tools.

The same search is available to your own tools through the REST API — see Search Transcripts in the API Reference.