> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/operate/recording-and-interaction-data/manage-transcripts.md).

# Manage transcripts

Review transcript storage behavior, SharePoint transcript recording, and Dialogue Insights transcript availability for supported Dialogue Cloud deployments.

Use this page to review how transcript display in Dialogue Insights differs from the separate transcript recording path that can write transcript files to SharePoint.

## Before you begin

* Confirm which administrators can change transcript recording settings.
* Confirm the SharePoint document library and permissions used for transcript files when transcript recording to SharePoint is enabled.
* Confirm retention and access requirements for transcript files, because transcripts can contain customer data and regulated content.

{% hint style="warning" %}
Transcript files can contain sensitive conversation content. Validate retention, access, and compliance requirements before enabling or changing transcript recording to SharePoint.
{% endhint %}

## Dialogue Insights display versus SharePoint transcript files

The transcript and summary shown in Dialogue Insights are read from Dialogue Insights. This display path is separate from transcript recording to SharePoint.

When transcript recording to SharePoint is enabled, the Unified Contact Center (UCC) can also write a transcript file to SharePoint. Do not treat the SharePoint transcript file as the storage source for every transcript or summary shown in Dialogue Insights.

| Path                                             | Purpose                                                                                                       |
| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------- |
| Dialogue Insights transcript and summary display | Provides the transcript and AI-generated summary shown in Dialogue Details.                                   |
| SharePoint transcript recording                  | Provides a separate transcript file written to SharePoint when transcript recording to SharePoint is enabled. |

## Transcript recording setting

The documented setting for the SharePoint transcript recording path is `UseTranscriptRecording`.

| Setting                  | Documented value | Effect                                                                     |
| ------------------------ | ---------------- | -------------------------------------------------------------------------- |
| `UseTranscriptRecording` | `TRUE`           | Enables the UCC to write the transcript as a JSON text file to SharePoint. |

Use the setting only for the SharePoint transcript recording path. It does not mean that the Dialogue Insights transcript and summary display is read from SharePoint.

Set `UseTranscriptRecording` to `FALSE` when the UCC should not write transcript files to SharePoint. Default `FALSE`. A transcription path must be configured before transcript files can be generated.

## Transcription provider settings

Some voice transcription paths require a configured speech-to-text provider before transcripts can be generated or before Dialogue Studio flows can consume transcription output.

Review these settings with the configuration owner for the environment:

| Setting                                     | Use                                                                               |
| ------------------------------------------- | --------------------------------------------------------------------------------- |
| `TranscriptionServiceProvider`              | Selects the speech-to-text provider used by the UCC transcription path.           |
| `CredentialsJson` or `GoogleCredentialJson` | Stores provider credentials when the selected provider requires JSON credentials. |

Treat provider credential values as secrets. Do not copy them into tickets, docs, chat messages, or screenshots.

## Dialogue Details download availability

In Dialogue Details, a transcript download link can appear when transcript recording to SharePoint is enabled and the transcript file is available for the dialogue.

If the transcript is visible in Dialogue Insights but the download link is not available, check the SharePoint transcript recording path separately from the Dialogue Insights transcript display.

## Timeline event semantics

The **Transcript saved** timeline event is tied to the SharePoint transcript recording path. In that context, it indicates that the UCC saved the transcript file to SharePoint.

Use this event as a SharePoint-write indicator only. It does not mean that every Dialogue Insights transcript or summary is stored in SharePoint.

## Configuration and reference ownership

Use Contact center configuration for the native setting path. This Operate page owns operational, storage, retention, and compliance guidance.

{% content-ref url="/spaces/gIhRKIrtrwqPt8cNlAy6/pages/GPmS80qb4nnck1OqlN4w" %}
[Service and Contact Center Settings](/contact-center-configuration/service-and-contact-center-settings.md)
{% endcontent-ref %}

Use Product reference only when interpreting the legacy Skype for Business WebChat transcript table in the Power BI Template; it does not describe WebAgent text-session transcripts.

{% content-ref url="/spaces/scZpnEdBjDgQmlVn1iLr/pages/1yljYNPjDbEaLoVvXDYD#transcript" %}
[Power BI Template data reference](/product-reference/reporting-and-power-bi/power-bi-template-data-reference.md#transcript)
{% 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://atlas.anywhere.now/operate/recording-and-interaction-data/manage-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.