> For the complete documentation index, see [llms.txt](https://help.zipcaptions.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.zipcaptions.app/transcriptions/getting-started-with-transcripts.md).
# Getting Started with Transcripts
{% hint style="info" %}
You must enable Transcripts in the settings, before you can use them.
You can read how to do this [here](/settings/transcripts.md).
{% endhint %}
{% hint style="warning" %}
Transcripts are only stored locally on your device, they are not synced to the cloud. This means that you will only be able to see transcripts on the device that you created them on. If you want to use them on other devices you can export them using the instructions [here](/transcriptions/exporting-your-transcripts.md).
{% endhint %}
1. When you open the captioning window you will now see a Transcription Enabled notification
This session is now being captioned.
2. Once you have finished the captioning session, click on the Microphone to end captioning
3. Click on the three lines ☰
4. Click on Transcripts\
5. The Transcripts screen will now appear, this will show all of your locally stored transcripts\\
6. Clicking on the transcript will allow you to view it
---
# 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://help.zipcaptions.app/transcriptions/getting-started-with-transcripts.md?ask=&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.
