Service Level Agreements

We take our service seriously. We have broken it down below for our customers to see what they can expect from us.

Service Level Agreements (SLAs) define how we respond to your issues and requests. They reflect our reliability, efficiency and confidence in the support that we provide.

The Basics

Service Level Agreements (SLAs) essentially represent our promise to deal with your ICT issues and requests within a given time frame. They show that we have an efficient and mature process for providing IT support and that you can have confidence in us.

Our SLAs depend on the agreed hours cover and the priority of your issue or request.

We can provide bespoke SLAs to suit your needs – extended hours of cover (24x7x365, weekends, public holidays), different speeds of response, priority, or cover for different types of equipment.

Standard Hours of Cover

  • While many clients have extended and out-of-hours of support, our standard cover runs from 7:30 am to 6:30 pm (GMT/BST), from Monday to Friday, but excluding public holidays for England.
  • Our monitoring service runs 24×7 and major issues are dealt with accordingly by our out-of-hours incident team.
  • Our SLA timers run only during your agreed hours of cover.
  • Our monitoring runs 24x7x365 regardless of your cover, so you can elect to increase cover for critical systems if you wish.

How We Work Out Priorities

Our SLA timers also depend on the priority of your issue or request. When you raise a ticket with us, we make an assessment based on the information you have given us.

We let you know the priority we have assigned, but are happy to take extenuating circumstances into account, if you think we’ve got it wrong.

Priority is based on two factors: severity and impact.


Roughly, this is how many people are affected by the incident, e.g.

  • LOW – one person or small group of people affected
  • MEDIUM – department or large group of people affected
  • HIGH – whole organisation is affected



Again, roughly speaking, this relates to how disruptive the incident is, e.g.

  • LOW – there’s an easy and effective workaround, so this is more an irritation than a stoppage
  • MEDIUM – operational efficiency is degraded, but there is either a reasonable workaround or other members of the team are unimpeded
  • HIGH – the issue is critical and one or more major business processes are stopped

We Then Apply Our Priority Matrix As Follows:

HIGH SeverityMEDIUM SeverityLOW Severity
HIGH ImpactPriority 1Priority 2Priority 3
MEDIUM ImpactPriority 2Priority 3Priority 4
LOW ImpactPriority 3Priority 4Priority 5

Two Clocks Are Ticking...

We have two clocks (timers) running on every ticket you raise.

“Respond within…”

This is the maximum amount of time (within your hours of cover) that it should take us to get back to you, and confirm who is dealing with your ticket – you get to speak to a trained technical expert straight away, rather than a recorded menu system or a call-logger.

“Resolve within…”

This is the one that everyone is really interested in: the maximum time it should take to get everything up and running.

These timers represent maximums – we generally come well within these time limits.

In certain circumstances we will put a clock on hold – for example when we are awaiting a response from you with further information or an approval for work that may have a temporary impact on you or your business.

The Goal Percentage

Sometimes, with the best will in the world, and in spite of our best efforts, there are extenuating circumstances that mean the time limit is breached. This is exceptionally rare, but just to cover this we set a target “goal %”.

This is how many of your tickets we promise to achieve within the time limits. To date we are well above these targets for all our clients, of course.


PriorityExampleFirst Response WithinTarget Resolution
P1. HighestA major fault or error that prevents all users from accessing the system or prevents the entire system from functioning. Everyone is affected.30 Minutes4 Working Hours
P2. HighA major fault or error that affects one or more applications, such as email is not accessible. Efficiency is affected.1 Hour1 Working Day
P3. MediumA fault that affects part of an application or system but does not prevent the use of the system for example there is only 1 printer in the organisation and it is not accessible. Multiple people are affected.4 Hours2 Working Days
P4. LowA fault that may prevent a function from working but there is an alternative and is an inconvenience, for example there are multiple printers and 1 printer is not accessible. Only you are affected.8 Hours3 Working Days
P5. LowestA shortcut you are used to is missing or you can’t access your bookmarks. Only you are affected.8 Hours5 Working days

Some Examples of Priorities

  • Priority 1 – nobody can send or receive emails (everyone is affected, and a major business process is stopped)
  • Priority 2 – Internet access for the whole company seems slower than usual (everyone is affected, and efficiency is degraded)
  • Priority 3 – After the web browser has been upgraded for the company some of the shortcuts have disappeared (everyone is affected but there is an easy workaround)
  • Priority 4 – Your computer is slow starting up in the morning, but everybody else is fine (your efficiency is lower but you’re the only person affected)
  • Priority 5 – Someone is missing the shortcut everyone has to a shared folder, though they can save files to it by manually navigating to the folder (there’s a straightforward workaround, and only one person is affected)

Other Exceptions To Our Priorities

The following are exceptions to our priorities and timers in the above matrix:

  • Paid workshop repairs – very often we’re dependent on supply of parts or arrangements with you for collections and returns, so we usually allocate a priority of 5 for these jobs.
  • Quotes – we have no timers on these requests, but we do our best to be prompt and keep you fully up to date.
  • Low priority admin requests – these have response times that match priority 4 but a resolve time of a priority 5. Generally we get plenty of advance notice and these requests are not urgent.