Your CSAT surveys are being ignored. You're getting a 6% response rate, you've been told that's "normal for email surveys," and you've more or less accepted it.
You shouldn't. Industry average CSAT response rates for B2B service desks on default email setups run 8–15%. If you're under 8%, that's not a participation problem — it's a process problem. And it's fixable.
There are four specific levers. Here's how each works and what you can do in JSM today.
1. Timing: Send the survey while the experience is still warm
The gap between ticket resolution and survey delivery is the single biggest variable you control. A survey sent 30 seconds after resolution captures a respondent who just completed their interaction. A survey sent 6 hours later — because Jira notifications queued up, or automation ran in a batch — reaches someone who has moved on.
Memory fades fast. Emotional signal fades faster.
In JSM, check your CSAT notification settings under Project Settings → Notifications. Look at the trigger for the "Customer satisfaction survey" notification. If it's triggered by "Issue resolved" but is sending within a scheduled digest window, responses will be delayed. The survey should fire immediately on resolution, not on a batch schedule.
If you're using custom automation to send surveys, check the rule trigger and confirm it fires on Issue Transitioned (to Done/Resolved), not on a scheduled basis.
The target: survey delivered within 5 minutes of resolution. Everything else being equal, surveys in this window consistently outperform delayed sends.
2. Channel: Get out of the promotions tab
JSM CSAT emails are automated emails from Atlassian's infrastructure. Gmail's promotions tab catches many of them. Outlook's focused inbox filters others. On mobile, they get swiped away in the morning inbox clear-out.
A better channel: a portal comment on the resolved ticket, posted automatically, containing the rating link. The customer is already in context — they went to the portal to check their ticket, they see the resolution, they see the feedback request right below it.
Here's how to set this up with JSM Automation:
- Go to Project Settings → Automation → Create rule
- Trigger: Issue Transitioned → Status is Resolved (or your equivalent closed status)
- Condition: Issue matches →
issueType in (Service Request, Incident)(adjust for your project) - Action: Comment on issue → check Visibility: Roles → select Service Desk Customers
- In the comment body, include your rating prompt and a link to the portal issue. Format it so it reads naturally — "How did we do? Rate your experience: [link]"
The customer receives this as a portal notification (if they've opted in) or sees it when they revisit the ticket. No email client, no promotions tab, no context switch.
3. Friction: Every extra step costs you respondents
The gold standard for CSAT is a single-click or single-tap rating. Any additional step — opening a separate form, being asked to log in again, being redirected to a third-party site — compounds drop-off.
Audit your current flow the way a distracted customer would. Open a resolved ticket in the portal. Find the satisfaction survey. Count the actions required before the rating is submitted:
- Does clicking the rating take you to a separate page? That's one extra step. Some respondents will close that page.
- Does that page require authentication? Another loss.
- Does it ask for more than a rating and an optional comment? Longer forms perform worse.
The JSM default CSAT (thumbs up/down) is low-friction but limited — you lose granularity. If you're using a marketplace app, make sure the rating widget is rendered inline in the portal, not behind a link. If it's behind a link, you're losing a significant percentage of willing respondents before they ever see the question.
4. Follow-up reminders: Build what JSM doesn't ship
JSM has no native CSAT reminder. If a customer doesn't rate within the first few hours, the survey expires silently.
You can approximate a reminder with an Automation rule. The logic: 48–72 hours after resolution, check whether the satisfaction field is still empty. If it is, re-send the portal comment with the rating request.
Here's the setup:
- Trigger: Scheduled — runs daily
- JQL for issue filter:
project = YOUR_PROJECT AND status = Done AND "Customer satisfaction" is EMPTY AND resolved >= -72h AND resolved <= -48h - Action: Comment on issue (same template as the initial request, slightly reworded — "We'd still love to hear how we did on your recent request.")
Adjust the -72h / -48h window to match your preference. Don't send more than one reminder — two unsolicited requests in a week feels pushy and can generate negative sentiment before a rating is even given.
This alone typically adds 3–5 percentage points to response rate, because some customers simply miss the first notification.
What to expect
Implementing all four fixes won't take you from 6% to 60%. The realistic ceiling for a well-configured B2B service desk is 25–35% on portal-native CSAT, lower if email is your only channel. But getting from 6% to 20–25% transforms your data from anecdote to signal — enough to break down scores by agent, by ticket type, by week, and actually see patterns.
The process problems will surface quickly. That's the point.
Forge-based apps like Myra handle follow-up logic and multi-channel delivery natively — including portal-embedded ratings, automated reminders, and response writeback to Jira fields. Worth a look if you'd rather not wire up five automation rules manually.