Recent searches


No recent searches

Need a placeholder for satisfaction reason

Not Planned


Posted Aug 17, 2016

Hello, I would like to request that you add a placeholder for the customer satisfaction bad rating reason. We use a trigger to notify all team leads when a bad rating is received. This notification includes information about the rating and ticket, and I would like to add the reason to this list:

Requester: {{ticket.requester.name}}
Assignee: {{ticket.assignee.name}}
Group: {{ticket.group.name}}
Ticket ID: {{ticket.id}}
Link: {{ticket.link}}

Satisfaction comment: "{{satisfaction.current_comment}}"

Thanks!


42

32

32 comments

Official

image avatar

Scott Allison

Zendesk Product Manager

Thank you all for your feedback and upvotes. We don't currently have anything planned to address this in the roadmap but we continually reevaluate based on priorities and resources. The next time we’ll look at this again would be the second half of this year.

-1


+1

We need the reason placeholder for the exact same use case (a bad rating triggered email).

1


We also need the reason placeholder for the exact same use case.

Thanks

Bye

0


We have the same use case.  It seems like just an oversight that -- when the functionality was added -- a placeholder wasn't also added to allow the inclusion of reason in a triggered Notification email.

0


+1 for this

0


+1 from me

0


+1 here as well, please!

1


image avatar

Nicole Saunders

Zendesk Community Manager

Hi all, 

to register your "+1" please use the voting buttons on the original post, and in the comments share details about your use case, or the scope and impact it would have on your workflows/business. 

Thanks for your participation! 

1


Yes, please!

1


Yes please! We need to inform our Agents about which reason the user chosed, not only the coment.

1


Please consider adding this placeholder. We need it for the same reasons mentioned by everyone else. Thanks! 

1


+1 on this feature request.

This placeholder is absolutely required to notify team leaders here as well.

This is crucial for us to know why a ticket has been bad rated. Please consider adding this asap, thanks!

1


+1 - We have the exact same use case as the original post.

1


+1
We need it for the same reason outlined in the original post. Seems like an oversight, so here's hoping. Thanks!

1


image avatar

Stephen Belleau

Zendesk LuminaryCommunity Moderator

Interestingly, the Satisfaction Reason is available to use in triggers. So you could create a matching ticket dropdown field, and a series of triggers that populates your ticket field for each Satisfaction Reason. Then, use that ticket field placeholder in your notifications.

@...

1


Same use case as original post.

1


Me too.

1


same use case here

1


This feedback is from 2016... Do you think Zendesk will ever add it?

1


Same use case. 

2


in May 2021, still no news from the team? I don't get the point to propose the reasons if we can't display by the triggers?

Do you take in consideration the needs of your customers?

 

thank you

4


+1

1


+1

0


+1

0


+1 again

0


+1

0


+1

0


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.

0


Same use case for me too

0


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

0


Please sign in to leave a comment.

Didn't find what you're looking for?

New post