A service-level agreement (SLA) is a contract between you and your customers that sets the expectations for your service level. SLAs help ensure that your customers receive timely responses and resolutions to inquiries.
Policy users can set SLA breach and warning targets for three metrics: first response, next response, and full resolution. Each metric has its own breach and warning target. You can specify whether the metrics are calculated using calendar hours or business hours while defining breach and warning targets.
Create an SLA
Go to Settings > SLA > + Create.
In the Create SLA window, provide a name and description of the SLA.
After creating the SLA, assign policies to it.
Creating policies within SLA
Multiple policies can be created within an SLA. Each policy has a priority order, so if a ticket meets the conditions of two or more policies, the policy with the highest priority is applied.
To create a policy within an SLA, do the following:
- Click + Policy.
- Select either Ticket Policy or Conversation Policy.
- In the New ticket policy pane, under Conditions, select the ticket attributes values of Tag, Part, and Severity.
- Under Metrics, enable or disable First response, Next response, and Resolution time.
- Click Publish.
SLA metrics are only applied to tickets or conversations that meet the policy's conditions.
Publishing an SLA
SLAs can be published once all policies are created. Published SLAs can't be edited. The user can't change the policies or priority order of a published SLA.
SLAs can only be assigned to customers once they're published. Users can't add or remove customers until the SLA is published. Each workspace has its own SLA, and a single customer can have multiple workspaces.
In the Customer Details section, you can find the current SLA.
Select the customer by searching or clicking on the customer's name. The Customer Details pane is displayed.
Click ⁞ (next to Opportunities) > Workspace.
SLA details are available on the workspace. The applied SLA can be updated from here.
A default SLA can be set for any new customer created in DevRev. If no default SLA is set, SLAs have to be applied manually.
SLA metric calculation
SLA metrics are calculated based on the policy that's applied to the conversation or the ticket. There can be one or more SLA metrics active on a given conversation or a ticket. Each metric is tracked separately. SLA metrics are calculated according to the policy applied to the conversation or ticket. There can be one or more SLA metrics active on a given conversation or ticket, with each one being tracked separately.
SLA metric can be in one of the following stages:
- Active: The metric is currently being tracked on the conversation or ticket.
- Close to breach: The time spent by the SLA metric is greater than or equal to the close to breach target defined in the policy.
- Breached: The time spent by the SLA metric is greater than or equal to the breach target defined in the policy.
- Paused: The metric is currently paused based on some condition. For example, when a ticket moves to awaiting customer response.
- Completed: The conversation or ticket has reached the completion condition.
Based on business hours defined for an organization, Active/Close to breach/Breached metrics can change schedules. Metrics move out of schedule when they remain at the same stage, but time spent out of schedule isn't included in the calculation.
The following table describes how each metric works for tickets and conversations:
The SLA targets applied to a particular conversation can be viewed in the Inbox and the Conversation Detailed view. For a ticket in any of the ticket vistas.
When there are two active metrics, vista displays the one closest to the breach. In the case of a conversation where both the first response and full resolution metrics are active, and the first response is due in five minutes but the full resolution is due in one day, the vista displays five minutes. In the case where the first response isn't provided within five minutes, the timer displays negative values (such as -10m), which indicates that it's been 10 minutes since the first response was due. Conversations or tickets can also be grouped by SLA stages.
In the Detailed View, all metrics applied to the ticket or conversation can be viewed along with their current stage.