MSP Reference Check Questions

Reviewed by the Fully Compliance editorial team. Updated March 2026.

The short answer: References are where the MSP's sales pitch meets operational reality. Ask for at least five references from organizations similar to yours in size and industry, including customers who've been with the MSP for two or more years. Focus questions on responsiveness during emergencies, billing surprises, staff turnover, and how the MSP handled specific problems. The tone of the answers matters as much as the words.

References are where MSP sales pitch meets reality. When you talk to actual customers about their experience, you get information the MSP can't control. A reference who's been with an MSP for years tells you things the sales team will never volunteer — what actually happens during an emergency, whether billing surprises emerge, whether support quality degrades over time. References who've had problems and can discuss how the MSP handled them are gold. They're showing you what to expect when things go wrong, which is when you'll find out what an MSP is really made of.

The challenge is getting useful references and asking the right questions once you have them. MSPs will naturally provide their happiest customers, so you're not getting a random sample. But even happy customers have complaints, and the way they discuss those complaints reveals the nature of the relationship. CompTIA's 2024 Channel Trends research found that 67% of organizations that checked MSP references before signing reported significantly higher satisfaction after 12 months compared to those that skipped reference checks. The investment of a few phone calls is worth it.

Get References That Actually Match Your Situation

Start by asking the MSP for at least five references. Specifically ask for customers who are similar in size and industry to you. A customer with 5,000 employees has a completely different experience than one with 50 — the infrastructure is different, the support requirements are different, the escalation processes might not even apply. You want apples to apples.

Ask for recent customers — ideally someone who's been with the MSP for two to five years. That's the sweet spot. Long enough that they've experienced the relationship through normal times and crisis, short enough that their experience is current. But also ask for at least one customer who's been with the MSP much longer — seven years or more if possible. Long-term customers tell you whether the MSP improves over time or whether service degrades, whether they're still delivering value or whether the customer is just locked in.

Be skeptical if the MSP can only provide two or three references. They should have many satisfied customers willing to talk. If they're struggling to get references, that's a signal. Be skeptical if all references are within the last six months — ask for older customers too. Be skeptical if they only provide references from the same industry unless you're in a specialized vertical.

Ask for a mix of roles. Talk to the IT decision-maker who evaluated and selected the MSP — they can discuss the sales process, pricing, and strategic fit. But also talk to the person who deals with helpdesk issues daily, like an office manager or IT support person. They experience service quality at ground level. One might say "they're a great strategic partner" while the other says "they're hard to reach when we need them." Both perspectives matter.

Responsiveness Is the Most Immediate Signal of Service Quality

Start with responsiveness because it's the most immediate signal of how the MSP will treat you. Ask references directly: When you have an issue, how responsive is the MSP? When you submit a ticket or call, how long does it take to hear back? How often do they fail to meet their stated response times?

Listen for specifics. A good reference says "they respond to critical issues within an hour, usually faster" or "I can usually reach someone within 15 minutes of calling." A vague reference saying "they're pretty responsive, I guess" is less informative and slightly concerning — if the customer can't remember responsiveness positively, it's inconsistent.

Ask a follow-up: Have you had situations where you desperately needed the MSP and couldn't reach them? How did that get resolved? This reveals whether responsiveness is consistent or whether there are failure modes where they go dark. Most vendors have bad days. The question is what happens on those days.

Ask specifically about account continuity: Has your main contact changed? "We've had the same account manager for three years" is a positive signal. "The account manager has changed three times in two years" is concerning. Institutional knowledge about your account matters, and constant turnover disrupts it. New technicians need time to understand your environment, and if they're constantly replaced, you're living in perpetual transition.

SLA Compliance Reveals Whether Commitments Are Real or Decorative

Ask: Do you have an SLA with your MSP? Can you tell me what it commits to? Most customers won't have memorized it, but they should know the basics — response time, resolution time, uptime targets. If a customer can't recall their SLA, they might not be tracking it, which is itself informative.

Ask specifically: Has the MSP ever missed an SLA commitment? No vendor hits SLAs 100% of the time — sometimes things happen. The question is what happens when they miss. If the reference says "yeah, they've missed it a few times," ask: What happened then? Did you get credit? Was that automatic or did you have to ask? An MSP that automatically credits customers when they miss demonstrates accountability. One that makes you fight for credit shows you a problem. TSIA's 2024 Managed Services Benchmark found that only 31% of MSPs provide automatic SLA credits — the majority require customers to request them, which means most customers never collect.

If the reference says "we have an SLA but neither of us really tracks it," that tells you the SLA is window dressing. It's not enforced and doesn't matter. You might not want an MSP that doesn't take its commitments seriously enough to track compliance.

Staffing Stability Determines Service Consistency

Ask: Has your MSP's team been stable? Do you interact with the same people or does the team constantly change? Staffing instability is one of the biggest complaints about MSPs. If references mention constant turnover, that's a major red flag. If they mention having built relationships with the same team over years, that's positive.

Ask more specifically: Do you feel like the people serving you understand your environment? Or are you constantly explaining things to new people? This is the operational impact of turnover. Even if the MSP is hiring competent replacements, the time spent reboarding new people is lost productivity for both sides.

Ask whether there's one primary contact or multiple people familiar with your account. Multiple people who all know your environment provides coverage if someone is unavailable. A single contact with no backup creates a single point of failure. Ask specifically: If you need something after hours, who do you reach? If the reference can't answer this clearly, the MSP isn't well-organized for emergency response.

Billing Transparency Reveals How the Relationship Actually Works

This is where many MSP relationships reveal problems. Ask: Is your MSP cost predictable? Do bills match the quote you received? Have there been surprise charges?

