Services and SLAs

On this page

When a ticket's workflow runs the calculation, it uses the following related records to calculate the ticket's due date, response date, and priority:

  • A service, the thing the ticket is about.
  • An SLA, which binds one service level to one service, either globally or for named receivers: organizations, groups, or people.
  • A service level of the service, which names the work calendar the clock runs on and holds two tables: the priority for each combination of impact and urgency, and the response time and resolution time for each priority.

A service is offered to one ticket class. A ticket's service field offers the active services offered to that ticket's class, and a Service Catalog item's service field offers the services offered to the Service Request class. The service field of an SLA, an announcement, a Knowledge Base article, or a library item is not limited to one ticket class.

Services and SLAs in the Web App

The service record

The General tab of a service has two columns:

  • First column: Details (ID, status, name, description, service manager, service provider, and availability hours), then the custom data and the modification information.
  • Second column: Categorization (workspace, type, tags, and category), then the support group and the ticket class the service is offered to, and then the service's levels.

NOTE: The availability hours of a service are recorded on the service only. The SLA clock does not read them; it reads the support hours calendar of the service level.

The service's levels are a grid, by default with the columns Service Level, Description, and Rank, and with New and Delete buttons. New, and opening a row, open the service level editor over the service. A level has no details pane and no command to open it in a new tab; only a middle-click on a row's link opens the level in a new tab.

The SLA tab lists the agreements built on the service, with their flag, name, service level, status, and whether the SLA is global.

The Receivers tab lists the receivers of every SLA of the service, with their ID, class, name, SLA, and status, grouped by class, without inactive ones. When the service has a global SLA, the tab shows "This service has a global SLA '<name>'. This service can be delivered to any service receiver through the global SLA."

Create or edit a service level

  1. On the service's General tab, click New in the levels grid, or open a level.
  2. In the service level panel, fill in the fields: the service level name, rank, description, and support hours. Empty support hours mean the default work calendar. The panel is captioned Service Level until you type a name.
  3. In Priority Calculation, choose a priority for each combination of impact (down the side) and urgency (across the top).
  4. In Ticket Response and Resolution Targets, which has one row per priority and the columns Priority, Response Time, and Resolution Time, click or double-click the row of a priority. In the Edit Ticket Response and Resolution Targets dialog, enter the response time and resolution time, and click OK. The priority cannot be changed in this dialog.
  5. Save the level.

Each of the two tables has a Show inactive items switch, which adds the inactive lookup values. Saving is unavailable until you change something, and while the service record is read-only. Canceling a changed panel asks "Do you want to close?".

The SLA record

The General tab of an SLA has two columns. The first column holds:

  • Details: ID, status, name, and service provider.
  • Categorization: workspace, type, tags, and category.
  • SLA Terms: start date, expiration date, the service level, and the level's support hours, calculated from the level.
  • The custom data and the modification information.

The second column holds:

  • SLA Scope: the Global check box, above the text "If no SLA is associated with a receiver of the specified service, the global SLA is used."
  • Service Information: the service, followed by the chosen service's type, category, status, service manager, support group, and availability hours, all read-only and refreshed when you choose another service. With no service chosen, these fields are empty.

The other tabs are Activity, Custom Data, Receivers, Related Objects, Notes, History, and Attachments.

Add or remove the receivers of an SLA

  1. Open the SLA's Receivers tab.
  2. Click Add receivers and choose Add Organization, Add Group, or Add Person.
  3. In the picker, select one record. The receiver is added when exactly one record is selected, and the tab's list and counter are refreshed.

To remove receivers:

  1. On Receivers, select the organizations, groups, or people to remove.
  2. Click Delete and confirm "Are you sure you want to delete the selected item(s)?"

This removes them from the SLA's receivers without deleting the organizations, groups, or people themselves.

The Receivers tab lists the receivers, by default with their ID, class, name, status, and type, grouped by class, without inactive ones. Opening a row opens the organization, group, or person itself.

