IT support means different things depending on who you ask: a helpdesk that answers the phone when something breaks, a managed services contract with monitoring built in, or an internal team backed up by an external provider for the gaps they cannot cover alone. Getting the model wrong is expensive in ways that do not always show up on an invoice — staff waiting on hold, the same fault recurring every few weeks, a security gap nobody actually owns.
This guide covers the real support models, what a good arrangement should include day to day, how to measure whether it is actually working, and how to choose a partner if you are bringing one in.
What are your IT support options
Most NZ businesses land on one of three models, and the differences matter more than the marketing copy usually suggests.
Break-fix vs managed IT services
Break-fix means you call someone when something breaks and pay for that call. There is no ongoing monitoring and no incentive for the provider to prevent the next problem, since they get paid when things go wrong. It can work for a business with a handful of computers and no real dependency on uptime.
Managed IT services flips that incentive. A fixed monthly fee covers monitoring, patching, and support, so the provider’s interest is keeping systems running rather than fixing what breaks. For any business that depends on its systems being up during the working day, this is the default model in NZ now, not a premium option.
| Factor | Break-fix | Managed IT services |
|---|---|---|
| How you pay | Per incident, unpredictable | Fixed monthly fee |
| Provider’s incentive | Gets paid when things break | Gets paid to prevent breakage |
| Monitoring | None | Ongoing, proactive |
| Response to a critical outage | Whenever the technician is free | Defined SLA, often with escalation built in |
| Best fit | A handful of devices, low dependency on uptime | Any business running on its systems during the working day |
Co-managed IT: keeping your internal team
If you already have IT staff but need more depth in a specific area — cybersecurity, cloud infrastructure, after-hours cover — co-managed IT adds an external provider alongside your existing team rather than replacing it. See our guide to co-managed IT for how this works day to day and the signs your business is ready for it.
For a closer look at what a managed service provider is actually responsible for day to day, see our guide to what an MSP actually does.
What good IT support actually includes
Beyond the pricing model, a handful of operational basics separate support that works from support that just generates invoices.
A ticketing system that does not lose requests
Every request needs a ticket number the moment it is logged — not an email thread, not a Slack message that scrolls out of view. A ticketing system gives you a record of what was asked, who is handling it, and how long it has been open. Without one, issues get raised twice, forgotten, or fixed with no record of what changed.
Clear escalation paths for complex issues
The person who answers the phone cannot solve everything, and a good support arrangement has a defined path for handing a problem to someone with deeper expertise: clear triggers for when to escalate, a named owner at each level, and a time limit before a ticket moves up automatically rather than waiting for someone to notice it has stalled.
Proactive maintenance, not just reactive fixes
Patching, monitoring, and scheduled system checks catch problems before they cause downtime. A provider that only shows up when something is already broken is running break-fix with a managed-services price tag attached.
A knowledge base that actually gets used
A well-maintained internal knowledge base lets staff solve routine problems — a password reset, a printer that will not connect — without waiting on a ticket. This only works if it is kept current and easy to search; an outdated knowledge base trains people to stop trusting it, which defeats the purpose entirely.
Signs your current IT support is not actually working
A few patterns are worth watching for even if nothing has gone catastrophically wrong yet: the same issue recurring every few weeks with no root-cause fix, staff routing around IT with their own workarounds, response times that quietly get slower over time, or a provider who cannot produce a ticket history when you ask for one. None of these show up in an uptime percentage, which is exactly why uptime alone is a poor way to judge whether support is working.
Cybersecurity is part of IT support, not an add-on
Multi-factor authentication, endpoint protection, email security, and regular patching are baseline requirements now, not upsells. If your current support arrangement treats security as a separate line item you have to ask for, that is worth questioning directly.
Employees remain the most common entry point for an attack, which is why ongoing awareness training matters as much as the technical controls — a well-trained team catching a phishing attempt before it is clicked is cheaper than any tool that cleans up after one. See our cybersecurity and antivirus service for what should be included as standard.
Business continuity: what happens when something breaks badly
Good IT support includes a tested plan for the day something goes seriously wrong — a ransomware incident, a server failure, a natural event. That means regular backups, documented recovery targets (RTO and RPO), and a runbook that names who does what. A backup that has never been test-restored is not a plan, it is an assumption, and it is one of the most common gaps found when a business finally needs to rely on it.
Our guide to business continuity and disaster recovery for NZ SMBs covers how to set those targets and test the result, and our disaster recovery services guide covers what to look for when comparing DR providers specifically.
How to measure whether your IT support is actually working
Uptime percentages alone do not tell you if support is working — they can look fine while staff quietly work around a slow, frustrating system. The metrics worth tracking:
- Average response time. How long before someone acknowledges a new ticket. OxygenIT publishes a sub-11-second average phone response during business hours as a working benchmark — ask any provider you are evaluating for their actual figure, not a target.
- Resolution time by priority. A password reset and a server outage should not share the same expected turnaround.
- First-contact resolution rate. How often a request is solved without escalation or a repeat ticket for the same issue.
- Ticket volume trends. A rising volume for the same recurring fault points to an unresolved root cause, not a support team working hard.
Ask any current or prospective provider to show these numbers directly rather than describing their process in general terms. A provider with nothing to show is telling you something.
IT support SLA benchmarks by severity
| Severity | Example | Target response | Target resolution | Escalation trigger |
|---|---|---|---|---|
| P1: Critical | Full outage, server down, active ransomware | Under 15 minutes | Under 4 hours | Immediate to senior engineer, management notified |
| P2: High | Single user blocked, key application down | Under 1 hour | Under 8 business hours | Escalate if unresolved after 4 hours |
| P3: Medium | Degraded performance, non-blocking fault | Under 4 business hours | 1 to 2 business days | Escalate if unresolved after 2 business days |
| P4: Low | General request, minor how-to question | Under 1 business day | 3 to 5 business days | Escalate if unresolved after 5 business days |
Ask any provider for their actual figures against a table like this, by ticket priority, not a single blended average. A blended average can look good while critical tickets quietly wait behind a queue of password resets.
How IT support is priced
Pricing usually follows one of three models. Per-user pricing bundles core support, device management, and security into a fixed monthly fee per staff member, and is the most common model for managed services because it scales predictably as headcount changes. Per-device pricing suits environments with shared workstations or specific server needs rather than a clean per-person mapping. Hourly or prepaid block hours can fit very low-complexity setups, but carry real risk during a major outage, since the cost is uncapped exactly when you need certainty most.
Whatever the model, ask what triggers an additional charge — onboarding fees, out-of-scope labour, and third-party licences are the most common sources of a bill that does not match the quote.
Choosing an IT support partner
Once you know what model fits and what a good arrangement includes, the harder part is evaluating specific providers against each other on scope, response commitments, trust signals, and price — not just the sales pitch. Our full guide to choosing a managed service provider walks through the evaluation criteria, red flags, and the questions worth asking on the first call.
IT support: frequently asked questions
What is the main difference between break-fix and managed IT support?
Break-fix means paying per call-out with no ongoing monitoring, so the provider only gets paid when something is already broken. Managed IT services charges a fixed monthly fee for ongoing monitoring, patching, and support, which keeps the provider incentive aligned with keeping your systems running rather than fixing what breaks. See our guide to choosing an MSP for how to evaluate providers under either model.
What should be included in an IT support agreement?
A clear agreement sets out scope, response and resolution targets, reporting frequency, and which services count as in-scope for the monthly fee. Our provider comparison guide covers the full checklist to run through before you sign.
How fast should IT support respond to a new request?
Response targets should be written into the agreement, not left as a verbal promise, and should vary by priority level. Our IT helpdesk and support service publishes a sub-11-second average phone response during business hours as a working benchmark.
What KPIs actually show whether IT support is working?
Average response time, resolution time by priority, first-contact resolution rate, and ticket volume trends for recurring issues are the metrics that matter. Uptime percentage alone can look acceptable while staff are still working around slow or unreliable support.
When does a business need co-managed IT instead of a fully outsourced model?
Co-managed IT fits businesses that already have internal IT staff but need more depth in a specific area, such as cybersecurity or after-hours cover. Our guide to co-managed IT covers the signs your business is ready for it and how to roll it out without disrupting your existing team.
IT support from OxygenIT in Christchurch
OxygenIT is Christchurch based and has operated here since 2005, running client IT through the Canterbury earthquakes along the way. We are ISO 27001 and ISO 42001 certified, and we run a single-provider model — managed IT, cybersecurity, professional services, and infrastructure under one accountable contract rather than split across vendors who each blame the others when something breaks.
We publish our own numbers rather than asking you to take our word for it: a sub-11-second average phone response during business hours, a 98% client retention rate, and a 90 day money back guarantee covering our own fees on any new engagement.
Contact us to talk through your current support setup, or call us on 0800 101 095.
