> For the complete documentation index, see [llms.txt](https://cc.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc.docs.landis.cloud/daily-usage-personas/supervisor-manager/quality-management.md).

# Quality Management

{% hint style="info" %}
Prerequisites: [Policy Call Recording](/setup/setup-policy-call-recording.md)

Optional: [Sentiment Analysis](/setup/set-up-sentiment-analysis.md)
{% endhint %}

Quality management (QM) is a way for organizations to monitor, evaluate, and improve how customer interactions are handled. Supervisors have the ability to score, tag, and make notes on an interaction.

An interaction can be scored in by selecting "View Score" option on the record context menu in the Recordings, Agent details, or IVR details report or by selecting "View Score" on the recordings tab in the Interaction Details report. A window will appear on the right with interaction details, including the recording and transcription. Only Interactions that have a recording or transcript can be scored.

Once quality management data is saved for an interaction, it will appear in the [Quality Management report](/reports/quality-management.md).

{% hint style="info" %}
If your user does not have the option to view, edit, or complete quality management records, you may lack the necessary permissions. See [Data Access Policies](/administration/data-roles.md)

If your user cannot access the Quality Management report, you may lack the necessary role permissions. See [Roles](/administration/roles.md)
{% endhint %}

| Option     | Description                                                                                                                                                                                                                                                              |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Score      | A numerical score that is given an interaction. This can be any range. Example 1-100                                                                                                                                                                                     |
| Notes      | Feedback related to the interaction. Example: Agent followed the correct greeting and verification process and demonstrated strong empathy when the caller expressed frustration about service delays. Issue was correctly identified and resolved on the first contact. |
| Tags       | Tags related to the interaction. Tags add structured meaning and metadata to a score. Once created, a tag is available globally for other interactions.                                                                                                                  |
| Save Edits | This will save any edits to the QM record.                                                                                                                                                                                                                               |
| Complete   | Once a QM record has been completed, it is no longer editable by any users.                                                                                                                                                                                              |


---

# 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://cc.docs.landis.cloud/daily-usage-personas/supervisor-manager/quality-management.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.