What do you know about SLA Performance? There’s more to it than you think

kpi

We know the SLA Automation in the Autotask PSA software is great at indicating:

1)    Which tickets need intervention

2)    Where in the Customers Journey tickets are getting stuck

3)    Which tickets need to be worked on next

4)    Which Customers are Managed Service Customers so they receive preferential treatment

5)    To the Customer when they can expect the Tech to engage on their request

Even more importantly, it lets us know how we are performing.  Are we meeting our Contractual Agreements, are we dropping the ball at Intake, Engagement, or Ending Strong?  And having the software recalculate a Due Date after we have been waiting on the Customer for months.

If this is news to you, schedule a call with us ASAP!.

Using SLA Automation as a Key Performance Indicator

When it comes to using the SLA Automation as a Key Performance Indicator, it can also tell us if the Service Delivery Team is worth a powder.  The SLA Performance report grades the Intake, Tech Engagement, and Completion scorecard of the team. 

If configured correctly, the First Response will tell you if the Intake process is on top of its game, the Tech engagement will tell you if the Techs are following protocols, and the Completion metric will tell you if the Customers are disappointed or frustrated.

Put your information below to download your free copy of our proposed SLA Settings.

At the end of the day, we hold the Service Coordinators responsible to shepherd all tickets from New to complete, making the SLA performance their primary scorecard.  If the Service Coordinator is doing their primary function (triaging tickets within 20 minutes of creation), then the First Response SLA will be met 97% of the time.  If the Service Coordinator is doing a great job reviewing the request and assigning it to the right skillset; or schedule when needed, then the Tech Engagement SLA will be 95%, and completion of all requests will be above 90%.  If your experience is different, or if your SLAs are not configured to provide this type of information, you are in trouble and need someone to guide you out of the weeds.

As a side note, we have rolled out the Service Delivery Foundational Improvement program for the last 2 ½ years; it has surprised us that once the intake processes (meaning that the First Response SLA is in the upper 90’s), the rest of the Service Delivery process starts working properly and the rest of the SLA benchmarks (Tech Engagement and Completion) meet expectations organically.

Summary: What you need to know about the SLA automation

So here are the specifics you need to know:

1)    First Response = Triage and is set as a 1-hour response time.

2)    Resolution Plan = Tech Engagement and response time depends on what Workflow the Request has been Triaged into

a.    Critical – 1 or 2 hours

b.    High – 4 hours

c.     High Backup – End of the day minus 2 hours

d.    Medium – 8 hours

e.    Standard – 12 hours

Note: the beauty of the Autotask PSA SLA Automation is that we can mix the Incidents listed above with the Service Requests listed below, and all requests will be sorted by Next SLA Due Date. Plus, they play nicely together.

f.     Quick Hit – 4 hours

g.    Moves/Adds/Changes < 4 hrs – 24 hours

h.    Moves/Adds/Changes > 4 hrs – 40 hours

i.      Installs – 80 hours

j.      Just in Time (JIT) Recurring Master Tickets – 40 hours

Note: these are in Business hours.

Completion is not something we promise to the Customer, but with Technician Effort less than 1 hour, should the Completion SLA match the Tech Engagement SLA?  And the First Contact Resolution (not the same as First Call Resolution) be 99%?

This brings up a great question.  If Triage is not meeting expectations, what is a Service Manager to do? 

-       Use the Service Delivery Forecast Supplemental Report as a tool for Resource Planning

-       Use the Workflow Distribution Report as a tool for Triage Quality

-       Last but not least, sit down with the Service Coordinator(s) and show them what the data is saying, and ask them what can we do as a Team to improve their #s.

From my experience, every Service Coordinator wants to do a good job, but there is very little Service Coordinator training available, until now.

Stephen Buyze

President of Advanced Global MSP Coaching

Previous
Previous

Using the Mean Time to Resolve (MTTR) KPI to Improve Your MSPs Bottom Line

Next
Next

The One thing MSPs Should Monitor to Measure Their Operations