Turning Negative JSM Feedback into Follow-Up Tickets Automatically

A 1-star rating on a resolved ticket is information. It tells you the interaction failed from the customer's perspective — the fix didn't work, the agent was unhelpful, or the resolution took too long. But most teams treat that rating the same way they treat 5-star ratings: they log it, it rolls into the average, and nothing else happens.

That gap — between capturing negative feedback and acting on it — is where customer trust erodes.

Why Manual Follow-Up Doesn't Scale

The instinct to "have someone review low scores" is right, but the execution is usually wrong. Manual review means:

Someone has to remember to check the CSAT dashboard
There's no SLA on when the follow-up happens
The customer who gave the low score never hears back unless someone specifically decides to reach out
If you're handling 100 tickets a week, "review the low scores" is a 30-minute task that regularly gets deprioritised

Automation solves the memory and consistency problem. You don't rely on anyone remembering — the system triggers the follow-up the moment the low score is submitted.

What a Good Follow-Up Workflow Looks Like

Before building anything, it's worth being clear about what you want to happen when a customer rates a ticket poorly. The most common patterns:

Pattern 1: Reopen and reassign When a ticket receives a 1 or 2-star rating, automatically reopen it and assign it to a senior agent or the original assignee's team lead. This signals to the customer that their feedback was heard and someone is looking at it again.

Pattern 2: Create a linked follow-up ticket Rather than reopening the original ticket (which muddies resolution metrics), create a new follow-up ticket linked to the original. The follow-up has a template description: "Customer rated this resolution 1/5. Review comments: [feedback text]. Please contact customer within 24 hours."

Pattern 3: Notify the team lead without creating a ticket For teams where volume is high and most low scores are edge cases, a Slack or email notification to the team lead may be enough — "Customer rated ticket IT-1234 as 1 star. Comment: [text]." The lead decides whether to act.

Most mature support teams eventually land on Pattern 2. It keeps the original ticket's resolution intact, creates a clear audit trail for the follow-up, and can be tracked as a separate SLA.

Setting This Up with Jira Automation

If your CSAT tool stores ratings as Jira issue custom fields (e.g., CSAT Rating), you can build this entire workflow using native Jira Automation — no third-party integration required.

Step 1: Create the automation rule

Go to your JSM project → Project Settings → Automation → Create rule.

Trigger: Field value changed
Field: CSAT Rating

Condition: Field value matches
CSAT Rating is less than 3 (adjust threshold to your preference — some teams use ≤ 2, others ≤ 3)

Step 2: Add a branch for the follow-up

Use a Branch action to target the current issue, then:

Action: Create linked issue

Issue type: Task (or your internal ticket type)
Summary: Follow-up required: low CSAT on {{issue.key}}

Description:

Customer rated issue {{issue.key}} as {{issue.CSAT Rating}}/5.

Customer comment: {{issue.CSAT Comment}}

Original issue: {{issue.summary}}
Resolved by: {{issue.assignee}}
Resolution date: {{issue.resolutiondate}}

Please contact the customer within 24 hours to understand what went wrong.

Assignee: The original assignee's team lead (use a smart value or a fixed user for your escalation path)
Priority: High
Link type: "is caused by" → link to original issue

Step 3: Set a due date

Add a second action to set the due date on the new ticket: {{now.plusDays(1)}}. This creates an automatic 24-hour SLA for follow-up.

Step 4: Notify the customer (optional)

If you want the customer to know their feedback triggered a review, add a Comment on issue action on the original issue:

"Thanks for your feedback. We've noted your rating and a member of our team will be in touch shortly to understand how we can do better."

This is optional — some teams prefer to handle it proactively via the follow-up ticket rather than making a visible comment.

Measuring the Impact

Once this automation is running, you can track:

Follow-up resolution rate — what percentage of low-score follow-ups get resolved within 24 hours
CSAT uplift — do customers who receive a follow-up give higher scores on subsequent tickets?
Root cause patterns — after a month of follow-ups, do themes emerge? (Specific agents? Specific ticket types? Specific times of day?)

That last one is where the real value is. Individual follow-ups fix one customer relationship. Pattern analysis fixes the process that created the problem in the first place.

The One-Line Rule

If you take nothing else from this: a low CSAT score should never be a dead end. Whether you automate a full follow-up workflow or just fire a Slack message to a team lead, every negative rating deserves a next action. The customers who bother to rate poorly are the ones still willing to engage — they're telling you something went wrong, and they're implicitly asking whether you care.

Myra stores CSAT ratings and comments as native Jira fields, which means Jira Automation can trigger on them directly — no webhooks or middleware. Install Myra free from the Atlassian Marketplace and have this workflow running today.