# What's in a transcript

When a ticket closes, Ticket King generates an HTML transcript with the message history.

## What's captured

* **Member messages.** Content, timestamps, and author name and avatar. Edited messages show an "edited" marker.
* **Staff messages.** A **STAFF** tag appears on staff messages, and a **BOT** tag appears on bot messages.
* **Bot messages.** Including the welcome embed and any later bot replies.
* **Message embeds.** Title, description, fields, color, image, thumbnail, and footer.
* **Buttons and select menus.** Shown statically.
* **Attachments.** Image, video, audio, and other files attached in the ticket.
* **Stickers.** Shown as images. Animated stickers show a placeholder.
* **System messages.** Joins, pins, boosts, and similar.
* **Replies.** Reply chains stay visible.
* **Mentions.** Resolved @mentions of users and roles.

The transcript ends with a footer showing who closed the ticket (or "Staff Team" when **Hide Closing User** is on), the close reason, and the time the transcript was generated.

## What's NOT captured

* **Reactions.** They are not stored at all. The transcript shows no reaction emoji.
* **Edit history.** Only the latest version of each message is kept. Original text from before an edit is not kept.
* **A ticket-info block or participant roster.** The transcript does not contain the ticket number, opener, claim, or form answers. That information goes in the closed-log embed, not inside the transcript.

{% hint style="info" %}
Looking for the ticket number, who opened it, who claimed it, or the form answers? Those are in the **closed-ticket log embed**, not in the transcript.

→ [What goes into each log embed](/docs/logging/log-embed-contents.md)
{% endhint %}

## Per-author info captured

For each message the transcript stores the author's display name and avatar as they were at the time of the message.

If the author later changes their name or leaves the server, the transcript still shows their name as it was **at the time of the message**.

## Message capture cap

| Plan                                        | Messages per transcript |
| ------------------------------------------- | ----------------------- |
| **Free**                                    | 1,000                   |
| <i class="fa-crown">:crown:</i> **Premium** | 5,000                   |

If a ticket has more messages than the cap, the **most recent** N are kept. Older ones are not included.

→ [Transcript capture limits](/docs/logging/transcript-capture-limits.md)

## What the rendered transcript looks like

Discord-style timeline with avatars, usernames, timestamps, embed cards, attachments inline, and markdown formatting rendered.

<figure><img src="/files/0DQgVcLrwl7dcWyf48Rt" alt="A rendered transcript showing multiple message types"><figcaption></figcaption></figure>

## What you can do in the rendered transcript

Read it. There are no exposed UI actions to download, share, search, or copy individual messages. Browser-level features (Ctrl+F to find, "Save Page As" to download) are your options.

## Related

{% content-ref url="/pages/MVC61qSaXCm7eEUgQABZ" %}
[When a transcript is generated](/docs/transcripts/when-generated.md)
{% endcontent-ref %}

{% content-ref url="/pages/9LgYeMt3zCRpnojBs9ZU" %}
[Where to find a transcript](/docs/transcripts/where-to-find.md)
{% endcontent-ref %}

{% content-ref url="/pages/wCbUHb75fVzWZWVTbURD" %}
[Transcript capture limits](/docs/logging/transcript-capture-limits.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ticketking.xyz/docs/transcripts/whats-in-a-transcript.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.