NPS in Jira Service Management is a common leadership ask once CSAT exists. Loyalty is not the same as ticket satisfaction — and treating NPS like a post-resolution CSAT question usually pollutes both metrics.
The outcome
You run relationship-style NPS on a sensible cadence, store responses where service context still exists, and keep CSAT as the transactional metric on resolved work.
How it differs from CSAT
| CSAT | NPS | |
|---|---|---|
| Question shape | How satisfied with this interaction? | How likely to recommend? |
| Timing | After resolution | Lighter cadence / cohort pulses |
| Use | Ops quality | Relationship / advocacy |
Practical workflow
- Keep CSAT on resolution for most requests.
- Sample NPS for key accounts, portal cohorts, or quarterly pulses — not every ticket.
- Store responses in Jira so CX and ops share one record.
- Route detractors into follow-up ownership.
- Add CES later only where effort complaints already show up.
Pitfalls
- Asking NPS on every resolved incident
- Mixing NPS and CSAT into one vanity average
- Parking NPS in a tool agents never open
Next step
If you need the full trio, see the CSAT + NPS + CES use case. If you are choosing who this is for, open the for pages for CX leaders and JSM admins.