How fast is your support response time?

Response time commitments should always be documented in a clear Service Level Agreement (SLA) rather than left as a vague, informal expectation, and the specific committed time genuinely should vary based on the severity and business impact of the issue being reported, not a single flat number applied uniformly to every possible request.

Why Severity-Based Response Times Matter More Than One Flat Number

A complete network outage affecting the whole business genuinely warrants, and should receive, a faster response commitment than a single user's minor software question. A proper SLA structure defines multiple severity tiers, each with its own specific, documented response time commitment, rather than a single generic number that either overcommits on trivial issues or, more dangerously, undercommits on genuinely critical ones.

A Reasonable Structure to Expect

• Critical (complete outage, business-stopping issue), fastest committed response, often within the hour or less, with active work continuing until resolution
• High (significant impact, but not a complete stoppage), same-day response commitment
• Medium (moderate impact, workaround available), response within an agreed number of business days
• Low (minor issue, general questions, non-urgent requests), response within a longer, but still clearly defined, agreed window

"Response Time" Versus "Resolution Time", a Distinction Worth Understanding

Response time is how quickly someone genuinely acknowledges and begins actively working your issue, resolution time is how long until it's actually, fully fixed. Some issues can be resolved quickly, others (particularly those needing a specific hardware part, or vendor escalation outside direct control) genuinely take longer to resolve even with a fast initial response. A trustworthy provider is upfront and honest about this distinction rather than implying every issue is fully solved within the initial response window regardless of its actual complexity.

What Affects Realistic Response Times

• Time of day and day of week, after-hours support (if included in your specific agreement) may have different, typically somewhat longer response commitments than business hours
• Issue complexity, straightforward, well-understood issues get resolved faster than genuinely novel or complex problems requiring deeper investigation
• Third-party dependencies, issues requiring a hardware vendor, ISP, or other external party are partly outside your provider's direct control, though a good provider still actively manages this escalation on your behalf rather than simply handing you off

What to Genuinely Look For in Any SLA

Beyond the specific numbers themselves: is the SLA a real, documented, contractually binding commitment, or just an informal, unenforceable expectation? What happens, is there any genuine remedy or accountability, if the committed response time is consistently missed? Vague verbal promises without documented, tracked commitments offer considerably less genuine assurance.

Our Approach

We provide a clearly documented, tiered SLA with specific response time commitments matched to issue severity, and we track and report on our own actual performance against those commitments, so you have genuine visibility into whether the service is consistently meeting what was actually promised, not just what was verbally implied at the start of the relationship.