Skip to content

Insights / Support

How to Evaluate IT Help Desk Support Before You Sign

Judge a help desk on response and resolution targets, priority rules, escalation, after-hours terms, and ticket quality, not on a sales promise.

Managed IT

A clearer view of what comes next.

Every help desk says it is fast. The contract is where you find out what “fast” means, who decides how urgent your problem is, and what happens at 7 p.m. on a Friday.

If you are an IT director, operations leader, or practice manager comparing providers, the goal is to turn a friendly pitch into terms you can measure. This guide covers the six areas that separate a help desk that keeps your people working from one that mostly logs tickets.

Separate response time from resolution time

These are different clocks, and a provider can look good on one while failing on the other. Training provider Purple Griffon defines a response target as the maximum time before a support team member acknowledges a ticket, and says a response “is not about resolving the issue but about initial contact.” A resolution target is the maximum time within which the issue is expected to be resolved.

A fast acknowledgment with no resolution target tells you very little. Ask for both numbers, for every priority level, and ask what counts as “resolved.” Restoration of service and an acceptable workaround are not the same as a permanent fix, and the agreement should say which one stops the clock.

Read the fine print on whether the numbers are commitments or objectives. Many agreements, including ours, describe targets as good-faith objectives rather than guarantees. That is common, but you should know which kind you are buying and what remedy, if any, applies.

Demand clear priority definitions

Priority rules decide who gets help first. A common approach is to categorize incidents by urgency and impact, with the top tier reserved for severe impact on multiple users or essential business functions.

Check these points in any agreement:

  • Are examples given for each level, such as “email down for the whole organization” versus “one user cannot print”?
  • Who assigns the priority, you or the provider, and can it be changed as facts develop?
  • Do requests such as new user setup or password resets have their own category, so routine work does not crowd out outages?

Z7’s SLA is an example of the level of detail to look for: four severity levels with written definitions and examples, response targets for each, and resolution targets for each. It also states that Z7 assigns severity using those definitions and may reclassify a ticket as the facts develop.

Map the escalation path

Purple Griffon notes that when an issue is not resolved within the agreed timeframe, SLAs typically define the steps to escalate it. Ask to see that path in writing.

Question What a good answer includes
Who handles the ticket first? Named tier or role, with authority to resolve common issues
When does it escalate? A trigger based on time or severity, not on the technician’s judgment alone
Who is the next level? A defined tier or specialist group, not “we will find someone”
How do we reach a human leader? A named management contact for stalled or critical tickets
How are third parties handled? Who contacts the software or hardware vendor, and who owns the ticket meanwhile

Also ask how escalation works when an incident looks security related. A help desk that cannot hand a suspicious sign-in or malware alert to a security team quickly is a gap you will discover at the worst moment.

Pin down after-hours coverage in the contract

“24/7 support” on a website and after-hours terms in a contract are not always the same thing. Coverage can range from round the clock to business hours only, so the agreement should define when the desk is available.

Look for three details. First, the business-hours window and the holiday calendar. Second, whether after-hours response targets exist at all. Third, what happens to a ticket received outside coverage. In Z7’s SLA, for example, after-hours targets apply only to services that the statement of work identifies as including after-hours or 24x7 coverage. Otherwise a ticket received after hours is treated as received at the start of the next business period. Whatever provider you choose, ask for the same clarity, and confirm whether after-hours work is included or scoped separately.

Inspect ticket quality, not just ticket speed

Ask for a sample of anonymized closed tickets, or sit in on a review. You are looking for evidence of root-cause thinking:

  • A clear description of the problem in the user’s words
  • Steps taken and the reason for the fix
  • Whether the underlying cause was addressed or only the symptom
  • Notes that a different technician could pick up without starting over

Repeat tickets are the quickest signal. If the same password lockout, printer, or VPN problem returns monthly, the provider is closing tickets without fixing causes. Ask how recurring issues are identified and who is accountable for removing them.

Look at satisfaction surveys and reporting

Speed metrics can hide rushed or incomplete fixes. Pair them with outcome measures: first-contact resolution, reopened tickets, escalation rate, and user satisfaction collected after resolution. Treat any benchmark a vendor quotes as indicative unless it is tied to your own data.

Ask what you will receive and how often. A useful monthly report shows ticket volume by priority, performance against each target, the top recurring issues, and open items older than the agreed limit. Ask how the provider measures against its targets, and whether you can see the underlying ticket data rather than only a summary.

Questions to ask every provider

  1. How do you define and measure response time and resolution time, and what stops the clock?
  2. Can we see the full severity definitions with examples?
  3. Who sets priority, and how is a disagreement resolved?
  4. What are the escalation triggers and named contacts?
  5. What exactly is covered after hours, and is it in the statement of work?
  6. How do users submit tickets, and which channels are monitored?
  7. Can we review sample tickets and a recent monthly report?
  8. Who handles vendor and security escalations?
  9. What is excluded from the monthly agreement, including projects, hardware, and onsite work?
  10. How do you handle account access for your own technicians? CISA’s managed service provider guidance recommends that customers require MFA on provider accounts and keep them out of internal administrator groups.

Where Z7 fits

Z7’s help desk services offer phone, email, chat, or portal support, with response and resolution targets published in our SLA and reporting on performance against them. Your team can also submit a support ticket. If you want to test a provider against this checklist, book a conversation and bring your current agreement.

Put it into practice

Illustrative planning model

A practical path to recovery

Explore step 01

Name the critical work

What needs to return first?

Identify the services people need first after a disruption. Agree on the business impact and who can make recovery decisions.

Z7 Weekly Intelligence

We aim for one email a week: the threats that matter, new Z7 intelligence briefs and articles, and what to do about them. Unsubscribe anytime.

By subscribing, you agree to our Terms of Use. Our Privacy Policy explains how we use your email.

Let's talk about your next step.

Bring your questions, including the price ones. We will talk openly about scope, cost and whether we are a good fit.

Ask Zeus AI assistant