> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/reports/report-builder/report-items/net-promoter-score-r.md).

# Net Promoter Score®

## 👪 What is a Net Promoter Score® ?

The Net Promoter Score also called NPS is calculated based on responses to an [NPS question](/form-management/form-designer/questions/question-types/satisfaction-questions/net-promoter-score-r.md).The scoring of this type of question's answers is based on scale of 0 to 10. The primary objective of the Net Promoter Score is to predict customer loyalty and satisfaction. 

Respondents who answer with a score of 0 to 6 are labeled as **Detractors**, these are the less valued respondents which are showing the less interest.  Respondents with 7 and 8 answers scores are labeled as **Passives.**  Respondents who select an answer with score of 9 to 10 are called **Promoters**, and are considered to exhibit the most value like buying more, remaining customers for longer, and making more positive referrals to other potential customers. 

The NPS is calculated by subtracting the percentage of respondents who are Detractors from the percentage of respondents who are Promoters. The resulting score is a whole number that ranges from -100 to 100, a positive NPS is considered as good. 

## 🔢 Net Promoter Score Chart

Each bar is the total of respondents that were classified in that category.

![NPS Respondent Chart](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MBYTt5IlA168rwe-Qpr%2F-MBYVE_EgKNmbAB2gMMD%2Fimage.png?alt=media\&token=fd20c894-83ff-45fd-8834-a1de3040662f)

The NPS score can be found on the left surrounded by the NPS respondent categories based on their answers percentage.


---

# 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.ngsurvey.com/form-management/reports/report-builder/report-items/net-promoter-score-r.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.