Outcome. A low CSAT score on a closed ticket reaches the owner and their manager within minutes, with a task already sitting in the owner's queue, instead of surfacing only in a monthly satisfaction report.
flowchart TD
A[csat_score known and <= 2] --> B{Score value?}
B -->|1| C[Alert owner + escalation contact, immediate task]
B -->|2| D[Alert owner, task due next business day]
C --> E[Add to Negative CSAT - needs review list]
D --> E

When to use it, when not to
- UseUse it once a CSAT survey is already sending on ticket close (see tickets-sla-004) and the team wants a real-time save attempt on unhappy responses, not just a scorecard.
- UseUse it when a manager wants visibility into individual bad scores as they happen, for coaching or direct customer recovery.
- SkipDo not use it without a working CSAT send already in place; this workflow only reacts to a score, it does not send the survey itself.
- SkipDo not use it if survey volume is high enough that every low score already gets manual review some other way; duplicate alerting adds noise without adding coverage.
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.





