The Workflow Library

Library / Tickets and SLA / tickets-sla-010

NPS survey sent N days after ticket resolution

Tickets and SLATicketService Hub ProfessionalIntermediate~30 min to buildFull spec

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.

Workflow map Enrollment, branches and actions at a glance tickets-sla-010
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]
action or delay branch public on every spec, paid or not

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.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.4 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.5 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

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.