What we don't support
What we won't take on.
Most IT companies bury their limitations. We list ours up front. If your needs sit on this page, please use a different provider — we will not be a good fit.
Anything physical
Cabling, switch installs, printer paper jams, broken screens, swapping a dead SSD. We can ship you a recommendation; we cannot drive a van.
On-site visits
There is no van. There is no engineer. If a problem fundamentally requires hands at a location, we will tell you and suggest a local partner.
Highly regulated workloads
FCA-regulated trading systems, NHS patient-data infrastructure, classified or defence environments. Use a specialist with formal accreditations.
Custom software development
We will not build your internal app, write production code, or take ownership of a bespoke platform. Happy to advise on tooling.
Network architecture & cabling design
We do not design office networks from scratch, run site surveys, or take responsibility for physical infrastructure.
Legacy on-prem servers
If your business still runs an on-premise Exchange box, an SBS server, or a domain controller in a cupboard, we are the wrong fit. We are cloud-only.
24/7 SLAs with financial penalties
Our service is best-effort 24/7, not contractual. If you need penalty-backed uptime SLAs, you need an enterprise MSP.
Pretending to be a human
We will never roleplay as a person. Even if asked. The AI signs every message.
Issues we don't support
Where the agent stops, and why.
Three categories sit firmly outside the service. In each one, the agent will say so on the first message and will not attempt the work. The reasons are the same every time: physical presence, unacceptable risk, or the inability to safely validate the outcome.
Physical or on-site issues
Requires physical presence
Cabling or power faults
A cable, socket, or PDU has to be touched, tested, or replaced in the room it lives in. The agent operates entirely online and cannot do that.
Routers, switches, or printers requiring physical access
Reseats, port swaps, factory-reset pinholes, and toner or paper changes all need hands on the device. Out of reach for a remote-only service.
Hardware repairs or replacements
Failed SSDs, swollen batteries, broken screens, dead power supplies. These need a workbench and parts, not a chat window.
Wi-Fi coverage or signal issues
Coverage problems are answered by walking the building with a meter and moving access points. The agent cannot stand in the room with you.
High-risk or business-critical actions
Carries unacceptable risk
Tenant-wide deletions
Bulk removal of users, mailboxes, sites, or licences across an entire tenant is irreversible at scale. The agent will not perform changes whose blast radius it cannot bound.
Backup or data destruction
Deleting backups, purging retention, or wiping archives removes the safety net itself. The agent refuses any action that destroys the ability to recover.
Encryption key management
Rotating, exporting, or revoking tenant encryption keys can permanently lock data. This belongs with the key owner using their documented procedure, not an autonomous agent.
Ransomware response actions
Live incident response requires forensic preservation, legal coordination, and insurer involvement. The agent will help with prevention and hygiene, not the response itself.
Unsupported platforms
Cannot be safely validated
On-premise Exchange or servers
Local Exchange, SBS, file servers, and domain controllers sit behind your firewall with no standard remote surface. The agent cannot verify state or outcomes there.
Legacy operating systems
Windows 7, Windows Server 2012 and earlier, macOS releases past Apple support. They no longer receive security updates and behaviour cannot be safely predicted.
Bespoke or undocumented applications
In-house tools, vendor software without public documentation, or systems with no API. Without a known specification the agent cannot guarantee a safe, repeatable fix.
These limits exist to protect you. A service that refuses what it cannot do safely is more useful than one that tries everything and occasionally breaks the things you depend on. The boundary is the product.
How we say no
A refusal is a feature, not a failure.
When the agent declines a request, it does so in one short message. The reason is stated plainly and anchored to one of three things: safety, certainty, or scope. There is no apology, no padding, and no redirection elsewhere — just a clear answer so you know where you stand and can act on it.
Scope
"This issue requires physical access, which this service does not provide."
Safety
"This action carries significant risk and cannot be performed autonomously."
Certainty
"There isn't enough certainty to provide a safe recommendation."
What a refusal contains
- ·A direct statement that the request will not be carried out.
- ·The category it falls under: safety, certainty, or scope.
- ·A one-line reason in plain English.
- ·If a related, in-scope action exists, an offer to do that instead.
What a refusal never contains
- ×"Sorry", "unfortunately", or other apology language.
- ×Defensive explanations of the agent's limits.
- ×Suggestions to call, email, or visit a technician.
- ×Hedging language that leaves the answer ambiguous.
Get started
Open a chat. The AI picks up before the second ring — every time.
No onboarding calls. No sales process. Connect your devices and start raising tickets in under ten minutes.