A low score that nobody owns is worse than no score — it teaches requesters that feedback is ignored. Closed-loop follow-up turns negative CSAT/NPS/CES into tracked Jira work.
The outcome
When a score crosses your threshold, a follow-up issue (or linked task) is created, assigned, and visible next to the original request. Managers can report on recovery workload, not only averages.
Workflow
- Define thresholds (e.g. CSAT ≤ 2, NPS detractors, high CES effort).
- On response, create or link a follow-up issue with score + comment context.
- Route by queue / request type ownership rules.
- Measure time-to-first-response on follow-ups.
- Feed themes back into knowledge base and workflow fixes.
Why teams need this use case
Reporting without recovery is vanity. Recovery without ticket context is chaos. Closing the loop inside JSM keeps both in one system.
Next step
Pair with for pages for support/CX leaders when you want role-specific fit.