You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Service Level Agreements (SLAs) are critical to ensuring that customer support teams deliver quality and timely support to their customers. However, in the event of an SLA breach, it can lead to a loss of customer trust and damage to the company's reputation.
An SLA breach occurs when a support team fails to meet the agreed-upon service level targets within the agreed-upon time frame.
Any SLA has three status changes: MET, Breached, and Exceeded.
For example, if your SLA goal is 20 hours, the support team must complete the customer's request by that time. After 20 hours, the SLA is breached, and the team has failed to meet the time promised to the customer.
To prevent the SLA Breached status, we must set the specific Breached time — the extreme limit to which we must close the issue. In our example, it would be 2 hours before the end of the SLA.
The Breached interval can be adjusted so that you have enough time to handle the problematic SLAs.
The faster you set Breached, the more time you will have to close the SLA.
Here's an example of how to set the notifications in JSM configuration for “2 hours before breach”:
Here's how you can prevent an SLA breach by using the SLA Time and Report add-on:
Setting realistic service level targets that the support team can meet is crucial for preventing an SLA breach. SLAs should be agreed upon by both the customer and the support team, and there should be a mutual understanding of the consequences of an SLA breach.
In an SLA breach, it is essential to take immediate action to minimize the impact on the customer. Here are some best practices for handling an SLA breach:
An SLA Time and Report for Jira add-on can help prevent and handle SLA breaches effectively. This add-on provides an easy way to track service level targets and measure the support team's performance.
In conclusion, breaching an SLA can have serious consequences, so it's essential to set realistic targets and have a plan to prevent and handle breaches. Set specific breached times and adjust them as needed, use automation tools to notify team members and escalate issues when necessary — this is all you need to prevent the SLA breach. In an SLA breach, acknowledge the breach, investigate the cause, and communicate with the customer.
The SLA Time and Report for Jira add-on can help prevent and handle SLA breaches effectively. Try a 30-day trial, and book a demo call if you require additional information.
2 accepted answers