> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Collect CSAT, NPS and CES surveys

> Configure CSAT, NPS and CES in OpenCX, choose one automatic survey after a session closes, and use workflows to control delivery and follow-up.

Use **Settings → Surveys** to configure three independent surveys:

| Survey | Measures | Scale |
| - | - | - |
| CSAT | Satisfaction with the support experience | 1–5, higher is better |
| NPS | Likelihood of recommending your business | 0–10 |
| CES | Ease of getting help | 1–5, higher is easier |

Each survey has its own channels, question, delay, resend rules, score-change window, email template and feedback page. A session can have one recorded response for each type. A new response updates that type’s existing score and comment; it does not overwrite the other surveys.

## Choose when to send

Open the **CSAT**, **NPS** or **CES** tab for the survey you want to configure. Under **Delivery**, turn on **Send automatically after a session closes**, then choose the delay. Only one survey can send automatically. If another survey already does, the page explains which survey saving will replace.

Enable the delivery channels, then click **Save CSAT**, **Save NPS** or **Save CES**. This applies all changes in that tab together. The **Auto** badge identifies the saved automatic survey. To stop automatic sending, switch it off in that survey's tab and save. Workflows can still send surveys.

New survey types start disabled. The default delay is five minutes. Changing tabs keeps unsaved edits; each tab has its own save button and changes in other tabs remain unsaved.

Changing the automatic selection affects future closes. A survey already scheduled keeps its original type. Channel eligibility and that type’s resend rules still apply when it sends.

Automatic sending requires OpenCX to manage session closure. With an external ticketing integration, use workflows to control survey delivery.

You need permission to read **Surveys** settings to view the page, and write permission to change settings or send a test email. Existing CSAT permissions continue to grant this access.

## Send through workflows

Every type has matching actions:

* **Send CSAT/NPS/CES Request** sends through the session’s channel, using that type’s settings.
* **Generate CSAT/NPS/CES Link** returns a hosted feedback link for a message you control.
* **Get CSAT/NPS/CES Score** retrieves the latest response for the session.
* **Cancel CSAT/NPS/CES Request** stops accepting responses to the outstanding request. It does not delete a recorded score or recall a delivered message.

Use the matching **CSAT/NPS/CES Score Submit** trigger for follow-up. NPS and CES submission triggers can filter by session channel, direction, status and sub-status before a workflow starts. For example, a low CES response can trigger an internal follow-up, while an NPS response can feed a separate customer relationship workflow.

Workflows can send any survey even when another type is selected for automatic sending. Filter sessions on the workflow trigger and use delays and conditions to choose the timing. NPS does not have to follow every closed session: use a workflow to target the customers and occasions that fit your feedback program.

Open **Advanced settings** to change how often a session is surveyed and whether customers can change their scores. The default resend rule is **Once per session**. **Once per close**, **Until answered** and **Always** are also available. Rules apply independently to each type and cover automatic sends and the corresponding Send Request workflow action. **Until answered** defaults to a seven-day wait. Customers can change scores without a time limit unless you enable **Prevent score changes**; comments remain editable after a score locks.

## How customers receive surveys

All types use the existing CSAT delivery channels and eligibility checks.

| Channel | Delivery |
| - | - |
| Web Chat | Native rating card in supported widgets; a hosted feedback link in older widgets |
| Email | Rating links leading to the feedback page, followed by an optional comment |
| WhatsApp | CSAT and CES use a five-option native list; NPS uses a hosted link for its 0–10 scale |
| SMS / Phone | SMS with a hosted feedback link |
| Web Voice | Email follow-up |
| Slack | A reply containing the feedback link |
| Instagram / Messenger | A message containing the feedback link |
| API channel | Email delivery when a customer email is available |

WhatsApp delivery requires an eligible customer reply window. Voice surveys are follow-ups; they are not an in-call keypad survey. Existing external CSAT survey detection and imports remain CSAT-only and do not suppress NPS or CES.

## Customize email and feedback pages

Under **Appearance**, use **Preview** to inspect the feedback page or email. Choose **Customize** beside either design to open its editor, then **Insert starter template** to start editing. Without a custom template, the email preview uses the default survey design and your saved survey wording. Your email channel can add its own surrounding design and signature. Feedback-page previews use the starter design. Email previews open the page preview when you click a rating. **Send test email** sends the current email template to your own account email. Save each tab to use its templates for future sends.

Default CSAT feedback pages and emails use labeled emoji ratings. NPS and CES use numbered scales with clear endpoint labels. Choosing a rating opens the optional comment step. Leave template fields empty to use the default designs; existing custom HTML stays unchanged. NPS email templates support `score_link_0` through `score_link_10`. CSAT and CES support `score_link_1` through `score_link_5`. NPS and CES templates also support `survey_link`; the existing `csat_link` variable remains accepted. Each email needs at least one rating link.

Custom pages use the same `data-csat-score`, `data-csat-submit` and `OpenCX.csat.submit(...)` controls as CSAT. These names remain the same for all three types. The receiving page validates the appropriate score range, including NPS **0**. Web template context contains session and organization details, not customer contact details.

Default questions follow the session language where supported. A custom question is used as written.

## Read the results

The session timeline shows separate requested, submitted and cancelled events for each survey. Responses preserve the agent and team attribution captured at first submission.

Use the [CSAT API](https://docs.open.cx/api-reference/csat.md), [NPS API](https://docs.open.cx/api-reference/nps.md) or [CES API](https://docs.open.cx/api-reference/ces.md), the corresponding MCP tools, or a Mini-App to read results. Existing CSAT reports and exports remain CSAT-only. NPS and CES are available through separate analytics views: `report_nps` and `report_ces`, with matching `report_partner_nps` and `report_partner_ces` for partner reporting.

**NPS** is the percentage of promoters (9–10) minus the percentage of detractors (0–6). Passives (7–8) count in the total responses. For example, two promoters, one passive and one detractor produce **25**. Do not report the average numeric rating as NPS. No responses means no NPS value, rather than zero.

**CES** is the average of the 1–5 ratings. Higher means easier. Keep survey types separate when aggregating.

Subscribe to `nps.requested`, `nps.score_submitted`, `ces.requested` and `ces.score_submitted` for integrations. See [webhook payloads](https://docs.open.cx/api-reference/webhooks/types.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.