Ability to change state in a freshdesk ticket

Hi @mymuk 

Greetings from the freshworks community!

I understand that some of the responses like ‘thank you’ don’t need a reply from the agent. However, these flags are generated by the system based on the actions performed. Unfortunately, as of now, we do not have an option to remove the system-generated flags as these are hard coded from the backend and will also impact SLA and other factors. As a suggestion, you can add an empty public note to the ticket to remove the “customer responded” state.

The feature release is a part of the road map, but we do not have any tentative ETA yet. We’ll share the details once there is some considerable progress :)

Hey FreshDesk Team, do you have any update on this? Customers have been complaining about this for awhile, on several different forums threads. Please fix it. It’s very annoying. You need to add a way for us to manually clear the Customer Responded flag. Please listen to us.

Hello!

@Aishvarya as for the workaround you’ve mentioned - creating an empty public note to the ticket.. I guess a customer will receive an empty e-mail from support, correct? Then this workaround is not helping at all.

If state where a condition in automations, this wouldn’t be a problem.
Any chance on that happening?

Is there any update on the roadmap for this issue?

@Aishvarya 

Can you please provide any sort of update regarding the roadmap for this feature. There needs to be some way to clear “Customer Responded” from tickets that do not need an actual follow up. If a customer responds saying “Thank you, talk to you then”, are we expected to reply back to them saying “Thank you for thanking me. See you then”?

What if they reply back saying “Thanks”? We will then need to reply back to them saying “You’re welcome”? What if they then say “My pleasure”? I’m sure you see how this can keep going back and forth.

It is unnecessary clutter for the end-customer to have to continue to receive emails from the support desk, strictly because Freshdesk does not have a way (somehow) to clear this flag.

The workaround of “add an empty public note to the ticket” does not work, by the way. It is actually impossible to add an empty note to the ticket. The button is greyed out and will not let you post an empty public note. Further, this workaround would also result in an empty email to someone.

Please provide an update on this highly requested feature.

Thanks

To address the issue, you can set up an automation that ignores simple responses like "thanks," preventing them from triggering the "Customer Responded" state. Additionally, you could customize tools like the "Thank You Detector" to apply to open cases as well, or create a custom status like "waiting" for cases with minor responses. This way, you can keep track of them without marking them as "Customer Responded." Another option is to use tags or flags to manually identify these cases, making it easier to monitor them without needing to click into every case.

​@motaro this only work if there is a ‘thank you’ rather than a response that is not actually a response to the request (i.e. more information) - for example when they say “I’ll check and get back to you” - this triggers the status and we have to keep checking the last updated time field which is a pain when you are managing multiple tickets.  We just need a way to trigger the status change.  Flags/tags are not a solution as these just add additional elements to manage.  Is there an update on this, or are we not getting this feature request?

Enhance ticket management in Freshdesk by enabling the ability to change state within a ticket. This improves workflow efficiency, ensures accurate status updates, and streamlines customer support processes. Get more info on configuring ticket state changes for better tracking and resolution.

In Freshdesk, you can change ticket states Open, In Progress, Resolved) to manage customer queries effectively.

Thanks

Being able to change the state of a ticket in Freshdesk quickly and reliably is a core part of agent productivity. One of the things that often slows teams down isn’t just the UI control itself, but the number of steps required to get there. If agents have to open the ticket, scroll to a dropdown, wait for a reload, then confirm — that adds up over a day of 100+ tickets.

What helps a lot in practice is customizing the ticket form and workflows so that state changes are as frictionless as possible. For example, placing the state selector near the top of the ticket view or adding hotkeys/quick buttons reduces clicks and cognitive load. Automations that transition state based on simple actions (like adding a tag or a note) can save even more time.

Another practical improvement is auditing your current states to make sure they align with how teams actually work. Too many unnecessary states or poorly named ones can cause hesitation or mistakes. Regularly reviewing and simplifying your state taxonomy with input from the agents themselves often yields bigger productivity gains than UI tweaks alone.

In a broader productivity context, it’s interesting how other digital tools approach smooth interactions. For instance, mobile apps and games that emphasize quick, intuitive state changes — like progressing through levels or advancing stages in Super Bear Adventure — demonstrate how minimizing unnecessary steps improves overall experience. Thinking in those terms when designing ticket flows can help your support team work more efficiently and with fewer interruptions.