> 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/sentiment-index.md).

# Sentiment Index

## 😁 What is a sentiment index ?

The sentiment index will give you insights in unstructured text entered by your respondents.

For example if your question has a field Comment and your respondent answered "I didn't like your service" ngSurvey will analyze that text and rate it as a negative sentiment.

Unstructured text entered by your respondents can be evaluated to be positive, neutral negative or mixed [sentiments](/form-management/reports/text-reports/sentiment-analysis.md) when they have both positive and negative insights.

## 📈 Sentiment index  chart

Each bar is the total of respondent text answers that were found matching that sentiment category. 

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MBYNrBR2LzpTwrYAUPx%2F-MBYOQDo_ozl4GgCGMjS%2Fimage.png?alt=media\&token=0300558a-0cb4-4f62-9ec2-2a6f79b235b9)

The sentiment index on the left ranges from -10 (very negative) to +10 (very positive). and is surrounded by the sentiment categories based on their answers percentage.

{% hint style="warning" %}
Only text based answer with enabled [compute sentiment score](/form-management/form-designer/answers/answer-properties.md) properties can be used for sentiment index reporting. 
{% endhint %}


---

# 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/sentiment-index.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.