> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/hablla/cs-cx/nps-and-satisfaction-survey.md).

# NPS and satisfaction survey

{% file src="/files/b9158ecc79713be7b2f20e0b99740653bfc75a74" %}

<figure><img src="/files/709778742b8a03aa4da1a6f74420b0be48c34c13" alt=""><figcaption></figcaption></figure>

## How to use this flow template in Hablla

This flow was created to facilitate interaction with customers, but to use it correctly some important points need to be adjusted.

### 1. Replace the WhatsApp templates

In the flow there are **two spots that use WhatsApp templates (HSM)**.

* These templates need to be replaced by your company's approved models.
* If you don't have approved templates yet, you will need to create them and submit them to Meta before replacing.

Without this replacement, the send will not work, since WhatsApp requires that only valid templates be used in outbound messages.

### 2. Adjust the Hablla components

In addition to the templates, the flow also has **two Hablla components** where the **survey test**:

* In the **first component**, add the survey test so that it validates the response received.
* In the **second component**, configure it the same way, ensuring the flow can correctly identify and classify the response.

These adjustments are mandatory for the flow to run without errors and deliver the expected results.

### 3. Correct way to trigger

This template **must not be used in manual individual interactions**.\
It was designed to be triggered in **bulk**, that is, through a previously defined customer list.

This way, each contact receives the initial template, and the responses follow the flow automatically, ensuring greater efficiency in the process.

***

✅ **Summary:**

* Replace the two WhatsApp templates with approved versions.
* Configure the survey ID in the two Hablla components.
* Always run the flow by **bulk customer dispatch**.

📌 **Practical tip:** Before running in production, do a test with a reduced contact list to confirm that the replacements and configurations are working correctly.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hablla.com/hablla-docs-en/hablla/cs-cx/nps-and-satisfaction-survey.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.