IT SLA Management in Console

Why SLA management matters in Console

Service Level Agreements define how quickly teams respond and how fast issues are resolved. In Console, SLA management is tightly connected to priority tiers, automated triage, alerting, and reporting. Instead of manually tracking deadlines, teams configure expectations once and let Console enforce them in real time.

Priority tiers and configuration

Console supports four configurable priority tiers: Urgent, High, Medium, and Low. Each tier has independently configurable response time and resolution time targets. Response time and resolution time are separate fields, giving teams granular control over both first touch and full resolution expectations.

Priority tiers are configured using natural language prompts. No code is required. For example, an Urgent definition can be: “if this is directly blocking the user from working.” Teams can define all four tiers to ensure complete coverage across request types and to set a clear tone for how quickly users can expect support.

How priority is assigned automatically

Every incoming ticket is automatically assigned a priority by Console’s AI based on the content of the request. This ensures consistent triage. even when submissions vary in detail or clarity.

Priority can also be influenced by contextual signals such as:

• Requester seniority, for example auto-marking VP-level and above as Urgent

• Impact scope, such as escalating when an issue affects all of Austin or 1,000 users

• Issue type or request category

Multiple layers of priority logic can stack together. Seniority, impact scope, and request content can combine to determine the final priority without manual intervention. For example, a request submitted with minimal context may automatically be assigned Low priority.

SLA alerting and escalation

Console fires SLA alerts when tickets are approaching their response or resolution deadlines and when those deadlines are breached. Alerts surface risk early so teams can intervene before compliance is lost.

Alerts are available as:

• In-app notifications inside Console

• Slack notifications to a dedicated channel

• Microsoft Teams notifications to a dedicated channel
  
  

Alert timing can be differentiated by priority tier. Urgent tickets can trigger earlier and more aggressive alerts than Medium or Low tickets. SLA alert configuration lives in the Alerts section of each workspace’s settings.

Escalation rules can be configured so tickets automatically escalate if they are about to breach or have breached SLA targets.

What agents see in the Inbox
SLA compliance status is visible directly in the ticket list view. Tickets that are out of SLA compliance are visually flagged so they surface prominently without requiring manual tracking.

Assigned agents receive:

• Direct notifications when their tickets are approaching SLA deadlines

• Automated SLA reminders

• Clear visual indicators for out-of-compliance tickets

This ensures SLA adherence is operationalized inside daily workflows rather than managed through separate reporting tools.

SLA in multi-approval and long-running workflows

For tools like Opal, Tori, and Lumos where approval flows can take days, Console’s SLA timer begins the moment a ticket is created, regardless of whether part of the workflow is handled in a third-party system.

Once a request is handed off externally, Console may not have direct visibility into that downstream workflow. To bridge this gap, teams can configure a status-check playbook that calls the third-party API and returns a live update such as: pending approval from X person. This reduces repeated status inquiries while keeping SLA tracking consistent from intake onward.

SLA analytics and reporting

Console provides SLA visibility in the Inbox dashboard and in out-of-the-box analytics with no custom setup required. Teams can monitor performance and isolate risk quickly.

Tickets can be filtered by SLA status to identify breached or at-risk items. Custom views can be built to focus on:

• Out-of-SLA tickets

• Tickets assigned to a specific person

• Specific request types

Analytics can also be filtered by ticket creator, status, assignee, category, channel source, and playbook triggered. This gives IT leaders operational visibility into response performance and resolution reliability across the organization.