Configuration

SLA Tracking

Automatically monitor tickets against response and resolution time targets by priority. When a ticket exceeds its target, Servelo emails a breach alert to admins and the assigned technician.

This page covers the SLA tracking feature inside the Servelo app. For Servelo's uptime and support commitments to you as a customer, see the Servelo Service Level Agreement.

Enabling SLA Tracking

Go to Settings > SLAs and toggle Enable SLA tracking. Once enabled, Servelo checks all open tickets every hour and sends breach alert emails when a ticket exceeds its response or resolution target.

Disabling SLA tracking stops all future alerts. It does not delete historical breach records.

Response and Resolution Targets

Targets are configured per ticket priority. Each priority has two thresholds:

Priority Default first response Default resolution
Urgent 2 hours 8 hours
High 4 hours 24 hours
Normal 8 hours 72 hours
Low 48 hours 168 hours (7 days)

All targets are editable. Enter any whole number of hours in Settings > SLAs and click Save SLA Settings.

Business Hours

By default, the SLA clock only runs during your configured business hours. Time outside those hours does not count toward response or resolution targets.

Configure your schedule in Settings > SLAs under Business Hours:

Turn off Business hours only to run a 24/7 clock instead.

Breach Alerts

When a ticket exceeds a target, Servelo sends a breach alert email with the ticket number, priority, SLA target, and elapsed time. Alerts include a direct link to the ticket.

Configure who receives alerts under Breach Alerts in Settings > SLAs:

Each breach type (response, resolution) triggers at most one alert per ticket. Servelo will not re-send the same breach alert if the ticket remains open.

How It Works

The SLA engine runs as a background job every hour. For each open ticket it:

  1. Calculates elapsed business hours since the ticket was created.
  2. Compares elapsed time against the response and resolution targets for that ticket's priority.
  3. If a threshold is exceeded and no alert has been sent yet for that breach type, sends the alert email and records it.

Tickets in resolved, closed, or cancelled status are excluded from checks.

Tickets with no priority set are evaluated as Normal priority.