Agents live in Jira Service Management. CSAT lives somewhere else — a form tool, a CX suite, a spreadsheet export from last quarter. That split is a problem, not a neutral architecture choice.
Symptoms
- Leadership asks “what’s our CSAT?” and three people open three tools
- Agents never see the score on the ticket they just worked
- Negative feedback arrives as an email to a shared inbox, not an issue
- Reporting requires manual joins on issue keys that sometimes do not match
- Security / compliance asks where customer comments are stored — and the answer is “also over there”
Why it happens
Teams reach for familiar survey products because sending a form is easy. Integration is promised later. Later becomes a brittle sync: tags, comments, or custom fields that drift out of date.
Meanwhile the system of record for the work — Jira — only knows the ticket happened, not how it felt.
Cost of the split
- No closed loop — recovery depends on someone watching the other tool.
- No trustworthy segmentation — queue, request type, and SLA context are painful to reattach.
- Adoption death — agents will not open a second analytics home every day.
- Audit risk — customer free text sits outside the Atlassian boundary you already govern.
What “fixed” looks like
Feedback does not have to be primitive. It has to be operable next to the issue:
- Score and comment visible where agents work
- Trends sliceable with Jira fields you already trust
- Poor scores creatable as follow-up work
- Clear answer to “where does the data live?”
Next step
If this is your pain, look at use cases for collecting and reporting CSAT inside JSM.