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

# Send Thread's built-in CSAT survey when a ticket closes

> Set up Thread's workspace CSAT survey so contacts rate closed tickets in Messenger, Microsoft Teams, Slack, or email, and see where those ratings show up in Thread Inbox.

> [!WARNING]
>
> Thread CSAT surveys are a limited-availability beta. Ask your Thread contact to turn them on for your workspace before you look for **CSAT** in Thread Admin.

Thread CSAT surveys ask a contact to rate a ticket without a third-party survey tool. Thread posts the survey, records the rating on the ticket, and shows it to your team in Thread Inbox.

You set up a **Default** survey for your whole workspace on the **CSAT** page in Thread Admin. Thread can send it automatically when a ticket closes, or only from Flows that use the **Send Thread CSAT survey** action. You can also create [named surveys](#use-a-named-survey-in-a-flow) and pick one in a Flow step instead of the Default survey.

If you already use a CSAT vendor such as CrewHu, see [Send a CSAT survey from a Flow](https://docs.getthread.com/inbox/send-a-csat-survey-from-a-flow.md) instead.

## Before you start

* You have Admin access to Thread.
* You know which boards and ticket sources should get a survey.
* Check whether your PSA already sends satisfaction surveys for those boards. If it does, contacts can get two surveys for the same ticket.

## Set up the workspace survey

The **CSAT** page in Thread Admin has three tabs: **Settings**, **Dashboard**, and **NPS**. The **Settings** tab lists your surveys under **Surveys**, starting with the **Default** survey. Select **Default** to open the **Default survey** page, which has its own **Survey**, **Post-survey**, and **Delivery** tabs.

**1. Open the Default survey**

In Thread Admin, go to **CSAT**. On the **Settings** tab, under **Surveys**, select **Default**.

**2. Turn on surveys**

On the **Survey** tab, turn on **Send CSAT surveys**.

**3. Choose when to send**

On the **Delivery** tab, under **Sending**, pick **Automatically when a ticket closes** or **From your flows**. See [Choose when the survey is sent](#choose-when-the-survey-is-sent).

**4. Adjust the survey and channels**

On the **Survey** tab, change any of the [survey settings](#choose-the-survey-settings). A preview next to the settings shows the survey as contacts see it. On the **Delivery** tab, under **Channels**, turn off any channel you don't want surveys on.

**5. Save your changes**

When you change a survey setting, an **Unsaved changes** bar appears at the bottom of the page. Select **Save** to store your changes, or **Discard** to undo them. If something still needs fixing, such as a missing board, **Save** stays off and the bar says what to finish first.

Survey changes apply to the next survey. Surveys already sent don't change. The **Surveys from your PSA** and **Send results to your CSAT vendor** settings on the **Delivery** tab and the **CSAT recognition** settings on the **Post-survey** tab still save as soon as you change them. If you try to leave the page with unsaved survey changes, Thread asks you to save or discard them first.

Thread sends one survey per ticket, whichever way it's sent.

## Choose when the survey is sent

### Automatically when a ticket closes

This is the recommended option. Thread sends the survey when the ticket moves to a status that counts as closed. To check which statuses count as closed, go to **Status automation** in Thread Admin.

You can limit the automatic send on the **Delivery** tab, under **Boards and statuses**:

* **Boards**: **All boards**, **Only these boards**, or **All boards except these**. For the last two, pick the boards to survey or skip.
* **Sources**: **All sources**, **Only these sources**, or **All sources except these**. For the last two, pick the ticket sources to survey or skip.
* **Statuses to skip**: a ticket closed in one of these statuses gets no survey. Leave it empty to survey every closed ticket.

Thread only surveys a ticket when it matches both limits. For example, if you pick one board under **Only these boards** and the Microsoft Teams source under **Only these sources**, Thread skips email tickets on that board. To survey every board except your internal one, choose **All boards except these** and pick that board.

An empty list covers everything in either mode. A ticket with no board or no source is only skipped by **Only these boards** or **Only these sources**. **All boards except these** and **All sources except these** still survey it.

With automatic sending on, a Flow's **Send Thread CSAT survey** action set to the **Default** survey doesn't send. The action card in the Flow builder shows a warning that says so. Actions that use a [named survey](#use-a-named-survey-in-a-flow) still send.

### From your flows

Pick **From your flows** when you need to target specific clients, contacts, or priorities. Only Flows with a **Send Thread CSAT survey** action send the survey. By default, they send the **Default** survey.

**1. Open Flows in Admin**

In Thread Admin, go to **Flows** and open the Flow you want the survey on, or create a new one. For a refresher on building Flows, see [Flows](https://docs.getthread.com/inbox/flows.md).

**2. Set the trigger**

Add the trigger you want the survey to fire on, such as a ticket moving to a closed status.

**3. Add the action**

Under **Add action**, choose **Send Thread CSAT survey**. Under **Survey**, keep **Default** to send your workspace survey, or pick a named survey. See [Use a named survey in a Flow](#use-a-named-survey-in-a-flow).

**4. Save the Flow**

Save the Flow. Only one CSAT survey action can run per trigger.

If **Send CSAT surveys** is off on the **Default** survey, the action doesn't send, and the card shows a warning. This applies to named surveys too.

A Thread CSAT survey and a vendor CSAT survey can't both run for the same tickets. If an active Flow sends a vendor survey, such as the **Send CSAT survey** action, to tickets your Thread survey also covers, Thread doesn't save the Flow. The message names each conflicting Flow with a link to it. Turn one of the Flows off, or limit both to different boards with a **Board** condition. Thread runs the same check when you save the **Default** survey with **Automatically when a ticket closes** selected.

### Use a named survey in a Flow

Use a named survey when some tickets need a different survey from the rest of your workspace. For example, one client can get a 5-star survey while everyone else gets 3 faces.

**1. Create the survey**

On the **CSAT** page's **Settings** tab, under **Surveys**, select **New survey**. Give it a **Name**, set the rating scale, questions, and other [survey settings](#choose-the-survey-settings), and save it. You can only create a named survey after the **Default** survey has been saved.

**2. Pick it in a Flow**

In the Flow's **Send Thread CSAT survey** action, pick the survey under **Survey**. Select **Edit in CSAT settings** under the field to change it later.

Each named survey is listed under **Surveys** with the number of Flows that send it, or **Not used in any flow yet**. A survey that a Flow still uses can't be deleted. Remove it from those Flows first.

To stop a named survey without deleting it, turn off the switch next to it under **Surveys**. Its card then reads **Off**. A Flow step that picks a survey that's off sends nothing, and the ticket shows why the survey wasn't sent. Turn the switch back on to send it again. Surveys that are off still show in the ratings report filters.

Tickets that a Flow with a named survey matches get that survey instead of the Default survey, never both. This works with both **Automatically when a ticket closes** and **From your flows**. Thread still sends one survey per ticket. Tickets that no such Flow matches get the Default survey as usual.

Actions saved before this option existed keep sending the workspace survey. Actions that had their own custom survey keep sending it, and show **This step has its own survey from before named surveys**, until you pick a survey.

## Choose the survey settings

| Setting | What it controls | Default |
| - | - | - |
| **Rating scale** | **3 faces** (Happy, Neutral, Unhappy), **5 stars** (Very poor to Excellent), or **Thumbs up/down**. On the 5-star scale, 4 and 5 stars both count as positive. | 3 faces |
| **Rating order** | **Bad to good** or **Good to bad**: the order contacts see the rating options in. Scores stay the same. A PSA survey link you already pasted keeps its order until you create a new key and paste it again. | Bad to good |
| **Rating names** | The name shown on each rating option in every channel, 1 to 30 characters each. Scores stay the same. | The scale's default names |
| **Question** | The text shown above the rating buttons, up to 200 characters. | How did we do? |
| **Ask for a comment** | **Never**, **After a negative rating**, or **Always**. | Always |
| **Survey expires after** | How many days the contact has to answer, from 1 to 30. | 7 days |
| **Survey frequency** | **Every closed ticket**, or **At most once every** a set number of days (1 to 90). | Every closed ticket |
| **On a negative rating** | What Thread does when a contact gives a negative rating. See the next section. | Notify the assigned technician |
| **Rating icons** | **Thread icons**, or **Custom** icons with a light and dark version for each rating. For each icon, paste an `https://` URL or upload a PNG, JPEG, GIF, or WebP image of up to 512 KB. A preview shows the whole survey. | Thread icons |

**Survey expires after** and **Survey frequency** are on the **Delivery** tab, under **Timing**. The other settings are on the **Survey** tab.

The frequency limit counts per contact across all of their tickets. If a contact was surveyed on any ticket within the window, Thread skips the survey.

### Add follow-up questions

**Follow-up questions** are set per rating. Pick a list under **Follow-up questions**, then add questions to it:

* **If positive**: asked only after a positive rating.
* **If neutral**: asked only after a neutral rating. Thumbs up/down surveys have no neutral rating, so they skip this list.
* **If negative**: asked after a negative rating.
* **If negative, no comment**: asked after a negative rating when the contact leaves no comment. Once this list has a question, it replaces the **If negative** questions for that rating. With **Ask for a comment** set to **Never**, it applies to every negative rating.

Each list holds up to three questions. Questions from older surveys that are asked for every rating count toward that limit. Each question can be a **Scale 1–5**, **Multiple choice**, **Yes / No**, or **Free text** question.

You can also turn on quick reasons. These are one-tap answers the contact can pick after rating, such as **Fast response** or **Not fixed**. You set one list for positive ratings (**What went well?**) and one for every other rating, with 2 to 6 reasons in each. Positive ratings are the top face, thumbs up, or 4 or 5 stars.

## Decide what happens after a negative rating

Pick one option under **On a negative rating**:

* **Do nothing**: Thread records the rating and takes no other action.
* **Notify the assigned technician**: the technician credited with the ticket gets an in-app notification with the rating and comment.
* **Notify a manager on duty**: under **Who to notify**, choose **Manager on duty** or **Team admins of the ticket's team**.
  * **Manager on duty**: the member you pick gets a Slack or Teams message with the rating and comment. Thread only notifies an active member of your workspace who can see the ticket.
  * **Team admins of the ticket's team**: each team admin on the credited technician's Thread teams gets one Slack or Teams message. The credited technician isn't told. If the team has no team admin, Thread tells the manager you pick, then workspace admins.
* **Post to a channel**: Thread posts the rating and comment to the channel you pick.
* **Add an internal PSA note**: Thread adds an internal note with the rating and comment to the ticket in your PSA.

### Let contacts reopen the ticket

To give contacts a way to say the problem isn't fixed, open the **Default** survey's **Post-survey** tab and turn on **Show 'Issue not resolved' button** under **Negative ratings**. The setting is off by default. You can also turn it on for a custom survey in a Flow step.

The **Issue not resolved** button sits apart from the rating buttons. When a contact presses it:

1. The contact must leave a comment that says what's still wrong.
2. Thread reopens the ticket, in Thread and in your PSA. It moves the ticket to the status you picked for its board under **Move the ticket to**, or to the board's reopen status when you didn't pick one.
3. Thread assigns the ticket back to its last technician, who gets the usual assignment notification.
4. Thread adds the comment, and any earlier rating, as an internal note on the ticket.
5. The contact sees a message that the ticket was reopened.

A survey marked not resolved no longer counts toward your CSAT %, even if the contact rated it first. The contact can't rate or comment on that survey again. In Thread Inbox, the survey shows a **Not resolved** tag.

The button only appears when the ticket's board has a reopen status. If Thread can't reopen the ticket, the contact is asked to reply to their ticket instead.

The button works in Messenger, Microsoft Teams, and on the email rating page. Slack surveys don't show the button yet.

### Alert admins about negative ratings

Workspace admins and the credited technician's team admins get an in-app notification in Thread Inbox for each new negative rating, whatever you pick under **On a negative rating**. Thread only notifies people who can see the ticket and its client.

To also post the alert in Microsoft Teams, open the **Default** survey's **Post-survey** tab, go to **Negative ratings** > **Alert a Teams channel**, and pick a team and channel. The post names the workspace admins and the credited technician's team admins. Select **Clear channel** to stop posting.

### Automate on ratings

To build more of your own automation on ratings, create a Flow with the **CSAT rating received** trigger. You can filter it on **CSAT score (0–100)**, **CSAT rating is negative**, **CSAT rating is positive**, and **CSAT rating channel**. On the 5-star scale, a 4-star or 5-star rating fires **CSAT rating is positive** and counts toward your CSAT %. **CSAT rating channel** includes Slack.

## Post every rating to a channel

To see each new rating in Slack or Microsoft Teams, open the **Default** survey's **Post-survey** tab and go to **Results channel** > **Post each rating to a channel**. Pick a channel, then choose **All results** or **Negative results only**.

Thread posts each counted rating with its label, the comment, the technician's first name, and a link to the ticket. The contact's name isn't included. If an admin later changes the score or hides the rating, Thread posts a second message. Select **Clear channel** to stop posting. To pick a channel, your workspace needs Slack or Microsoft Teams connected.

## Decide what happens after a positive rating

These settings are on the **Default** survey's **Post-survey** tab.

* **Message the technician**: under **Positive ratings**, turn this on to send the credited technician a Teams or Slack message with the rating, the ticket, and the comment.
* **Google review link**: under **Positive ratings**, paste an `https://` link to your Google review page. After a positive rating, the Messenger thank-you message and the survey email page offer **Leave us a review** with this link. Leave it empty to offer nothing.

The preview beside the **Post-survey** settings shows what the contact sees and what the technician gets after a rating. Switch between **Positive** and **Negative** to check both.

## Brand the survey

These settings are on the **Default** survey's **Survey** tab.

* **Survey page logo and name**: under **Survey page branding**, set the **Logo URL** and **Name** shown on the page contacts open from an email or PSA survey link. Leave both empty to use your company name and, when your Messenger logo is an `https://` URL, that logo.
* **Rating card icon**: choose the badge above the question on the rating card. Pick **None**, **Logo** (your **Workspace logo** or an **Uploaded image**), or **Technician photo**, which shows the credited technician's profile photo and hides the badge when there's no photo. This choice also updates surveys already sent.

## Where contacts see the survey

Thread sends the survey on the channel the contact uses for that ticket. Microsoft Teams and email surveys are turned on separately during the beta. If a channel isn't on for your workspace, the **Channels** section on the **Default** survey's **Delivery** tab shows **Not available** next to it.

To stop surveys on Messenger, Microsoft Teams, or email, turn that channel off under **Channels**. Thread then uses the ticket's next available channel. For example, with Messenger off, a ticket that also has a Teams chat gets the survey in Teams, and a ticket with no Teams chat gets the survey by email.

Slack surveys are off by default. To turn them on, turn on **Send surveys in Slack** under **Channels**.

* **Messenger**: a rating card appears in the conversation.
* **Microsoft Teams**: a rating card is posted in the ticket's Teams chat.
* **Slack**: the contact gets a message with rating buttons in their Slack DM. On the 5-star scale, the message shows one row per star level, each with a **Select** button, like the Teams card. After rating, they can use **Change** to pick a different rating and **Add comment** or **Edit comment** to leave a comment of up to 500 characters. Thread keeps their latest answer while the survey is open.
* **Email**: for tickets that came in by email, the contact gets an email with rating buttons.

Thread does not send a survey when:

* The ticket has no contact.
* The contact has no channel Thread can reach.
* The ticket already has a survey.
* With automatic sending, the ticket's board or source isn't covered by your **Boards** or **Sources** choice.
* **Only survey closed tickets** is on and the ticket isn't closed.

When Thread skips a survey, the ticket's CSAT section in Thread Inbox shows **CSAT survey not sent**, with the reason and the time.

### Also email the survey on PSA tickets

Tickets from your PSA usually get the survey in Messenger, Teams, or Slack, so the contact never gets it by email. To also email those contacts, turn on **Also email the survey on PSA tickets** under **Channels** > **Email**. It's off by default, and only shows when email ratings are on for your workspace.

With it on, Thread emails the survey in addition to the chat survey. Both are the same survey, so the contact answers once. Thread skips the email when you send surveys from your PSA.

### Surveys sent from your PSA email template

The survey that Thread provides for your PSA's email template uses its own fixed rating scale, labels, and comment prompt. After the contact rates, it also asks your workspace's [follow-up questions](#add-follow-up-questions) and quick reasons, the same as the workspace survey.

By default, the survey link only rates closed tickets. If your team closes in two steps and leaves a ticket in an open status such as Completed first, add those statuses per board on the **Delivery** tab, under **Surveys from your PSA** > **Statuses the survey link rates**. The link then rates a ticket while it sits in one of those statuses, for 7 days after its last update.

### Only survey closed tickets

If you send surveys from your flows, you can make sure contacts only rate finished work. On the **Default** survey's **Delivery** tab, under **Sending**, turn on **Only survey closed tickets**. This setting only shows when **From your flows** is selected, because automatic surveys already go out on close. It's off by default. When it's on, Thread checks that the ticket is closed before it sends the survey. A ticket counts as closed when it's **Done** in Thread or closed in your PSA. Thread skips tickets that aren't closed. If Thread can't reach your PSA to check, it still sends the survey.

Turn this on once your CSAT Flows filter on a closed status. The Flow builder shows a warning when a Flow with the **Send Thread CSAT survey** action filters on a status that leaves the ticket open. The warning is advisory and never blocks saving.

### Hand contacts off to Crewhu

If your workspace's Crewhu hand-off is on, Thread sends contacts on to your Crewhu survey after they rate. Thread fills in the rating, the ticket, and the technician the rating is credited to. The hand-off depends on where the contact answered:

* **Email** and **PSA email**: after the last step on the rating page, the contact goes straight to Crewhu.
* **Messenger**: the thank-you message shows a **Continue to the survey** link.
* **Slack**: the thank-you message shows a **Continue to the survey** button.
* **Microsoft Teams**: no hand-off. The contact only answers the Thread survey.

The Crewhu hand-off is off by default and needs a link to your Crewhu survey. To turn it on, ask your Thread contact. For Crewhu surveys sent from a Flow instead, see [Crewhu CSAT survey integration](https://docs.getthread.com/crewhu-csat-survey-integration.md).

## Where your team sees ratings

After a contact rates a ticket, the rating shows up in Thread Inbox:

* In the ticket feed, next to the survey that was sent.
* In the ticket's **Sentiment** card.
* On ticket cards.
* In the ticket list, in a **CSAT** column after **Sentiment**. To choose which rating columns show, open the **Display** menu and pick an option under **Rating columns**: **CSAT and Sentiment**, **CSAT only**, or **Sentiment only**.


## Related topics

- [Set Up a SmileBack CSAT Survey with Snippets](https://docs.getthread.com/inbox/how-to-setup-a-csat-survey.md)
- [Configure Status Mapping in Thread](https://docs.getthread.com/get-started/status-mapping-in-thread.md)
- [What is Thread?](https://docs.getthread.com/get-started/what-is-thread-an-overview.md)
