> 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/indialogue.md).

# InDialogue phase in Dialogue Studio

Use the InDialogue phase in Dialogue Studio to run automations while the caller and agent are connected.

Use the InDialogue phase for automations that should run after the caller is connected to an agent.

## When this phase runs

The **InDialogue** node starts after an audio conversation connects to an agent.

| Output path     | Purpose                                   |
| --------------- | ----------------------------------------- |
| Customer output | Returns the customer-side session payload |
| Agent output    | Returns the agent-side session payload    |

This phase is limited to audio conversations.

## Prerequisites

* You can open the target Dialogue Studio flow for the contact center and edit the dependent configuration surfaces referenced on this page.

## How to use this phase

Use the InDialogue phase for live-session actions such as:

* whisper prompts to the agent or the caller
* transcription or translation while the conversation is active
* actions triggered by keypad input during the live call
* other automations that depend on the active session context

## Design notes for the live session

This phase follows a one-on-one conversation model. If more participants are added, the documented behavior is not defined.

Keep the phase focused on actions that depend on the active dialogue state.

Good practice in this phase is to:

* keep customer and agent branches distinct
* test whisper and prompt timing against a live connected call
* verify any data collection or translation path during a real conversation
* confirm the flow exits cleanly when the call disconnects

## Verification

1. Place a test call and connect it to an agent.
2. Confirm the intended live-session automation runs only after the conversation is connected.
3. Test one customer-facing branch and one agent-facing branch if both are used.
4. Disconnect the call and confirm the next configured phase starts as expected.

## Related topics

Go to **PostDialogue phase in Dialogue Studio** for the after-call actions that begin when one participant disconnects.

{% content-ref url="/pages/RObHMpN5fSP9cksiszPH" %}
[PostDialogue phase in Dialogue Studio](/contact-center-configuration/building-your-callflow/via-dialogue-studio/postdialogue.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/contact-center-configuration/building-your-callflow/via-dialogue-studio/indialogue.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.