How long should a company keep support tickets?

What is the right retention period for support tickets?

Keep them as long as a contract, regulation, product need or dispute requires, and set that period in writing. There is no universal number. Helpdesk tools ship with their own defaults and cleanup features, so the real risk is not a policy but an unreviewed automation that quietly deletes resolved history.

For a company with 50+ full-time employees at peak (contractors excluded), years of resolved tickets are also one of the more useful records an AI developer can license. Deleting them to save a few seats of storage can end that option before anyone has weighed it.

What does the law require?

Mostly it requires nothing about tickets by name. Retention comes from the content: contracts with customers, industry rules for regulated data, tax and accounting records, and litigation holds. Privacy law adds a pull in the other direction, since personal information should not be kept longer than needed.

One cited example: California's consumer privacy statute requires the businesses it covers (it applies only above certain thresholds) to give notice at collection of the categories of personal information collected, the purposes, and the retention periods (California Civil Code, CCPA). If your client's tickets contain California residents' personal information, its retention schedule should already match what its notices say. This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

Which retention approach fits which ticket?

What are typical helpdesk defaults and traps?

Settings differ by vendor and plan, so check your client's current admin console rather than assume. These are the patterns that cause surprises:

• Automatic deletion rules. Some tools can archive or delete closed tickets after a period. A rule set years ago may still be running.
• Plan downgrades. Moving to a cheaper tier can shorten history or limit export.
• Agent offboarding. Removing an agent can detach authorship from tickets.
• Attachments and call recordings. These may live under separate storage limits.
• Migration between desks. Moving from one helpdesk to another often carries only the last year or open tickets.

As a CX consultant you already sit in the admin console during implementations. Add the retention settings to your discovery notes.

Why resolved tickets matter to AI buyers

Training and evaluating support agents needs records of how real problems were diagnosed and closed: the customer's message, the steps taken, escalations and the final outcome. Resolved tickets with context carry exactly that. Our guide on identifying tickets with useful resolution context shows what separates a strong ticket from a thin one, and the page on licensing customer support data for AI covers the rights angle.

Rule: the keep-before-purge check

Before any bulk delete or tier downgrade, ask four things.

1. How many years of resolved tickets exist, and does anyone depend on them?
2. Are they exportable, with comments, tags and outcomes intact?
3. Does the customer contract allow the company to use support correspondence this way?
4. Is there a decision-maker who could consider a licensing assessment first?

If the answers are yes, yes, probably and yes, pause the purge and flag it.

What to say to the support or operations lead

What does a partner reward look like here?

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. Management consultants and CX advisors should check client contracts and their own firm policies on referral fees before registering.

When not to raise it

• The tickets mainly belong to the client's customers, for example an outsourced support desk working under a client brand without consent.
• The ticket base is mostly consumer personal data with no licensing basis.
• The data has already been licensed for AI training.
• The company is under 50 full-time employees at peak.

Related reading: referral opportunities for management consultants, MSP revenue streams, exporting from unsupported systems and the Salesforce archiving guide. Compare the company with who qualifies.

Next step

Add retention settings to your next helpdesk discovery, then register as a partner and use the network opportunity finder to list clients with deep ticket history.