> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/intelligence/heart/happiness.md).

# Happiness

What the Happiness dimension measures, how the CSAT survey works, and when the dimension is ready to contribute to HEART.

Happiness is the HEART[^1] dimension that captures how users feel about an application. It is the only dimension based on direct user feedback rather than behavior. Userlane sends a standardized customer satisfaction (CSAT) survey automatically, with a fixed question and scale and nothing for you to configure.

## What Happiness measures

Happiness answers three questions about an application:

* How satisfied are users with it overall?
* Is satisfaction improving or declining over time?
* Which audiences are most or least satisfied?

The other four dimensions score what users do, how often, and how successfully. Happiness asks users directly and scores the answers.

<div data-with-frame="true"><figure><img src="https://259567114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF6bxg8i3T6U4vZ3k7PHi%2Fuploads%2FgcsSg5imBDGPCCI7PAGp%2FH%20HEART.png?alt=media&#x26;token=084f3d39-af29-4844-bfc3-ba370660e36e" alt="Happiness dimension in the HEART scorecard"><figcaption><p>The Happiness dimension detail in the HEART scorecard.</p></figcaption></figure></div>

{% hint style="warning" %}
Net Promoter Score (NPS) surveys and standard surveys are separate and **do not feed** Happiness. Only the standardized CSAT survey described below contributes to the Happiness score.
{% endhint %}

## How the score is calculated

The Happiness score is the share of CSAT responses rated 4 or 5, out of all responses received, on a scale of 0 to 100.

When Happiness is inactive, for example because the application has not collected enough responses yet, HEART handles it as described in [How the score is calculated](/intelligence/heart.md#how-the-score-is-calculated).

## The CSAT survey

The CSAT survey is run by Userlane. It appears in the **Messages** tab of the Assistant, alongside announcements and other surveys. For how surveys are delivered and how to read results, see [Surveys](/intelligence/surveys.md).

The survey asks "How satisfied are you with this application?" on a 1-to-5 scale, from "Very dissatisfied" to "Very satisfied", with an optional comment. The question, scale, frequency, and translations are fixed.

The survey runs quarterly per application. Each quarter a portion of active users receive it, rotating through the user base so coverage spreads evenly and nobody is surveyed too often.

The survey only starts once the application has enough active users. Until then, no survey is sent and Happiness stays **Calibrating**.

<div data-with-frame="true"><figure><img src="https://259567114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF6bxg8i3T6U4vZ3k7PHi%2Fuploads%2FAZQBH1G58LgzC15nQ8oJ%2FCSAT.png?alt=media&#x26;token=d04f46a7-ace4-4461-9b50-250fb91a9158" alt="CSAT survey shown to an end user in the Assistant"><figcaption><p>The standardized CSAT survey as end users see it.</p></figcaption></figure></div>

## Disabling CSAT

You can disable CSAT per application. When CSAT is disabled:

* No new surveys are sent for the application.
* Happiness is removed from HEART for that application.
* Data readiness[^2] moves to **Input Needed**.

Response history is kept. When you enable CSAT again, the survey resumes where it left off, without re-surveying users who were contacted recently.

## Relevant articles

{% content-ref url="/pages/TBF4QYHDMWQghy26u8xI" %}
[HEART](/intelligence/heart.md)
{% endcontent-ref %}

{% content-ref url="/pages/eZyCMoDQCbFnb6Z0c7g7" %}
[Surveys](/intelligence/surveys.md)
{% endcontent-ref %}

{% content-ref url="/pages/u9prdKFyiVHAh3Rcojqn" %}
[NPS: how to set up surveys that produce usable results](/best-practices/nps-how-to-set-up-surveys-that-produce-usable-results.md)
{% endcontent-ref %}

## FAQ

<details>

<summary>Does NPS affect the Happiness score?</summary>

No. NPS is a separate survey with its own analytics. Only the standardized CSAT survey feeds Happiness.

</details>

<details>

<summary>Can the CSAT question or scale be changed?</summary>

No. The question, scale, frequency, and translations are fixed.

</details>

<details>

<summary>How often is a user surveyed?</summary>

A few times a year at most, with several months between surveys.

</details>

<details>

<summary>What happens if the application does not have enough active users?</summary>

The survey does not start. Happiness stays **Calibrating** until the application reaches the required activity level.

</details>

<details>

<summary>What happens to survey data when CSAT is disabled?</summary>

Response history is kept. When CSAT is enabled again, the survey resumes without re-surveying users who were contacted recently.

</details>

<details>

<summary>Does the CSAT survey replace NPS?</summary>

No. NPS continues as a separate survey. CSAT feeds the Happiness dimension only.

</details>

[^1]: HEART is Userlane's five-dimension model for scoring how well an application works for the people using it, on a scale of 0 to 100.

[^2]: Data readiness shows whether a HEART dimension has enough data to produce a meaningful score. The three states are Ready, Calibrating, and Input Needed.


---

# 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.userlane.com/intelligence/heart/happiness.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.
