Sample Support Tickets CSV File — Free Download
A helpdesk export with created and resolved timestamps, priority, category, status and a CSAT score — enough to compute resolution time, SLA compliance and an open backlog.
Download the sample file
CSV · 280 rows · 23.2 KB · synthetic data, free for any use
Download CSV samplePreview
| ticket_id | created_at | customer_id | priority | category | status | resolved_at | csat |
|---|---|---|---|---|---|---|---|
| TCK-00001 | 2026-01-01T00:38:00Z | CUST-0189 | High | Billing | Resolved | 2026-01-03T07:01:00Z | 3 |
| TCK-00002 | 2026-01-01T00:51:00Z | CUST-0036 | High | Integration | Resolved | 2026-01-01T17:25:00Z | 1 |
| TCK-00003 | 2026-01-01T01:40:00Z | CUST-0179 | Medium | How-To | In Progress | · | · |
| TCK-00004 | 2026-01-01T02:45:00Z | CUST-0194 | Medium | Integration | In Progress | · | · |
| TCK-00005 | 2026-01-01T03:31:00Z | CUST-0015 | Low | Bug | Resolved | 2026-01-03T07:26:00Z | 4 |
| TCK-00006 | 2026-01-01T03:40:00Z | CUST-0067 | Medium | Account | Resolved | 2026-01-01T17:32:00Z | 1 |
Showing the first 6 of 280 rows.
Columns
| Column | Type | Description |
|---|---|---|
ticket_id | string | Primary key, TCK-00001… |
created_at | datetime (ISO 8601) | When the ticket opened |
customer_id | string | Foreign key to the customers sample |
priority | string | Low, Medium, High or Urgent |
category | string | Billing, Bug, How-To, Feature Request, Account, Integration |
status | string | Resolved, Open, Pending or In Progress |
resolved_at | datetime or blank | Blank while the ticket is still open |
csat | integer or blank | Satisfaction score 1–5, blank if unresolved |
What makes this file useful
- Roughly 22% of tickets are still open, so resolved_at and csat are intentionally blank on those rows — a realistic missing-data pattern.
- created_at and resolved_at are full ISO 8601 timestamps, so datetime parsing and duration math are part of the exercise.
- customer_id references the sample customers file, so you can enrich tickets with segment or country.
Use cases
- Compute resolution time as resolved_at − created_at
- Measure SLA compliance by priority
- Filter to the open backlog (blank resolved_at)
- Correlate CSAT with priority or category
Open it in a tool
Load this sample — or your own file — into a real tool. Everything runs client-side.
Related guides
More sample datasets
Frequently asked questions
Is this a Zendesk / Freshdesk export?
No, but it mirrors the columns those tools export, so it is a good stand-in for testing a helpdesk analytics workflow.
Why are some fields blank?
Open tickets have no resolved_at or csat yet. That is deliberate, so you can practise handling missing values.
How do I calculate average resolution time?
Parse both timestamps, subtract, and average across rows where status = Resolved.
Turn this into a saved workflow
Create a free account to save the steps from this guide as a reusable workflow and re-run it on any file, from any device.
Follow HowToCSV on Google
Add us as a preferred source on Google Search so our latest CSV guides and tutorials surface more often in your Top stories.