Service catalogue
The list of what is covered, each line carrying a target, an owner and, where relevant, an approval route. That one document ends the conversations that begin with I assumed that was included.
A helpdesk answers the question who will help me. A service desk deals with a different one: is support working properly, and what exactly tells us so. The point is no longer rescuing one user but running a system: a catalogue setting out in writing what is covered, priorities based on real impact, approval routes for anything that commits the company, and numbers to put in front of the board instead of two people swapping opposite impressions.
The aim is visibility: knowing what support covers, where each case stands and what it all amounts to. The arrangement works whether we are your entire IT function or an extension of an internal team.
The list of what is covered, each line carrying a target, an owner and, where relevant, an approval route. That one document ends the conversations that begin with I assumed that was included.
Email, portal and Teams feed the same queue. A message sent straight to an engineer becomes a case in one click; otherwise it drops out of the figures and nobody picks it up on the day its recipient is away.
A matrix weighs urgency against how many people and processes are stopped. The job title of whoever wrote in plays no part, which spares everyone the habit of ranking by volume.
Time to pick up and time to resolve, counted in working hours and kept separate for each priority level. The tool warns before the deadline, not the morning after it slipped.
A new account, access to an HR folder, installing software: forms with a manager approval step, in place of messages that open with can you just give me.
Known errors, workarounds, step-by-step guides. Part of it is published for staff so they can settle simple cases alone; the rest keeps the team from working the same thing out twice.
Volume, categories, share of targets met, repeat incidents, workload by area. The report doubles as the agenda for the monthly meeting and leaves a usable trail for an ISO 27001 audit or NIS2 work.
How long setup takes depends mostly on you: agreeing the catalogue and the priorities eats more calendar time than configuring the tool ever does.
Together we write the catalogue, the categories, the priority levels, the targets and the approval routes. Nothing gets configured until that document is settled.
Portal, forms, mail and Teams connected, user accounts created, approver rights granted. A request can be raised where people already are.
A short online briefing for staff, then close attention through the first weeks, when categories and targets almost always need adjusting.
We go through the breaches, the repeats and whatever can be automated, granting a permission the moment a manager approves the form being a typical example.
The most useful figure in a report is not average response time, it is the list of repeats. If the same scanner stops sending files every week, ten quick replies still add up to ten interruptions. Each report therefore isolates the three causes that come back most often and sets out what has to change for them to go away for good.
No. Requests land in our portal by default, and it is part of the service. If you already own something that measures targets, we work inside it. What makes a service desk good is the catalogue and realistic targets, not the logo on the sign-in screen.
In the working hours named in the contract, Monday to Friday from 8:00 to 18:00 CET, and separately for each priority. A low-priority request raised on a Friday at 17:40 does not burn through the weekend. Time spent waiting on you or on a software publisher is paused and shown as such in the report.
We ban nothing. A Teams message turns into a case with one click and the answer comes back carrying a number. After a few weeks many people head for the portal of their own accord, because progress is visible there without having to chase anyone.
Yes. Categories are split between your people and ours, with one shared view and one set of figures whoever closes the case. That is also what lets you show an auditor how incidents are received, classified and recorded.
Your Start, Business or Premium plan sets the targets; the service desk sets out how they are met and how that is proven. The two belong together: a 15 min commitment with no catalogue and no measurement is a promise nobody can verify.
Describe how requests reach you today and who deals with them. We will propose a catalogue, a set of priorities and a tool that produces figures from month one.
Message received
An answer follows inside one working day. Report an outage that is stopping people working and it moves ahead of everything else.
Nothing here under that name. Check the spelling, or simply choose the nearest large city instead. Since every engagement runs remotely, whichever you pick changes nothing about what we do for you.