What is included

The value lies in transparency: you can see what is happening with your tasks and discuss it using numbers.

Discuss the scope

Logging requests

Every task with a number, an author, a description and the conversation history.

Prioritisation

An impact and urgency matrix. Priority is set by rules rather than by the persistence of the requester.

Deadline control

Automatic tracking of response and recovery time, with alerts as a breach approaches.

Knowledge base

Standard solutions, so the same problem is not worked out from scratch every time.

Escalation

Rules for passing to the next line and to a manager when things drag on.

Reporting

How many requests, the split by type, the share closed on time and repeat requests.

How the work runs

Implementation takes two to three weeks. Most of the time goes into agreeing the classification and the priority matrix.

01

Process setup

Request categories, priorities, deadlines and routing. This is done before the system is deployed.

02

The system

Deployment, form configuration and integration with email and telephony.

03

Launch

Training for employees and engineers, with manual oversight for the first weeks.

04

Regular review

Monthly analysis: what recurs, where deadlines are missed and what to automate.

The classification matters more than the system. If the request categories are invented at random, the reports will be useless: you will see that 80 percent of requests fall into the Other category. A good classification is built from the decisions you want the data to support.

Frequently asked questions

From 20 to 30 employees, yes, at least in a simple form. Below that, records can be kept more simply, but even then it helps for a request to have a number: it settles arguments about whether you got in touch at all.

It will if you demand ten fields be filled in. A workable form has three fields plus the option of simply sending an email from which the request is created automatically. Record keeping should be invisible to the requester.

They will happen: people come over in person and write in messengers. The engineer logs such requests themselves, otherwise the work is done but does not appear in the report. Over time the share of bypasses falls if the system is convenient.

We will implement a Service Desk

Tell us how requests are recorded today. We will set up the process and the system so support quality becomes measurable.