Most bad IT relationships don’t fail because the provider lacked technical skill. They fail because nobody asked the awkward questions up front. If you’re working out what to ask before hiring a managed service provider, the goal is simple: find out how the provider behaves on a bad Tuesday, not how they present on a good sales call.
The questions below are grouped by the problems that tend to show up later: slow support, gaps in security and recovery, and contracts that cover less than you assumed.
What to Ask Before Hiring a Managed Service Provider About Day-to-Day Support
Start with the part your staff will feel most. If the help desk is slow, people stop reporting problems and start working around them. The accountant who can’t open a shared file asks a coworker. The coworker restarts something. Two weeks later, nobody remembers what broke or why.
Ask these:
- What is your target response time, and how is it measured? “Fast” means nothing. You want a number, and you want to know whether it covers the first reply or an actual fix.
- Who answers when someone calls? A dedicated team that knows your setup is different from a rotating queue where every call starts from zero.
- What counts as an emergency, and what happens then? Ask for the escalation path in writing. If your internet drops at a location with 25 people, who gets called, and how fast does it move past a first-level technician?
- Do you offer on-site support, and when? This matters most for multi-location teams or an office move, when phones, internet, and printers all need attention at once.
- What reporting will we see? Ticket volume, repeat issues, and response times should be visible to you. If the same Wi-Fi complaint comes up every month, someone should be fixing the cause, not the symptom.
A good provider answers these directly and doesn’t need a slide deck.
Security and Recovery Questions Most Buyers Skip
Many buyers focus on support and assume security comes bundled. Sometimes it does. Sometimes it’s an add-on, and sometimes it’s a line item nobody has defined.
Phishing, stolen credentials, ransomware, and payment fraud remain practical risks for smaller organizations. The basics that keep getting recommended are multi-factor authentication, regular backups, and recovery procedures that have actually been tested. So ask about those specifically.
Backups and recovery
- How often do you test restores, and can you show me the last test?
- What is the target for how long we can be down, and how much data we can afford to lose? Who decided those targets?
- Does our Microsoft 365 setup have its own backup? Microsoft 365 is not a complete backup strategy, and plenty of owners find that out after a deleted mailbox or a bad sync.
A backup that has never been tested is not a recovery plan. It’s a hope. The worst time to learn a backup failed is during the outage.
Access and accounts
- Is multi-factor authentication required for our staff, and for your own technicians?
- How do you handle new hires and departures? Slow offboarding leaves former employees with live email, file access, or software logins.
- How do you manage your own access to our systems, and to the vendors you bring in?
That last one gets overlooked. Third-party access, including from your IT provider, deserves dedicated planning. A provider that can reach every system you own should be able to explain how that access is controlled and reviewed.
The Common Mistake: Assuming the Agreement Covers Everything
Here’s a scenario that plays out often. A business signs with a provider, assuming “managed” means “everything.” Eight months later, the office adds a second location. The provider quotes the network setup as a separate project. The line-of-business software vendor says the issue is on the IT side. The IT provider says it’s the software. Staff sit in the middle, and nobody owns the problem.
Most of that confusion can be prevented before you sign. Ask:
- What is not included? Projects, hardware purchases, after-hours work, and on-site visits are common exclusions.
- Who handles third-party vendors? Will they call your internet carrier, phone vendor, and software supplier on your behalf, or are you the go-between?
- Who owns the documentation? Passwords, network diagrams, license records, and admin accounts should belong to you, not live only in the provider’s tools.
- How do we leave if it’s not working? Ask what a handoff looks like and whether there’s a notice period or fee.
- How are licenses handled? Microsoft 365 licensing mistakes quietly raise costs, especially when departing employees’ licenses never get removed.
An agreement that is vague about scope tends to get expensive in the gaps.
How to Weigh the Answers
You don’t need a technical background to compare providers. You need to listen for specifics.
Consider a simple scorecard. For each provider, note whether they gave:
1. A clear answer, with an example or a document to back it up 2. A vague answer that sounded reassuring but had no detail 3. No real answer, or a redirect to price
Providers who land mostly in the first group are usually easier to work with later. Be cautious when every answer is “we handle that” without explaining how.
Also consider fit. A company with no internal IT may want a fully outsourced model. One with an IT manager already on staff may do better with a co-managed arrangement, where the provider backs up that person rather than replacing them. Ask whether the provider is comfortable with either, and whether they’ll work alongside your existing people.
Finally, ask for a reference from a business your size and in a similar situation, such as multiple locations or heavy Microsoft 365 use. Then ask that reference one thing: what happened the last time something went wrong?
What This Means for Your Business
The cost of choosing poorly rarely shows up as one dramatic failure. It shows up as repeated slow tickets, staff workarounds, an outage that runs longer than it should, or a recovery plan nobody tested. Each one costs time and money, and each one can be spotted in a good conversation before signing.
Use the questions above as a working list. Write down the answers, compare them side by side, and push for specifics.
If you’d like a second opinion on a proposal or want to see how managed IT support for growing businesses is typically scoped, TECHZN is happy to walk through it with you, with no pressure to switch.
