QNN SolutionsService levels

Clear priorities.
Agreed commitments.

Agree response targets, coverage hours and a named escalation route before the service begins.

Targets agreed in writingFour priority levelsNamed escalation

Priorities

Four levels,
agreed before we start.

Priority is set by business impact, not by how loudly it was reported. We agree the definitions with you during scoping so there is nothing to argue about at 9am on a Monday.

Our commitment Target, not a guarantee where a third party owns the fix

P1 · Critical
Business stopped, or an active security incident.

Response target

Critical incident response target agreed in your signed service schedule

Target resolution

Continuous until service is restored or a workaround is in place

P2 · High
A team or a core function blocked. One department cannot work.

Response target

High-priority response target agreed for your coverage window

Target resolution

Restoration target agreed for the affected service

P3 · Medium
A single user blocked, or a degraded service with a workaround.

Response target

User-support response target agreed in your service schedule

Target resolution

Planned against impact and available workarounds

P4 · Low
Requests, changes, questions, new starters and leavers with notice.

Response target

Request handling time agreed during scoping

Target resolution

By the agreed date in the request

Targets apply within your agreed coverage window. Where a vendor, an ISP or a hardware supplier owns the fix, we manage the escalation and keep you updated — but we do not promise a resolution time we cannot control, and we say which is which in the ticket.

Coverage

Choose the hours
your business actually runs.

Business hours

Your working day, your time zone, Monday to Friday, public holidays excluded. The default. Suits most SMEs.

Extended hours

Early start and late finish, covering two time zones or a longer operating day. For teams spread across regions.

24/7

Round-the-clock response on P1 and P2, with an on-call rota and a named escalation contact. For systems where downtime has an hourly cost.

Escalation

Four steps,
ending with a person.

If something is stuck, you should not have to find out who to chase. This ladder is in your agreement with names against it.

  • Level 1 — Service desk

    Logged, triaged and either fixed or routed within the response target.

  • Level 2 — Specialist

    Cloud, network, security or application specialist picks it up.

  • Level 3 — Engineering lead

    Owns anything unresolved past target, and tells you why.

  • Level 4 — Delivery owner

    Your named contact. Reachable directly, by name, without a ticket.

Reporting

Performance you can
check, not take on trust.

Every month, in writing. If we miss a target, it appears in the report with the reason — we do not wait to be asked.

  • Tickets raised, resolved and open, by priority
  • Performance against each response and resolution target
  • Incidents, changes and anything still outstanding
  • Spend on licences, cloud and third parties
  • What we recommend next, and what can wait
Monthly service reportIllustrative structure

One page, then the detail.

  1. Did we hit the targets?A yes or no per priority level, with misses explained.
  2. What changed this month?Incidents, changes, new starters and leavers, projects moved.
  3. What should happen next?Prioritized, costed where it needs budget, and honest about what can wait.

Questions we get asked.

Your signed agreement sets the contractual response targets and coverage window. This page explains our priority model; it does not create a separate response-time commitment.

It appears in the monthly report with the reason, whether or not you noticed. Where a service credit regime applies, it is set out in your agreement.

On P1 and P2, yes, where the engagement justifies it. Round-the-clock cover on low-priority requests costs money and helps nobody, so we do not sell it.

You do, against the definitions above. If we think something has been mis-rated we will say so and explain why, but we do not quietly downgrade your tickets.

Want these targets against your environment?

Tell us your coverage hours and what would count as a P1 in your business. We will come back with targets we can commit to.

  • 1
    We aim to reply within one working dayA person, not an autoresponder.
  • 2
    A 20-minute scoping callEnough to tell you whether we are the right fit.
  • 3
    A written scope and priceWith the exclusions stated, before anything starts.
No obligationNo lock-in contractsWe never ask for credentials

Or write to info@qnnsolutions.com

What is this about?
Helps us come back with something specific.

We use your details to respond to this enquiry. Privacy policy.