> 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/contact-center-configuration/building-your-callflow/via-dialogue-studio/merge-conversations.md).

# Merge audio conversations in Dialogue Studio

Map queued and incoming audio session IDs correctly before merging conversations.

Use the Merge action to combine two audio sessions in the same UCC. One session must already be queued with a selected skill. The other is an incoming session, which can still be in its IVR.

{% hint style="warning" %}
Action availability depends on the installed version and connect model. The [Connect and Unify comparison](/set-up-dialogue-cloud-neo/connect-vs-unify.md) records DC2025.02a behavior and lists Merge as planned for Unify. Do not assume this reference changes that availability.
{% endhint %}

## Map the Session IDs

| Action Field         | Session to Supply                                                 | Prerequisite                                                 |
| -------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------ |
| **Session in queue** | ID of the session that has selected a skill and entered the queue | The session belongs to the same UCC as the incoming session. |
| **Incoming session** | ID of the incoming audio session to merge with it                 | The session can still be in its Incoming IVR.                |

Store the IDs temporarily using Function nodes or other standard nodes. Keep the two values distinct. Do not overwrite one with the other while preparing the action.

Before invoking Merge, check both IDs, the shared UCC, and the queued session's skill selection. This is a two-session action, not a skill-routing substitute.

## Diagnose a Failed Merge

Look for errors in both Dialogue Studio and the UCC log. Correlate the error with the two session IDs and verify their current state.

Return to [Core Nodes](/contact-center-configuration/building-your-callflow/via-dialogue-studio/core-nodes.md) for the other routing actions.


---

# 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/contact-center-configuration/building-your-callflow/via-dialogue-studio/merge-conversations.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.