What it does
When a ticket is resolved, Chatarmin CX can send the customer one short satisfaction survey. The customer rates the support they received, and the score appears in your CSAT reporting. Three settings on this page decide whether a survey goes out:
A separate Skip panel holds surveys back, including Tickets with these tags.
If your CSAT survey was carried over from an earlier CSAT agent, the channels, inboxes, and skip tags from that agent still apply. Everything on this page works within that scope.
Set it up
1
Turn the survey on
In Survey, switch on Send a satisfaction survey. While this is off, no survey goes out at all, whatever the channel switches say.
2
Switch on a channel
In When and where, switch on Email, WhatsApp, Live chat, or Social. Each switch sends only on that channel group. Email includes contact forms; Social covers Instagram, Facebook, and TikTok.
3
Set the send delay
Each switched-on channel shows its own delay, for example after 48 hours. Choose a number and a unit: minutes, hours, or days. Count from sets the starting point: when the ticket is resolved or the customer’s last message.
4
Choose the inbox scope
Under Inboxes, choose All inboxes, Only these inboxes, or All except these inboxes. The scope applies to every switched-on channel.
5
Add skip tags
In Skip, add tags to Tickets with these tags. A ticket carrying any tag on this list gets no survey.
Inbox scope
- All inboxes covers every inbox in the workspace, including inboxes you add later. No inbox is excluded.
- Only these inboxes sends only from the inboxes you list. Add each inbox explicitly.
- All except these inboxes sends from every inbox except the ones you list.
Skip tags
Tickets with these tags is the built-in survey’s own skip list. The survey skips a ticket when the ticket carries a tag on this list. Tags that AI agents or workflows use in their own survey logic — for exampleno_csat or csat_sent — are not part of this list automatically. Adding a tag to an agent or workflow does not protect a ticket here: add the tag to Tickets with these tags instead.
Skip has other rules beside the tag list, and some tickets are always skipped. Open Always skipped in the Skip panel to see the current list (for example spam, social comment threads, side conversations, and email customers without an address).
Before a new inbox goes live
When you add an inbox, check three things before it starts receiving tickets:1
Check the master switch
In Survey, is Send a satisfaction survey on or off? While it is off, no inbox receives a survey.
2
Check the inbox scope
In When and where, look at Inboxes. All inboxes pulls the new inbox in automatically. With Only these inboxes or All except these inboxes, check whether the new inbox belongs in the list.
3
Check the skip list
In Skip, review Tickets with these tags. If tickets from the new inbox must never be surveyed, add the tag your team uses to the list.
Export survey results
To export individual surveys for reporting, use the CSAT, session and ticket-action exports endpoint.FAQ
A resolved ticket got no survey. Why?
A resolved ticket got no survey. Why?
Check Send a satisfaction survey first. Then check the channel switch for the ticket’s channel and the Inboxes scope. Finally, check the Skip panel: a tag on Tickets with these tags, one of the other skip rules, or an always-skipped ticket all hold the survey back.
Do no_csat or csat_sent stop the built-in survey?
Do no_csat or csat_sent stop the built-in survey?
Not by themselves. A tag that an AI agent or workflow checks for itself does not stop the built-in survey; add the tag to Tickets with these tags so the survey respects it.
Can the built-in survey send twice on one ticket?
Can the built-in survey send twice on one ticket?
No. The built-in survey sends at most one survey per ticket and skips a ticket that already has one.
What does “Tag the ticket after sending” do?
What does “Tag the ticket after sending” do?
In Survey, Tag the ticket after sending adds the tags you choose once the survey has gone out. It is not a skip list, and it does not hold a survey back.
Who can change these settings?
Who can change these settings?
Teammates with the Manage CSAT surveys permission, which Admins have by default. See Roles and permissions.