Overview

A CSAT survey is the simplest way to measure how customers feel about their support experience.

After a teammate closes a conversation, you can automatically send customers an emoji rating survey with an optional comment box – so you can spot patterns, follow up with unhappy customers, and track how your team is performing over time.

How it works

When a teammate closes a conversation, the workflow waits 2 minutes in case the conversation reopens or the teammate replies again. After that window, the customer receives the CSAT survey – inside the Messenger if the conversation was on Web, or as an email reply with five emoji buttons if the conversation was on email.

The customer picks an emoji, and their rating is recorded against the most recent agent in the conversation – the teammate, Fibi, or the workflow that handled the chat. They can then optionally leave a written comment to add context.

Get started

1. Go to Automations → Workflows

2. Click + New Workflow and select the template "Ask customers to rate their closed conversation (CSAT)"

Configure trigger settings

First, configure the Trigger settings to decide who, where, and when the Workflow should run:

• Where to send (e.g. Web, Email)

• Audience (e.g. users, visitors, or specific customer segments like ‘Paying customers’)

• Scheduling (e.g. always, or only during/outside of office hours)

Notice that the trigger for this workflow is Teammate changes the state of a conversation and the only state selected is Closed. This means that this workflow will only ever trigger when a teammate has actively closed a conversation they consider resolved.

When finished, click ‘Save and close’ to start building your workflow.

Build your workflow

Once created, the template includes prebuilt steps you can edit to fit your tone and process:

1. Adjust the wait time – By default, the workflow waits 2 minutes after a conversation is closed before sending the CSAT survey. This buffer prevents the survey from going out if the teammate replies again or the customer reopens the conversation. You can shorten or extend this depending on how reactive your team usually is.

2. Configure the CSAT action – Click the Ask for conversation rating (CSAT) step to open its settings. Three optional toggles are available:

   • Prevent customers from rating after a given period of time – sets an expiration on the rating request. After this window, the customer can no longer rate

   • Prevent customers from changing their initial rating after a period of time – customers can rate any time, but once submitted they can only edit their rating within this window

   • Wait for customers to give a rating before continuing the Workflow – pauses the workflow until the customer rates, so you can branch on the response

3. Add branches for low and high ratings – After the CSAT step, you can split the workflow based on how the customer rated. Common pattern:

   • If Conversation Rating is less than Okay → send a follow-up message asking what went wrong, then assign the conversation to the support lead

   • If Conversation Rating is greater than Okay → end the workflow

   • Note: Branching only works when Wait for rating is turned on – the workflow can't branch on a rating it never waited for

4. Set it live – When you're happy with your setup, click Save and Set live.

With this workflow, every closed conversation turns into a chance to learn something – and dissatisfied customers don't slip through the cracks.