An exercise on support-tickets

An exercise worth doing on support-tickets.

4,000 rows, 10 columns, one row per ticket. Four thousand support tickets with free-text subjects, priorities, queue routing, first-response and resolution times, and SLA breaches concentrated in exactly the places you would not guess.

Every dataset here is synthetic, which is a deliberate trade. It costs realism and buys three things: we can ship it CC0 with no licence trap, we can bake in the exact quirk a lesson needs, and nobody's real records end up in a tutorial.

Something to try: Find which subject keywords predict an SLA breach. The SQL playground has it loaded already, and the data explorer will profile every column in one pass if you would rather look before you query.

select *
from support_tickets
limit 20;

The file is generated from a fixed seed, so the CSV you download today is byte-identical to the one from last year. That matters more than it sounds: it means a lesson can say "row 412 is the interesting one" and still be right in eighteen months.

Download it, break it, keep it. CC0 — no attribution required, no account, no email.