The Freshdesk Thank You Detector
A customer replies with one word to say thanks, the ticket springs back open, and an agent closes it again. The Freshdesk thank you detector exists for exactly that.
The problem it exists to solve
By default, a reply from a customer on a resolved ticket reopens it. That behaviour is correct almost all of the time, because a reply usually means the fix did not land.
Almost. Then there is the other kind of reply. Thanks. Perfect, cheers. Got it, appreciate the help.
Those reopen the ticket too, and every one of them costs somebody a click. Worse, they poison two numbers you probably report on. Your reopen rate, which is supposed to tell you how often you failed to solve something first time, starts counting gratitude as failure. And your resolution time gets a second, later resolution stamp on tickets that were fine.
On a queue of a few hundred tickets a month the noise is annoying. On a queue of ten thousand it's a fake trend line that somebody will eventually build a quality initiative around.
What the Freshdesk thank you detector does
Freshdesk includes a thank you detector, sometimes described as thank you note detection, that inspects incoming customer replies on resolved or closed tickets and works out whether the message is purely an acknowledgement.
When it decides the reply is gratitude and nothing else, the ticket stays resolved or closed instead of reopening.
Two things it doesn't do, and they matter. It does not discard the message. The reply is still added to the conversation, so the thank-you is there in the thread and your record of the interaction stays complete. And it doesn't act on tickets that are still open, because there is nothing to prevent there.
It's a setting rather than a default in most accounts, and where it lives and whether your plan includes it are both things to confirm in your own admin area rather than take from an article. Look under the ticket or email behaviour settings.
Where it gets things wrong
This is a language classifier, so it fails in language-shaped ways.
None of this is a reason to leave it off. It's a reason to sample. Pull a week of tickets where the detector suppressed a reopen and read twenty of them. If it caught something it shouldn't have, you'll know within ten minutes.
What to pair it with
The detector solves one narrow thing. Two settings around it do most of the rest of the work.
A sensible auto-close window. Resolved tickets should close after a period of silence, commonly three to seven days. That window is what gives a customer room to come back in the same conversation rather than opening a fresh one. The ticket status guide goes into why the resolved and closed distinction is worth keeping.
A clear reply-to-closed rule. Check what your account does when somebody replies to a fully closed ticket. Some configurations reopen it, others spawn a new ticket linked to nothing. The second is how one conversation becomes two records, and it is worth knowing which you have.
And a small cultural one. If your resolution email ends with an invitation to reply if anything else comes up, you'll get more polite replies. That's a fair trade, but it does mean the detector is doing more work in your account than in someone else's.
Measuring whether it helped
Take your reopen rate for the month before you switched it on and the month after. If the detector is doing its job, that number falls and your genuine reopens, tickets where the customer described a problem again, stay flat.
If both fall, be suspicious. That's the shape of over-suppression, and it means real follow-ups are being swallowed into resolved tickets that nobody looks at again.
Then check the other direction. Count tickets created within 48 hours of a resolution, by the same contact, on the same topic. If that number went up, customers whose replies were suppressed are starting fresh conversations instead. Your reports can build both views without much effort.
Frequently asked questions
How do you stop tickets reopening in Freshdesk?
Turn on gratitude detection. A Freshdesk thank you note reopening a resolved ticket is the classic Freshdesk reopen ticket on reply problem, and Freshdesk gratitude detection is what stops tickets reopening for a one-word reply.
What does the Freshdesk thank you detector do?
It inspects customer replies on resolved or closed tickets and keeps the ticket resolved when the reply is nothing but an acknowledgement. The message is still added to the conversation, it just doesn't trigger a reopen.
Does it delete the thank-you message?
No. The reply lands in the ticket conversation as normal. The only behaviour it changes is whether the ticket status reverts.
Does it work in languages other than English?
Detection quality varies by language and Freshworks does not guarantee parity across the full portal language list. Sample your own tickets before relying on it for a non-English queue.
What happens if the customer says thanks and then asks something new?
That's the failure case. A mixed message may be classified as gratitude and the ticket may stay resolved. Auditing suppressed reopens periodically is the only reliable safeguard.
Is the thank you detector on by default?
Treat it as a setting to check rather than assume. Availability and location vary, so confirm it in your own admin settings.
The other cause of a phantom reopen
Sometimes the second message isn't a thank-you but a second ticket. Ticket Merger spots duplicates from the same requester and merges them into one thread automatically.
Start free trial14-day free trial. No credit card required.