It was a Tuesday in August. Half the team was out. The server threw a critical error at 2 PM, and the IT manager spent three hours on hold with their managed service provider before anyone called back. By the time someone actually helped, they’d lost an afternoon of productivity across 40 users.
That IT manager wasn’t unlucky. He was unprotected — and he didn’t know it until he needed to be.
Managed IT providers are businesses too. They take PTO. They run skeleton crews in August. And if your SLA doesn’t explicitly include guaranteed response times during summer months, you’re not a priority client — you’re the next ticket in the general queue, behind everyone else whose named contact also took the week off.
For internal IT managers, this creates a specific kind of exposure. You’re the one who gets the call when something breaks. You’re the one standing in front of leadership explaining why the fix is taking longer than expected. And when your MSP finally calls back six hours later, that conversation with leadership gets a lot harder.
The average response time at an understaffed MSP for non-critical issues in summer is six to eight hours. If your business can’t run for six hours — and most can’t — that’s not a vendor problem. It’s a contract problem. And the contract is yours to fix.
The day after the Tuesday incident, he pulled up the MSP agreement. He’d signed it 18 months earlier and hadn’t looked at it since. What he found was a masterclass in vague language. “We’ll respond as soon as possible.” No defined timeframe. No summer coverage provision. No documented escalation path if the first tech couldn’t resolve the issue. No backup contact if his account manager was out. Just a handshake dressed up in legal language.
If you haven’t read your MSP agreement recently, that story might be yours too.
A contract that actually protects you looks different. Response time SLAs with teeth — not aspirational language, but specific timeframes for critical versus non-critical issues, with defined consequences if those timeframes aren’t met. Coverage during PTO and holidays that names a backup contact, not just a promise that “someone will be available.” A documented escalation path that tells you exactly who picks up the ticket when the first tech can’t solve it, and how long that handoff takes. These aren’t extras. They’re the difference between a resolved incident and a three-hour hold.
And then there’s the reactive versus proactive distinction — which matters more than most internal IT managers realize. Every reactive support interaction has a cost: your time diagnosing, your time on hold, your credibility with the people watching the clock. A good MSP is eliminating those interactions before they start. If every conversation begins because you called them, you don’t have an IT partner. You have a repair shop.
NCI maintains full staffing and documented escalation procedures year-round — summers included. Our internal IT clients get a named account contact, a documented backup contact, and SLA commitments that don’t flex based on what time of year it is.
We also believe internal IT managers shouldn’t be carrying the weight of coverage gaps their MSP created. If you’re handling work your MSP should be covering, or you’re not sure what your contract actually guarantees when it matters most, we’ll have that conversation plainly — no sales pitch, just an honest look at where the gaps are and what it would take to close them.
You’re the one on the hook when something breaks. You deserve a partner whose contract reflects that.
The IT manager from our story? When he finally got the vendor on the phone, he was three hours into an incident with no documentation, no escalation path, and a leadership team asking questions he couldn’t answer. That’s the real cost of a vague SLA — not just the downtime, but the credibility you spend in the room afterward. Once leadership starts asking why it took so long, the answer “we were waiting on the MSP” only works once.
Book a free 30-minute consult with NCI. We’ll review your current MSP coverage model and tell you plainly where the gaps are — before you find out the hard way.