Help Center/Admin Operations/How to use the SLA screen (Support)
Admin Operations•Last updated: 2026-10-20•3 min read

How to use the SLA screen (Support)

The first-response and resolution targets per ticket priority. Tickets opened after a policy exists get due times from it.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the page

Sign in as an administrator and use Admin sidebar → Support → SLA, or go to /admin/support/sla. The heading reads "Support SLA Policy".

2

Know where the data comes from

This page reads i8_hd_sla_policies (and the tickets, to count breaches). KPI tiles "Policies configured", "Breached now", "At risk", "Met", "No policy". One row per priority (LOW, MEDIUM, HIGH, URGENT) with Policy (CONFIGURED or NOT CONFIGURED), targets in minutes, ticket and breach counts.

3

Set a policy

Click New Record (Super Administrator only), choose the Priority, enter "First response target (minutes)" and "Resolution target (minutes)" (not smaller than the first), and save. Saving a priority that already has a policy replaces it.

4

Understand the scope

A policy applies to tickets opened afterwards; existing tickets keep their due times. With no policy for a priority a ticket simply has no due time.

5

Use the shared controls

Use the shared controls: the search box ("Search records, hashes, DIDs...") filters rows by any text; "Status:" offers ALL, CONFIGURED, NOT CONFIGURED; "Page Size:" sets 10, 15, 25 or 50 rows; Refresh reloads; Export saves the rows currently loaded as a JSON file; New Record opens the form described above. The line "Data:" under the heading names the real source.

Expected Operational Outcome

The policy is stored and shown; new tickets of that priority carry due times.

Troubleshooting & Failure Modes

Symptom: "Changing SLA policy requires a Super Administrator"
Likely Cause: Policy is platform configuration.
Resolution: Ask a Super Administrator.
Symptom: Error "Failed to load support/sla: HTTP 401" or "HTTP 403"
Likely Cause: The session is not signed in or does not hold an administrative role.
Resolution: Sign in again with an administrator account and click Refresh.

Was this guide helpful?

Help us refine our platform documentation