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

# Surveys

Create and send out-of-the-box and customized surveys to your customers

{% hint style="info" %}
You can create and send CSAT, NPS, or Custom surveys!
{% endhint %}

Create surveys on the [Surveys](https://app.usepylon.com/settings/surveys) page and preview how the survey looks in Slack, Email, Chat, and a Popup. Customize the wording of questions, coloring, notifications, who the survey is sent to and more.

Surveys come with:

* Customization on survey language, followup, and notifications
* Out-of-the-box analytics and raw results
* Audience and recurrence customization using triggers
* Live previews of what customers will see and ability to send yourself a preview

## CSAT

CSAT surveys are on a industry standard "Very Dissatisfied" to "Very Satisfied" 5-point scale.

Use [Triggers](https://docs.usepylon.com/pylon-docs/platform/triggers.md) to control the cadence and audience of your CSAT survey.

## NPS

NPS surveys are on a industry standard 0-10 scale with ranges for detractors (0-6), passives (7-8), and promoters (9-10). NPS surveys can also have a free response follow up and customization on coloring, language, and notifications.

These surveys can be sent on a cadence and can have additional configurations.

#### Progressive Rollout

Instead of sending the survey to all audience members at once, enabling progressive rollout will send out the survey to all eligible audience members evenly over the course of the recurring cadence.

Example: A monthly survey with 100 eligible audience members would send to 3-4 randomly selected audience members every day of the month.

#### Cooldown period

Set up a minimum time before survey responders get sent the survey again.

Example: Once an audience member responds to the survey, they won’t get sent the survey for 3 months, regardless of the rollout method or cadence.

#### Follow-ups

Remind audience members to fill out the survey if they haven’t responded yet.

Example: 3 days after the survey has been sent, if the audience member hasn’t responded yet, send the survey to them again

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FpAbeStLrp6HMls1SXx7h%2FScreenshot%202026-02-06%20at%2010.04.00%E2%80%AFAM.png?alt=media&amp;token=8ad60311-f4a0-46ca-bc83-61c681bca977" alt="" width="563"><figcaption></figcaption></figure>

## Custom

Create and send custom surveys with a custom rating scale and follow up question, across any supported source (Slack, Email, Chat, Popup).

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FMimHPQ0nsRFpOz7FO83t%2FCleanShot%202025-08-04%20at%2015.36.36%402x.png?alt=media&amp;token=8d8433af-6cec-48e7-9da2-c699f7e9f01e" alt="" width="375"><figcaption><p>Example of a customized popup survey</p></figcaption></figure>

### Link results to a field

Save answers to a custom survey question on the respondent's contact, so you can filter, report, and build rollups on them.

1. On a question, select **Link a Field**.
2. Enter a **Field name** and select **Save**. A new contact field will be created with this name when you save the survey.

The field type depends on the question:

| Question type   | Contact field created               |
| --------------- | ----------------------------------- |
| Linear Scale    | Number                              |
| Multiple Choice | Select, with the question's options |
| Short Answer    | Text                                |

Once linked:

* Each new response writes its answer to the respondent's contact. If the respondent skips the question, the field is left as is.
* Past responses to the question are backfilled in the background. Contacts who already answered get their most recent answer, unless the field already has a value.
* For Multiple Choice questions, new or renamed options are added to the field. Removing an option from the question keeps it on the field, so past answers keep their label.
* For new responses, field history shows which survey set the value.
* To change the question's type, unlink the field first. Duplicating a question doesn't copy its link.

To stop saving answers, select the **x** on the linked field and then **Unlink Field**. New answers to this question will no longer be saved to the field, but the field and its existing values aren't deleted.

Linking and unlinking require permission to manage contact field settings. Each field name must be unique among your contact fields.

{% hint style="info" %}
Use a `Most selected` [rollup](https://docs.usepylon.com/pylon-docs/account-intelligence/fields/rollups.md) to show the most common answer to a linked Multiple Choice question across an account's contacts.
{% 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.usepylon.com/pylon-docs/platform/surveys.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.
