Outcome. A set number of days after a ticket closes, the requester gets a short NPS survey, giving a relationship-level signal that is separate from the immediate reaction a CSAT survey captures.
flowchart TD
A[Ticket status = Closed, not spam/test, contact not surveyed recently] --> B[Wait N days]
B --> C{Still closed?}
C -->|yes| D[Send NPS survey to requester]
D --> E[Set NPS last sent date on contact]
C -->|no, reopened| F[Skip - reopen workflow takes over]

When to use it, when not to
- UseUse it alongside CSAT (tickets-sla-004) when you want a longer-horizon relationship health signal, not just "how did this one interaction go."
- UseUse it with a fatigue guard for contacts who close several tickets close together; NPS is meant to sample sentiment periodically, not fire on every close.
- SkipDo not send NPS on every single ticket close for a customer with frequent tickets; gate it, see Prerequisites and tickets-sla-039.
- SkipDo not use it as your only account-health signal; pair it with usage or product data where available.
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.





