AppsIT Desk

Incidents, problems and changes · Autessa IT Desk

SLA management

Autessa IT Desk includes SLA management: SLA definitions decide which tickets get a response or resolution target, when the clock starts, pauses and stops, and whether it counts 24x7 or business hours in a time zone with holidays. Every matching ticket gets a running task SLA that warns at 75% and records a breach, with timers shown at the top of the record.

A core ITSM / ITAM capability, done properly
Start free
SLA definitionsTask SLAsSAMPLE
NameApplies toTargetSchedule
P1 response (1h)Incident60 min24x7
P1 resolution (4h)Incident4 h24x7
P3 resolution (3d)Incident3 dBusiness hours
Requested item fulfillment (3d)Requested item3 dBusiness hours
Starts
When created
Pauses
State is On hold
Stops
State is Closed or Canceled
Warn at
75%
Running clocks
INC0001042 · P2 resolution62% · 3h 02m left
INC0001037 · P1 resolutionBreached 14m ago
RITM0001007 · fulfillmentPaused · On hold

The problem

Promises nobody can see until they are broken

An SLA only helps if the clock is visible while there is still time. Spreadsheet SLAs are measured after the fact. IT Desk runs the clocks on every ticket, pauses them when you are waiting on the caller, and tells the owner before the target is missed.

What you get

  • SLA definitions apply to any record type, such as incidents or requested items, with a condition set that picks the tickets (for example, priority is 1).
  • Start, pause and stop conditions are built with the same condition builder as lists: response stops once work starts, resolution pauses On Hold or Resolved and stops on Closed or Canceled.
  • Schedules count 24x7 or business hours, with working days, hours or split windows, holidays and a time zone.
  • Each task SLA tracks elapsed time, business time, paused time, percent used and the breach time if it keeps running.
  • A warning is recorded once at the warn percent (75% by default) and a breach is recorded once, and the owner can be emailed for each.
  • The clocks advance every 15 minutes and keep each ticket's SLA due date and made-SLA result current.
  • Starter SLAs: P1 1 hour response and 4 hours resolution, P2 4 hours and 1 day, P3 1 day and 3 days, P4 2 days and 5 days, plus requested item fulfillment in 3 business days.

How it works

How does sla management work in Autessa IT Desk?

  1. Define the target

    In Settings, SLA definitions, set the record type, response or resolution target, duration and schedule.

  2. Choose the tickets

    Use conditions to say which tickets get it, such as P1 incidents.

  3. Set the clock rules

    Add start, pause and stop conditions, or leave start empty to start at once.

  4. Watch the timers

    Every matching ticket shows its timers at the top of the form, and the Task SLAs list shows every clock, with a Breached (running) view.

  5. Act on warnings

    At 75% the owner gets a warning, and a breach is latched and reported. Dashboards show SLAs at risk and breaches by month.

Every option

SLA definition settings

OptionWhat it does
Applies toThe record type: incident, requested item, problem, change and other task types.
TargetResponse or resolution.
ConditionsWhich tickets get this SLA; empty means every ticket of that type.
Start conditionWhen the clock starts; empty means at once.
Pause conditionWhen the clock pauses, such as state is On Hold.
Stop conditionWhen the clock stops for good, such as state is Closed or Canceled.
DurationThe target in minutes, counted on the schedule.
Schedule24x7, or business hours: working days and start and end times, or several windows a day, plus holidays.
Time zoneAny named time zone or a fixed offset.
Warn percentWhen to warn; 75% by default.
Task SLA stagesIn progress, paused and stopped, with percent used, breach time and whether it breached.

Permissions

Who can do what?

RoleCan
IT administratorCreate and edit SLA definitions, schedules and warn thresholds.
IT agentSee SLA timers on their tickets and the Task SLAs lists, and get warning and breach emails.
EmployeeNothing to manage; their requests are simply handled on time.

AI assist

How the IT Desk Assistant helps

Ask the IT Desk Assistant which of your tickets are closest to breaching, or to filter the list to SLAs over 75%.

The assistant acts as you, with your role. It fills forms but never saves them, and anything risky waits for you to press Confirm.

About the IT Desk Assistant →

Connected

How it connects to the rest of IT Desk

FAQ

Questions about sla management

Can SLAs count only business hours?

Yes. A business-hours schedule counts only working days and hours in a time zone, skips holidays, and can use several windows a day, such as a lunch break.

Does the SLA pause when we wait on the caller?

Yes, if the pause condition says so. The starter resolution SLAs pause while an incident is On Hold or Resolved. While you wait, an Autessa agent can call or email the requester for the missing details, on your team’s instructions.

How often do SLA timers update?

Every 15 minutes in the background, and immediately whenever the ticket is saved.

What SLAs come with Autessa IT Desk?

Starter SLAs for P1 to P4 incidents (response and resolution) and a 3-day requested item fulfillment SLA. You can edit or remove them.

Try sla management in Autessa IT Desk

Autessa IT Desk includes SLA management: SLA definitions with start, pause and stop conditions and business-hours schedules attach timers to tickets, warn at 75% and record breaches.

Start free

Setup wizard · starter catalog, SLAs and dashboards included · remove sample data any time

100% customizable, code and all

Make Autessa IT Desk fully your own.

Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.

Start free and make it yours