The Linux Help Desk
One address your Linux desktop users write to and get a person back inside four working hours — up to 30 tickets a month for 25 named people, with ten of them becoming a live screen share when writing will not do it.
Your senior engineer is the help desk, whether anybody has said so or not. They are the one who knows why the shared drive stopped mounting, and your staff have worked out that asking them beats filing anything.
Give your people an address instead. They write in, a technician who has answered the same question on forty other Linux estates replies with the steps, and most are working again before lunch. Up to ten times a month, when writing will not do it, they get a 45-minute screen share where the technician talks and they click.
We hold no access to your machines, run no sudo commands, and never take remote control, so there is no supplier with root on your estate. That also means some tickets have to go elsewhere, and we tell you which ones and who covers them rather than quietly trying.
What's included
An address your 25 named people write to directly, answered by a person inside four working hours, or two if somebody cannot work at all — and a monthly report showing every target we met and every one we missed, with the reason
Up to 30 tickets a month, counted by rules published up front, and anything we should not have accepted answered anyway and not counted against you
Up to 10 live 45-minute screen shares a month, one user at a time, with their own hands on the keyboard and no remote control at any point
Linux depth a generalist desk cannot reach: reading the logs a user can read, the per-user software layers where most desktop problems actually live, and configuration inside their own account
No supplier with root on your estate — we hold no standing access to any machine, server or account you own, which is a security position as much as a support one
A written finding whenever a ticket turns out to need admin rights, a server, or somebody other than us, naming what we saw and who covers it, in your contacts' inboxes the same shift
The questions your people keep asking, counted and set beside last month, so you can see which ones are costing you the most — and your whole ticket history if you ever leave
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
A list of up to 25 people who may write in, with each one's email, distribution and desktop
Linux desktops on Debian 12+, Ubuntu 22.04 or 24.04 LTS, Linux Mint 21 or 22, or Fedora 40+
Two named technical contacts, plus an escalation address for anything we can't fix from a user's account
Who owns admin rights on the machines, password resets, your servers and your printers, even if the answer is your MSP
A Zoom, Microsoft Teams or Google Meet account for the screen shares, and the list of software your people may install themselves
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The Walk-Through Support
Up to 20 booked calls a month for your Linux desktop users. A technician talks each person through their problem on your own Zoom, Teams or Meet while their hands stay on the keyboard, with no remote control at any point.
The Server Admin Day
A senior system administrator works a full day on your server backlog, from the patch level nobody has checked to the backup nobody has restore-tested. Book one day or a run of dates, and each day ends with a written account of every hour.
The End-User Training Pack
Up to 40 of your people taught one system across three live hours, and a guide, task cards and an FAQ built from their own questions — yours to hand every new starter next year without asking us again.