Enable Workflows to Trigger Based on Final CSAT Rating (Post-Update) | Community
Skip to main content
Submitted

Enable Workflows to Trigger Based on Final CSAT Rating (Post-Update)

Related products:Workflows

Description:

In our current CSAT workflow, we occasionally see customers accidentally click a negative rating and then immediately change it to a more accurate, positive score (e.g., from “Terrible” to “Great”). However, Intercom currently triggers workflow branches based on the first submitted CSAT rating, not the final one.

 

This results in workflows being misrouted, customers receiving unnecessary follow-ups, or agents being wrongly notified for poor feedback that was actually revised.

 

Request:

Introduce the ability for workflow branches to trigger only after the CSAT input is finalized, i.e., after a brief delay or when the customer has stopped interacting with the CSAT for a set time (e.g., 30 seconds). Alternatively, allow the workflow to consider the last rating submitted, not just the first.

 

Why it matters:

 

  • Reduces false negatives in CSAT reporting

  • Prevents unnecessary escalation or remediation steps

  • Improves accuracy of agent performance tracking

  • Enhances customer experience by respecting their updated input

 

We already use the “Wait for customer to give rating” toggle, but this doesn’t solve the issue of rating changes after the initial input.

 

Frequency:

This is not a rare edge case for us—we’ve seen multiple instances of customers correcting their rating within seconds, which shows this is a meaningful pattern, not a one-off.

2 replies

This would be great to have!!! Currently, we are limited on triggers where a team member has to change the conversation state (does not account for FIN), and when customer sends any message (which only works if they reply after giving a csat score). Adding this would be great for internal reporting!


I agree that this is a must. Our workflow is that we want to dive deeper into customer feedback over “less than OK” ratings, but there are so little options to do so over the email. Furthermore, if the initial communication channel is Email, but customer sets a rating over the chat, that part of workflow will not trigger at all. And we explicitly split both emails and chat/mobile because widget provides better options for streamlining feedback.