What happens at 2 a.m. when the billing system freezes and nobody can log in? That question, more than any glossy brochure or sales pitch, tells you what kind of IT support company you are actually dealing with. Most businesses choose a provider based on price and a friendly first meeting, then discover the gaps months later when something breaks and the fine print starts to matter. The right questions, asked early, close that gap.
Quick Answer: What questions should I ask an IT support company before hiring?
Ask for written commitments, not verbal promises. The core set covers response and resolution times, data protection and where data is stored, security certifications, breach notification speed, backup and tested recovery targets, and who holds administrative control of your accounts. Get each answer in the contract or service schedule.
Some questions belong to the contract stage rather than the first call. Certifications and staffing models can be checked in a discovery meeting, while liability caps, exit terms, and data-export formats need to appear in writing before signature. The two conversations are different, and skipping either one leaves you exposed.
Before signing, compare response and resolution targets, business-hours versus 24/7 coverage, GDPR processor terms, ISO/IEC 27001 certification status, recovery point and recovery time objectives, breach notification timelines, account ownership, liability limits, and exit assistance.
Start With the Contract, Not the Sales Deck

A good support relationship is built on documents, not personalities. The sales conversation tells you how a provider wants to be seen. The contract tells you what they will actually do when things go wrong. Ask for the master services agreement, the service schedule, and any acceptable use or security policy before the second meeting. Read them. If a provider hesitates to share these documents early, that hesitation is itself an answer.
The questions below are grouped so you can work through them in order. Some are technical, some are commercial, and a few are simply about honesty. All of them are checkable.
Service Levels: What Exactly Are You Promising?
Service-level agreements (SLAs) are the standard mechanism for defining response and resolution targets. They are a long-standing part of IT service management practice, and they are the first thing to pin down.
Ask three things about every SLA commitment:
- What is the response time (someone acknowledges the ticket) versus the resolution time (the problem is fixed)?
- Are the targets measured in business hours or around the clock? A four-hour response target means very different things on a Tuesday afternoon and a Sunday night.
- What remedy applies if the provider misses the target? Credits, escalation, or nothing at all?
That third question separates serious providers from optimistic ones. A service credit schedule, even a modest one, shows the provider has thought about failure. “We always hit our targets” is not a remedy.
Also ask how tickets are prioritized. Most providers use severity tiers, and the definition of “critical” matters enormously. If a single user’s email outage counts as critical, your genuine emergency will sit in a queue behind routine requests.
Data Protection and Where Your Information Lives
Under the EU GDPR (Regulation (EU) 2016/679, applicable from 25 May 2018), a provider processing personal data on your behalf is typically a processor. That triggers Article 28 obligations, including a written contract with specified terms. Ask directly: will you sign a data processing agreement, and can I see the template now?
Then ask where data is stored. Cloud backups, helpdesk systems, and remote monitoring tools all hold your information somewhere. If the answer is “in the cloud,” push further: which country, which provider, and what happens if that sub-processor changes? Sub-processors are a common blind spot. A support company may outsource monitoring to a third party without mentioning it.
For healthcare organizations in the United States, HIPAA obligations extend to business associates, so ask whether the provider will sign a Business Associate Agreement. Sector rules vary by country, so name your regulator and ask how the provider handles it.
Security Certifications and Incident Response
ISO/IEC 27001 is the international standard for information security management systems, first published in 2005, with the current edition dated 2022. Asking whether a provider is certified, and by which certification body, is a concrete and checkable question. A certification certificate has a scope statement. Read it, because the scope may cover only part of the business.
Certification is not the only signal, but it is a useful filter. Equally telling is how the provider answers questions about its own security: multi-factor authentication on admin accounts, endpoint protection, patch cadence, and staff background checks.
Then move to breach notification. Under GDPR Article 33, a controller must notify the supervisory authority within 72 hours of becoming aware of certain breaches. That clock starts when you become aware, which means your provider’s notification speed directly affects your compliance. Ask for a specific commitment in hours, not “promptly.”
This is where a broader review helps. If you are also evaluating security tooling, the same discipline applies to the questions in this guide to AI chatbot security: 9 questions to ask before buying, and the same logic underpins this managed detection response checklist of 12 questions to ask before signing. Vendors in adjacent categories tend to have the same weak spots.
Backup, Recovery, and the Difference Between Them
Backups are not recovery. A provider can run nightly backups for years and still fail to restore anything useful when a ransomware event wipes the environment. Ask for two numbers:
| Term | What it means | Question to ask |
|---|---|---|
| RPO (recovery point objective) | How much data you can afford to lose | How old will the newest backup be at worst? |
| RTO (recovery time objective) | How long recovery takes | How quickly will systems be back, and is that tested? |
The follow-up matters more than the numbers: when was the last restore test, and can I see the report? Untested backups are a hope, not a plan. Ask whether backups are stored separately from the main environment and whether they are immutable, meaning ransomware cannot encrypt them.
Account Ownership: The Question Nobody Asks
Who holds the administrator credentials for your domain registrar, your Microsoft 365 or Google Workspace tenant, your cloud infrastructure, and your backup platform? If the answer is the provider, you have a problem. You should hold administrative control, with the provider granted delegated access that can be revoked.
This is widely recommended practice rather than a formal standard, but it is the single most common source of pain when a business changes providers. A departing IT company that controls your domain can hold your email hostage, intentionally or through simple disorganization. Ask for a written list of accounts, who owns each one, and confirmation that ownership sits with you.
Staffing, Escalation, and the Human Side
Ask whether support is handled in-house or subcontracted, which time zones are covered, and what the escalation path looks like when the first-line technician cannot solve the problem. A provider with three engineers and forty clients may be excellent, or may be stretched thin. Ask how many clients each engineer supports.
Practical tip: ask to meet the person who will actually answer your tickets, not only the account manager. The account manager sells; the technician delivers. If a provider resists introducing the delivery team, treat that as a warning.
Insurance, Liability, and the Exit Door
Ask about professional indemnity and cyber liability insurance, and ask for the liability cap in the contract. Many agreements cap liability at twelve months of fees, which may be far less than the cost of a serious outage. That may be acceptable, but you should know the number before you sign.
Exit terms deserve equal attention. What is the notice period? In what format will your data be returned? Will the provider assist with handover, and at what cost? A provider confident in its service will not flinch at these questions.
Comparing Providers Side by Side
Once you have answers, put them in one table. It forces clarity.
| Question | Provider A | Provider B | Provider C |
|---|---|---|---|
| Response time (business hours / 24/7) | |||
| Resolution target and remedy | |||
| GDPR processor agreement offered | |||
| ISO/IEC 27001 certified (scope) | |||
| Breach notification commitment (hours) | |||
| RPO / RTO and last restore test | |||
| You hold admin control of key accounts | |||
| Liability cap | |||
| Exit assistance and data export format |
Three providers, one page. Patterns appear fast, and the cheapest option often loses on three or four rows at once.
Common Mistakes Buyers Make
The most frequent error is accepting verbal assurances. “We’ll get to you quickly” is not an SLA. The second is ignoring the exit terms because the relationship feels good at the start. The third is failing to test the relationship before committing: ask for a paid trial month or a small project first, and watch how the provider handles a minor incident. Small failures predict large ones.
A fourth mistake is choosing on price alone. Support pricing varies widely, and a low monthly fee often reflects a high technician-to-client ratio. For a useful parallel on how buyers get caught out by headline numbers, this Rillabox review of what buyers should know before ordering shows the same pattern in a different market. The principle holds: the sticker price is rarely the real cost.
Finally, do not skip references. Ask for two clients of similar size and sector, and ask those clients specifically about response times during incidents, not about general satisfaction.
Conclusion
Hiring an IT support company is a risk transfer decision. You are handing over responsibility for the systems your business runs on, and the only protection you have is what is written down. Ask about SLAs and remedies, data protection and processor terms, security certification, breach notification speed, tested recovery targets, account ownership, staffing, insurance, and exit terms. Get each answer in writing. The providers worth hiring will welcome the questions, because they have good answers ready. The ones who dodge them have just told you everything you need to know.
Frequently Asked Questions
How many IT support companies should I compare before choosing?
Three is a workable number. Fewer than three gives you no real benchmark, and more than four becomes noise. Use the same question set and comparison table for each, so the differences are visible rather than impressionistic.
Is a cheaper managed service provider always worse?
No, but price usually reflects something. A low monthly fee may mean a high technician-to-client ratio, limited hours, or exclusions buried in the service schedule. Ask what is not included, and compare the exclusions across providers before comparing the fees.
Do I need a provider with ISO/IEC 27001 certification?
It is a strong signal rather than a legal requirement. The standard defines an information security management system, and certification means an independent body has audited it. If a provider is not certified, ask what equivalent controls it operates and whether it plans to certify.
What is a reasonable breach notification commitment?
Ask for a specific number of hours, and make sure it is short enough for you to meet your own obligations. Under GDPR, a controller must notify the supervisory authority within 72 hours of becoming aware of certain breaches, so a provider that promises notification within 24 hours leaves you room to act.
Should the IT support company own our admin accounts?
No. You should hold administrative control of your domain registrar, cloud tenant, and backup platform, with the provider given delegated access. That way you can revoke access and change providers without losing your email, files, or systems.
What should happen at the end of the contract?
Your data should be returned in a usable format, access should be handed over cleanly, and any agreed handover assistance should be delivered. Ask for the notice period, the export format, and the cost of exit assistance in writing before you sign, not after you decide to leave.


