Recording
Summary, requester, device and every message exchanged kept together, including cases that started as a quick chat on Teams.
Visibility is the goal: you can follow any case and talk about support using data. This holds true whether we are your sole IT provider or work alongside in-house staff.
Summary, requester, device and every message exchanged kept together, including cases that started as a quick chat on Teams.
Order is determined by weighing impact against urgency. Seniority of the person asking plays no part; what matters is how many people and processes are blocked.
Time to respond and time to resolve are counted in business hours for each priority level, and warnings fire before a target is breached.
A new login, access to HR files, installing software: approval-based forms replace emails beginning “could you quickly give me…”.
Documented known issues and workarounds, so nothing is solved twice from scratch, plus self-help articles for staff.
Defined triggers for bringing in second line, a software supplier or leadership. Each month: volume, category split, percentage met and recurring problems.
How long roll-out takes depends on the company, with most of the time spent settling categories and priority rules rather than on software set-up.
Categories, priority levels, target times and approval routes are agreed with you before any configuration.
Portal and request forms go live, with mail and Teams hooked up so people can report problems from wherever they already work.
A short online briefing for employees, followed by close monitoring during the opening weeks while rules get adjusted.
Breached targets, recurring cases and automation opportunities are examined, such as granting rights automatically after a form is approved.
The most telling figure is not average response speed but the list of recurring issues. When somebody reports weekly that scans never arrive, ten rapid responses still add up to ten interruptions. Every report therefore highlights the three commonest causes of requests, with a proposal for eliminating each permanently.
No. Requests go into our portal by default. Should your organisation already use Jira Service Management or a similar tool able to track due dates, we can work there instead. Good categories and achievable targets determine quality far more than any product name.
Solely within contracted hours, weekdays 8:00-18:00 CET, and per priority level. A minor request logged on Friday at 17:40 does not accumulate time across Saturday and Sunday. Premium clients and those with 24/7 IT support have critical cases timed without breaks. Waiting for input from the requester or a vendor stops the timer, and that pause is visible in reports.
Banning it does not work. One click converts a Teams message into a case, and the employee gets a reply containing its reference. Over time many people go to the portal first, since they can check status there without chasing.
Certainly. Categories may be routed to your team or to ours, producing a single dashboard and unified figures regardless of who resolved a case. That proves useful during an NIS2 or KRI audit, when evidence of incident handling is required.
Explain how requests are logged at the moment and who deals with them. We will recommend a process and tooling that turn support quality into measurable data.
Your enquiry has reached us
You will hear back within one working day, and if you have reported an outage that is holding up work, it goes to the front of the queue.
No match for that name. Try a different spelling or pick a bigger town nearby - all our support is delivered online, so your choice has no effect on the service.