SLAs reports
Overview
The Service Level Agreements (SLAs) report measures your SLA metrics by the specific rule, times, and statuses so that you can identify the missed SLAs you should invest in. You will be able to understand the performance of your SLAs based on the goals you've set and how many SLAs you've breached. You'll first need to set up SLA rules in order to use this report.
Take a Front Academy course here to learn more about leveraging Front analytics to achieve your goals.
SLA breach definition
How does Front identify an SLA breach?
SLA reports are linked to SLA rules. With these SLA rules, a tag is added each time an SLA breach happens. The SLA report counts an SLA breach each time a conversation gets tagged with the SLA tag within the time period of the report. Removing the SLA breach tag from the conversation does not impact this, as the SLA breach will still be counted by the SLA report.
Example
The SLA rule VIP customers adds the SLA breach tag on a conversation on April 7th. You reply right after it's added and the SLA breach tag is removed automatically.
If your SLA report time period is:
April 6th to April 8th: the conversation counts as an SLA breach for the report.
April 8th to April 20th: the conversation does not count as an SLA breach. The breach happened before the time period requested.
Report sections
Main Metrics cards
Features
Three Averages cards feature metrics about your SLA performance.
Click on each metric to see the metric details; how it was calculated and which conversations were counted into the metric.
List of metrics
SLA Performance Over Time graph
Features
The SLA Performance Over Time line graph shows the changes in several key SLA metrics over time.
Click the dropdown menu to choose the metric you want to display, listed below.
Hover over points in the line graph to see specific metrics for each time increment.
Click on each metric to see the metric details; how it was calculated and which conversations were counted into the metric.
Metrics
SLA Details table
Features
The SLA Details table shows performance metrics for each SLA rule so that you get more granular statistics about your response times and breach volume.
Type in the search box to find a specific SLA rule.
Click the gear icon at the top right of this table to select which metrics you want to display, listed below.
Customize how many rows you'd like to display on each page using the Rows per page on the bottom left.
Click to more pages using the arrows and numbers on the bottom right.
"Not applied by SLA rules" metric details:
There are two situations that count towards the "Not applied by SLA rules" metric:
(1) Teammates manually adding the SLA breach tag to a conversation
(2) Regular, non-SLA rules adding the SLA breach tag to a conversation. e.g. The rule wasn't explicitly set up as an SLA rule, but it uses "THEN: Add tag: SLA breach" in its rule actions.
The SLA breach time (avg) metric for "Not applied by SLA rules" is calculated using conversations where the following situation occurred:
SLA breach tag added via any method
SLA breach tag removed manually or removed by a regular, non-SLA rule
The SLA breaches metric measures the number of times an SLA breach tag was added. So for "Not applied by SLA rules", if the SLA breaches column is 0, this means that there were no times where a teammate manually applied an SLA breach tag or a non-SLA rule applied an SLA breach tag. In other words, every time an SLA breach tag is added during your reporting period, it is done so by an actual SLA rule.
If there is a value for SLA breach time (avg) for "Not applied by SLA rules", this means that there were times where an SLA breach tag was removed manually or by a regular, non-SLA rule.
List of metrics
SLA goal: the time limit defined in the SLA rule's conditions
Instructions
Set up a new report view by following this guide.
Pricing
Analytics are available on the Growth plan or above. Some legacy plans with different names may also allow access to this feature.