Freshdesk Archived Tickets
A ticket you closed two years ago isn't gone. Freshdesk archived tickets are read-only, mostly invisible, and quietly missing from some of your reports.
What Freshdesk archived tickets actually are
Freshdesk moves old, long-closed tickets into an archived state. The point is performance. A helpdesk carrying eight years of closed conversations gets slower to search, slower to filter and slower to report on, and archiving keeps the working set to the tickets people actually work.
An archived ticket still exists. The conversation, the attachments, the requester, the properties, all still there. What changes is that it becomes read-only and it drops out of your normal views.
Nothing is deleted. Worth saying clearly, because "archived" panics people the first time they meet it. It is a filing cabinet, not a shredder.
When it kicks in
Archiving is time based and applies to tickets that have been closed or resolved and left alone for a long period. Think in terms of years rather than months.
The exact threshold, whether it's configurable on your plan, and whether it runs automatically or on request have all varied, so check the current Freshworks docs for what applies to your account. Do not design a data retention policy around a number you read in a community thread.
What is consistent is the precondition: the ticket has to be finished. An open ticket, however old, doesn't get archived. Neither does one still receiving replies. If a customer responds to a closed ticket, it reopens and it is back in the working set.
Finding an archived ticket
They aren't in your default views, which is the whole point, so you have to go looking.
The reliable routes, in order of how often they work:
Search behaviour is the thing to be careful about. Do not assume a global search covers archived tickets, and do not conclude a ticket never existed because a search came up empty. Check by contact before you tell a customer you have no record of them.
Unarchiving, and whether you should
Restoring an archived ticket brings it back into the active set so it can be edited, replied to and reported on normally. Whether that is a self-service action or something you raise with Freshworks support depends on your plan, so check the current Freshworks docs.
The better question is usually whether you need to. Three legitimate reasons to restore one:
And the illegitimate one: restoring a batch of tickets so a dashboard looks right. If archiving is distorting your reporting, fix the report or export the data. Do not undo the performance feature that's keeping your helpdesk quick.
What it does to reporting and the API
Here is where archiving stops being an abstract housekeeping detail and starts affecting numbers you present to people.
Reporting. Archived tickets may be excluded from some analytics, particularly anything built on the live ticket set. A multi-year trend chart that suddenly drops off a cliff at the same point every time is the classic symptom. It's not that you handled fewer tickets in 2021. It is that those tickets left the dataset. Confirm which reports include archived data before you present a long-range trend, and note it on the chart.
The API. Archived tickets behave differently on the API. List and filter endpoints may not return them by default, and write operations against them won't work, because read-only means read-only. A bulk update that includes archived ids will report failures for exactly those tickets, which is the correct behaviour and a confusing one if you were not expecting it.
The practical rule for anyone building an integration: never assume a ticket id you can read is a ticket id you can write. Handle the failure per ticket and log it.
And if you are exporting for a warehouse or a migration, work out early whether your export path covers archived tickets. Finding out afterwards that three years of history never came across is a genuinely miserable discovery.
Frequently asked questions
Can you restore an archived ticket?
Yes. Freshdesk restore archived ticket by unarchiving it, which makes it editable again and puts it back in reporting. Whether you should depends on why it was archived in the first place.
Are archived Freshdesk tickets deleted?
No. Archiving moves old closed tickets out of the active working set to keep the helpdesk fast. The conversation, attachments and properties are all retained, but the ticket becomes read-only.
When does Freshdesk archive a ticket?
After a long period with the ticket closed or resolved and untouched, measured in years rather than months. The exact threshold and whether it is configurable vary, so check the current Freshworks docs.
How do I find an archived ticket?
Go to the ticket id directly, use the archived filter in ticket search, or open the requester contact record and look at their ticket history, which is usually the quickest route.
Can I unarchive a Freshdesk ticket?
Restoring a ticket to the active set is possible, though whether you can do it yourself or need to ask Freshworks support depends on your plan. Check the current Freshworks docs.
Do archived tickets show up in reports and the API?
Often not by default. Some analytics exclude them, and API list endpoints may omit them while write operations against them fail. Confirm coverage before presenting a multi-year trend.
Fewer tickets to archive in the first place
A fifth of a typical queue is duplicates. Ticket Merger merges them as they arrive, so the history you archive is one clean thread per problem.
Start free trial14-day free trial. No credit card required.