Option to disable ticket reopening in Help Desk

Hello!

I would like to suggest adding the ability to manage the ticket reopening behavior in Help Desk — specifically, to move this logic into settings and allow enabling or disabling the automatic transition of a ticket from a closed status back to an open status after a client reply. Currently, this works the same way for all accounts using Help Desk, but for companies that track support SLA, this is a serious issue.

A common situation is when a support agent closes a ticket, and the client replies a day later (or later) with a follow-up question or simply to say thank you. In such cases, the ticket is automatically moved from the closed stage back to the very beginning of the pipeline. As a result, agents have to repeatedly re-close tickets instead of replying to the client within the closed ticket or, if necessary, manually splitting the request into two separate tickets.
Each time a ticket is closed, a customer feedback form is sent to the client. If the ticket is closed multiple times, the form is sent multiple times as well.

Additionally, Help Desk may receive requests that are not related to support. In such cases, agents forward these requests to other teams by moving the ticket to a specially created final status. After that, automation copies the request and creates a new ticket outside of Help Desk, in a different workspace.

However, when the original ticket is reopened, agents have to close it again, and duplicate tickets are repeatedly created for other teams.

These are only the most common cases; in reality, there are many more.

For our account, this is a critical issue. It confuses support agents and other teams and takes a significant amount of time to understand what happened each time and to re-close a ticket that was previously closed.

Not all companies operate according to the same principle. For a significant number of them, it is important that a previously closed ticket remains in a closed stage.

We follow the same principle as in most CRM client workflows: there should be no backward movement of a request. Otherwise, it leads to confusion—especially when the same clients contact support frequently—and makes it impossible to collect accurate analytics.
Unfortunately, I was not able to find a single article in the HubSpot knowledge base that describes this behavior. Therefore, I will attach a link related to how Help Desk works.

Fully support the idea! Having the same issue in our company and that would help us a lot.

Hello,

Thank you for taking the time to share this detailed feedback. We fully understand the challenges you’ve described, especially for teams that rely on accurate SLA tracking, clean workflows, and reliable analytics.

The current behavior—where a closed ticket is automatically reopened and moved back to the start of the pipeline after a client reply—can indeed create confusion. As you pointed out, this leads to repeated closures, multiple feedback forms being sent, duplicated tickets for other teams, and unnecessary manual work for agents. In environments where tickets should remain closed unless explicitly reopened by an agent, this behavior becomes a serious operational issue.

We agree that not all companies follow the same support model, and flexibility here is essential. Having a setting to control whether a client reply can reopen a closed ticket would allow teams to align Help Desk behavior with their internal processes and CRM logic. For many organizations, preventing backward movement of tickets is critical to maintaining clarity, efficiency, and accurate reporting.

Your suggestion to move this logic into Help Desk settings—so it can be enabled or disabled per account—makes a lot of sense and would significantly improve usability for teams with different workflows.

Thank you as well for pointing out the lack of clear documentation around this behavior. Additional transparency in the knowledge base would be very helpful for users trying to understand or plan around this functionality.

For reference, here is a related resource that explains a different but well-documented workflow example, which highlights how clear behavior definitions can improve understanding:

We appreciate you raising this issue and hope it can be considered for future improvements.

Best regards,
Nelson

Hi Nelson,

Your message doesn’t include a link to the resource you mentioned. Maybe it was lost during the HubSpot Community platform migration?

In any case, could you help me find it?

Agree - this needs to be a setting in the Helpdesk so the re-opening of tickets can be entirely disabled.