Need a placeholder for satisfaction reason

+1

+1

Following up on this. It looks like the product team had last updated in 2022. Not sure if this had made the roadmap for 2023?

Like many others, we are able to use the satisfaction reasons within triggers to notify our leadership teams--but not fully able to provide a quick, full snapshot of the CSAT. Having the ability to have a native placeholder {{satisfaction.reason}} would allow less swivel time for our leaders, quicker coaching for our support teams, and a faster resolution should a customer not be satisfied.

Same use case for me too

Vote from us. We use satisfaction placeholders for our Slack notifications and satisfaction reason is one required

Hey, ZD team, it's been more than two years since your last “official” announcement about this feature.
Can you share when it will be released (as part of your roadmap)? 

Same here! +1

+1

Actually, if you are on Legacy CSATS (not with the rating scale) you can use this: satisfaction.current_comment

+1

I find this here at the end of 2025, and this request is soon gonna celebrate it's 10 year anniversary.

I would very much like this feature 🙂

Hi! Are there any updates on this? It's quite unusual that we're unable to use the default CSAT survey results in our workflow. Please look into this matter.