Ticketing reports and metrics are all over the place, and your service desk productivity goes haywire. Countless ‘Thank you’ messages and responses get accumulated, and it all becomes one giant iceberg that you’re looking to steer clear off and perhaps not sink your so-called “metrics boat”.
This is why we’ve come up with a simple, but robust solution - the Thank You Detector.
Powered by Freddy, our savvy AI buddy, the Thank You Detector can be set up using Freshservice’s Workflow Automation. Freddy can intuitively detect when your end-users respond with a ‘Thank You’ and will keep resolved or closed tickets at bay or from re-opening.
I had to disable "Freddy's" thank you detector for closing tickets that should not be closed.
Thanks for taking the time to give feedback. Could you give us examples of customer responses that should have prompted Freddy to reopen the tickets instead? This will help us understand what went wrong and what we could do to improve.
I can. Could you email me, that way I am not posting these responses in the public forum.
I think the information on how to set this up needs to be more detailed. I setup following the instructions from Fresh Service and the automator ended up Reopening .....already OPEN tickets. Because the ticket was NOT Closed or Resolved...AND NOT a thank you....it defaulted to setting the ticket as OPEN...even though it already was.
I tweaked some settings in my workflow automator, for now Freddy seems to be doing allright. It's working pretty good.
Use the option "Freddy Suggestion is not thank you message.
Than you give other conditions to reopen a ticket if not thank you message.
It is picking up pretty good, i would say test it :).
Glad to know that the Thank You Detector worked out well for you. Thank you for sharing the solution article here and writing to us.