Skip to content
Hypamoon

For teams that run on Freshdesk

Freshdesk customer responded: skip the thank-yous

When a customer replies to a resolved ticket, Freshdesk opens it again and marks it as customer responded. That is what you want for a real question. For a short thanks or an out-of-office message, someone still has to open the ticket and set it back.

How it goes today

  1. Open each ticket that shows customer responded to see what was said.
  2. Set the status back to resolved when the reply was only a thank-you.
  3. Write a short answer just to move the ticket off the list.
  4. Leave long-running tickets marked as customer responded for weeks.

How it can go

Let a thank-you stay a thank-you, so the ticket stays resolved.

Each reply on a ticket you had resolved is read as it comes in. When it is only a thank-you or an automatic out-of-office message, the ticket goes back to resolved with a private note that shows the reply and the reason. A reply with a question or new detail stays open for your team. Each Friday you get a short list of what was set back, so you can check it.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your Freshdesk key in the portal, never in the chat.

Your request

With Hypamoon, when a customer replies to a Freshdesk ticket we had resolved, read the reply. If it is only a thank-you or an automatic out-of-office message, set the ticket back to resolved and add a private note with the reply and the reason. Leave any reply with a question or new information open for us. Every Friday email me the list of tickets that were set back.

Each Freshdesk agent finds a personal API key under Profile settings, and it sees what that agent may see. For some requests an admin also sets up a rule in Freshdesk that passes ticket updates on. It stays yours.