• Home
  • Blog
  • The employee portal: report issues instead of writing e-mails
News
Tickets

The employee portal: report issues instead of writing e-mails

6 min read

Introduction

Anyone in the company who needs something, or finds that something isn't working, usually writes an e-mail — and afterwards doesn't know whether it has arrived. HaiSoTec Tickets now has a dedicated interface for this: the employee portal.

The benefit is that a request called across the office becomes a case that both sides can track. And that everyone in the company finds exactly what concerns them there — their issue, their devices, their requests.

Report it, then see what becomes of it

The home page greets you by first name and puts the main thing at the top: “Anliegen melden” (report an issue). The form asks what it is about, leaves room for a description, offers a choice of area and accepts files of up to 10 MB — a screenshot often says more than three paragraphs.

What follows reads like a conversation: your own account as the first speech bubble, the support team's replies below it, files in both directions. If a reply moves the case on, this appears as a separate line.

When reporting, nobody chooses the urgency or the processing status themselves — the system sets both according to the company's rules, and from then on the agreed deadline runs as it does for any other case. The responsible group sees the report at the same moment; the case shows that it came from the portal.

If something is waiting for a response, it appears at the very top of the home page: “Das wartet auf Sie” (this is waiting for you), one line per open item, each leading straight to it. If nothing is waiting, nothing appears there either — so the notice remains a prompt and does not turn into a tile that people read past.

What is assigned to me

Under “Meine Ausstattung” (my equipment), you see what the company currently has assigned to you: devices with serial number and date, licences, services, each with the date it has been active since. Below that, in an expandable section, is your previous equipment, with the period and the reason for its return.

Every active entry has “Problem melden” (report a problem). It leads to a pre-filled form, and the device is then attached to the case — together with its warranty end date as at the time of the report, so that support doesn't have to look it up. The server checks whether the device really belongs to the person reporting it and is still active.

Licence keys are deliberately not shown on this page — it gets opened in open-plan offices.

Requesting something without writing an e-mail

The catalogue shows what is available for the workplace. Anyone who needs something opens the entry and requests it there; replacing or returning an existing device works the same way, just from the entry under “Meine Ausstattung”.

The decision is made by the manager — provided they are on record, active and not the requester themselves. Otherwise a named group decides, and here too only active members are eligible. If neither is on record, no request is created in the first place, and the message says exactly what is missing in the admin area.

Where a value threshold has been set and the request is below it, it goes through automatically; the history then says so. A return needs no approval anyway. And with the approval, the ticket for IT is created in the same step — there is no in-between state of “approved, but nobody knows about it”. If two approvers decide at the same time, there is still only one ticket.

Nothing is left hanging

Requests that require a decision are given a deadline. If the first deadline passes, the system reminds the approvers; if the second passes, it brings in more people — the approver's manager, failing that the designated group, failing that the administrators. The defaults are 48 and 120 hours and can be adjusted.

The check runs every 15 minutes. Anyone who has decided is therefore out of the reminder loop straight away, and each reminder goes out exactly once.

The first working day and the last

For new starters, an equipment package can be set up — for example “Office workstation” with a notebook, docking station, monitor and the necessary licences. One click turns this into one case for IT per item, with the start date as the due date and the new colleague as the recipient. Before the first day, the system sends a single reminder about anything still open.

When someone leaves, it runs in reverse: the returns appear as separate cases, and the system sends a reminder about them and names what is still missing. On the leaving date, it locks the account — from then on, signing in is no longer possible, open ticket assignments and group memberships are removed, and the account is kept along with its history. Once all returns are done, the offboarding counts as complete.

How long it really takes

The admin area has a dedicated report: how long it takes from request to provisioning, how long decisions take, how long onboarding and offboarding run — each as a count, mean and median. Automatic approvals are not counted in the approval time, otherwise every figure would look better than reality.

Alongside this, it shows how many portal users currently have any equipment at all and which cases are past their deadline — listed individually and directly clickable.

Everyone sees only their own

That an employee sees only their own cases is enforced not by the interface but by the database: the access rule admits only cases linked to the person's own user ID. A query without this restriction is rejected — rather than, say, returning too much by mistake.

Everyone gets access via an invitation link that is valid for seven days and can be used once. The invited person sets the password themselves; no e-mail contains one.

An everyday example

On Tuesday, an employee's docking station stops working. She opens her equipment in the portal, clicks “Problem melden” on the entry, attaches a photo and sends it off. The report reaches support with the device, serial number and warranty status.

The replacement costs more than the approval threshold, so a request goes to her manager. The manager decides that same afternoon; with the approval, the task lands with IT. Had the approval stalled, a reminder would have chased it up two days later.

Who it pays off for

The companies that gain the most are those where issues currently arrive by word of mouth, e-mail and chat all at once: IT service providers with internal and external users, trades businesses with equipment in their vehicles, property management companies with several sites. The more people who can report something, the bigger the difference between an inbox and a list.

Availability

The employee portal is part of HaiSoTec Tickets and is switched on for each company individually — six modules that can be activated separately: the portal itself, equipment, catalogue, requests, deadlines and support for onboarding and offboarding. Anyone who only wants reporting gets only that. Hosted in Frankfurt.

Try it out

You might also like