Intake
A call, an email or a ticket through the portal. Nobody has to work out whom to approach.
The first line exists not to solve absolutely everything but to sort the flow: close the simple items at once and route the rest to the right specialist.
A call, an email or a ticket through the portal. Nobody has to work out whom to approach.
The engineer sees what is on the screen and resolves it without a visit.
Where to click, why it will not open, how to do it. A noticeable share of all requests.
Password resets and granting rights to folders and systems by an established procedure.
Connecting devices, sorting out print errors. An eternal source of tickets.
Complex items go to a specialist engineer with the full history; nothing has to be repeated.
Launch takes a few days: configuring intake and telling people where to turn.
We set up a number, a mailbox and a portal instead of calls to a friendly programmer next door.
A short instruction for staff: where to write and what to state up front.
We take it, solve it or pass it on. Every ticket has its own number and thread.
Every month we look at what recurs and remove the causes rather than the symptoms.
A ticket saying nothing works doubles the time to resolve it. The engineer spends time working out what exactly broke, for whom and since when. A short three-point note - what happened, when it started, what the screen says - shortens closure time more than any set of rules.
The response time is written into the contract and depends on priority: a department at a standstill is handled at once, a request to install software can wait a few hours. Promising everyone an immediate reaction is dishonest.
Roughly four requests out of five. The rest need hands on site: replacing a part, re-patching, a physical fault in a device. Those tasks pass to a visit with the history already collected.
We help within work tasks: mail, access to systems, a secure connection. Setting up personal devices and home printers is sensibly left outside the scope, otherwise the flow becomes limitless.
Write how many people are in the company and how questions are handled now. We will set up a single channel and take the flow.
Request received
It is already with a manager. You will get an answer within the working day, and urgent requests go to the duty engineer immediately.
There is no such city in the list. Check the spelling.