Service level agreement

The commitments, before you are a customer

Most providers will not show you an SLA until you are at contract stage, which is exactly when it is hardest to negotiate. This is ours, published where anybody can read it and compare it against the alternative.

The contract, before the service levels

Three month rolling. ICS does not tie customers into long-term service agreements. If you are not happy with the service in the first month you can simply say goodbye. After that, three months notice either way.

This is deliberate. A provider that locks you in for three years has no commercial reason to keep earning the work. We would rather retain you by being consistently good at it.

How we charge

We will not put a headline figure on a website, because the honest answer depends on how many people you have and what state your systems are in. What we will publish is the shape of the bill, so there are no surprises in it.

ServiceChargedWhat moves the number
Managed ITMonthly, per user or per deviceHeadcount, number of servers, how many sites
Business VoiceMonthly, per seatSeat count, whether you keep existing handsets
Contact CentreMonthly, per agentConcurrent agents, inbound or outbound, recording
Carrier platformPer deployment, then per nodeCapacity, interconnects, which edition
MessagingPer message, tiered by volumeMonthly volume, destinations, HLR lookup
Software, websitesFixed price per project, or hourlyScope. We quote after scoping, not before
Fibre and field workPer project, or day rate per technicianCrew size, duration, travel
Repairs and trainingHourlyTime on the bench or in the room
  • The audit is free. We look at what you are running and quote against it at no charge, whether or not you engage us.
  • Three month rolling. No long-term lock-in, so the price has to keep being worth paying.
  • Out-of-scope work is quoted, not absorbed silently. You approve it before it happens.
  • No charge for travel inside the Bay of Plenty and Waikato on contracted work.

How to raise something

ChannelDetailAvailability
Telephone+64 7 347 704424/7/365
Emailinfo@icsservices.nz24/7/365
CRM portalTicket raised and tracked to closure24/7/365
Instant messagingFor existing customers, by arrangementBusiness hours
On siteBay of Plenty and WaikatoDispatched by severity

Every issue raised through any channel is recorded in the trouble-ticketing system, so it is tracked, monitored and formally closed rather than lost in somebody's inbox.

How severity is decided

Severity is about business impact, not about how loudly it was reported. It is assigned at logging and can be revised as the picture changes.

LevelDefinitionExample
S1 CriticalThe business cannot trade. Total loss of a core service with no workaround.Site network down, phone system down, server unavailable
S2 HighSevere degradation, or a critical fault with a workaround in place.Calls failing intermittently, one site of several offline
S3 MediumA component is faulty but the business continues to operate.A single user cannot print, one handset faulty
S4 LowRequests, questions, changes and scheduled work.New starter setup, a configuration change, advice

What we commit to

SeverityAcknowledgementWork begins
S1 CriticalWithin 30 minutesWithin 1 hour
S2 HighWithin 1 hourWithin 4 hours
S3 MediumWithin 4 hoursNext business day
S4 LowWithin 1 business dayBy agreement
  • Acknowledgement means a named person has the issue and has told you so. It is not an automated ticket receipt.
  • Work begins means diagnosis has actually started, not that it has been queued.
  • Restoration time is not committed to for faults whose cause is outside our control, such as a carrier outage or a hardware failure awaiting a part. Status updates continue at the agreed interval regardless.
  • On-site attendance follows where a fault cannot be cleared remotely, dispatched same day for S1 and S2 within the Bay of Plenty and Waikato. Travel time depends on where you are; see the coverage map on the home page.
  • S1 and S2 are answered around the clock. S3 and S4 are worked during business hours, 8am to 5pm weekdays.

Escalation, if you are not getting anywhere

An escalation path only works if it is written down before you need it. This one is short, because the company is small enough that the managing director is genuinely reachable.

  1. Support engineer

    First point of contact, and where the large majority of issues are resolved.

  2. Service desk lead

    Escalate if an acknowledged issue has not progressed within the committed window.

  3. Managing Director

    Muhammad Asif. Escalate at any point where you believe the response is inadequate.

What is in scope, and what is not

In scope

  • Products and platforms supplied by ICS
  • Hardware supplied and installed by ICS
  • Systems ICS has been contracted to manage, whoever supplied them
  • Support desk access through all published channels
  • Trouble-ticket tracking through to formal closure

Out of scope

  • Hardware and third-party systems procured by you directly, unless separately agreed in writing
  • Faults in a third-party carrier or internet service, beyond diagnosis and liaison
  • Software vendors we have no contractual relationship with, beyond acting on your behalf
  • Work outside the agreed service description, which is quoted separately rather than absorbed silently

This page describes the standard commitment. Where a contract states something different, the contract governs.

Compare this against what you have now

If your current provider will not show you theirs, that is itself an answer.