AI does the repetitive half. An engineer owns the rest.
Plenty of providers now put AI on the homepage. Fewer will tell you which tasks it touches, where it is not allowed, and who is accountable when it is wrong. Here is our version, in full.
Automation is a cost decision, not a feature
A managed service is priced on how many engineer-hours your account consumes. Most of those hours go to work that is repetitive and low-judgement: the same five requests, the same noisy alerts, the same notes nobody wrote down. Take that work out and two things change: answers come back faster, and the rate per user stops climbing every time you hire.
That is the whole argument. We are not claiming a smarter product; we are claiming a cheaper way to run the same promise, and we would rather show you the mechanics than the word.
What runs automatically
Four areas. Each one is a place where speed matters more than judgement.
Alert triage
A network of a hundred devices produces thousands of alerts a week, and the overwhelming majority are duplicates, flapping sensors or known-benign events. Automation correlates, de-duplicates and ranks alerts before an engineer sees anything, so attention goes to the handful that represent a real fault. We keep the raw stream rather than discarding it, so we can always show you what was suppressed and why.
Routine service requests
Password resets, account lockouts, licence assignment, distribution-list changes, new-starter provisioning from an approved template, software installs from an approved catalogue. These follow a fixed, auditable path and complete without waiting in a queue. Anything that deviates from the template stops and goes to a person.
Documentation
The reason MSP documentation is always out of date is that writing it is a separate chore from doing the work. We generate the record from the work itself (the change made, by whom, on what, and why), and an engineer approves it. When your account manager changes, or when you leave us, the documentation is current rather than archaeological.
Reporting and review prep
Automation assembles ticket patterns, recurring faults, licence drift, ageing hardware and security posture into your quarterly review, so the meeting is spent on decisions instead of on someone assembling slides the night before.
What we deliberately do not automate
This list matters more than the one above. These are the places where being fast and wrong is far more expensive than being slow and right.
Security incident response
Detection is automated; the response is not. Isolating a machine, disabling an account or declaring an incident is a human decision with a name attached to it.
Anything that deletes or restores data
Backups run on a schedule automatically. An engineer performs every restore and verifies it against what you expected to get back.
Permissions and privileged access
Granting admin rights, changing security groups or opening firewall rules goes through a person and is recorded, whoever asked and however urgently.
Advice about your business
Roadmaps, budgets, vendor choices and the answer to “should we replace this now or next year” come from an engineer who knows your environment.
How we keep it accountable
Automation without an audit trail is just a faster way to lose track of your environment. Four rules, and we will hold ourselves to them in writing.
- Every automated action is logged: what ran, when, on what, and what changed
- If an action cannot be undone, a person does it rather than the automation
- A named engineer owns your account, so escalation reaches them and not a rota
- We do not feed your environment into shared models, so your data is never training data
What we are not claiming
Questions we get asked
Does our data get used to train an AI model?
What happens when the automation gets it wrong?
Will we ever be forced to talk to a bot?
Do you charge extra for the automation?
Can we see what has run on our environment?
Find out which of your tickets can leave the queue
Bring us a month of your current tickets, from a helpdesk tool, a shared mailbox, or just memory. We will tell you which categories are automatable and which are not, and what that does to the monthly number.