> 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/product-reference/dialogue-studio/dialogue-studio-faq-and-troubleshooting.md).

# Dialogue Studio transcript limitation after agent handoff

Review the known Dialogue Studio transcript limitation for invite, blind transfer, and consult transfer scenarios.

Use this note when you review the known transcript limitation where a Dialogue Studio conversation shows only one agent after another agent joins the same session.

## Why does the transcript show only one agent after an invite or transfer?

If a second agent joins an active session by invite, blind transfer, or consult transfer, the conversation transcript records only the first agent participant.

{% hint style="info" %}
If transcript continuity after **Skill Transfer** matters for your service, validate that handoff path in a test flow before you depend on it.
{% endhint %}

## What this means for administrators

* Expect transcript history for these handoff paths to show only the original agent participant.
* Validate multi-agent transfer paths in a test flow before you depend on transcript history for coaching, audit, or troubleshooting.
* Use the same limitation when you interpret transcript output in Dialogue Studio investigations or support cases.

## Verification

1. Start a controlled test conversation that reaches the relevant Dialogue Studio flow.
2. Join a second agent by invite, blind transfer, or consult transfer.
3. Review the resulting transcript and confirm whether only the first agent participant appears.
4. Repeat the test with **Skill Transfer** if your service depends on transcript continuity after a handoff.

## Related topics

Go to **Troubleshoot Dialogue Studio** for recurring runtime errors related to connection ownership, node input data, and transcription setup.

{% content-ref url="/spaces/gIhRKIrtrwqPt8cNlAy6/pages/1DZ33M6NXFEl7w5wpxlG" %}
[Troubleshoot Dialogue Studio](/contact-center-configuration/building-your-callflow/via-dialogue-studio/troubleshoot-dialogue-studio.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://atlas.anywhere.now/product-reference/dialogue-studio/dialogue-studio-faq-and-troubleshooting.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.