Closed vs Resolved in Freshdesk
Freshdesk closed vs resolved looks like two words for the same thing. The gap between them is where your reopen rate and half your reporting live.
Freshdesk closed vs resolved, plainly
Resolved means the agent believes the issue is fixed and has told the customer so. The customer has not confirmed anything. It's a claim.
Closed means the ticket is finished. Nobody expects further movement on it.
That's the whole distinction, and it sounds like semantics until you notice what sits in the gap: a period during which the customer can say "actually, no" and land back in the same conversation rather than starting a new one.
Both statuses stop the SLA clock, so from a target perspective they behave the same. The difference is entirely about what happens next, and about what your numbers mean. There's broader status design context in the ticket status guide; this page is about these two specifically.
Reopen behaviour, which is the real difference
Here's the mechanic that makes the two statuses worth having.
When a customer replies to a resolved ticket, it normally reopens. The conversation continues in the same record, the agent sees the full history, and nothing is lost. That is the behaviour you want, and it's the reason not to close things immediately.
When a customer replies to a closed ticket, what happens depends on your configuration. Some setups reopen it. Others create a new ticket that references the old one, or a new ticket that references nothing at all.
That second behaviour is how one conversation quietly becomes two records, each with half the history, potentially handled by two different agents.
Go and check which behaviour your account has. Genuinely go and look, in the admin ticket settings, rather than trusting anyone memory including your own. Then send yourself a test: resolve a ticket, close it, reply from an outside address, and see what appears in the queue.
If your configuration creates new tickets on reply to closed, you have a steady background source of split conversations, and the fix is either a settings change or merging the pairs back together as they appear.
Automation timing: the auto-close window
Almost nobody should be closing tickets manually. The standard pattern is a time-triggered automation: resolved for N days with no customer reply becomes closed.
Choosing N is the interesting part, and it is a judgement about your customers rather than a best practice.
One refinement worth adding. Send a message when a ticket is resolved that says explicitly what happens next: "if this isn't sorted, just reply and we will pick it straight back up". That sentence converts silent dissatisfaction into a reopen you can actually see.
What you should not do is auto-close from Open or Pending. A ticket nobody resolved is not finished, it's abandoned, and closing it hides the problem instead of surfacing it. If you've such a rule, you have a metric that looks good and a queue that lies. Patterns for building these safely are in the automations guide.
What to report on
This is where the distinction pays for itself, and where mixing the two ruins numbers.
Resolution time should measure to Resolved, not to Closed. Otherwise every ticket carries whatever your auto-close window happens to be. I have watched a team celebrate a two day improvement that turned out to be a change from a seven day window to a five day one.
Reopen rate needs Resolved to exist. Count tickets resolved in a period, then count how many of those reopened. It is one of the best quality signals available, because it measures whether your answers actually worked rather than whether they arrived quickly. A rate near zero usually means agents are resolving prematurely or customers have given up. Above roughly one in five and your first replies are not landing.
Satisfaction surveys generally belong on resolution, while the interaction is fresh, rather than on closure days later.
Backlog counts should exclude both. If resolved tickets appear in your open backlog view, that number isn't measuring work outstanding.
One caveat when you export: check which timestamp your reports are actually using. Resolved-at and closed-at are different fields and it is easy to build a dashboard on the wrong one without noticing for a quarter.
Common mistakes
Using only one of them. Teams that never use Resolved lose their reopen signal entirely. Teams that never close end up with thousands of resolved tickets and no idea which are genuinely done.
Closing to hit a target. Bulk-closing an aged backlog makes the queue look healthy on Friday and produces a wave of new tickets from people whose issue was never fixed. The work doesn't go away, it just loses its history.
Assuming closed is permanent. Depending on configuration a closed ticket can reopen, so do not treat it as an archive state or as a deletion.
Frequently asked questions
What does auto close do to a resolved ticket?
Freshdesk auto close moves resolved tickets to closed after a set window. Before that window, a customer reply is a Freshdesk reopen ticket event; after it, they get a new one. Freshdesk close ticket manually and you skip the window entirely.
What is the difference between Resolved and Closed in Freshdesk?
Resolved means the agent believes the issue is fixed but the customer has not confirmed. Closed means the ticket is finished. The gap between them is the window in which a customer can reply and reopen the same conversation.
Does a resolved ticket reopen when the customer replies?
Normally yes, in the same record with the full history. Replies to closed tickets vary by configuration: some reopen, some create a new ticket. Check your account settings and test it.
How long should tickets stay resolved before closing?
Three days for fast consumer support, five to seven for most B2B. Longer than a fortnight generally means nobody chose a number. Tell the customer in the resolution message that a reply reopens the ticket.
Should resolution time measure to Resolved or Closed?
To Resolved. Measuring to Closed bakes your auto-close window into every ticket, so changing that setting appears to change your resolution time when nothing about the work has changed.
Can I skip Resolved and close tickets directly?
You can, and you will lose your reopen rate, which is one of the most useful quality metrics you have. You also remove the customer window to come back in the same thread.
When a reply becomes a second ticket
If replies to closed tickets create new records, one conversation splits in two. Ticket Merger detects those pairs in Freshdesk and merges them back into one.
Start free trial14-day free trial. No credit card required.