Check ticket response times with AI
Compare recorded first-response and resolution times with the limits for each ticket priority. Identify the missed threshold and keep incomplete records visible.
Check ticket response times with AI from a service desk export when the team needs to distinguish a late first reply from a late resolution. The support-sla-breach-detector skill calculates elapsed minutes between recorded timestamps and compares each interval with its own priority threshold. It produces per-ticket results and a summary by priority.
An urgent request might have received an immediate reply and still taken too long to resolve. An open request has no final resolution interval at all. Treat missing timestamps as incomplete evidence, even when the report does not flag a breach for that interval. The script uses elapsed time, so working-hours calendars need separate handling.
What it does
- Measure the recorded time to a first response.
- Check resolution against its own threshold.
- Distinguish first-response, resolution and combined breaches.
- Summarise completed cases by priority.
- Trace a finding to the source ticket identifier.
Install and use
- Install the skill and provide Python 3, an authorised CSV with ISO timestamps, and minute limits for each priority. Ticket text and personal contact details are unnecessary.
- Ask, “Review this week’s closed tickets against our response and resolution limits. Flag missing times separately in the interpretation.”
- Check the timestamp zones, priority mapping and incomplete records before presenting compliance figures.
FAQ
Source
Made by sisodiabhumca. Original skill: support-sla-breach-detector, published on GitHub under the MIT licence.
View on GitHub