Buyer's Guide / MSP Evaluation
How to Choose an IT Help Desk Provider: 8 Questions to Ask Before You Sign a Contract
Your last IT vendor promised "fast response times" — then took four hours to answer a ticket while your point-of-sale system was down on a Saturday. Before you sign another contract for IT Help Desk Services, you need eight specific, contract-level questions that expose exactly what you're buying — not what a salesperson says you're buying.
Why "Fast Response" and "Flat Rate" Mean Nothing Without the Right Contract Questions
MSP sales language — "fast response," "proactive support," "flat-rate pricing" — is deliberately unanchored to any measurable standard. The only way to compare managed IT services for small businesses on equal footing is to move every conversation to the contract and SLA level, where vague promises become enforceable commitments or disappear entirely.
Why Sales Language Fails Buyers
Nothing in standard MSP language is legally binding. "Fast response" means whatever a technician felt like that day. Until you ask for written SLA terms with defined priority tiers and resolution clocks, you are comparing marketing copy, not services.
The 8-Question Framework
Send these questions verbatim to any provider you're evaluating. A well-run MSP will answer each one in writing without hesitation. A provider who deflects or says "we'll cover that after you sign" is telling you exactly how they operate once you're locked in.
- Questions 1-2: Response time SLAs and escalation path
- Questions 3-4: Scope of work and compliance coverage
- Questions 5-6: After-hours staffing and technician-to-client ratio
- Questions 7-8: Exit terms, documentation ownership, and vendor lock-in
Most comparison guides stop at soft criteria. This guide hands you contract-language questions tied to SLA accountability, escalation structure, and compliance coverage that a low-commitment MSP cannot answer confidently.
Questions 1-2: Response Time and Escalation — What Happens When Tier 1 Can't Fix It?
A first-response SLA — the time until someone acknowledges your ticket — is not the same as a resolution SLA, which is the time until your problem is fixed. Most providers quote only the first number. You need both, broken out by ticket priority level, in writing.
Question 1: What Are Your Guaranteed SLAs by Ticket Priority?
Ask the provider to produce a priority matrix — typically P1 through P4 — listing both first-response and resolution times for each level. Copy this exactly: "Please provide your written SLA matrix showing first-response and resolution time commitments by ticket priority level."
A P1 outage — full system down, no workaround — should have a first-response time in minutes and a resolution target in hours. If a provider's P1 resolution SLA is "next business day," your Saturday POS outage waits until Monday.
Question 2: What Is Your Escalation Path?
Ask: "How many support tiers do you have, what triggers escalation between tiers, and who is the named escalation contact for our account?"
- Tier count: A credible MSP has at least two tiers — help desk generalist and senior engineer. Three tiers is common for complex environments.
- Escalation trigger: Escalation should be time-triggered and severity-triggered, not left to a technician's discretion.
- Named contact: You need a specific engineer's name, not just a queue. If the provider can't name one, no one owns your problem.
Questions 3-4: Scope and Compliance — What's Actually Covered, and What Gets Billed Extra?
The most common source of unexpected charges in a managed IT services contract is scope ambiguity. A provider's flat-rate fee covers whatever the contract explicitly lists. Everything else is a billable add-on, whether they disclosed that upfront or not.
Question 3: Provide a Written Scope-of-Work Listing Exclusions
Ask exactly: "Please provide a written scope-of-work document listing what is included and what is explicitly excluded from the monthly fee." Verify these three items are addressed:
- User onboarding and offboarding: Setting up or deprovisioning accounts, devices, and permissions is frequently excluded from base pricing — even though it happens routinely.
- Personal device (BYOD) support: Most contracts exclude troubleshooting personal phones or laptops used for work.
- Vendor-liaison calls: Time spent on the phone with your ISP, software vendor, or hardware manufacturer is commonly billed hourly outside the flat rate.
Question 4: Which Compliance Controls Are Included vs. Billed as Add-Ons?
Ask: "For [your specific regulation], which required technical controls are included in the base contract, and which are add-on services?"
Regulated industries should verify coverage before signing. Take Ctrl provides dedicated HIPAA compliance IT services for healthcare organizations, PCI compliance support for businesses handling cardholder data, and FINRA compliance IT for registered financial firms. A provider who cannot answer Question 4 for your regulation has not done compliance work in your industry.
Questions 5-6: Staffing and Coverage — Who Actually Answers the Phone at 9 PM?
After-hours IT support is one of the most misrepresented promises in managed IT services. "24/7 support" frequently means a third-party answering service takes a message and a technician calls back the next morning — which is not support. Ask directly before you sign.
Question 5: Who Handles After-Hours Support, and Do They Have Full System Access?
Ask verbatim: "Is your after-hours support handled by in-house technicians or a third-party answering service? Does the after-hours team have access to our full documentation, system credentials, and network diagrams?"
An answering service can log a ticket. It cannot restore a failed server or resolve a ransomware alert at 11 PM. Without access to your environment documentation, after-hours staff can only relay messages — not resolve anything.
Question 6: What Is Your Technician-to-Client Ratio?
Ask: "How many client accounts does each help-desk technician actively support?" A bloated ratio is a direct predictor of slow resolution regardless of what the SLA document says.
| Ratio Range | What It Signals |
|---|---|
| Under 50 clients per technician | Well-staffed; technicians have capacity to engage deeply with each account |
| 50-100 clients per technician | Acceptable for simple environments; watch for SLA drift during peak periods |
| Over 100 clients per technician | Overstretched; SLA commitments become aspirational rather than operational |
A provider who refuses to share this number, or says it "varies," is signaling it's not a selling point. That answer is data.
Questions 7 and 8 — covering exit terms, documentation ownership, and vendor lock-in via proprietary RMM tools — are equally important before signing any outsourced IT support agreement. Confirm in writing who owns your backups on exit: your data backup and recovery assets should transfer to you immediately upon termination, not be held pending a transition fee.
Frequently Asked Questions
What should be included in a managed IT services contract for a small business?
A managed IT services contract should include a written scope-of-work with explicit exclusions, SLA response and resolution times by ticket priority, escalation procedures, after-hours coverage terms, compliance responsibilities, technician-to-client ratio commitments, and exit and data-ownership clauses.
What is a reasonable SLA response time for an IT help desk?
For a P1 critical outage, a first response within 15-30 minutes and a resolution target within 4 hours is a reasonable benchmark. Lower-priority tickets should receive same-business-day response. Always confirm both the first-response time and the resolution time in writing, by priority level.
How many clients should an MSP have per technician?
A well-staffed MSP typically supports fewer than 50 client accounts per help-desk technician. Ratios above 100 clients per technician are a strong predictor of slow resolution times and SLA drift, regardless of what the contract states.
What is the difference between an IT help desk and managed IT services?
An IT help desk is a reactive support function — users submit tickets and technicians resolve them. Managed IT services is a broader engagement that includes proactive monitoring, patch management, vendor management, compliance oversight, and strategic planning, typically under a single flat-rate contract.
How do I know if a managed IT provider handles compliance requirements like HIPAA or PCI?
Ask the provider to list, in writing, which specific technical controls required by your regulation are included in the base contract versus billed as add-ons. A provider with real compliance experience will answer by framework — HIPAA, PCI, FINRA — without needing to research the question first.
What happens to my data and system access if I cancel my MSP contract?
Your contract should state that all passwords, network documentation, backup data, and admin credentials transfer to you immediately upon termination — with no transition fees. If a provider uses a proprietary RMM tool that locks configuration data inside their platform, get the offboarding terms in writing before you sign.
Is 24/7 IT support actually staffed, or is it an answering service?
Many MSPs route after-hours calls to a third-party answering service that logs a ticket but cannot resolve anything. Ask directly: "Is after-hours support handled by your in-house technicians, and do they have real-time access to our system documentation and credentials?" Get the answer in writing.
What questions should I ask an IT company before signing a contract?
Ask for written SLAs by ticket priority, a defined escalation path with named contacts, a scope-of-work document listing exclusions, compliance control coverage for your specific regulation, after-hours staffing model, technician-to-client ratio, and written exit terms covering data and documentation ownership.
Still Comparing IT Help Desk Providers? Ask Us These 8 Questions First
When you reach out to Take Ctrl, you'll get a no-pressure discovery call where our team answers every contract-level question in this guide — in writing — before you're asked to sign anything.
Schedule Your Discovery Call
