Excluding specific tickets, users, or groups from customer satisfaction surveys Follow

Comments

9 comments

  • Avatar
    Bradley W

    We set up the 'no_csat' tag automation for excluding specific tickets and while it functionally works, it has opened the floodgates for abuse by agents. It wasn't long before the agents noticed the tag and started applying it to any ticket they thought would give them a bad survey. Of course, this is now an operational issue to tackle, but does anyone have any ideas for alternative solutions? I thought of adding a custom ticket field (checkbox) but I can't restrict that to managers only. 

  • Avatar
    Nicole - Community Manager

    Hey Bradley - 

    Not many people come across the comments on our Support Tech Notes. I suggest posting this query in the Q&A section of the Community with a link to the article for reference. 

  • Avatar
    Catherine Michalak

    Is there a way to exclude agents from surveys? We have different hr groups resolving tickets and sometimes agents create tickets as "end-users" for personal hr queries and get the survey link but obviously cannot provide a rating although would like to. I would prefer that they could rate a ticket but since that's not possible would be great if I could exclude them in the trigger but there's no possibility to use a condition like requester is not agent. Is there another work around for this?

  • Avatar
    Jessie - Community Manager

    Hi Catherine!

    In the satisfaction survey system automation, the option to add the requester role as a condition is definitely available:

    Are you not seeing it in your instance?

  • Avatar
    J Johnson

    Is there a way to condition the csat survey to only send to a user if 90 days has passed since the last survey? In other words, only send a csat survey at a certain cadence. I am concerned that we will open the floodgates as mentioned by others here and exhaust our customers.

  • Avatar
    Jessie - Community Manager

    Hey J!

    A couple of our Community Moderators, Joel and Graeme, collaborated on a Tip that shows you how to do this! You can find that Tip here: Restricting Satisfaction Surveys by Date

    That should get you started!

  • Avatar
    Demetrius Pais

    How do I stop CSAT surveys from going out to tickets that have been set to solved without an agent comment?

    Im trying to modify the CSAT Automation so it only goes out to tickets with an agent comment on it and not when the ticket is set to solved without a comment. It's strange for a customer to receive a CSAT survey where the ticket is not responded to. We may have decided to set a ticket to solved without replying.

    I’ve added `Ticket Privacy: Ticket has public comments` condition but it looks like the CSAT survey is going out to tickets without an agent comment too. Anybody attempted something like this earlier? Is there a better way to achieve the goal? Thanks!

    https://snag.gy/xaUSu8.jpg

    --

    Comment from Community Team: link above has been checked and goes to a screencap. It is safe to click. 

  • Avatar
    Catherine Michalak

    Hi Jessie,

    Thanks for your answer. 

    The problem I have is that our survey link is in the resolution notification trigger and for some reason there is no condition like "role/requester is not agent". Do you know if there's a different way I can achieve this?

    Thanks

    Catherine

  • Avatar
    Diogo Maciel

    Hi Demitrias,

     

    What I can suggest is to add a tag to these tickets being closed without an agent comment. This can be done manually or via a trigger (maybe the same trigger that are solving these tickets?). Then you can edit the survey automation to skip tickets with that tag (tags: contains none of the following) and this should make the automation ignore these tickets.

Please sign in to leave a comment.

Powered by Zendesk