> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/applications/monitoring-applications/monitoring-web-applications/ahead/delight.md).
# Delight
The **Delight** tab measures employee satisfaction with an application using the **Delight score**, helping you identify low-sentiment groups and prioritize improvements.
The Delight score combines two data sources: the quantitative survey rating employees give through **Campaigns** (1–5), weighted at 70%, and **frustrating page loads**, weighted at 30%. Campaigns also collect qualitative feedback through a free-text field, shown in the **Comments** section below. Frustrating page loads require no additional configuration. If the survey is not configured for the application, the system calculates the Delight score using frustrating page loads alone, at 100% weight.
## Explore overall satisfaction trends
The top section of the **Delight** tab visualizes how the Delight score evolves over the last 13 months, with each data point calculated over a rolling 30-day period.
From the **Delight** tab of the target application:
* Determine how employees experience the application by reviewing the **Delight score**.
* Explore the histogram to see how many employees gave each rating.
* Use the trend indicator to compare the current score against the previous period.
* Hover over the **Delight score** to open the **action menu** and drill down into the specific employees behind the aggregate.
To avoid over-surveying employees, the system enforces a minimum interval between campaigns for the same employee: **30 days** between two campaigns on different applications, regardless of whether the employee responded; **90 days** between two campaigns on the same application if the employee declined or partially answered the previous one; and **90 days** between two campaigns on the same application if the employee fully answered the previous one.
{% hint style="info" %}
The survey component of the Delight score must be enabled for the application before its data appears. Enable it in Manage Applications under the **Collect Feedback** toggle. Refer to [Configuring AHEAD](/user-guide/applications/setting-up-and-managing-applications/configuring-applications/configuring-web-applications/configuring-ahead.md) for configuration details. This survey does not count toward your Engage license, and you can set it up even without the Engage module.
{% endhint %}
## Analyze satisfaction across employee groups and application features
Examine the heatmap to understand how satisfaction varies across your organization and within the application itself.
From the **Delight** tab of the target application:
* Filter the heatmap by organizational dimensions (**Division**, **Department**, or **Entity**) to identify which business areas have the lowest satisfaction. Note that the available options depend on the user organization fields configured in your Nexthink environment.
* Filter the heatmap by device location (**Countries**, **Cities**, **States**, or **Sites**) to detect where low satisfaction is concentrated.
Visually identify groups with consistently low satisfaction. Combine the satisfaction score with the response rate to distinguish reliable signals from results based on too few responses.
{% hint style="info" %}
On heatmaps with more than 10,000 rows, the system displays an infobar indicating that not all rows are shown, so the resulting ranking may not reflect the complete dataset.
{% endhint %}
## Investigate satisfaction insights and comments
Use the AI-powered **Insights** to understand the context behind the satisfaction scores, the likely causes of low ratings, and the affected groups. The insights cover:
* Why the selected satisfaction pattern matters.
* The main drivers and root causes behind the pattern.
Understand the reasons behind satisfaction scores by reading employee free-text feedback in the **Comments** section.
{% hint style="info" %}
The system displays the ✦ sparkles icon to indicate AI-generated content or insights. AI is evolving rapidly and delivering great insights, but it can still make mistakes. Nexthink recommends validating your results to ensure accuracy and support informed decision-making.
Refer to the [Nexthink Insights - AI Model Card](https://docs.nexthink.com/legal/global-ai-hub/nexthink-insights-ai-model-card) documentation for more information.
{% 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.nexthink.com/user-guide/applications/monitoring-applications/monitoring-web-applications/ahead/delight.md?ask=&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.
