Managed IT Service Desk

A managed service desk is an outsourced single point of contact for all IT requests, run by a provider against agreed response times, with the ticket data used to identify and remove recurring causes.

It covers incidents, service requests, access requests and information requests. The distinguishing feature against ad-hoc support is that it is measured: response times against target, first contact resolution, recurring issues and trend, reported monthly.

P1, meaning business stopped or a security incident in progress, is 30 minutes including after hours through the standby escalation. P2, major degradation with a workaround, is 4 business hours. P3 and non-contract work is next business day.

Response means an engineer who can work the problem has made contact and started. Ask any provider to define what their response time measures, because a fifteen-minute figure that counts an automated email receipt is not comparable to one that counts a person starting work.

No, and be cautious of anyone who does across all incident types. Resolution depends on the nature of the fault, on third-party vendors and on access, none of which a provider fully controls.

What we commit to is response, continuous work on a P1 until service is restored, and communication at defined intervals. Where a specific recurring incident type has a known resolution path, we will commit to a time for that specific type, because that is a commitment we can actually hold.

Phone, email and a self-service portal. All three create a ticket and all three are equally valid routes.

Phone matters more than it is fashionable to admit. A user with a genuine business-stopping problem will phone, and routing everything through a portal adds friction at the worst moment. The portal earns its place for routine requests and for status checking, not as the only door.

First contact resolution is the proportion of tickets resolved during the initial contact without escalation. A realistic target on a mature arrangement is sixty-five to seventy-five percent.

It is driven by the knowledge base, by how much access first-line engineers have and by whether recurring issues have been documented. Be sceptical of quoted rates above about eighty-five percent. They usually mean something is being counted differently or that difficult contacts are being triaged out before they become tickets.

Not unless that is what you want. The more common arrangement is co-managed, where the desk handles high-volume user contact and your internal person keeps the application knowledge, the business-specific vendor relationships and the project work.

That split puts your internal person on work nobody external can do as well. It is also the arrangement they generally prefer, because the volume of interruption is what makes an internal IT role unsustainable rather than the difficulty of the work.

Two to four weeks. Environment documentation, contact channel setup, severity definitions agreed against your specific systems, request catalogue built, knowledge base seeded from your existing documentation and a communication to your users.

The user communication is the part most often rushed and it determines adoption. People need to know the number, the address and what to expect. A desk nobody uses because they carried on phoning the person they always phoned is a common and entirely avoidable failure.

Either. Using ours is faster to start and gives you our reporting immediately. Using yours keeps the history in one place and matters where you have integrations or an existing process built around it.

Where you use ours, the ticket data is yours and it is exportable. Confirm that with any provider before starting, because ticket history that cannot leave the provider’s platform is a genuine constraint on ever changing provider.

Monthly: volume by category and severity with trend, response performance against target, first contact resolution rate, recurring issues, top requesters and categories and ageing. Quarterly: a service review covering trend, problem records and what is proposed next.

The recurring issues and top categories sections are the useful ones. They routinely identify a training gap or a badly designed process rather than a technical fault, and those are cheaper to fix than anything technical.

Yes. In a well-run arrangement volume should be measurably lower by the end of the second quarter as recurring causes are removed. Flat volume after six months means tickets are being closed and causes are not being addressed.

This is the single most useful measure of whether a service desk is doing more than answering the phone. Ask for the trend rather than the count, and ask what was done about the top three recurring categories.

For first-line support, usually yes, once we have documentation and access. Deeper support depends on the application and is normally a shared arrangement with the vendor or with your internal expert.

We are direct about the boundary. Taking first-line contact and escalating to the right place with context is genuinely valuable even where we cannot resolve it, because it removes the routing burden from your users. Claiming full support for an application we do not know would not survive contact with the first real ticket.

Below roughly twenty to twenty-five users, a managed service desk is generally more structure than the volume justifies. Direct access to an engineer is faster and cheaper at that size.

The case gets strong once volume is high enough that tickets queue behind each other, once you have more than one site, or once you need response commitments you can point to. If you are below that, ad-hoc support with an agreed rate and a good relationship will serve you better, and we are happy to work that way.