Every help desk makes promises. 'We will get to it today.' An SLA simply writes the promise down and starts a clock - and in ServiceDesk Plus, that clock will publish your real performance every month, whether you like the story or not. Set the promise carelessly and the report becomes a monthly embarrassment nobody reads.
SLA management in ServiceDesk Plus is genuinely capable: separate response and resolution targets, targets that vary by priority, site and other criteria, business-hour calendars with holidays, and multi-level escalations that fire before a breach, not after. The tooling is not the hard part. The hard part is choosing numbers that describe the team you actually have - and then treating every breach as information instead of shame. This guide sets SLAs the honest way: measured first, promised second, tightened slowly.
Keep the two SLA clocks separate in your head, because they measure different virtues. The response clock measures acknowledgement: a human has seen this, owns it, and has told the requester so. It should be short and almost never breached - responding is cheap. The resolution clock measures the fix, and it honestly depends on parts, vendors and access to the user. ServiceDesk Plus tracks both, and reports both, and conflating them produces the classic lie: a ticket "answered" in five minutes by an auto-reply that then sat for nine days. Configure what counts as a response - a technician's real reply, not the system's acknowledgement mail - and judge your team on both numbers separately. Requesters forgive a slow fix they are told about; they do not forgive silence.
The honest way to choose numbers: run the desk for a few weeks, export what actually happened, and set the first SLA slightly better than your measured average - close enough to be credible, stretched enough to require effort. Targets copied from an ITIL textbook ("critical resolved in one hour") collapse on contact with a two-technician team and a parts vendor in another city, and once staff learn the targets are fiction, the clock stops meaning anything. Set targets by priority, and let them differ by site if your sites honestly differ. Configure the operating hours calendar to your real working pattern with your real holidays, or every Monday morning will open with a screen of red breaches that happened while the office was closed - the quickest way to train everyone to ignore red.
An escalation that arrives after the breach is an obituary. ServiceDesk Plus lets you stack escalation levels at chosen times before the deadline - use them as a ladder of attention. First level, ahead of the response deadline: remind the assigned technician. Second level: notify the group lead, who can reassign or unblock. Third level, near resolution breach: the IT manager sees it, with the ticket's full history attached. Keep the ladder short and the messages rare - if escalations fire on a third of all tickets, your targets are wrong or your staffing is, and no notification setting will fix either. Also configure the on-hold behaviour honestly: when a ticket waits on the requester or a vendor, a defined status can pause the clock, but require a note saying what is awaited, or "on hold" becomes the drawer where hard tickets go to stop ageing.
Once a month, read the breach report with the technicians in the room and sort every breach into one of three buckets: target wrong (the promise never matched reality), process wrong (waiting, handoffs, missing access), or capacity wrong (too few hands at the peak). Each bucket has a different fix, and only one of them is "try harder". Adjust one target at a time, tighten gradually as the numbers improve, and publish the trend where the office can see it. An SLA you meet 96 percent of the time with visible effort is a standard. One you miss 40 percent of the time is a decoration - and decorations get ignored precisely when a real critical ticket arrives.
The walkthrough shows tickets moving through assignment and status live - the same flow your SLA clock will be measuring.
Watch Full VideoOnly if you configure the SLA with round-the-clock hours. Most offices should run SLAs on a business-hours calendar with their holidays marked, so tickets raised on Saturday evening are measured from Monday morning. ServiceDesk Plus supports both patterns per SLA policy.
Yes - statuses such as On Hold can be configured to pause the SLA clock, which is fair when the delay is genuinely not yours. Protect the honesty of it: require a note on what is awaited, and review on-hold tickets weekly so the pause does not become a hiding place.
One derived from your own last month. Measure your current average response and resolution times per priority, set the first targets a little better than those averages, and tighten one notch per quarter as you improve. Borrowed textbook numbers fail because they describe someone else's staffing.