> 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/transcripts/where-to-find.md).

# Where to find a transcript

How to access a transcript after a ticket closes.

After a ticket closes, the transcript is accessible from multiple places.

## 1. The close-log embed

The close embed in your Closed Tickets Log Channel has a **View Transcript** link button right below the embed fields.

## 2. The dashboard's single-ticket detail page

**Dashboard → Ticket History** → click any closed ticket → its detail page has a **"View Transcript"** link in the Ticket Information card.

## 3. The author's DM (when DM User Close Message is on)

When **DM User Close Message** is on (the default), the ticket author receives the close embed in their direct messages, including a **View Transcript** link.

## 4. Your "My Transcripts" page

Members can visit [**ticketking.xyz/user/transcripts**](https://ticketking.xyz/user/transcripts) to see every transcript they have access to, across every server.

<figure><img src="https://1268186137-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrnuG1qjzbOoh0efVpoK8%2Fuploads%2Fgit-blob-39d689d74d51fc25e21a852d00cf4ec04ca3ba9b%2Fuser-transcripts-page.png?alt=media" alt="The user/transcripts page showing a list of transcripts grouped by server"><figcaption></figcaption></figure>

## Authentication

Viewing a transcript requires signing in with Discord.

→ [Role-Specific Transcript Viewing](https://ticketking.xyz/docs/transcripts/role-specific-viewing.md)

## Sharing a transcript

Opening a transcript relies on the viewer having permission. Sharing the link with someone who does not have permission does not grant them access. They are denied when they try to open it.

## Related

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

{% content-ref url="/pages/u3CSFXLeg5ky3c3XzTMd" %}
[Role-Specific Transcript Viewing](https://ticketking.xyz/docs/transcripts/role-specific-viewing.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ticketking.xyz/docs/transcripts/where-to-find.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
