> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/logging/transcript-capture-limits.md).

# Transcript capture limits

Transcripts are generated when a ticket closes, capturing every message that was in the ticket. The maximum number of messages captured depends on your plan.

## The cap

| Plan                                        | Messages captured 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** messages are kept up to the cap. Earlier ones are not in the transcript.

## What counts as a "message"

* Member messages.
* Staff messages.
* Bot messages (including the welcome embed and any later bot replies).
* System messages (for example "X pinned a message" or "X joined the thread").

What does **not** count:

* **Reactions.** They are not captured at all.
* **Edits.** Only the latest version of each message is stored. Edit history is not kept.

## When the cap matters

Most tickets stay well under the cap. The cap can matter for:

* **Very long-running tickets** with weeks of back-and-forth.
* **High-traffic tickets** with many participants.
* **Tickets with many attachments or embeds.** Each attachment or embed message counts toward the cap.

A premium server can capture up to 5,000 messages per transcript instead of 1,000.

## What you see if a transcript was capped

The transcript does not show a note saying the ticket had more messages than were captured. It shows the captured messages, oldest captured first.

## Hosted transcripts

All transcripts, free or premium, are hosted on the transcript viewer and kept indefinitely. This is marketed as "Lifetime Storage". The cap applies to what goes into the transcript at close time. Once written, the transcript stays available.

→ [Transcripts overview](/docs/transcripts/whats-in-a-transcript.md)

## Related

{% content-ref url="/pages/Gjspl5mwSsfoYl8bZR1H" %}
[What's in a transcript](/docs/transcripts/whats-in-a-transcript.md)
{% endcontent-ref %}

{% content-ref url="/pages/exzL4IxFJ6d9jWNjp6BF" %}
[The premium-only feature list](/docs/premium/feature-list.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://ticketking.xyz/docs/logging/transcript-capture-limits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.