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

# Quality-monitoring phase in Dialogue Studio

Use the quality-monitoring phase in Dialogue Studio to run post-call survey questions and collect the caller's answers.

Use the quality-monitoring phase to run post-call survey questions after the live dialogue ends and collect the caller's answers in sequence.

## When this phase runs

This phase starts after the PostDialogue branch completes when quality monitoring is configured and the remaining participant is the customer. The **QM Question** node then triggers once for each configured quality-monitoring question.

| Output field              | Purpose                                           |
| ------------------------- | ------------------------------------------------- |
| `payload.questionId`      | Configured quality-monitoring question identifier |
| `payload.welcomeText`     | Spoken introduction or question text              |
| `payload.goodbyeText`     | Closing text                                      |
| `payload.valueStartRange` | Lowest valid answer value                         |
| `payload.valueEndRange`   | Highest valid answer value                        |

Questions trigger in order, starting with the configured question that has the lowest order value.

## 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 quality-monitoring phase to submit survey answers in sequence and control how the survey moves from one configured question to the next.

## Submit an answer and continue

Use the **QM Answer** node to submit the caller's answer for the active question.

In this phase:

* each answer is tied to the current question identifier
* the next question is triggered after an answer is submitted or the previous question times out
* the call disconnects after all configured questions are answered or timed out

## Keep the configuration aligned with the contact center settings

This phase depends on the quality-monitoring settings already configured for the contact center.

Use [Dialogue Cloud quality monitoring](/contact-center-configuration/building-your-callflow/quality-monitoring.md) to configure the survey questions, timeout values, rating range, and overall feature settings that the Dialogue Studio phase relies on.

## Reporting and operational notes

Captured answers are available in reports. Use the reporting or analytics surface configured for your deployment rather than assuming one fixed reporting destination.

Where an optional plugin handler is configured for a quality-monitoring question, confirm that behaviour in your deployment before using it in production.

## Verification

1. End a test call so the survey path starts.
2. Confirm the first question is the one with the lowest configured order.
3. Submit one answer and confirm the next question starts or the survey ends as expected.
4. Confirm the recorded answer is visible in the reporting or analytics surface used by your deployment.

## Related topics

Go to **PostDialogue phase in Dialogue Studio** to control the handoff conditions that start the survey branch.

{% content-ref url="/pages/RObHMpN5fSP9cksiszPH" %}
[PostDialogue phase in Dialogue Studio](/contact-center-configuration/building-your-callflow/via-dialogue-studio/postdialogue.md)
{% endcontent-ref %}

Go to **Dialogue Cloud quality monitoring** to configure the survey questions, timeouts, rating range, and feature settings that this phase uses.

{% content-ref url="/pages/FP1h7W7KRI6hM4c4W6ma" %}
[Configure post-call quality monitoring](/contact-center-configuration/building-your-callflow/quality-monitoring.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/quality-monitoring.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.