Outsourcing your service desk
The reason to outsource first line support is almost never cost. It is that your own people are spending their week on password resets instead of the projects you hired them for.
An outsourced service desk is priced per user per month, and the figure is driven by three things: how many hours you need covered, how fast the agreed response is, and how much second line work is included rather than billed separately.
Outsource the volume: password resets, account changes, device problems, standard software questions. Keep in house the things that need context nobody outside your organisation has, such as your line-of-business application and vendor relationships.
Quality survives the handover if three things are agreed up front: a documented environment, named escalation contacts on both sides, and a monthly report you both read.
The real reason people outsource
When we ask why a service desk is being outsourced, the first answer is usually cost. The second answer, after a few minutes, is the real one: the two internal specialists are unreachable because they spend their day answering the phone, holiday cover is a single point of failure, and nobody has looked at the ticket backlog in months.
Cost matters, but a service desk that costs the same and frees two engineers for project work is already worth doing. That is the calculation to make.
What to hand over and what to keep
| Hand over | Keep in house |
|---|---|
| Password resets and account lifecycle | Your line-of-business application and its supplier |
| Device faults, replacements and imaging | Decisions about architecture and budget |
| Standard software questions and licences | Relationships with sector-specific vendors |
| Monitoring, alerting and routine changes | Anything that needs internal political context |
| Out-of-hours and weekend cover | The final say on priority during an incident |
What it costs
Pricing is almost always per user per month, and the spread between the cheapest and the most complete arrangement is wide because the variables are. Cover hours move it most, followed by how much second line work is included.
| Scope | What changes at this level |
|---|---|
| First line, office hours | Calls answered and simple issues resolved. Anything deeper goes back to your own team. |
| First and second line, office hours | Most tickets close without reaching you. This is where an internal specialist gets their week back. |
| Extended and weekend cover | Support follows your opening hours instead of office hours. The largest single step in price. |
| Full cover including monitoring | Problems get noticed before somebody calls, which is a different service rather than more of the same one. |
A quote that looks unusually low usually means first line only, a long response time, or a per-ticket model that gets expensive in a bad month. Ask which of the three it is before you compare it with anything.
Where quality actually gets lost
Not in the first week. It gets lost around month three, when the documentation that was accurate at handover no longer matches reality, and the desk starts guessing.
Three habits prevent that. Keep the environment documentation as a living thing rather than a project deliverable. Give the desk a named person on your side for the things only you know. And review the top five recurring ticket causes every month, because a service desk that only closes tickets faster is treating symptoms.
Do you need 24/7?
Less often than people assume, and more often than they admit. The honest test is whether anything in your organisation loses money or safety outside office hours. A retailer on a Saturday, a distribution centre on a night shift and a care location at any hour all say yes. An accountancy firm at three in the morning does not.
Where cover is needed, it has to be staffed rather than promised. Our nights and weekends are worked as a shift by our own people, which means someone is awake rather than on call, and that difference shows in the response times.
How a transition should run
Inventory first: what is there, what is documented, what is broken and being worked around. Then a shadow period where we take calls alongside your team rather than instead of them. Then the switch, with the old route still open for a fortnight.
The migrations that go badly are the ones that happen on a Monday with no shadow period. The user experience of a handover is the whole judgement, and it is formed in the first two weeks.
What we take on is described under IT service desk, and the reporting rhythm under service governance.
Questions we get about this
What comes up in every service desk conversation.
What drives the price of an outsourced service desk?
Cover hours first, by a wide margin: extending support to evenings and weekends is the single largest step. After that, how much second line work is included rather than billed on top, and the response times you agree per priority. Ask any supplier to price those three separately so you can compare like with like.
Will our users notice the difference?
In the first fortnight, yes, and that is the period that decides their opinion. A shadow period where we take calls alongside your own team, plus documentation that was checked rather than assumed, is what makes the change invisible after a month.
Can we outsource only out-of-hours cover?
Yes, and it is a common starting point. Your own team keeps office hours and we pick up evenings, nights and weekends. It removes the on-call burden without changing anything your users see during the day.
What happens to our existing ticket system?
We can work in yours or bring ours. Working in yours keeps history and reporting in one place, which is usually worth more than tooling preference. What matters is that one system holds the truth rather than two.
Where this lands in our work
What sits around the desk.
Want this looked at for your own sites?
Half an hour on a call is usually enough to tell you whether we are the right party for it, and we will say so if we are not.