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

# PostDialogue phase in Dialogue Studio

Use the PostDialogue phase in Dialogue Studio for after-call actions before the flow exits or hands off to quality monitoring.

Use the PostDialogue phase for actions that happen after one participant disconnects and before the flow exits or hands off to quality monitoring.

## When this phase runs

The **PostDialogue** node triggers when either the caller or the agent disconnects the call.

| Output path     | Purpose                                       |
| --------------- | --------------------------------------------- |
| Customer output | Used when the customer remains in the session |
| Agent output    | Used when the agent remains in the session    |

This phase is audio-only, and the remaining participant is passed into the flow.

## 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 PostDialogue phase for after-call handling such as:

* post-call follow-up messages
* confirmation steps for an external system
* final prompts to the remaining participant
* handoff into quality-monitoring logic when a survey is configured

## Design notes for the end of the call

The PostDialogue phase normally contains only one participant, depending on who disconnected first.

Keep this phase focused on short after-call actions and test the end-of-phase behaviour explicitly after each change.

{% hint style="info" %}
Use **No Action** to end the PostDialogue branch. No other action should be used to end this phase. If quality monitoring is configured, the survey starts after the PostDialogue branch completes and only when the remaining participant is the customer.
{% endhint %}

## Verification

1. Place a test call and disconnect it from both the customer side and the agent side in separate tests.
2. Confirm the intended remaining-participant branch runs.
3. Confirm the flow ends cleanly after the final post-dialogue action.
4. If quality monitoring is enabled, confirm the survey starts after the post-dialogue branch completes.

## Related topics

Go to **Quality-monitoring phase in Dialogue Studio** for the survey branch that can start after the PostDialogue branch completes.

{% content-ref url="/pages/0hmRKOTaU5ozV5bjyuV3" %}
[Quality-monitoring phase in Dialogue Studio](/contact-center-configuration/building-your-callflow/via-dialogue-studio/quality-monitoring.md)
{% endcontent-ref %}

Go to **Dialogue Cloud quality monitoring** to configure the survey settings that this handoff depends on.

{% content-ref url="/pages/FP1h7W7KRI6hM4c4W6ma" %}
[Configure post-call quality monitoring](/contact-center-configuration/building-your-callflow/quality-monitoring.md)
{% endcontent-ref %}

Go to **Dialogue Studio core nodes** for No Action and other node-level behavior that can affect phase completion.

{% content-ref url="/pages/8yQ45O2XttelAa6G6IVv" %}
[Dialogue Studio core nodes](/contact-center-configuration/building-your-callflow/via-dialogue-studio/core-nodes.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/postdialogue.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.