Often, a requester will respond with a useless "Thanks" or something else which requires absolutely no ticket action. This will trigger the "Requester Responded" flag on the ticket which will then stick around and cause me to repeatedly open the ticket and check if action is needed when there is none.
A way to clear this flag would be very nice.
My vote is for an "Acknowledge Response" button inside the ticket on the requester's response. This would force you to open the ticket once and look at the response, but still allow you to clear the "Requester Responded" flag if no action was needed.
This is a fantastic idea. We struggle with the same issue. We are always responding back to "Thanks" and "Thank you" etc, in order to clear the "Requester Responded" flag. Thanks!
This would also be useful for the "New" flag. We have some tickets which are auto-submitted via email from other systems. These tickets require no response but some time to work on, so they sit in our queue as "New" for quite a while.
Freshservice, I can understand why you might always want the agent to have had the last say. It's probably some wonderful best practice for how service desks should operate. But it doesn't always work out that way in reality, as the other posters have explained.
Please provide a way to reset the REQUESTER RESPONDED flag when there is nothing more to say to the requester for the moment.
If you can't find a way to do it, at least feel free to use this case as great source material for next year's comic calendar...
Agent: We'll get back to you when we have an update.
Requester: Thanks! (REQUESTER RESPONDED)
Agent: Like I said, we'll get back to you. Please don't reply to this email.
Requester: Okay (REQUESTER RESPONDED)
Requester: You okay? (REQUESTER RESPONDED)
I'll throw my upvote in for this as well. Lots of our customer service reps do this to us all the time and kind of causes a disorganization of our service desk.
A workaround we've used is to simply mark the ticket resolved when you receive the "thank you", and filter your view such that resolved tickets are not in it.
Throwing support behind this one too. It has been annoying our service desk since implementation!
@Justin Alvey: That doesn't work too well when you are in the middle of the ticket. For example:
Agent: Let me look into this.
FreshService: <Requester Responded>