Listen carefully to how they answer. If they say "the base price is what we agreed to, but we get billed extras for things like new user setups and additional servers," that's concerning. The contract should specify what's included and what isn't. If surprises keep happening, the MSP is either interpreting scope narrowly or is intentionally vague so they can bill for extras.

If they say "cost is exactly what we agreed to and we rarely see surprises," that's a positive signal about billing predictability. Ask: What would trigger an extra charge? The reference should give specific examples. If they say "we don't really know what might cost extra," the scope definition in the contract is too vague.

Ask about price increases: Have your costs gone up? By how much? Were you informed in advance? Reasonable MSPs increase prices to keep up with inflation — 3% to 5% annually is standard in the current market. Higher increases or surprise notifications are a problem. Ask: Does the MSP try to upsell you on things you don't need? An MSP trying to juice revenue by recommending unnecessary add-ons will be obvious to references.

Security and Incident Handling Reveal the MSP's Real Priorities

Ask: Have you had any security incidents while using this MSP? If yes, how did the MSP handle it? If they've had an incident, they tell you how the MSP responded — whether they were transparent, whether they helped investigate, whether they fixed the underlying problem or just patched it.

Even if the reference hasn't had an incident, ask: If you had a security breach affecting your data, do you feel confident the MSP would help investigate and notify? Or do you think there would be finger-pointing? This is about trust. A customer should feel like the MSP is a partner in security, not someone they'd have to fight with during a crisis.

Ask about security monitoring: Does the MSP provide security monitoring? What does that look like? If they include security monitoring, how often does the reference see the MSP proactively catching things and alerting them? If the answer is "we've never seen them find anything," either the monitoring is weak or the environment is exceptionally clean. If the answer is "they catch things regularly," the monitoring is working.

Ask whether the MSP is proactive or reactive about security. When the MSP finds something concerning, do they tell you immediately or do you discover it later?

Problem Escalation Shows Whether the MSP Owns Issues or Deflects Them

Ask: When something goes wrong, how does the MSP handle escalation? Do they investigate the problem or blame your systems? Listen for whether the reference trusts the MSP to solve problems or whether they feel like they're fighting with the MSP to accept responsibility.

A good MSP owns problems and works toward resolution, even if the ultimate cause wasn't their fault. A bad MSP defends their processes and blames the customer. Ask: Can you think of a time a problem wasn't resolved to your satisfaction? What happened? Some problems take time to resolve — that's normal. What matters is whether the MSP is transparent about progress, responsive to follow-up questions, and willing to escalate when the initial approach isn't working.

Overall Satisfaction Signals Come Through Tone as Much as Words

Ask directly: Would you recommend this MSP to others? Why or why not? Listen for enthusiasm versus resignation. "Yeah, we're happy with them, we'd recommend them" is different from "they're fine, we'll stick with them." The first sounds like genuine satisfaction. The second sounds like they've accepted their current situation but aren't impressed.

Ask: If you could change one thing about working with them, what would it be? This usually elicits honest feedback. Even satisfied customers have something. The nature of the complaint tells you what the MSP's weak spots are.

Ask forward-looking: How much longer do you plan to stay with this MSP? "We're actively looking at other options" or "until we find someone better" signals dissatisfaction. "Probably for years, they're doing a good job" signals satisfaction.

Pay attention to patterns across multiple references, not just individual comments. If multiple references mention poor communication, that's a pattern. If multiple mention constant staff changes, that's consistent. Patterns are more meaningful than individual complaints.

References won't tell you everything, but they'll tell you whether the MSP's sales pitch matches the reality customers experience. The best references come from customers who have similar needs to yours, have been through crises together, and have clear eyes about both the MSP's strengths and weaknesses. A customer who says "they're great for X and weak at Y" is more credible than one who says "they're amazing." Take reference calls seriously. Listen not just for what they say but for how they say it.

Frequently Asked Questions

How many references should I ask for?
Ask for at least five. This gives you enough data points to identify patterns. If all five mention great responsiveness, that's credible. If two out of five mention billing surprises, that's a pattern worth investigating. An MSP that can't produce five willing references either doesn't have enough satisfied customers or hasn't been in business long enough to establish a track record — both are relevant data points.

What if the MSP only provides hand-picked references?
Every MSP provides hand-picked references — that's expected. The value comes from asking the right questions. Even the MSP's happiest customers will share honest feedback about shortcomings when asked directly. Ask about specific problems, billing surprises, staff turnover, and what they'd change. Also ask the reference if they know of other companies using the same MSP — you may get a less curated introduction.

What's the most important question to ask a reference?
"Tell me about the last time something went seriously wrong and how the MSP handled it." This single question reveals responsiveness, accountability, communication quality, and whether the MSP owns problems or deflects them. A reference who can describe a crisis and how the MSP navigated it gives you the most operationally relevant insight.

Should I talk to references who left the MSP?
If you can find them, absolutely — former customers provide the most unfiltered perspective. Ask the MSP if they're willing to connect you with a former customer. Most won't volunteer this, but some confident MSPs will. You can also ask current references if they know organizations that left the MSP and why.

What patterns across references should concern me?
Multiple references mentioning the same issue is the strongest signal. If two or more references cite billing surprises, poor communication, staff turnover, slow responsiveness during emergencies, or blame-shifting when problems occur, treat that as a confirmed characteristic of the MSP, not an isolated incident.

How much weight should I give reference checks versus certifications and proposals?
Reference checks are the most reliable predictor of your actual experience because they reflect real operational performance rather than marketing promises or point-in-time audits. Certifications and proposals tell you what the MSP says it can do. References tell you what it actually does. Use certifications to filter, proposals to understand scope and pricing, and references to validate that the MSP delivers on its claims.