Suptask
Suptask Web AppSignup for FREE
  • Welcome
  • Getting Started
    • Install Suptask
      • Slack permission scopes
      • Invite the Suptask App
    • Your first Inbox & Form
    • Ticket submission
    • Manage and Reply on tickets
    • Key concepts
    • User Guides
      • Ticketing as an Agent
      • Ticketing as a User
      • Rollout and Onboarding guide
    • FAQ & Troubleshooting
    • Contact Support
    • Videos
  • Setup & Configure
    • Inboxes
      • Inboxes
      • Users and Agents in the same channel
      • Service Level Agreements (SLA)
      • Agent Work Hours
      • Automatically create tickets from new messages
      • Migrate to the new generation
    • Forms & Fields
      • Forms
      • Custom Fields
      • Default Fields
      • Custom Statuses
      • Tags
      • Using the Organization field
    • Users & Permissions
    • Slack External Connections
    • Multiple Slack Workspaces
      • Multiple Workspaces & Slack Community
      • Enterprise Grid
    • Branding & White-labeling
    • Language & Translations
  • Working with tickets
    • For Agents: who respond and manage tickets
      • Overview and manage tickets as an Agent
      • Responding to tickets
      • Move or Escalate to another Inbox
      • Submit tickets on behalf of a user
      • Request and manage Approvals
      • Customer Satisfaction Score (CSAT)
      • Templated answers with Canned Replies
      • AI Assistant
      • Followers
      • Delete tickets
    • For Users: who submit tickets
      • How to submit a ticket
      • Overview your tickets as a user
    • Overview & Analytics
      • Overview and track tickets
      • Dashboard
      • Reports
    • Essentials for Your daily work
      • Tickets Summary Notifications
      • Setup one-click emoji reactions
      • How to search for tickets
      • Display Suptask in Slack
  • Integrations, Automations & Workflows
    • Introduction to Integrations
    • List of integrations
    • Integration guides
      • Slack Workflows
      • WhatsApp
      • JIRA Software
      • Zendesk
      • ClickUp
      • Notion
      • Google Sheets
      • Suptask API
      • WebHooks
      • Export API
      • Integrate with other Slack Apps
      • External issue & ticketing systems
        • Create tickets from Suptask to GitLab
        • Create tickets from Suptask to GitHub
        • Create tickets from Suptask to JIRA
    • Email-to-Slack Ticketing
      • Email-to-Slack Ticketing
      • Gmail & Google Workspaces
      • Microsoft Outlook
      • AI Email routing
    • On-call rotation
    • Automations in Suptask
  • Account Management
    • Account Settings
    • Subscription & Billing
      • Subscription & Billing
      • Integrations billing
      • Limitations in the Free plan
Powered by GitBook
On this page
  • Overview
  • SLA rules and thresholds
  • Breaches, escalations and notifications
  • Example SLA configuration
  • Custom Performance Metrics

Was this helpful?

Export as PDF
  1. Setup & Configure
  2. Inboxes

Service Level Agreements (SLA)

Send automatic reminders when tickets break a threshold

PreviousUsers and Agents in the same channelNextAgent Work Hours

Last updated 2 months ago

Was this helpful?

Overview

Contact to get access and set up SLAs on your account.

Service Level Agreements (SLA) enables you to define how Agents should work with tickets in order to provide a good experience to requesters.

This is done by defining certain thresholds that are applied to your Inbox, where tickets need to comply by these thresholds.

Agents will automatically be notified about potential or executed breaches, making it easier to stay on top of your tickets.


SLA rules and thresholds

  • Priority levels: Define what Priority levels the SLA rule should be applied on. None, or Low, Medium, High, Critical

  • Resolution time: Time it takes to move a ticket to Closed (Solved). Calculated from when the ticket is created to when it is closed.

  • Reply time: Time it takes to send replies as an Agent (via the Responder channel) to Requesters. Calculated from the last reply. For the first reply, it is calculate from when the ticket was created.


Breaches, escalations and notifications

Tickets who are about to breach its SLA threshold, or faces a risk of doing so, can automatically notify Agents and other users.

  • Send a notification prior to a threshold breach: Define the time in minutes when the assigned Agent should be notified about a potential breach coming up.

  • Send a notification when a threshold has been breached: Define the time in minutes when the assigned Agent should be notified when a threshold has been breached.

  • Send an escalation notification: Select another user than the Agent who should be notified about the breach, for example the manager or team lead of the Agent team.

Example breach notification in:

Example escalation notification:


Example SLA configuration

Priority thresholds

An SLA breach will occur when a threshold is exceeded.

Priority
Reply time threshold
Resolution time threshold

None

24 hours

7 days

Low

12 hours

4 days

Medium

8 hours

2 days

High

4 hours

1 day

Critical

1 hour

12 hours

Ticket notifications

Notifications are sent in the ticket targetting the assignee(s) when a threshold is breached.

Optionally you can configure a reminder notification prior to a breach.

Notify before & after
Excluded statuses
Max Notifications
Notify every

30 min

Waiting for customer

3

Daily

Escalation notifications

Escalations can be sent to any user of your choice.

Escalate after
Escalate to users
Excluded statuses
Max Notifications
Notify every

1 day

Greg (Manager)

Waiting for customer

3

6 hours

Custom Performance Metrics

Custom Performance Metrics is available in the Custom plan and might come with an additional cost.

Suptask allows you to customize how your performance metrics are calculated, such as the Time to Resolution.

By defining what ticket statuses you want to include or exclude from the time, you can achieve a custom calculated performance metric that is aligned according to your needs.

Example of a custom Time to Resolution (MTTR):

  • Open - Excluded

  • Assigned - Included, start to calculate from when the ticket is Assigned.

  • In-Progress - Included

  • Escalated - Included

  • Waiting for customer - Excluded, stop calculating when the ticket is waiting for the customer.

  • Closed - Stop calculation.

Suptask Support
This message is sent in the ticket thread as a notification to the team and Assignee
This summarized escalation message is sent to e.g a manager directly from Suptask