> 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/use-myra/understand-field-type.md).

# Understand Field type

## Response format (the main question) <a href="#field-types" id="field-types"></a>

When you create a new Feedback Survey, you choose a **Response format** for its main question. This defines how customers answer that first question, and — unlike most other survey settings — it cannot be changed after the survey is created.

* **Rating:** Customers provide feedback using a visual 1–5 star interface. This is ideal for quick, intuitive satisfaction checks.
* **Number Pick:** Customers select a value on a 0–10 scale. This is best for precise metrics like NPS or effort scores.
* **None:** No quantitative main question. Customers are prompted to provide feedback via the comment question only, which becomes mandatory.

{% hint style="info" %}
The NPS calculation strategy requires **Number Pick** as the response format, since NPS scores are calculated over a 0–10 scale.
{% endhint %}

## Adding more question types later

Once a survey exists, open its **Survey builder** tab to add further questions on top of the main one. You can mix in:

* **Rating** — another 1–5 star question.
* **Number Pick** — another 0–10 scale question, with its own helper text.
* **Text** — a free-text question with a configurable placeholder and max length.

An **Email** question is also included automatically on every survey — it isn't something you add manually, and together with the main question and its comment, it's one of the three reserved questions every survey starts with.

See [Survey Builder](https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/survey-builder.md) for how to add, reorder, hide, or delete questions.


---

# 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/use-myra/understand-field-type.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.
