Recipe ≈ 75s to first insight

SLA-breach analysis on support tickets

Identify tickets whose first-response time exceeded the priority-specific SLA.

Run this recipe in the demo Upload your own file

No signup required. We load the dataset in your browser; your own files never leave it.

Dataset

Support tickets — last 30 days

200 rows · JSONL

What you'll see

An SLA-breach rate broken down by priority and channel, with the worst combination called out.

Pre-filled question

Using support-tickets, compute the share of tickets whose first_response_minutes exceeded the priority-specific SLA (urgent: 30, high: 120, medium: 480, low: 1440) and break the rate down by channel.

Topics

slasupportoperations