How long should a company keep customer support tickets?

Is there a standard retention period for support tickets?#

There is no standard retention period for customer support tickets that fits every company. A ticket can be a warranty record, a contract notice, evidence in a billing dispute, a security report or a simple how-to question, and each of those carries different obligations.

That is why one blanket number, such as deleting everything after a fixed period, usually fails in both directions. It keeps low-value tickets full of personal data longer than needed, and it deletes tickets that a warranty claim or lawsuit later requires. Legal and operations should set periods by ticket type, with counsel confirming which laws and contracts apply.

The factors that set ticket retention#

Six factors set ticket retention for most companies, and they rarely point to the same answer. Laying them side by side shows which ticket types need to stay, which can go, and which can stay in a reduced form.

Set retention by ticket type, not one number#

Retention by ticket type means classifying tickets with forms, tags or custom fields, then letting each type carry its own period and deletion method. Most help desks support this, and it turns a policy document into something the system can enforce.

Privacy rules generally expect companies to keep personal information no longer than needed for the purposes they disclosed. Laws such as GDPR and CCPA may apply depending on where your customers are, and counsel weighs them alongside contract and warranty duties rather than picking a single number. Tickets that mix types should follow the longest applicable rule: a billing complaint that turns into a warranty claim is a warranty record.

What your help desk deletes on its own#

Help desk settings can delete tickets without anyone deciding to, so a retention policy is only as good as the configuration behind it. Zendesk is a useful reference because its rules are well documented, but every support tool, including chat, phone and email systems, has its own.

Start by recording the current settings for every support tool, and who can change them, before adopting a new policy. Lost history often traces back to a cost or privacy cleanup that nobody wrote down.

• 1Archiving: Zendesk automatically archives tickets 120 days after they reach Closed status. Archived tickets stay searchable and reachable by API, but drop out of views and no longer fire rules.
• 2Deletion schedules: Zendesk admins can create schedules that delete archived tickets after a set period. Deleted tickets cannot be restored, and schedules keep running against every matching ticket.
• 3Cancellation: under Zendesk's Service Data Deletion Policy, an automated process permanently deletes service data starting 90 days after an account is canceled or terminated.
• 4Other tools differ: Intercom says cancelling a subscription does not remove data, although the customer cannot see it until the subscription restarts.

How to minimize ticket data without losing the record#

Minimization does not have to mean deleting the whole ticket. The parts that create risk are usually personal and sensitive details, while the parts that carry value are the problem, the steps taken and the outcome. Separating the two lets a company shrink its exposure and keep its history.

Write the redaction steps into the policy and document each pass, so the company can show what was removed and when.

• 1Block or mask payment card data at intake. PCI DSS says sensitive authentication data, such as card verification codes, must not be retained after authorization, even if encrypted.
• 2Remove or redact risky attachments such as ID scans, screenshots showing credentials and exported customer files.
• 3Replace names, emails and phone numbers with consistent placeholders once the contact details are no longer needed.
• 4Keep internal notes, tags, timestamps and links to engineering issues, which explain how the problem was solved.

Illustrative: a SaaS company replaces its blanket rule#

Illustrative: a fictional B2B software company that sells inventory tools to wholesalers had one rule: delete every ticket after a fixed period. Its Zendesk instance linked many tickets to Jira issues, and its customer agreements included warranty terms and deletion-on-termination clauses.

General counsel and the COO replaced the rule with ticket forms by type. How-to tickets now keep the conversation but lose contact details after a set period, warranty and billing tickets follow counsel's periods, and a departing customer's tickets are handled under that customer's deletion clause. The support lead paused the existing deletion schedule until the new forms were live.

The company now holds less personal data overall and better history where it matters. Bug-related tickets still connect to the Jira issue and release that fixed them, which the product team uses to spot recurring defects.

Writing the policy down and keeping it current#

A ticket retention policy should name the periods, the owner of each setting and the process for legal holds, then be checked whenever the company changes plans, adds a channel or migrates help desks. Migrations are where tickets most often disappear, because old tools are cancelled before anyone confirms what moved.

Old tickets with their resolutions are also one of the record types AI developers look for, since they show real problems worked through to an outcome. That is a reason to keep well-redacted history, not to override privacy or contract duties. When a company considers licensing tickets, SourceX runs the SourceX five-step transaction: the Rights step reviews contracts and notices, Preparation removes personal and confidential details, and the company approves the final package before Delivery. Each package is documented in a SourceX Evidence Packet.