It’s a Tuesday afternoon in May. A Polokwane school’s M365 tenant has just locked out 280 student accounts after a misconfigured Conditional Access policy. The deputy principal can’t get her staff into Teams. The IT teacher resigned last term. The principal phones us.
Not a ticket. Not a chat widget. A phone call.
Forty-three minutes later the policy is reverted, the lockouts are cleared, and afternoon classes haven’t missed a beat. The principal didn’t even know what a “Conditional Access policy” was. She knew there was a number, and we answered.
The ticket-system arms race
Most managed IT providers we compete against in South Africa have, over the last decade, quietly rebuilt themselves around ticket queues. ServiceNow, Freshdesk, Zendesk, ConnectWise. The pitch is always the same: “Submit a ticket and we’ll route it to the right engineer.” The reality is usually: a Level-1 person in Pretoria reads your description, copies it to a Level-2 queue, and someone gets back to you in four hours.
This works fine for “the printer is out of toner.” It works terribly for “we just got encrypted and the ransom note is on every screen.” And in our experience, the gap between those two extremes is exactly where most businesses break.
What we automate vs what stays human
We’re not anti-automation. RMM watches every endpoint we manage, 24/7. Patches deploy on schedule. Backups verify themselves nightly. Alerts route through PagerDuty. None of that needs a human to be useful.
What stays human is the bit that matters when stress is high:
- The first 90 seconds of an incident. Someone calling at 02:00 because their POS is down doesn’t need a chatbot asking them to “describe the issue in detail.” They need a real engineer who knows their environment.
- The judgement calls. Restore from last night or last week? Take the database offline for the next hour or limp through end-of-month? Phone the auditor or wait for the lawyer? You can’t script those.
- The handover. A new staff member’s first day. A finance team after their accountant leaves. A school after their IT teacher takes another post. The continuity work is conversation, not configuration.
What it costs us
Phone-first SLAs are more expensive than queue-first ones. We staff a real human on every shift across three time zones we cover. We pay senior-engineer salaries, not Level-1 outsourced rates. We don’t scale to thousands of clients per engineer the way the SaaS-pure MSPs do.
The trade-off is deliberate. The kind of South African business we work with — between 10 and 500 staff, in a regulated sector, downtime measured in rands — gets more value from being known by name than being efficient on a per-ticket basis. So that’s what we charge for, and that’s what we deliver.
The 2005 promise
When Burika started in Polokwane in 2005, the founding business plan had one sentence highlighted: when something breaks, we pick up the phone. Twenty years and three provinces later, the line still holds. It’s in every onboarding deck, every contract, every internal review.
The number to call is on our contact page. We answer.