> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/connected-insights/configure/configuration/c-preferred-transcripts.md).

# Preferred Transcripts

The Preferred Transcripts section allows you to upload a preferred transcript file that defines which transcripts for a gene are preferred. These transcripts are prioritized over other transcripts of the gene when the default transcript for a variant is determined. For more information, refer to [Transcripts](/connected-insights/interpret-and-report/inter-transcripts.md).

Upload the preferred transcript file as follows.

1. On the top toolbar, select **Configuration**, and then select the **General** tab.
2. Select **Preferred Transcripts**.
3. If there are no preferred transcripts, select **Create One**.
4. For Template File, select **Upload** and select your transcript file. You can also download a template to customize and upload as your preferred transcript file.
5. Select **Open**.
6. After the file displays, Select **Save**.
7. Select **Download & View** to download the transcript file.
8. \[Optional] To upload an updated version of the file, select **Upload New Version**.


---

# 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.bioinsight.illumina.com/connected-insights/configure/configuration/c-preferred-transcripts.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.