> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/myra-master-your-ratings/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/myra-master-your-ratings/users-guide/built-in-feedback-surveys.md).

# Built in Feedback Surveys

To help you start gathering actionable insights immediately, Myra includes two ready-to-use feedback surveys: **CSAT** and **NPS**.

{% hint style="info" %}
These surveys are automatically generated for every space. To maintain data integrity and standardized reporting across your workspaces, they **cannot be deleted or renamed**.
{% endhint %}

### Configuring CSAT and NPS

Both built-in surveys use the same **Survey builder**, **Display & scoring**, and **Translations** screens as any custom survey you create — with two differences for CSAT:

* You can't add extra questions to CSAT. Its rating and comment questions are the only ones with an answer path, since CSAT answers are read and written directly on the Jira request itself, not stored as separate Myra feedback data.
* CSAT's calculation strategy is locked to **Average** and can't be changed.

NPS has no such restrictions — you can add extra questions, translate them, and adjust its calculation strategy like any custom survey. See [Survey Builder](https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/survey-builder.md) for details.

#### Customer Satisfaction Score (CSAT) <a href="#customer-satisfaction-score-csat" id="customer-satisfaction-score-csat"></a>

CSAT is a transactional metric designed to capture how satisfied your customers are with a specific experience or interaction. Please note: The built-in CSAT survey is only available at the space level.

All historical Customer Satisfaction feedback is automatically aggregated into Myra’s reports, allowing you to seamlessly track performance trends over time.

To ensure feedback is requested at the perfect moment, the CSAT survey comes with two predefined Collection Rules that cannot be deleted:

* **Request Closed**
* **Reporter Only**

#### Net Promoter Score (NPS) <a href="#net-promoter-score-nps" id="net-promoter-score-nps"></a>

NPS is a relational metric that measures overall customer loyalty by asking how likely users are to recommend your product or service on a scale from 0 to 10. The built-in NPS survey is only available at the space level.

NPS helps you see the big picture of your customer relationships. It easily identifies your biggest fans (Promoters) and highlights customers who might be unhappy (Detractors). Myra’s built-in NPS report automatically calculates your score, making it simple to track overall loyalty and product health over time.

By default, the built-in NPS survey starts with these collection rules:

* **Last Submission** set to **90 days**
* **Last Resolved** set to **8 hours**


---

# 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://docs.meta-inf.hu/myra-master-your-ratings/users-guide/built-in-feedback-surveys.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.
