IT Support Providers in Kampala: Comparing SLAs and Response Times

What matters in practice:

• Response time beats resolution time: the number that protects your business is how fast a qualified human acknowledges a P1 outage, and it should be written in minutes
• Coverage hours are a different product: business-hours-only support and genuine 24/7 cover sit in different price bands, and a quote that does not state the window is not a quote
• Escalation needs named owners: a provider who cannot tell you who picks up the phone at 11pm, and who drives to your office, has not thought about your worst day

Every managed IT proposal in Kampala arrives with the same promises. Fast response. Proactive monitoring. A dedicated team that knows your business. The words are nearly identical across proposals, which is exactly why they are useless for comparison.

What separates one proposal from another is not the adjectives. It is the numbers behind them, and whether anyone signs up to those numbers in writing.

This guide is a scoring framework for comparing IT support providers on the terms that actually decide your day-to-day experience: SLA response times, coverage windows, escalation paths, monitoring tooling and reporting. It does not tell you who to hire. It gives you a repeatable way to score any provider, including the one you already use, side by side.

Note on figures: bands below describe what you will typically encounter in the Kampala market in 2026, not quotations from any single firm. Pricing depends on user count, device age, number of sites and coverage hours.

What an SLA Actually Promises

A service level agreement is a written commitment on how a provider behaves when something breaks. Most SLAs contain two numbers, and buyers routinely confuse them.

Response time is the elapsed time between you raising a ticket and a qualified engineer acknowledging it and beginning work. This is the number you can hold a provider to, because it depends only on their staffing.

Resolution time is the elapsed time until service is restored. This depends on spare parts, vendor lead times, ISP tickets and physical access to your building, so providers correctly hedge it. Treat a resolution figure as a target, not a guarantee.

The four severity levels you should insist on

A serious provider defines severity before you sign, not after your outage starts.

If a proposal does not contain a table like this, you are not buying an SLA. You are buying a reassurance.

The Criteria That Separate Providers

Use these six rows for every provider you evaluate. Ask the same questions, in the same order, and write the answers down before the salesperson leaves.

Response Time Benchmarks by Severity

Numbers matter more than promises. A benchmark you can sanity-check against any proposal:

• P1 first response, business hours: 15 to 45 minutes is competitive. Anything above two hours means your outage is queued behind routine tickets.
• P1 first response, after hours: under 60 minutes is achievable only with a real on-call rota. Ask how many engineers are actually on the rota.
• P2 first response: 1 to 4 hours. This is where most providers quietly slip, because P2 work does not feel urgent until it becomes P1.
• On-site dispatch: same business day for Kampala premises, next day upcountry. Confirm whether travel time is inside or outside the response clock.
• Average resolution across all tickets: 8 to 24 hours is normal for a healthy estate. Sustained multi-day resolution points to understaffing, not complexity.

Ask for evidence: request the previous month's ticket report with the numbers anonymised. A provider who tracks response times will produce it in a day. A provider who does not track them will go quiet.

Coverage Hours and What After-Hours Actually Costs

Coverage is where quotes diverge most, and where comparison shopping quietly fails. Three tiers cover almost every Kampala business:

Two things to check before you compare numbers. First, whether on-site visits are included in the per-user fee or billed separately, and if separately, at what rate. Second, whether the after-hours surcharge applies from the moment you call or only once the ticket is classified P1.

For a fuller breakdown of how these models are built, see our guides to managed IT services pricing in Uganda and IT support cost per user in Uganda. This article is about comparing providers on service terms; those two explain how the price is constructed so your comparison stays apples to apples.

Monitoring, Ticketing and Escalation

Proactive versus reactive support

Reactive providers fix what you report. Proactive providers find it first. The difference is visible in the tooling, not the brochure.

Ask directly: which agents run on our servers, how are switches and firewalls polled, what threshold triggers an alert before users notice, and who watches those alerts outside working hours. If the answer is a monitoring platform with defined thresholds and an on-call rota behind it, you are talking to an operator. If the answer is "call us when it breaks", you are buying break-fix with a retainer attached.

Ticketing discipline

Every request should produce a ticket with an ID, a severity, an owner and a timestamp. WhatsApp is convenient for reporting a problem, but a WhatsApp thread is not a record. When a issue recurs, ticket history is what proves the pattern and gets it fixed permanently rather than patched every month.

Escalation ownership

The escalation path should be written, with names or roles, not improvised. Ask three questions: who is the named account owner, who is the after-hours duty engineer, and who arrives on site when remote support cannot fix it. Then ask what happens when all three are unreachable.

A Scoring Matrix You Can Copy

Score each provider from 1 to 5 against weighted criteria. The weights below suit a 20 to 100 user office; adjust to your reality.

Weighting price at 10% feels counter-intuitive until you have run a cheap contract for a year and counted the hours your staff spent waiting. Our guide to comparing IT companies in Uganda covers red flags and proposal analysis in more depth.

Questions to Ask Before You Sign

• What is your average first response time over the last three months, for P1 and P2 separately?
• How do you handle after-hours incidents, and how many engineers are on the rota this month?
• Can I speak to two clients of a similar size to ours, and may I call them without you present?
• What exactly is excluded from the monthly fee, and what triggers an extra invoice?
• What happens to our ticket history, asset register and documentation if we leave?

Ask for answers in writing. A verbal commitment that does not survive the contract draft was never a commitment.

Frequently Asked Questions

Q: How long should an IT support contract run in Kampala?

A: Twelve months is standard and reasonable. It gives the provider time to stabilise your estate and gives you a full quarter of measured performance before renewal. Avoid three-year agreements without service credits, and avoid any contract that has no defined exit process for your data, documentation and admin credentials.

Q: Do I need 24/7 support?

A: Only if your systems must work while your staff are asleep. If you run a hotel, a clinic, a transaction platform or a multi-site retail operation, yes. If you are a Monday-to-Friday office, extended-hours cover plus a documented P1 on-call route usually delivers better value than paying for a full overnight rota you never use.

Q: What is a reasonable SLA credit policy?

A: Credits, not refunds. Typical structure: a service credit of 5 to 10% of the monthly fee for each missed P1 response target, capped at 25 to 50% of the monthly fee in any period. The point is not the money. A provider willing to put credits in the contract is a provider who believes their own response times.

Q: Can we keep our current in-house IT person and still buy managed support?

A: Yes, and it is common. The in-house person handles day-to-day user issues and local presence, while the managed provider supplies monitoring, escalation depth, patching discipline and after-hours cover. Define the boundary in writing so tickets do not bounce between two parties while your staff wait.

Score Your Current Provider This Week

Pull the last three months of tickets, or your memory of them, and score your provider against the matrix above. Most businesses discover their support contract is weakest on exactly the two things that hurt most during an outage: response time and escalation.

Backspace's IT support services cover helpdesk, on-site engineering, monitoring, backup oversight and security basics for Kampala businesses, with response targets written into the agreement.

Message us on WhatsApp or request a free site assessment and we will review your current support arrangement, mark the gaps against this framework, and give you a proposal you can score against anyone else's.