The database enforces these rules. When Add receivers is refused, the refusal is shown in an alert.

  • A service can have only one global SLA: "Only one global SLA can exist for a service."
  • A global SLA has no individual receivers. The Global check box and the Receivers tab both stay available, but checking Global on an SLA that has receivers is refused when you save ("No individual receivers can be associated with a global SLA."), and adding a receiver to a global SLA is refused.
  • An organization, group, or person receives a service through only one non-global SLA, for example "An organization can receive a particular service only through one SLA."

An organization receiver covers the people whose own organization it is. The SLA of a parent organization does not reach the people of its sub-organizations.

Give an organization an SLA from its record

An organization's record has its own SLA tab.

  1. On the organization's SLA tab, click Add.
  2. In the picker, select one existing SLA. The organization becomes a receiver of it when exactly one SLA is selected. The receiver rules above apply.

Nothing on this tab creates an SLA. Delete asks "Are you sure you want to delete the selected item(s)?" and then removes the organization from the selected SLAs' receivers; the SLAs themselves stay.

How the SLA clock runs

Alloy Navigator calculates a due date, a response date, and a priority from a person, a service, and the ticket's values. The calculation runs when the ticket's workflow calls it, and nothing else runs it: with a workflow that does not call it, tickets get no calculated due date, response date, or priority. The due date and response date need a service, a submit date, and a priority; when one of them is missing, there is no date.

In a new 2026.1 database created with the Default Workflow (see Default Workflow Configuration), the workflow contains three macros that call the calculation: Calculate Due Date, Calculate Response Date, and Calculate Priority. Each passes the ticket's requester as the person, the ticket's service, and the ticket's own values, so the service level is resolved for the ticket's requester. An upgraded database need not contain these macros, and an administrator may have changed them.

The service level is resolved in this order:

  1. When a person is given: among the service's non-global SLAs, the ones that cover the person through their organization, one of their groups, or directly. Of these, the level with the lowest rank wins; a level with no rank is skipped.
  2. If that finds no level, or no person is given, and the service has exactly one service level, that level.
  3. Otherwise, the level of the service's global SLA.

If no level is found, there is no due date or response date.

The priority is read from the level's Priority Calculation table for the ticket's impact and urgency, on the level resolved in the same order. A ticket with no impact, no urgency, or neither of the two still gets a priority when the table has a matching entry.

The due date adds the level's resolution time for the priority to the submit date, and the response date adds its response time. A missing time counts as zero, which gives the submit date itself. Only working time counts, on the level's support hours calendar or, when the level names none, on the default work calendar. When the level names a calendar that does not exist, or names none and no work calendar is the default, the time is counted around the clock. A personal calendar is never used by the SLA clock, and the Calendar page, which plots the dates of records, has no effect on it. See Work Calendars for how a calendar's weekly hours, exceptions, and inheritance decide which time counts.

In the Default Workflow, the default work calendar is set to Default Work Calendar: working hours from 09:00 to 20:00 on five days of the week, the other two days non-working, and the U.S. federal holidays of its attached U.S. Holidays list non-working. The configuration also supplies a second work calendar, After Hours Work Calendar, which is not the default and also inherits U.S. Holidays. On a new 2026.1 database created with that configuration, the SLA clock therefore counts these business hours for a service level that names no calendar, without further setup.

What an SLA decides in the Self Service Portal

Services and their SLAs also decide what a Self Service Portal user is offered. A user receives a service that is not inactive when the service has no SLA, or has an SLA that is not inactive and is global or names the user, the user's organization, or one of the user's groups as a receiver.

  • A Knowledge Base article, an announcement, or a library item is offered when it has no service or its service is one the user receives. An article must also be public and live, and an announcement must be meant for Self Service Portal users.
  • A Service Catalog item is offered only when its service is one the user receives, so an item with no service is not offered. The item must also be active and be in a public category whose parent categories are public as well.