What an IT support agreement should guarantee

When your systems go down and your team can't work, a vague promise of "support" isn't enough. An IT support agreement worth signing lays out exactly what you'll get, how fast, and what happens if it doesn't show up. Too many businesses discover mid-crisis that their contract was full of gaps—and by then it's too late.

The difference between response time and resolution time

Many agreements promise a response within two hours, which sounds reassuring until your systems are still broken after four. Response time is when someone picks up the phone or opens a ticket; resolution time is when your systems are actually working again. These are not the same thing. A provider who responds quickly but then takes days to fix the problem has technically met their agreement while your business bleeds money. Your contract needs to specify both: how fast they'll acknowledge the issue, and by when it should be fixed. For critical systems, these windows should be tight. For routine requests, they can be more relaxed. The key is that you both agree in advance, not that you discover the difference when you're desperately waiting for a fix.

What "available" actually means

If a provider says they offer 24/7 support, does that mean a live person answers at 2 a.m. on Sunday, or is it an automated ticketing system that a technician checks Monday morning? Is support available on public holidays? What happens if your issue falls outside their stated scope—do they still respond, or do you get told "that's not covered"? Write these details into your agreement. Specify whether support is live helpdesk, phone-only, or ticket-based, and whether urgent issues get different treatment than routine ones. Ask them to define what "urgent" means to them. If your business runs on Sundays or operates during times when most IT providers are quiet, flag this now rather than discovering they're understaffed during your peak hours.

Escalation paths when the first fix doesn't work

Sometimes a problem needs more than a junior technician can offer. Your agreement should spell out what happens next: who handles escalations, how long before it moves up the chain, and whether you stay in the loop. If your issue is escalated to a senior technician, are you told? If it needs to go to a vendor, does the provider manage that or do you? Who pays if the vendor charges? Some agreements cap support at frontline troubleshooting and refer everything else elsewhere, leaving you scrambling. Others promise full accountability through the repair chain. Neither is inherently right, but you need to know which one you're signing up for. A good agreement also tells you what metrics they track—average time to escalation, success rate on first-contact fixes, that sort of thing—so you can measure whether they're actually meeting their commitments.

Scope, exclusions, and what costs extra

Read the fine print on what is and isn't covered. Does the agreement include software setup and configuration, or only troubleshooting when things break? What about training your team on new tools? Are remote sessions included, or does on-site support cost extra? Some providers bundle in a set number of hours per month; others bill by the hour after a retainer. Some exclude certain brands of equipment or specific software. Some won't touch legacy systems. The worst contracts bury these exclusions in a paragraph near the end. Push back if something you rely on is excluded, and don't assume "everything" is covered if the contract is vague. Ask the provider to walk you through three recent support requests from other clients—with names redacted—so you see what their scope actually looks like in practice.

When you're ready to move forward, look for a provider who can put their commitments in writing and explain them clearly. Strove's verified IT support providers include their response and resolution commitments upfront, so you're comparing apples to apples before you book.