Remote
Support
Remote Support

Service Level Agreements (SLAs) define how we respond to your issues and requests.

Service Level Agreements (SLAs) essentially represent our promise to deal with your IT issues and requests within a given time frame.They reflect our reliability, efficiency and confidence in the support that we provide. They show that we have an efficient and mature process for providing IT support and that you can have confidence in us. Our processes follow ITIL guidelines to ensure high levels of service across all areas

Our SLAs depend on our agreement with you and the priority of your issue or request.

Standard Hours of Cover

Support Hours

While some clients have extended and out-of-hours of support, our standard cover runs from 8:30 am to 6:00 pm from Monday to Friday, but excluding public holidays for England.

Major Issues

Our monitoring service runs 24×7 and major issues are dealt with accordingly by our out-of-hours incident team

SLA Timers

Our SLA runs only during our agreement with you.

Optional 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’s depend on the priority and urgency 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: Urgency and Impact.

Impact

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

  • Low – one person or small group of people affected
  • Minor – department or large group of people affected
  • Major – whole organisation is affected and not running at full capacity
  • Critical – whole organisation is affected and running at zero productivity
Urgency

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
  • Urgent – the issue is preventing the whole business from operating
Ticket Allocation

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

  • Repairs and installations – 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.
  • 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.
Escalation Process

To ensure best practice and to maintain our levels of service we have an escalation process, please refer to your account manager who will deal with this for you.

We Then Apply Our Priority Matrix As Follows

Ticket Allocation

These are our priority levels and the timescales in which we aim to respond and resolve

We Then Apply Our Priority Matrix As Follows

Ticket Allocation

These are our priority levels and the timescales in which we aim to respond and resolve
About us
Who we serve
Where we serve
  • Rochdale
How to get support
Contact us
General
Parent Company
X-twitter Linkedin

© 2025 Weald Computer Systems Limited. All Rights Reserved.