Outcome. A chat-originated ticket gets a satisfaction survey scoped to the chat experience, separate from the general CSAT send used for email and form tickets, so the team can compare chat quality on its own.
flowchart TD
A[Ticket status = Closed, source = Chat, not spam/test, not sent before] --> B[Send chat CSAT survey to requester]
B --> C[Set chat_csat_sent_date]

When to use it, when not to
- UseUse it when chat is a meaningful share of ticket volume and the team wants channel-specific CSAT numbers, not one blended score across every channel.
- UseUse it alongside tickets-sla-004, restricting that workflow to non-chat tickets so the two do not both send a survey to the same ticket.
- SkipDo not use it if chat volume is too low to produce a meaningful separate score; one blended survey from tickets-sla-004 is simpler and enough.
- SkipDo not use it if your survey tool cannot distinguish which survey to send by channel; check that a second, chat-specific CSAT survey actually exists before building the workflow around it.
or the tickets and sla pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





