SLA reporting dashboard overview (Professional and Enterprise)

Zendesk Explore is our new analytics software. In the future, we’ll be discontinuing Insights and you’ll need to start using Explore. To make the move now, see Moving to Explore from Insights.

The SLA reporting dashboard enables you to easily view how well you are meeting your SLA policies. This dashboard breaks down your SLA metrics by policy, time, and status, so you can identify problem areas.

Note: You must have set up SLA policies to use the SLA reporting dashboard (see Defining and using SLA policies). If you just created your first SLA policy, the dashboard might take up to 24 hours to appear.

To view SLA reports, you must select a SLA metric. You can select a metric from the SLA metric drop-down list on the headline report. If you do not select a metric, the reports will read 'No data'. The drop-down list is shown below. Only the metrics that are currently being used in your policies will appear. For a total list of SLA metrics you can use see, Defining and using SLA policies.

You can specify your results with filter options like date range, ticket group, SLA policy, organization, ticket priority, and brand. The filter options are available at the top of the dashboard above the headline reports.

You can also view more detailed information for several of these reports by drilling-in. A report can be drilled in if the icon appears at the bottom of the report.

It's important to note that these results are not calculated on a per ticket basis. To accommodate all metrics, we calculate reports on a per instance basis instead. For more information on instances, see Defining and using SLA policies.

SLA headline reports

Achieved percentage is the number of instances where the selected SLA metric's target was achieved over the total number of measured instances for the selected SLA metric.

Fulfill time is the median minutes it takes to fulfill the selected SLA metric.

Breach time is the median amount of time by which the target time is breached.

Breached tickets is the number of tickets that breached the metric's target time.

You can click % Achieved or Breached tickets to drill-in and to view underlying ticket information, including the SLA policy and the median breach time.

SLA policy by status report

The SLA policy by status report enables you to view the percentage of tickets in each policy that achieved the metric in the target time, fulfilled the metric but surpassed the target time, or have not fulfilled the metric but surpassed the target time. The percentage is based on the total number of tickets in the policy. This graph can help you identify which policies are or are not being met.

You can drill-in to view underlying tickets in each status by selecting a status' bar, or you can view tickets in each policy by selecting the Policy name. Along with ticket ID information, you can view the median amount of time the metric was active (SLA Metric Value) and the median target time (SLA Metric Target).

You can choose to view one status at a time by hovering over the Status label, or you can view the number of tickets in a percentage by hovering over the percentage number.

SLA breaches by weekday and hour report

The SLA reporting dashboard helps you better understand your SLA breaches by breaking your breached percentage down by weekday and hour. These two reports can help you identify when your SLA breaches are at their highest and plan accordingly. Neither of these reports contain drill-in functionality.

SLA breaches by weekday

The SLA breaches by weekday report displays the number of instances where the selected SLA was breached out of all instances for the selected SLA.

SLA breaches by hour

The SLA breaches by hour report displays the number of breached instances for the selected metric out of all instances for the selected metric at every hour. You can use this report in conjunction with the SLA breached by weekday report above to identify what time during the week SLAs are more frequently breached.

SLA metric achievement over time

The SLA metric achievement over time report displays your SLA metrics' achievement percentage over the last ninety days, in respect to your filtered time range. You can use this report to analyze how you are currently meeting your SLA goals compared to previous weeks.

You can drill-in to this report in two ways. You can view one metrics' individual tickets achieved and breached during one week by selecting a point on the graph, or you can see all tickets during one week by selecting week name. In addition to ticket ID information, you can see the median amount of time the SLA metric was active and the median target time. If you drill-in by week you can view the SLA metrics applied, the metric status, and the median amount of time the SLA metric was active.

Additionally, you can hover over a metric's name at the bottom of the graph to view one metric at a time.

This all sounds very interesting, could you please update the article with directions on how to find the SLA Dashboard?
I have had a (one) policy set up for some time (and I'm on the Enterprise plan), so I expect the Dashboard should be visible for me.
Probably somewhere like: Reporting > Insights > Advanced Metrics (maybe?), but I'm not seeing it.

I'm also waiting for it to appear, as a new tab to the right of the Agent Activity tab as Colin mentioned.

Zendesk Support tells me that not all projects have migrated to SLAs, they could not give me an ETA on when it would happen either. They quoted from an update on this article:

[Update: August 25] While most customers using SLAs will now have the SLA dashboard, there are some Insights projects that are still loading.
• If you see the SLA dashboard but it's empty, your project is still in the process of downloading the SLAs data
• If you cannot yet see the SLA dashboard, your project is still in the queue to be migrated to SLAs

Can you be more specific? I'd like to know what subdomain you're working with, the name of the report, what the name should be, and whether this is a report you built yourself or if was automatically generated. Once I have that I can look into it for you. :)

As for the SLA breach thing, I talked with some folks who are smarter with SLAs than myself and my understanding is that if you have SLAs that are already breached at the end of business on Friday, and then an agent goes through and updates those tickets (and only those tickets) on Saturday, you will end up with 100% breach on Saturday, regardless of your business hours.

If I'm understanding it correctly, the system won't automatically check for SLA breaches outside of business hours, but if the ticket is updated by an agent outside of business hours it'll record the breach for the time at which the update was submitted without regard to whether you're actually "open" at that time.

Otherwise, if the SLA won't be breached until the next business day (according to your business rules), updating tickets on a Saturday won't have a negative impact - it'll consider that the SLA for those tickets was met.

I feel like there are probably some layers here that need some in-depth research, though, depending on the circumstances surrounding these specific tickets and your business rules and stuff. If this explanation doesn't clear things up for you, I'd recommend submitting a ticket with as much detail as you can provide so we can take a closer look for you.

Provided that there's data to be found, it should be imported with the rest of your data when Insights and Zendesk sync. If you don't have any data for that new policy yet, though, nothing's going to show up.

My guess is that you haven't yet had any tickets that meet the conditions of the new policy yet, which would explain the lack of data.

If you've definitely had tickets that meet those conditions and you're still not seeing the data, though, I'd recommend shooting a ticket over to Support so we can dig into it and figure out what's going on.

Zendesk Support found the issue for me - only one SLA can apply to each ticket, in my case, my second SLA was the more specific one and the first SLA had already been applied to it. Switching the specific SLA to the first position should resolve this.

Might be worth mentioning the importance of ordering SLAs from specific to generic in the article :)

It looks like you've posted two separate SLA questions which are both similar. To best answer these questions for you we're going to need to discuss account specific information so I'm going to go ahead and bring you into a ticket for both of these so we can review this with you!